Update stuck (Update: FreeNAS-9.10.1-U4 has already been applied. Please Reboot the system to avail)

[Harmless Drudge]

I'm having the same problem trying to update FreeNAS-9.10.1-U4 (ec9a7d3). I assumed that the update had crashed part way through ; it seemed to get stuck at 20%. There are unapplied updates pending. Checking for updates says I should just activate 9.10.2 but this returns an error. I'll try rebooting and redoing via the CLI eventually -- I didn't actually abort it, I simply refreshed the screen, whereupon the "installing" box disappeared. Presume it's not still busy as I was able to check for updates.

Suggestion: for future updates that may take a LONG time: it would be useful to know that and to have a confirmation as part of the update process.

First EVER problem updating FreeNAS. :(

 

[willrun4fun]

Guess I will keep waiting. Mine has been on 20% 1/5 for 1:20:00 so far. Will just let it go I guess. I see activity on the two USB drives in gstat from the console.

 

[Harmless Drudge]

Two USB drives? I have one 8Gb USB boot drive on the motherboard (64% used; 4.8Gb). The alert light is flashing but I can't click on it without closing the shell window.

It used to be Intel giveth and Microsoft taketh away<sigh>.

[root@freenas ~]# cd /var/tmp
[root@freenas /var/tmp]# wget http://download.freenas.org/9.10/STABLE/9.10.2/FreeNAS-9.10.2.tar
--2017-01-03 15:02:47-- http://download.freenas.org/9.10/STABLE/9.10.2/FreeNAS-9.10.2.tar
Resolving download.freenas.org (download.freenas.org)... 217.23.2.147
Connecting to download.freenas.org (download.freenas.org)|217.23.2.147|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 414834866 (396M) [application/octet-stream]
Saving to: ‘FreeNAS-9.10.2.tar’

FreeNAS-9.10.2.tar 100%[==========================================================>] 395.62M 404KB/s in 21m 22s

2017-01-03 15:24:10 (316 KB/s) - ‘FreeNAS-9.10.2.tar’ saved [414834866/414834866]

[root@freenas /var/tmp]# freenas-update FreeNAS-9.10.2.tar
Status: Installing base-os
Total Progress: [########________________________________] 20.00%​

So far nobody has posted how long this might take. Presumably with USB2 it should be reasonably similar across machines?

Update: on my box* it took just over 30 mins to reach 100% and then a few minutes more to get back the shell prompt. I got a warning that I was at 81% capacity used on the boot drive and have rebooted and deleted a few boot environments and am back to 50% and everything seems to be working fine.

*HP N54L with 16Gb ECC, 1x8Gb, 5x2Tb

 

[willrun4fun]

Two USB drives? I have one 8Gb USB boot drive on the motherboard (64% used; 4.8Gb). The alert light is flashing but I can't click on it without closing the shell window.

It used to be Intel giveth and Microsoft taketh away<sigh>.

[root@freenas ~]# cd /var/tmp
[root@freenas /var/tmp]# wget http://download.freenas.org/9.10/STABLE/9.10.2/FreeNAS-9.10.2.tar
--2017-01-03 15:02:47-- http://download.freenas.org/9.10/STABLE/9.10.2/FreeNAS-9.10.2.tar
Resolving download.freenas.org (download.freenas.org)... 217.23.2.147
Connecting to download.freenas.org (download.freenas.org)|217.23.2.147|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 414834866 (396M) [application/octet-stream]
Saving to: ‘FreeNAS-9.10.2.tar’

FreeNAS-9.10.2.tar 100%[==========================================================>] 395.62M 404KB/s in 21m 22s

2017-01-03 15:24:10 (316 KB/s) - ‘FreeNAS-9.10.2.tar’ saved [414834866/414834866]

[root@freenas /var/tmp]# freenas-update FreeNAS-9.10.2.tar
Status: Installing base-os
Total Progress: [########________________________________] 20.00%​

So far nobody has posted how long this might take. Presumably with USB2 it should be reasonably similar across machines?

This is when I have a board with IPMI. You could also just SSH in or open another browser window to look though.

 

[willrun4fun]

Mine just finished in around 3.5 hours. Dual Cruizer Fit 16GB drives in mirror.

 

[Harmless Drudge]

> You could also just SSH in or open another browser window to look though.

Hah, yes, I know. I'd have had a look eventually. :)

I don't follow the IPMI logic. I haven't ever used one -- it's an option for my HP N54L but FreeNAS doesn't support it so I never pursued it; I'd even forgotten. If FreeNAS 10 supported it and I could get one cheap I'd do it.

My boot disk is a single SanDisk Cruzer Facet 8Gb. You have a pair of 16Gb in mirror mode? Is this might-as-well or is possible downtime THAT bad?

 

[sef]

Most systems with IPMI also have a remote console capability. (Using Java, of all bloody things, wtf?)

Mirroring the boot devices isn't about downtime, it's about catching errors. Thumb drives are horrible -- slow, and with crappy media that will fail on you when you most need it not to. With ZFS and a mirrored pool, you won't lose data unless both devices lose the same logical block.

I'm fed up with thumb drives, though, and am recommending SSDs whenever you can.

 

[Wallybanger]

It is working, it just takes forever and a day. USB devices are a pain in the ass.

Yep, let her sit for ages and it finished successfully.

 

[Harmless Drudge]

> remote console capability with java

That's a useful tip. Thanks.

My FreeNAS build is 3 years old and boots daily (mostly I just use it for backups and it shuts down afterwards). Luckily, never had a problem with a USB drive -- swapped from 4Gb to 8Gb when FreeNAS needed it, but I did have an HD go bad. I started with a mishmash of leftover disks and low cost box with expensive ECC ram (because ZFS). Over time I'm becoming more inclined to make it my main NAS. Maybe this year. Will recycle an SSD by then.

 

[Arkhen]

Yep, let her sit for ages and it finished successfully.

Same here - around 40 minutes of waiting on the 20% "freeze" did the trick for me, on the below system.

- Motherboard: SuperMicro X11SSH-F
- CPU: Xeon E3-1270 v5
- HDD: 7x WD 4TB Reds
- RAM: Crucial 32GB Kit (2 x 16GB) DDR4 ECC
- USB /w Boots: Corsair Flash Voyager GT 32GB
- Updating from: 9.10.1-U4

 

[rogerh]

> remote console capability with java

That's a useful tip. Thanks.

I've got an N54L running FreeNAS with the IPMI card and it can do everything I've wanted in terms of remote console and remote control via the web browser and java. (Better with IE on Windows 8.1 than Safari or Firefox on OS X as the remote host though.)

 

[destructive]

the CLI cmd did the trick for me too, although that really shouldn´t be a required course of action

after applying the update this way the first reboot ended in a second one witch yielded two or three tracebacks before showing the console setup screen. they don´t seem to have anything to do with the update, but I put in a ticket anyway https://bugs.freenas.org/issues/20055

 

[soupdiver]

I have the same problem with the 9.10.2 stuck update.
What is the recommended way to clean up the update and then proceeding to install via CLI?
Not sure how to remove the boot record and downloaded update files

 

[sef]

Worst case: from the grub boot menu, pick the previous BE. After booting, use "beadm activate" to activate it; this will then allow you to delete the bad one using "beadm destroy -F". After that, "freenas-update -v check" and then "freenas-update -v --reboot update".

 

[I-Tech]

I was able to resolve by using the CLI updater and the 9.10.2 tar image. YMMV.

If you've already attempted to install and failed. Reboot (or find and kill the failed update process), delete the boot record for your failed 9.10.2.

Then as root:

cd /var/tmp
wget http://download.freenas.org/9.10/STABLE/9.10.2/FreeNAS-9.10.2.tar
freenas-update FreeNAS-9.10.2.tar


did this and was done in about 20 minutes.
thanks!!

 

[sremick]

Apparently this is still a "thing." Trying to upgrade from 9.10.1 -> latest 9.10-stable. It did 1/5, then the GUI hung and I saw from the Java IPMI console that it was rebooting (thanks for the warning, heh). Now I get the dreaded: "Update: FreeNAS-9.10.2-U2 has already been applied. Please activate 9.10.2-U2 via the Boot Environment Tab and Reboot to use this updated version."

Well, I did that, and now on the Boot screen, "9.10.2-U2" says "On Reboot, Now" but I'm still getting the above error. I've read through this thread but am not 100% certain, so on the chance that I'm misreading things or something has changed in the last 2 months, I'm posting here to play it safe.

Should I:
- Change back to the 9.10.1 boot and activate it?
- Delete the 9.10.2-U2 boot?
- Follow the command line updating method outlined in this thread?
- Do anything else?

 

[sef]

Go back to the previous BE (and activate it while you're there), and then do the command-line updating method.

 

[NamoMitK]

Go back to the previous BE (and activate it while you're there), and then do the command-line updating method.

I second this, but also advise making sure your boot drive isn't full (I'm sure you already did) and deleting the failed 9.10.2-U2 environment before heading to the command-line.

This was what I found to work (quoting myself the lazy way):

I was able to resolve by using the CLI updater and the 9.10.2 tar image. YMMV.

If you've already attempted to install and failed. Reboot (or find and kill the failed update process), delete the boot record for your failed 9.10.2.

Then as root:

cd /var/tmp
wget http://download.freenas.org/9.10/STABLE/9.10.2/FreeNAS-9.10.2.tar
freenas-update FreeNAS-9.10.2.tar

EDIT: Substitute http://download.freenas.org/9.10/STABLE/9.10.2-U2/FreeNAS-9.10.2-U2.tar if that's where you want to go....

 

[sremick]

Ok looks like I'm on "FreeNAS-9.10.2-U2 (e1497f2)" now with no pending updates. Thanks for your help and for humoring my cautiousness.

 

[norbs]

Wow this does take incredibly long. I thought I was stuck at 20% but I did a

Code:

beadm list

a few times and the latest environment does appear to keep growing but very slowly. It eventually rebooted and updated successfully.