Ahh, did you do the zpool upgrade on the boot pool? If so, that would render it non-bootable by GRUB, since it has new feature flags. Generally you never update the boot pool, we handle that in the software in the background if necessary.,
Oh my, please do not do that. Use the UI to do the zpool upgrade on the disk screen, or at minimum specify the pool name to upgrade. That is exactly what happened, the boot-pool got updated and its running newer ZFS which GRUB can't read.
To fix you will need to re-install and re-apply your config file.
@Kris Moore I also ran that command as it was mentioned in an alert after upgrading to Cobia. If it is not meant to be ran, maybe prevent that alert from showing? Kinda sending us into the woods.
@Kris Moore I also ran that command as it was mentioned in an alert after upgrading to Cobia. If it is not meant to be ran, maybe prevent that alert from showing? Kinda sending us into the woods.
* Upgraded from Scale to Cobria.
* Reports screens were not functioning.
* Loud banner message ZFS pool upgrade
* Everything seemed to be running fine so I went ahead and upgraded the ZFS pool.
* grub cannot recognize files system
* At least it's saturday.
* My only real concern is... if I reinstall Cobria, will the new install be able to read my data pool?
* Upgraded from Scale to Cobria.
* Reports screens were not functioning.
* Loud banner message ZFS pool upgrade
* Everything seemed to be running fine so I went ahead and upgraded the ZFS pool.
* grub cannot recognize files system
* At least it's saturday.
* My only real concern is... if I reinstall Cobria, will the new install be able to read my data pool?
Not my Jira ticket. But, yes. Someone has submitted such a ticket Jira: NAS-125081. Which further leads to there apparently being an PR for it already NAS-124771. Scheduled for 23.10.1.
Set compatibility property to 'grub2' on boot-pool. This inhibits feature
upgrades that could potentially break grub2 compatibility when zpool
upgrade is done on boot-pool to enable additional features.
Not my Jira ticket. But, yes. Someone has submitted such a ticket Jira: NAS-125081. Which further leads to there apparently being an PR for it already NAS-124771. Scheduled for 23.10.1.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.