Summary: | initramfs:/etc/initrd.scripts USE_MADM USE_MULTIPATH_NORMAL order | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | weissgerbers |
Component: | genkernel | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Patch looks invalid -- no changes. Anyway, please report if you are still experiencing any problems with genkernel-4.1.0 which switched to udev. |
probing md devices before activating multipath devices avoids detecting md devices based on multipath devices Reproducible: Always Steps to Reproduce: 1. provide your system with multipath devices 2. configure md devices based on multipath devices 3. create lvm based on md as pv's and use lv as root device 4. genkernel --mdadm --multipath --lvm --mdadm-config=/etc/mdadm.conf all 5. try to boot title Gentoo Linux 3.7.10-r1 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-3.7.10-gentoo-r1 root=/dev/ram0 lvmraid=/dev/md0,/dev/md1,/dev/md2 real_root=/dev/vg/root init=/linuxrc ramdisk=8129 dolvm domultipath domdadm udev initrd /boot/initramfs-genkernel-x86_64-3.7.10-gentoo-r1 Actual Results: The root device /dev/vg/root is not found during boot because the md devicee are not initialized. Manually initializing multipath, then mdadm and lvm works fine. Expected Results: The boot should be complete without manual steps. pleas patch /usr/share/genkernel/defaults/initrd.scripts: 639,648d638 < if [ "${USE_MDADM}" = '1' ] < then < if [ -e '/sbin/mdadm' ] < then < /sbin/mdadm --assemble --scan < else < bad_msg "mdadm not found: skipping mdadm raid assembly!" < fi < fi < 657a648,657 > > if [ "${USE_MDADM}" = '1' ] > then > if [ -e '/sbin/mdadm' ] > then > /sbin/mdadm --assemble --scan > else > bad_msg "mdadm not found: skipping mdadm raid assembly!" > fi > fi