https://bugzilla.novell.com/show_bug.cgi?id=421379 User jnieuwenhuizen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=421379#c421369 Summary: mkinitrd-2.4-16 fails with root on lvm+md Product: openSUSE 11.1 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnieuwenhuizen@novell.com QAContact: qa@suse.de Found By: --- mkinitrd-2.4-16 fails with root on md0: [after I got a bootable system again with a downgraded mkinitrd] Upgrade: root@peder:/etc/zypp# zypper install mkinitrd Reading installed packages... The following package is going to be upgraded: mkinitrd Overall download size: 57.0 K. After the operation, 38.0 K will be freed. Continue? [YES/no]: Retrieving package mkinitrd-2.4-16.x86_64 (1/1), 57.0 K (101.0 K unpacked) Retrieving: mkinitrd-2.4-16.x86_64.rpm [done] Installing: mkinitrd-2.4-16 [done] Test: root@peder:/etc/zypp# mkinitrd -k /boot/vmlinuz-2.6.25.5-1.1-default -i /tmp/initrd egrep: /lib/mkinitrd/setup/31-evms.sh: No such file or directory egrep: /lib/mkinitrd/setup/41-md.sh: No such file or directory egrep: /lib/mkinitrd/setup/81-dasd.sh: No such file or directory egrep: /lib/mkinitrd/setup/81-iscsi.sh: No such file or directory egrep: /lib/mkinitrd/setup/81-zfcp.sh: No such file or directory egrep: /lib/mkinitrd/setup/92-busybox.sh: No such file or directory Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-2.6.25.5-1.1-default Initrd image: /tmp/initrd Root device: /dev/lvmraid/lvm1 (mounted on / as ext3) Resume device: /dev/sda6 Device md0 not handled Script /lib/mkinitrd/setup/72-block.sh failed! Note that no /tmp/initrd image is created here. Downgrading to mkinitrd-2.2-19.1.x86_64.rpm fixes it for me. I'm not sure how, but during the dist-upgrade process from 11.0 to factory, an initrd was created that fails to mount the raid. The upgrade process finished (apparently) succesfully. When booting, it says Waiting for device /dev/md0 to appear: ok node name not found invalid root filesystem -- exiting to /bin/sh not very useful, because the keyboard does not work yet. The impact of this bug is made especially worse by n#421369. $ mount /dev/mapper/lvmraid-lvm1 on / type ext3 (rw,acl,user_xattr,errors=remount-ro) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/mapper/lvmraid-lvm2 on /home type ext3 (rw,errors=remount-ro) /dev/mapper/lvmplain-lvm0 on /biek type ext3 (rw,errors=remount-ro) /dev/mapper/lvmraid-lvm0 on /other type ext3 (rw,errors=remount-ro) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) /proc on /var/lib/ntp/proc type proc (ro) $ sudo pvdisplay --- Physical volume --- PV Name /dev/sdc2 VG Name lvmplain PV Size 465,74 GB / not usable 972,50 KB Allocatable yes (but full) PE Size (KByte) 4096 Total PE 119230 Free PE 0 Allocated PE 119230 PV UUID ZvABzO-Tzzz-v5ho-r9pG-RTz5-DEEB-sWlM7G --- Physical volume --- PV Name /dev/md0 VG Name lvmraid PV Size 295,41 GB / not usable 1,25 MB Allocatable yes PE Size (KByte) 4096 Total PE 75624 Free PE 19304 Allocated PE 56320 PV UUID 6AGq0k-ldg0-yswb-ft3W-LG1b-nuIe-40Mcl7 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.