I could not believe simply creating a snapshot of the top level bpool would cause this, so I was curious enough to try it again and indeed this causes grub-probe to stop recognizing /boot as being zfs. Deleting the snapshot does not help, and I had to use my repair script to fix the boot again.
Before I fixed the bpool again, I saved zpool and zfs properties for the bpool and compared them afterwards. The only differences are the following:
zpool properties:
---
broken state:
bpool feature@extensible_dataset active
working state:
bpool feature@extensible_dataset enabled
zfs properties
---
broken state:
bpool snapshots_changed di dec 19 10:57:22 2023 -
working state:
(property does not exist)
I used to have sanoid enabled to periodically create snapshots of my system, which I have now excluded bpool from to prevent this from reoccurring.
These ZFS and grub issues appear to be related as well: /github. com/openzfs/ zfs/issues/ 15261 /github. com/openzfs/ zfs/issues/ 13873 /savannah. gnu.org/ bugs/index. php?64297
https:/
https:/
https:/
I could not believe simply creating a snapshot of the top level bpool would cause this, so I was curious enough to try it again and indeed this causes grub-probe to stop recognizing /boot as being zfs. Deleting the snapshot does not help, and I had to use my repair script to fix the boot again.
Before I fixed the bpool again, I saved zpool and zfs properties for the bpool and compared them afterwards. The only differences are the following:
zpool properties: extensible_ dataset active
---
broken state:
bpool feature@
working state: extensible_ dataset enabled
bpool feature@
zfs properties
---
broken state:
bpool snapshots_changed di dec 19 10:57:22 2023 -
working state:
(property does not exist)
I used to have sanoid enabled to periodically create snapshots of my system, which I have now excluded bpool from to prevent this from reoccurring.