Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

System tries to mount from 11.2-U7 after updating 11.3

Joined
Feb 2, 2020
Messages
4
I just built fresh installation of 11.3 and then applied my saved config (previously 11.2-U7).

After I had the system working, I applied pending 11.3 updates. When the system rebooted, it hung trying to mount root from zfs:freenas-boot/ROOT/11.2-U7.

Well that sucked. So I reinstalled 11.3 fresh again, applied my saved config and got the system working again.

This time I deleted all of the old boot environments, including 11.2-U7. I rebooted a couple of times to make sure everything was still working.

I then applied pending 11.3 updates and was hit with the same "Trying to mount root from zfs:freenas-boot/ROOT/11.2-U7


Any idea whats going on? I can reinstall 11.3 again, but it would seem I'm unable to apply any 11.3 updates.
 
Joined
Feb 2, 2020
Messages
4
I probably should have added that the boot process stops with the messages:
Mounting from zfs:freenas-boot/ROOT/11.2-U7 failed with error 45; retrying for 30 more seconds
 
Joined
Feb 2, 2020
Messages
4
sure enough, when I look at bootenv, I see references to 11.2-U7. No idea why those were added back - perhaps by the updater?
 
Joined
Feb 2, 2020
Messages
4
Upon successful reboot, I now have a 11.2-U7 boot environment. This must have been added by the updates???

Sure enough, even though I have 11.3 STABLE selected, it is "upgrading" me from 11.3 to 11.2-U7


Train: FreeNAS-11.3-Stable-Release Train for FreeNAS 11.3 [release]
OperationName
Upgradebase-os-11.3-RELEASE-a67e6fa145e21a7cf074b3ec4e95676c -> base-os-11.2-U7-f93a3b67973bac31ececa871460a45e7
Upgradefreebsd-pkgdb-11.3-RELEASE-a67e6fa145e21a7cf074b3ec4e95676c -> freebsd-pkgdb-11.2-U7-f93a3b67973bac31ececa871460a45e7
Upgradefreenas-pkg-tools-11.3-RELEASE-a67e6fa145e21a7cf074b3ec4e95676c -> freenas-pkg-tools-11.2-U7-f93a3b67973bac31ececa871460a45e7
UpgradeFreeNASUI-11.3-RELEASE-a67e6fa145e21a7cf074b3ec4e95676c -> FreeNASUI-11.2-U7-f93a3b67973bac31ececa871460a45e7
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,033
This bug has already been reported
 

vafk

FreeNAS Experienced
Joined
Jun 22, 2017
Messages
114
DO NOT UPGRADE TO 11.3
This is crazy...

And for those who did do NOT install the 11.3-RC2 Update as suggested here:
 
Last edited:

vafk

FreeNAS Experienced
Joined
Jun 22, 2017
Messages
114
So here is the temporary solution, on a Valentine, from a country where you are not allowed to own a peacemaker and where knuckleheads run away with no excuse:

So you are stuck in boot after upgrading to 11.3?

Step 1 - get yourself a bottle of Jim Beam or similar
Step 2 - Do you have you boot stick with the FreeNAS-11.3-RELEASE.iso?
If yes, take a sip.
If no, take a sip, start a download and take a deep sip.
Step 3 - start the same **** it brought you here, i.e. do the upgrade boot.
Step 4 - hope that all went well and you will get there where you were before you selected to upgrade to 11.3-RC

Enjoy that fun? Start to upgrade to 11.3-RC. I did not do because it is Valentine and I don't want to get killed by my wife....


Edit: Sorry guys it looks like I repeated all your steps above, that was not my intention, after I briefly read your post I ran to the server and did what you did there. Don't be cross with me :)
 
Last edited:
Joined
Oct 3, 2015
Messages
57
Something like this happened for me as well. Upgraded from 11.2 U7 to 11.3, and after upgrade the system was stuck in self boot/reboot cycle.

From the boot menu, I went back to U7, but my jails were gone. :(

Sadly, even restoring a saved config would not bring them back. :( :(

What did I do wrong? Is there some simple way to get my jails back up?


EDIT: I'm not sure if it was trying to mount 11.2 U7 when booting 11.3. But for sure it was caught in the boot/reboot loop. So then I tried to install 11.3 as a fresh install, reformatting the boot media (mirrored SSD's), choosing the to go with the 16GB swap space. All as well until I tried restoring by config from 11.2 U7, then the boot/reboot cycle began again. Then I did an 11.2 U7 fresh install, and after restoring the backup config, my jails are still missing!
 
Last edited:

vafk

FreeNAS Experienced
Joined
Jun 22, 2017
Messages
114
@Bill McCormick
I fear your jails are gone... Did you backup them before?
Check under /mnt/your-pool-name if there are jails in the directory - you may be lucky and they are there. I don't know how to get them back because I do not use jails, but vm and I always keep one almost identical FreeNAS as backup in case my first FreeNAS fails so I just switch to the backup. Actually it is not backup but redundancy. If you don't have a second FreeNAS, consider some cheap HP N54L with 8 GB RAM and four 2 or 4 GB WD REDs. Will cost you from 400 to 550 Euro depending on the size of HDDs but keep your head free :)

I have on my FreeNAS Midnight Commander light so I can easily browse the directories and in case I need to save a file or directory I can copy/move them like in the old DOS-times.
 
Joined
Oct 3, 2015
Messages
57
I was able to recover with the following:

root@freenas:/mnt/z1/iocage # ll
total 39
drwxr-xr-x 4 root wheel 4 Feb 15 12:50 .plugins/
-rw-r--r-- 1 root wheel 2925 Feb 15 12:34 defaults_backup.json
-rw-r--r-- 1 root wheel 3325 Feb 15 12:34 defaults.json
drwxr-xr-x 3 root wheel 3 Feb 15 16:30 download/
drwxr-xr-x 2 root wheel 2 Feb 11 2018 images/
drwxr-xr-x 4 root wheel 4 Feb 15 16:33 jails/
drwxr-xr-x 2 root wheel 6 Jan 4 22:35 log/
drwxr-xr-x 3 root wheel 3 Feb 15 16:33 releases/
drwxr-xr-x 2 root wheel 2 Feb 11 2018 templates/
root@freenas:/mnt/z1/iocage # mv defaults.json defaults.json.OLD
root@freenas:/mnt/z1/iocage # mv defaults_backup.json defaults.json
root@freenas:/mnt/z1/iocage # iocage list
+-----+-------------------+-------+--------------+----------------+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+===================+=======+==============+================+
| - | plex-media-server | down | 11.2-RELEASE | 192.168.212.5 |
+-----+-------------------+-------+--------------+----------------+
| - | zoneminder | down | 11.2-RELEASE | 192.168.212.50 |
+-----+-------------------+-------+--------------+----------------+

EDIT: Also needed to do this (restore defaults_backup.json) in each jail dir as well. For me, it was also the case that the jail vol was maked Read Only, so that needed to be reset before restoring. I could set the zvol to NOT read only, then start the jail, but it would revert to read only when the jail was restarted.
 
Last edited:
Joined
Oct 3, 2015
Messages
57
@Bill McCormick
Actually it is not backup but redundancy. If you don't have a second FreeNAS, consider some cheap HP N54L with 8 GB RAM and four 2 or 4 GB WD REDs. Will cost you from 400 to 550 Euro depending on the size of HDDs but keep your head free :)
Surely you're not suggesting I try to keep 20TB backed up. Sort of defeats the purpose of RaidZ3 in the 1st place, don't you think?

I have on my FreeNAS Midnight Commander light so I can easily browse the directories and in case I need to save a file or directory I can copy/move them like in the old DOS-times.
I like ranger. More Unix like.
 

Adrian

FreeNAS Experienced
Joined
Jun 29, 2011
Messages
124
Surely you're not suggesting I try to keep 20TB backed up. Sort of defeats the purpose of RaidZ3 in the 1st place, don't you think?
Don't confuse RAIDZ*, even with snapshots, as a backup. Make the wrong mistake and you will be longing for a copy, or copies, of your data somewhere else. Resilient safe storage is even more expensive than you think.
 

millst

FreeNAS Experienced
Joined
Feb 2, 2015
Messages
130
Yeah, RAID is for reliability, possibly performance. It is not a substitute for a backup. Yes, you are expected to back up your 20TB (or the minimum portion you cannot stand to lose).
 
Top