upgrade challenges on 11.2 release trying to upgrade to 11.2-U5

[newfreenas]

I will start out by saying this is most likely a user error. I have read through the update guide [0] a couple times and I must be missing something.

I have tried to set the boot environment manually and activate the new version but when I reboot nothing occurs.


3 questions:


1.) Is there a debug log that would be useful for me to look at?

2.) Should I try manually upgrading? can anyone point me towards literature on towards how to accomplish from CLI?

3.) What else could I be missing?







[0] https://www.ixsystems.com/documentation/freenas/11.2/system.html#update

 

[dlavigne]

Post the output of beadm list between code tags.

 

[newfreenas]

Code:

% beadm list
BE                Active Mountpoint  Space Created               Nickname
default           N      /          900.0K 2018-12-17 09:43      default
Initial-Install   -      -            3.0M 2018-12-17 09:54      Initial-Install
11.2-RELEASE-U1   -      -            4.7G 2019-01-07 14:44      11.2-RELEASE-U1
11.2-U4.1         -      -          755.5M 2019-06-05 15:00      11.2-U4.1
11.2-U4.1-1       -      -          755.5M 2019-06-05 15:09      11.2-U4.1-1
11.2-U4.1-2       -      -          755.5M 2019-06-05 15:15      11.2-U4.1-2
11.2-U4.1-3       -      -          755.5M 2019-06-06 12:00      11.2-U4.1-3
asdf              -      -          481.0K 2019-06-06 12:04      asdf
11.2-U5           -      -          756.5M 2019-06-28 02:08      11.2-U5
11.2-U5-1         R      -            5.5G 2019-06-28 02:24      11.2-U5-1

when I try to 'activate' the 11.2 it shows the R which assume means for reboot?

do I need to mount the update somehow prior to activation?

 

[dlavigne]

That's showing a lot of failed updates (3 for U4 and 1 for U5). What if the full output of ifconfig within code tags?

 

[newfreenas]

I will try to get this evening in the mean time are there debug logs I can review?

is there additional info I can get tonight? I'm still learning a lot but I'm uncertain how the interfaces could be having an impact on this.

currently, one physical interface connected, several 'bridged' taps due to bhyve VM's.

should I try upgrading with all VM's shutdown?

 

[dlavigne]

Were you able to resolve this?

 

[newfreenas]

I have not resolved but unfortunately have not had time to even look at it. I am hoping later this week I can get some more info been quite busy.

I will hook up a monitor next time to see if anything is showing up during boot as I have been initiating this remotely and it did not occur to me that during the boot sequence something may be selected by default that I do not want.

 

[newfreenas]

I'm not sure why there is interest in ifconfig, but I just attempted to upgrade again with a monitor installed and while there was a 1-11 prompt of options after going through them none were able to assist with an upgrade.

can you advise of any debug logs I can review to troubleshoot this?


I have copied the output of my ifconfig below if you think that may assist.

Code:

% ifconfig
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
        ether redacted
        hwaddr redacted
        inet 0.0.0.2 netmask 0xfffffff0 broadcast 0.0.0.31
        inet 0.0.0.3 netmask 0xfffffff0 broadcast 0.0.0.31
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
        ether redacted
        hwaddr redacted
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect
        status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::redacted prefixlen 64 scopeid 0x3
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether redacted
        hwaddr redacted
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 4045
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether redacted
        nd6 options=1<PERFORMNUD>
        groups: bridge
        id redacted priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id redacted priority 32768 ifcost 0 port 0
        member: vnet0:2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 10 priority 128 path cost 2000
        member: igb1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 2 priority 128 path cost 2000000
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000000
tap1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether redacted
        hwaddr redacted
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 4045
bridge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether redacted
        nd6 options=1<PERFORMNUD>
        groups: bridge
        id redacted priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id redacted priority 32768 ifcost 0 port 0
        member: tap5 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 12 priority 128 path cost 2000000
        member: tap4 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 11 priority 128 path cost 2000000
        member: tap3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 9 priority 128 path cost 2000000
        member: tap2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 8 priority 128 path cost 2000000
        member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        member: tap1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 6 priority 128 path cost 2000000
tap2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether redacted
        hwaddr redacted
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 4379
tap3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether redacted
        hwaddr redacted
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 4349
vnet0:2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail:
        options=8<VLAN_MTU>
        ether redacted
        hwaddr redacted
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
tap4: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether redacted
        hwaddr redacted
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 4638
tap5: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether redacted
        hwaddr redacted
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: active
        groups: tap
        Opened by PID 4675

 

[pschatz100]

What is your boot device? If it is a flash drive, they often go bad during system updates. That is one of the reasons that flash drives are no longer recommended and users are switching to small SSD's for boot.

If you have a backup copy of your configuration (you should...), you can try a fresh install to a new boot device and restore the configuration. If all goes well with the new install, then you can remount your data drives and be all set.

 

[newfreenas]

I'm using an ssd, that being said, I have 2 as i intended to use a second as backup but have not truly configured it yet, so its an 'unmanaged' drive sitting connected.

I had not considered the fresh install and restore, while that may be above my ahead... thats probably the best method... I have some important (to me) research I'm doing with some VM's but I may try that after I'm fully comfortable of complete loss in case I screw something up.

I appreciate all the input given!

fear not I am the man spoken of in the mouse-over text --> https://www.xkcd.com/1586/

 

[pschatz100]

If you are going to boot from SSD, I wouldn't worry too much about mirrored boot devices. That is more of an issue when booting from flash drives, which is not recommended anymore. However, if you want mirrored boot devices then setting them up during a fresh install is a convenient time to do it.

A fresh install, followed by restoring the configuration, is not difficult and most importantly, there is no risk to your data. I would do the following:
1. Power down the system and then disconnect your data disks. You can re-import your pools after the new install is completed and you are confident it is stable.
2. Reinstall FreeNAS to your new boot devices. Make certain the new system boots OK and is stable.
3. Import your pools
4. Restore the configuration

If you have a backup of your configuration, you can restore the configuration from the backup, then import your pools. Doesn't really matter - the end result will be the same.

This is discussed in more detail in the documentation (section 2.5.5 in the 11.2-U5 docs.)