https://bugzilla.novell.com/show_bug.cgi?id=445490 User whiplash@pobox.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c45 Gordon Schumacher <whiplash@pobox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |whiplash@pobox.com --- Comment #45 from Gordon Schumacher <whiplash@pobox.com> 2009-03-11 14:59:41 MST --- So... I'm seeing this very issue on a brand-new-clean install of 11.1 (so re: #32 - an upgrade has nothing to do with it.) I have two SATA disks, each of which has three partitions. All partitions are RAID autodetect, configured as RAID 1 - the first set for /boot, the second for swap, and the third for the root partition. I did all this at install time, and hit this bug when the system did its first reboot to complete the installation. So I believe that the requirement for reproducing this is 1) having your root partition being handled by MD raid, and possibly 2) having it not be /dev/md0. (In reply to comment #29)
Without the ID_FS_TYPE info the fsck cannot work and stops booting.
I'll second that; the init dies in /boot/83-mount.sh, lines 79-90: if [ -z "$rootfstype" -a -x /sbin/udevadm -a -n "$sysdev" ]; then eval $(/sbin/udevadm info -q env -p $sysdev | sed -n '/ID_FS_TYPE/p') rootfstype=$ID_FS_TYPE [ -n "$rootfstype" ] && [ "$rootfstype" = "unknown" ] && $rootfstype= ID_FS_TYPE= fi # check filesystem if possible if [ -z "$rootfstype" ]; then echo "invalid root filesystem -- exiting to /bin/sh" cd / PATH=$PATH PS1='$ ' /bin/sh -i The patch in #39 worked perfectly, though. -- 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.