Latest update problem: 9.10 stable 201604261518

[esamett]

1. My NAS is running headless so I couldn't see the problem. I left the NAS about 30 minutes to update but I couldn't logon via Network. I did Hard Reset and it booted promptly in a couple of minutes.

2. I then got warning that my Flash drive was getting full and tried to clean out older Boots. 9.10 Initial delete seems to go wrong. Rather than the several seconds to delete it takes with the other entries this one takes only around 2 seconds. However the entry persists in the Menu. It is not seeming to Delete properly or it is deleted and still on the list.

Regards,

 

[BossyBear]

Other problems with this update. "Error: database locked" while installing, unable to remove it "Database locked" errors also.

I had to reboot twice to get to where I could delete this failed boot environment.

Glad to see it isn't just me :)
:(

 

[Will Dormann]

I had trouble as well with this update. I used the web UI to install the update, and the first attempt to install resulted in an "Error: database locked" error. Without performing a reboot or anything, I simply tried installing the update, and that worked. It got to the point of rebooting the machine, but it never came back up again. Walking over to the server, I was greeted with:

I typed "reboot" and the system came back up OK. Not the most pleasant upgrade experience!

 

[styno]

Same experience after the upgrade last night: the initial reboot (as part of the upgrade process) ended up on the db> prompt. A reboot seemed to fix it....
I didn't have time to investigate last night...

 

[Clevinger]

I'm have these same issues. Warning that boot was getting full, deleted the oldest boot which took about 5 minutes and was successful. Got the database locked error and am currently restarting before I attempt to delete the failed boot before retrying the install.

Edit: Got it working by not deleting the incomplete boot and retrying the update.

 

[Marc E]

Hmm, I'm having about the same issue as everyone else. For me, the update never gets to the point of rebooting though. After choosing "Apply Pending Updates", the update will go ahead, but will quit out part way through, close the update pop-up and leave me back at the web GUI. The error tooltip which appears briefly at the top of the screen is always, "Error: Database is locked". I've tried multiple times across several reboots. At this point, there are no other errors beyond the error from trying to update, so I'm probably going to leave it as-is for now. Try updating again at another time...

 

[statik]

Having same issue. Click update, download starts, then failes giving error code with "Error: Database is Locked". stuck at rebooting right now. I think its wise to just hold off on this update... maybe the developers forgot to test it? lol

 

[ericv]

Other issues with the db locked error over here...

https://forums.freenas.org/index.php?threads/9-10-hangs.43072/#post-283536

 

[BossyBear]

I had no trouble when I did the update from the CLI. In fact I like the verbosity of the CLI process better than the bar graph in the web GUI.