On 22:05, Christoph Egger wrote: > Steven Chamberlain <[email protected]> writes: > > On 20:59, Christoph Egger wrote: > >> Christoph Egger <[email protected]> writes: > >> > Update-grub seems to fail now for me. > >> > >> % sudo update-grub > >> Generating grub.cfg ... > >> Found kernel of FreeBSD: /boot/kfreebsd-11.0-0-amd64.gz > >> Found kernel module directory: /boot/lib/modules/11.0-0-amd64 > >> ls: cannot access /boot/lib/modules/10.0-1-amd64/unknown.ko: No such file > >> or directory > >> ls: cannot access /boot/lib/modules/10.0-1-amd64/unknown.ko: No such file > >> or directory > > > > Are you using the latest grub-pc from sid (>= 2.02~)? > > unstable grub works fwiw
It can be explained by: * your zpool was already version 5000 (created by zfsutils newer than that in wheezy), having feature@lz4_compress "enabled", but it wasn't "active"/in use yet (see `zpool get all`) * you started using kFreeBSD 10.1, which if feature@lz4_compress is enabled, will compress new metadata with lz4 compression (which is unrelated to the zpool 'compression' setting for file contents) * GRUB << 2.02 can't understand lz4, grub-probe returns "unknown" filesystem type and it's not handled very robustly here This seems like a rare situation. Normally an upgrade from wheezy or current jessie to sid would have: * zpool version 28 with no feature@lz4_compress, so kFreeBSD 10.1 can't make lz4 active in the pool unless they did a manual `zpool upgrade` * kernel upgraded together with grub-pc (>= 2.02~), which supports using lz4 in a zpool I see this perhaps being a problem if 10.1 migrates before grub-pc does. Or, trying to install a jessie system from sid d-i. What we could do is set feature@lz4_compress=disabled in partman-zfs, just temporarily, until the newer grub version migrates. Regards, -- Steven Chamberlain [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
