USB BOOT FULL

[norskman]

So my USB disk (16Gb) is full up.
I deleted all old boot environments using the delete command in the GUI, leaving just two.

The GUI still reports that the USB disk is 96% full.

So then I do a scrub. It completes. The USB disk is still 96% full.

How do I clear down the USB disk space so I can add new updates please?

I never had this problem before.

 

[dlavigne]

Does zpool status indicate that it is still that full?

 

[norskman]

my pool status output shows the following:
pool: freenas-boot

state: ONLINE

scan: scrub repaired 0 in 0h7m with 0 errors on Tue Oct 27 22:16:58 2015

config:



NAME STATE READ WRITE CKSUM

freenas-boot ONLINE 0 0 0

da0p2 ONLINE 0 0 0



errors: No known data errors



pool: store

state: ONLINE

scan: scrub repaired 88K in 13h32m with 0 errors on Sun Sep 27 13:32:16 2015

config:



NAME STATE READ WRITE CKSUM

store ONLINE 0 0 0

raidz1-0 ONLINE 0 0 0

gptid/16f6ea24-de85-11e3-93d4-e840f2ed2010 ONLINE 0 0 0

gptid/e59ff25d-02b2-11e4-9ecb-e840f2ed2010 ONLINE 0 0 0

gptid/c79fb407-f605-11e3-9126-e840f2ed2010 ONLINE 0 0 0

gptid/70dc6782-2f51-11e2-83bb-e840f2ed2010 ONLINE 0 0 0

logs

gptid/7128306b-2f51-11e2-83bb-e840f2ed2010 ONLINE 0 0 0



errors: No known data errors


So no errors. But the flashing red light on the GUI screen says its 96% full!

 

[dlavigne]

Sorry, brain fart. I meant to ask for the output of zfs get space freenas-boot. This time please use Insert -> Code to paste the output.

 

[norskman]

Here is the output:

Code:

# zfs get space freenas-boot
NAME          PROPERTY              VALUE          SOURCE
freenas-boot  name                  freenas-boot   -
freenas-boot  available             0              -
freenas-boot  used                  14.4G          -
freenas-boot  usedbysnapshots       0              -
freenas-boot  usedbydataset         31K            -
freenas-boot  usedbyrefreservation  0              -
freenas-boot  usedbychildren        14.4G          -

How do I clear that.....

many thanks - your brain fart is more knowledgeable than I am on this one.

 

[dlavigne]

Hmm, it's definitely still full... Which build of FreeNAS (from System -> Information)? Next up, paste the output of beadm list as inserted code.

 

[norskman]

FreeNAS version is:
FreeNAS-9.3-STABLE-201509282017

beads list output attached:

Code:

beadm list
BE                              Active Mountpoint  Space Created         Nickname
default                         -      -          509.4M 2015-05-31 14:51     default
FreeNAS-9.3-STABLE-201509220011 -      -          189.0M 2015-09-22 14:14     FreeNAS-9.3-STABLE-201509220011
FreeNAS-9.3-STABLE-201509282017 NR     /           14.3G 2015-09-29 21:28     FreeNAS-9.3-STABLE-201509282017
[root@freenas] ~#

 

[dlavigne]

FreeNAS-9.3-STABLE-201509282017 NR / 14.3G 2015-09-29 21:28 FreeNAS-9.3-STABLE-201509282017

This one is the culprit but currently can't be removed because of the "NR" flags. That should correspond to "On Reboot,Now" in the System -> Boot menu. Does that entry still show in the GUI? If so, highlight another entry and Activate it. If there is no other entry, see if it will let you make a new one, then activate it. Note that this may fail if you do not have enough space to make another entry.

 

[norskman]

I do show another one. When I select it I get the error 'Failed to activate boot environment'.

It will not allow me to create another boot environment - I get the error ' failed: to create a new boot'.
So that does not work either.

 

[dlavigne]

Does this command give an error?

beadm activate FreeNAS-9.3-STABLE-201509220011

If it works, that should move the "R" flag to that entry in beadm list. If not, paste the error it gives.

 

[norskman]

Still got an error - 'No space left on device' See attached code

Code:

beadm activate FreeNAS-9.3-STABLE-201509220011
Attempt to unmount boot environment 'FreeNAS-9.3-STABLE-201509220011' mounted at '/var/tmp/BE-FreeNAS-9.3-STABLE-201509220011.SxTzNp3x'
Gracefully unmounted boot environment 'FreeNAS-9.3-STABLE-201509220011' from '/var/tmp/BE-FreeNAS-9.3-STABLE-201509220011.SxTzNp3x' mount point
sed: fclose(): No space left on device

 

[dlavigne]

That's what I suspected. You still have a couple of options here. One is to save your config, download and install the latest SU to a new, bigger stick, and restore your config. This would be a longer term solution as it will give you more room.

Another option is to try booting into the "default" BE (pick it out of the boot menu at boot time). See if that will let you delete FreeNAS-9.3-STABLE-201509282017 from the GUI. Note that if it does, it will return the system back to its original install (ie no updates or config changes) so this may not be what you want.

I'm also not sure if it is a bug or a feature that the last boot entry was over 14GB in size. Someone else might know or it might be worth making a bug report about, especially seeing that the hardware requirements say that a 4GB stick should work as a bare minimum.

 

[norskman]

Will try option 2 first. But I will take a backup first. Then I will do option 1.