New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zfs-9999 + genkernel-3.5.0.5/9999 - block device mypool/ds is not a valid block device #5197
Comments
This looks like gentoo and from my experience is very likely related to a wrong grub configuration or a zpool.cache file that made it into the initramfs. Did your ZFS root before (re)emerging zfs-9999, if so with what version? |
Yes, this is on gentoo. Boot works just fine on an older git version from June-ish (0.6.5-329_g5c27b29 is what is reported from "modinfo zfs"). |
Working entry in my grub.cfg:
From memory what I have done to get it booting: Removed this block
from the grub menu entry since it seems to interfere in locating root Also quite important was to rename /etc/zfs/zpool.cache prior to creating the initramfs with
(extra --callback list to have zfs-kmod recompile). My guess is the zpool.cache in the initrd fucked it up pretty good, since every time I forgot to move it away I had to recover. Hope this helps. |
I think it is a Gentoo genkernel bug, so I raised a bug report and proposed a patch for you to please try here: https://bugs.gentoo.org/show_bug.cgi?id=597154 If you agree please continue the discussion in the above Gentoo bug report, thanks. |
Gentoo patch looks reasonable: a ZFS filesystem isn't a block device by definition. |
Agreed, I'm closing this. |
could not boot latest head (as of 09/27) with newer genkernel (which should have the fix for the libgcc_s bug). pool gets imported but doesn't get mounted anywhere.
The text was updated successfully, but these errors were encountered: