Summary: | >=sys-kernel/genkernel-3.4.30 creates a buggy initramfs w/o lvm/dmsetup binaries | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Turbov <I.zaufi> |
Component: | [OLD] Core system | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | mschiff |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alex Turbov
2012-05-13 05:53:34 UTC
Confirmed. I am really lucky to always have a previous kernel+initrd around because current genkernel created an initrd for me that complains about missing vgscan and vgchange and results in an unbootable system. Sh***, you're right: http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commitdiff;h=9f36ecc125bf2c20bd28c0ad513577a858140a77 This should help: http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commitdiff;h=9743f8b39c6050746d7ff1949fc98999a847c4f9 +*genkernel-3.4.32 (14 May 2012) + + 14 May 2012; Sebastian Pipping <sping@gentoo.org> -genkernel-3.4.30.ebuild, + -genkernel-3.4.31.ebuild, +genkernel-3.4.32.ebuild: + Bump to 3.4.32 (bug #415697), remove broken 3.4.30 and 3.4.31 + Sorry for the trouble. Please re-open as needed. Problem persists, since helper symlinks (i.e. vgscan and vgchange) actually end up in /sbin, and those symlinks link to 'lvm', without path. Solutions might include: a) copy/symlink /bin/lvm to /sbin/lvm b) move /sbin/* lvm symlinks to /bin c) update symlinks to link to /bin/lvm To check that, build initramfs and then mount image somewhere. (In reply to comment #4) > Problem persists, since helper symlinks (i.e. vgscan and vgchange) actually > end up in /sbin, and those symlinks link to 'lvm', without path. I don't see any symlinks for vgscan/vgchange nor any use of these in latest genkernel. Please let me know how and where you found it. Also, you can find me as "sping" on freenode IRC right now if you like. Forget that, my mistake. Seems like I had to clean /var/cache/genkernel before assuming a bug. |