Truenas Scale: Align boot-pool features to grub2 compat after migration from Core?

Hi,

I recently migrated from TrueNAS Core 13.0 to Scale 24.04 - yes, I’ll upgrade to more recent versions soon.

While researching “Stuck at ‘Welcome to grub’ issues” I came across the following zpool status boot-pool-Message:

One or more features are enabled on the pool despite not being
requested by the ‘compatibility’ property.

There are some features enabled (probably leftover from TrueNAS Core which didn’t use Grub2) which aren’t active, so there’s still something to do about. I’m thinking about aligning the pool’s features with what is listed in ‘grub2’ compatibility by disabling unsupported features, just to be on the safe side.

Do you think this is a good idea? I’ve already gotten to a place where I can pin-point which features are enabled but not listed in compatiblity, but before I mess things up, I thought to better ask others about it…

Of course a clean install would probably fix this, too, but I don’t want to disrupt service by re-install if not really needed.

This is the shell magic I’m using currently - it’s not fully automatic, the last step still is a “visual grep”…
zpool get all boot-pool | grep feature |cut -d@ -f2 | cat - /usr/share/zfs/compatibility.d/grub2| sort|grep -B1 enabled

If there’s an enabled feature which doesn’t have it’s name in the previous line, it’s not supported and maybe(?) would better be disabled?

As an example, resilver_defer and sha512 are enabled on the pool but the former is supported while the latter isn’t:
resilver_defer
resilver_defer enabled local
sha512 enabled local

Thanks for your suggestions,

Einhirn

Once a flag is enabled, it cannot be disabled.

Some “active” flags can be demoted to “enabled”, but not all.

I’m in the same boat here and I’m planning to just wait until I can recreate my boot volume.