9.3-Stable update fails

[larzeb]

I initiated the update from the console and got this message:

Dec 20 15:55:43 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: Unable to activate clone environment FreeNAS-9.3-STABLE-201412200530]
Dec 20 15:57:35 freenas updated.py: [freenasOS.Update:704] Unable to activate clone environment FreeNAS-9.3-STABLE-201412200530
Dec 20 15:57:35 freenas updated.py: [freenasOS.Update:710] Update got exception during update: Unable to activate clone environment FreeNAS-9.3-STABLE-201412200530
Dec 20 15:57:53 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: Unable to activate clone environment FreeNAS-9.3-STABLE-201412200530]
​

Anything that I've done wrong?

 

[dlavigne]

What's the size of the boot device? You may have to delete some unused boot environments in System -> Boot to make room for the new boot environment created by the update.

 

[larzeb]

It's a 32GB device.

Filesystem Size Used Avail Capacity Mounted on
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201412142326 28G 934M 27G 3% /
devfs 1.0k 1.0k 0B 100% /dev
tmpfs 32M 5.3M 26M 17% /etc
tmpfs 4.0M 8.0k 4M 0% /mnt
tmpfs 1.3G 48M 1.3G 4% /var
freenas-boot/grub 27G 7.8M 27G 0% /boot/grub
​

 

[dlavigne]

Lack of space doesn't seem to be the issue. Please create a bug report at bugs.freenas.org and post the issue number here.

I see that there is this related issue (https://bugs.freenas.org/issues/6886), but assuming you haven't set listsnapshots it seems like a different issue.

 

[larzeb]

Done

 

[cyberjock]

Does the clone environment already exist? Can I PM you to look at this more closely?

 

[cyberjock]

Just to update this thread I did a teamviewer and the problem is that the update scripts that run in the background when you initiate an update in the WebGUI was failing due to insufficient RAM. The user has only 4GB of RAM. We were able to manually run the update and the user is going to look into upgrading his system to newer hardware that can support >4GB of RAM.

 

[danb35]

I thought 9.3 was going to check for memory, and die if less than 8 GB present. Was I misinformed, or did this get dropped?

 

[cyberjock]

The CTO of iXsystems didn't want to add it.

 

[Ericloewe]

I imagine it would've made for some messy attempts at GUI updates or maintaining two installers.