Summary: | genkernel-3.4.0-r1 with gentoo-source (2.4), initrd mount / ro | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | David Bonnafous <david.bonnafous> |
Component: | genkernel | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
genkernel-3.4.0-ro-root-fix.patch
genkernel-3.4.0-r1.ebuild.patch |
Description
David Bonnafous
2006-08-10 03:34:19 UTC
This problem has affected my 2.4 box as well. Used genkernel-3.4.0-r1 to generate a new gentoo-sources-2.4.32-r7 kernel and initrd. Upon rebooting into the new kernel and initrd, the boot stopped unable to find the root device. Dropping to ash shell showed the root device node existed at /dev/discs/disc0/part3, but previous messages saying "unable to generate modules.cache" indicated this problem i.e. root filesystem in initrd ramdisk still read only. Based upon the information in this bug, I modified the genkernel-3.4.0-r1 ebuild in my portage overlay. The patch I applied modifies the linuxrc to mount the proc filesystem prior to remounting the root filesystem read-write, instead of the other way around. I rebuilt genkernel, then kernel and intrd and rebooted. The initrd now booted successfully. I therefore attach the patches for the linuxrc and patch to the ebuild for commit to CVS. Created attachment 95335 [details, diff]
genkernel-3.4.0-ro-root-fix.patch
Patch for linuxrc which corrects failure of read-write remount of root filesystem.
Created attachment 95336 [details, diff]
genkernel-3.4.0-r1.ebuild.patch
Patch for ebuild to epatch for read only root filesystem bug.
Just a further note, tried the patched genkernel-3.4.0-r1 with gentoo-sources-2.6.17-r4 on my 2.6 box. This change doesn't seem to have caused any problems. Fixed in 3.4.1, thanks! |