update failed

[ethereal]

i applied an update today and when it rebooted it said the update failed.

i rebooted and choose the boot before the failed update.

i am hopeless when it comes to the shell - can somebody tell me how to how to find out what the problem is.

thank you

 

[Fraoch]

Lots of reports of this, and the fix should be fairly easy:

https://forums.freenas.org/index.php?threads/freenas-9-3-update-through-webui-fails.26616/

https://forums.freenas.org/index.ph...3-stable-via-webgui-updater-any-longer.26778/

Just boot into a previous boot environment (looks like you've already done this) and apply updates. No shell required.

 

[hank]

i got the same failure:

Upgrade: base-os-9.3-STABLE-10199d3-2930742-97f6b5a -> base-os-9.3-STABLE-10594d6-cf4f77e-97f6b5a

Upgrade: FreeNASUI-9.3-STABLE-10199d3-2930742-97f6b5a -> FreeNASUI-9.3-STABLE-10594d6-cf4f77e-97f6b5a

Upgrade: freenas-pkg-tools-9.3-STABLE-82d7111 -> freenas-pkg-tools-9.3-STABLE-10594d6

Above update will not complete, gives below message:

Jan 16 11:28:47 nas mountd[2143]: bad exports list line /mnt/aaa/bbb

Jan 16 11:28:59 nas updated.py: [freenasOS.Update:741] Update got exception during update: Unable to mount boot-environment FreeNAS-9.3-STABLE-201501151844

Jan 16 11:29:00 nas manage.py: [middleware.exceptions:38] [MiddlewareError: Unable to mount boot-environment FreeNAS-9.3-STABLE-201501151844]

the boot '201501151844' does not exist in my boot, the last one is 201501150211.

 

[sef]

There were a couple of issues with some of the -STABLE updates.

First, a typo on my part. (Specifically the result of missing a git cherry-pick.) This caused the next update to fail, because it tried to execute "umount mount -t zfs blahblahblah" instead of "umount -f /boot/grub". Changing "arts =" to "args =" in /usr/local/lib/freenasOS/Update.py fixes that; otherwise, you can do an ISO install, or revert to a prior boot environment and update again.

The second one was that some /dev directory entries somehow got into the package file. And the new code mounts devfs in the target environment and the new install code attempts to do things to those, and then it fails because devfs doesn't let it. We've taken steps to ensure that none of the contents of /dev get in the package file again. (In this case, the update would not work, so things will Just Work when the next -STABLE update happens. Also, when the upgrade fails, it cleans up after itself.)

There are also multiple reports of "failed upgrade" after the reboot, which mostly appear to happen when doing what works out to be a downgrade.