https://bugzilla.novell.com/show_bug.cgi?id=445490 User joe_morris@ntm.org added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c17 --- Comment #17 from Joe Morris <joe_morris@ntm.org> 2008-12-24 02:53:41 MST --- Well, after looking around, and figuring out there was a boot folder that had the order of the scripts executing, I decided (since it failed right after resume device not found, ignoring) it had to be something in boot-mount.sh. I compared it with the one from 10.3 and too much has changed for me to understand what I could change. So I added the echo line (and then subsequent test still failed but I did has the ID_FS_TYPE this time), then added a sleep line after it to give it a bit more time. Now it will boot, but this is at best a kludge or desperate work around. To see what I changed: # And now for the real thing if ! discover_root ; then echo "not found -- exiting to /bin/sh" cd / PATH=$PATH PS1='$ ' /bin/sh -i fi echo change > /sys/block/md0/uevent sleep 1 sysdev=$(/sbin/udevadm info -q path -n $rootdev) # Fallback if rootdev is not controlled by udev if [ $? -ne 0 ] && [ -b "$rootdev" ] ; then devn=$(devnumber $rootdev) maj=$(devmajor $devn) min=$(devminor $devn) if [ -e /sys/dev/block/$maj:$min ] ; then sysdev=$(cd -P /sys/dev/block/$maj:$min ; echo $PWD) fi It surely isn't a fix, but at least now it will boot without me needing to hit Ctrl-D. Hope this helps to track down a real fix. -- 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.