ZFS Pool Upgrade for the boot volume doesn't work

[schojo]

So in my messages this pops up:
WARNING: Oct. 2, 2017, 10:20 p.m. - New feature flags are available for volume freenas-boot. Refer to the "Upgrading a ZFS Pool" section of the User Guide for instructions.

I then go to the Volumes, select freenas-boot, it show's the upgrade button. I click on it, i get the warning and then nothing happens...i can do this over and over again without anything happening.
I'm running FreeNAS-11.0-U4 on a mirrored 128GB USB stick freenas-boot

 

[MrToddsFriends]

So in my messages this pops up: [...]
I then go to the Volumes, select freenas-boot, it show's the upgrade button. [...]

Strange. Normally, freenas-boot is not displayed in Storage -> Volumes -> View Volumes in the GUI (at least in the "classic GUI"). Likewise no "Upgrading a ZFS pool" warning is displayed for freenas-boot, at least this is the case with the two new feature flags, which were added to FreeNAS 11.0.

Is this with the new upcoming GUI?

 

[schojo]

No, it's the current one.

 

[BigDave]

Please post the result (in code tags please) of the command
zpool status

Here is an example of one of my servers...

Code:

root@freenas:~ # zpool status
  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Mon Oct  2 03:45:44 2017
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  ONLINE	   0	 0	 0
		  ada0p2	ONLINE	   0	 0	 0

errors: No known data errors

  pool: plumber
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
		still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
		the pool may no longer be accessible by software that does not support
		the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 1h55m with 0 errors on Wed Sep 27 02:56:48 2017
config:

		NAME											STATE	 READ WRITE CKSUM
		plumber										 ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/9562a750-c341-11e6-a20a-90e2ba0045fc  ONLINE	   0	 0	 0
			gptid/c0a640f6-c3df-11e6-9356-90e2ba0045fc  ONLINE	   0	 0	 0
			gptid/18ed8eb6-f573-11e6-96fa-90e2ba0045fc  ONLINE	   0	 0	 0
			gptid/91cb5f7c-32a1-11e6-a5d4-90e2ba0045fc  ONLINE	   0	 0	 0
			gptid/1dc335b1-f551-11e6-acda-90e2ba0045fc  ONLINE	   0	 0	 0
			gptid/f7acbdd0-f5ab-11e6-9ee6-90e2ba0045fc  ONLINE	   0	 0	 0

errors: No known data errors

 

[BigDave]

I'm just curious here but did you name your pool freenas-boot???

 

[schojo]

pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h5m with 0 errors on Fri Oct 6 03:50:36 2017
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
da0p2 ONLINE 0 0 0
da1p2 ONLINE 0 0 0

errors: No known data errors

That's my freenas installation. The storage itself is another pool that i'm cutting off these logs sind it's not importsnt for the topic(?)

Gesendet von meinem Moto G (4) mit Tapatalk

 

[BigDave]

The storage itself is another pool that i'm cutting off these logs sind it's not importsnt for the topic(?)

It IS important. When looking at your picture in your post above, it appears that your storage pool has been named
"freenas-boot"!
We need a clarification as to the status of your storage pool AND your boot pool.

 

[Ericloewe]

DO NOT UPGRADE THE BOOT POOL. EVER.

With that ominous warning out of the way, what is almost certainly happening here is that you have a second pool called freenas-boot, so please provide the full output of zpool status. Pipe it to less to make sure that you get everything ( zpool status | less.

 

[schojo]

alrighty, i'm pretty sure about it, but here goes:


pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h5m with 0 errors on Fri Oct 6 03:50:36 2017
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
da0p2 ONLINE 0 0 0
da1p2 ONLINE 0 0 0

errors: No known data errors

pool: warehouse
state: ONLINE
scan: scrub repaired 0 in 0h45m with 0 errors on Sun Oct 8 09:39:12 2017
config:

NAME STATE READ WRITE CKSUM
warehouse ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/8dfdb265-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0
gptid/8eceb9d2-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0
gptid/8f9b3b2f-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0
gptid/90684d29-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0

errors: No known data errors



 

[Ericloewe]

alrighty, i'm pretty sure about it, but here goes:


pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h5m with 0 errors on Fri Oct 6 03:50:36 2017
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
da0p2 ONLINE 0 0 0
da1p2 ONLINE 0 0 0

errors: No known data errors

pool: warehouse
state: ONLINE
scan: scrub repaired 0 in 0h45m with 0 errors on Sun Oct 8 09:39:12 2017
config:

NAME STATE READ WRITE CKSUM
warehouse ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/8dfdb265-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0
gptid/8eceb9d2-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0
gptid/8f9b3b2f-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0
gptid/90684d29-9e04-11e7-a3d3-7085c225560d.eli ONLINE 0 0 0

errors: No known data errors



View attachment 21002

In the future, please use [CODE][/CODE] tags for console output, to preserve whitespace.

Now, back to your problem... It's an odd one. The boot pool should be hidden in the GUI, but it clearly isn't, which raises a number of questions... But it's probably best to file a bug report for that. Include a debug tarball.

 

[danb35]

But it's probably best to file a bug report for that. Include a debug tarball.

...and the easiest way to do that is to use the Support button in the web GUI to report the bug.

 

[schojo]

yep, done. thanks! i had no idea that i was not supposed to see it?!

 

[Ericloewe]

I'm somewhat comforted by the fact that William has just as much of an idea of how the hell this happened as I do.

https://bugs.freenas.org/issues/26112

 

[blakestock]

Sorry to necro an old post, but I'm having this issue on a new install of FreeNAS 11.1-RELEASE. - https://imgur.com/3tOEqMh

I updated it to 11.1.U2 and noticed the console messages being spammed every 2 minutes - https://imgur.com/Y770RzQ

Here's the zpool status output:

Code:

root@freenas:~ # zpool status | less
  pool: BackupVol
 state: ONLINE
  scan: none requested
config:

		NAME											  STATE	 READ WRITE CKSUM
		BackupVol										 ONLINE	   0	 0	 0
		  gptid/6953f205-2026-11e8-ac30-a4badb43ea2c.eli  ONLINE	   0	 0	 0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:22 with 0 errors on Sun Mar  4 20:43:28 2018
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  ONLINE	   0	 0	 0
		  da1p2	 ONLINE	   0	 0	 0

errors: No known data errors
root@freenas:~ #

Which brought me to this thread. Looks like the bug was closed - cannot reproduce. All I did was follow the install from the documentation. Installed from a USB drive to an old HDD for POC. I'll be reinstalling shortly to another drive after I'm done with further testing and can update here once it's reinstalled. Is there a fix for this? Let me know if I can provide any further info