https://bugzilla.novell.com/show_bug.cgi?id=445490 Michael McCarthy changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User mmccarthy@lojack.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c2 --- Comment #2 from Michael McCarthy 2008-11-16 06:49:03 MST --- Created an attachment (id=252502) --> (https://bugzilla.novell.com/attachment.cgi?id=252502) This is the boot.msg file NOTE: The sytem was stopped at the /bin/sh prompt when I inserted a USB flash drive. The follwing lines in the boot.msg file indicate the time when the system was stopped and the usb stick inserted prior to resuming with <CTRL-D>. <6>usb 1-1: new high speed USB device using ehci_hcd and address 2 <6>usb 1-1: configuration #1 chosen from 1 choice <6>usb 1-1: New USB device found, idVendor=0930, idProduct=6534 <6>usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 <6>usb 1-1: Product: USB Flash Memory <6>usb 1-1: Manufacturer: M-Sys <6>usb 1-1: SerialNumber: 087043505130A995 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 Michael McCarthy changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c4 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@novell.com, jkupec@novell.com AssignedTo|yast2-maintainers@suse.de |kernel-maintainers@forge.provo.novell.com --- Comment #4 from Ján Kupec 2008-11-18 06:35:48 MST --- Looks like a kernel problem then. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c6 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@novell.com --- Comment #6 from Neil Brown 2008-11-21 14:11:39 MST --- I think this might be the same as bug 433980 and bug 435778. I'm guessing some udev raciness but I'm no expert there. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c7 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasievers@novell.com AssignedTo|kasievers@novell.com |bwalle@novell.com --- Comment #7 from Kay Sievers 2008-12-08 14:35:59 MST --- Sounds like an initramfs problem. Initramfs can not just wait for /dev/md* devices to appear. Because of the weird lifetime rules of md, and it's legacy device-creation interface, it is always there, and does not show up when it available. I guess, it needs some special handling, to check when the device becomes "online". I can not tell for sure, I do not have any raid rootfs setup. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c9 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|nfbrown@novell.com | Resolution| |FIXED --- Comment #9 from Neil Brown 2008-12-11 12:38:04 MST --- According to bug 435778, this has been fixed. It needs a 'udevadm settle' before asking udev what the filesystem type is. Hannes added 'wait_for_events' in mkinird-boot.sh for mdadm, just after assembling the root device. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c11 --- Comment #11 from Neil Brown 2008-12-22 17:20:17 MST --- That is the correct file and (close enough to) the correct fix. We put "wait_for_events" just before the final "fi" of that file. One you do that, you need to recreate the initrd. Simply running mkinitrd as root should do this. Then try to reboot. -- 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.

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#c13 --- Comment #13 from Joe Morris 2008-12-23 04:59:11 MST --- Well, changing the timeout to 60 didn't change anything. The message "invalid root filesystem -- exiting to /bin/sh" is found in line 88 of boot-mount.sh where it looks like it is in the filesystem checking area. I suppose it cannot do a fsck, even though it looks like it has assembled the raid1, and not found the resume, before that message. If the wait_for_events is the fix, it isn't working here. Just to triple check, this is my last few lines from boot.md.sh: if [ "$md_dev" ] ; then /sbin/mdadm $mdconf --auto=md $md_dev || /sbin/mdadm -Ac partitions $mdarg --auto=md $md_dev fi wait_for_events fi (beware of word wrapping, that is only 5 lines). Thanks for any ideas. Should I reopen this bug? -- 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.

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#c15 --- Comment #15 from Joe Morris 2008-12-23 22:47:21 MST --- Thanks for that. This is what I found. udevadm info -q path -n /dev/md0 gave me the correct /devices/virtual/block/md0 udevadm info -q env -p /devices/virtual/block/md0 gave me 'no record for '/devices/virtual/block/md0/ in the database' (note: you had a typo) after some testing, I tried udevadm info -q all -n /dev/md0 That gave me some output, but ID_FS_TYPE was missing. I entered echo change > /sys/block/mdo/uevent and repeated udevadm info -q all -n /dev/md0 This time I did have ID_FS_TYPE as well as others. Not quite sure what this reveals yet, but it gives me more things to check. Either hitting Ctrl-D or entering exit continues the boot, but boot.md shows as failed, as well as it shows failed (but apparently succeeds) when it later tried to mount my raid 1 home partition md1. So I wil look again at the mkinitrd scripts. Thanks for your help so far. -- 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.

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 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.

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#c19 --- Comment #19 from Joe Morris 2008-12-24 08:26:06 MST --- Until the real developers are able to track this down, I thought of a slightly less cludgy fix. I took out what I added to boot-mount.sh, and added these 2 lines in the opposite order just before the wait_for_events in boot-md.sh. This is also working, and since it uses the md variable, it should work a bit better than the hard coded md0, which meant I needed to put this fix in boot-md.sh and not mount. Here is what it looks like now at the end. (watch the wrapping) if [ "$md_dev" ] ; then /sbin/mdadm $mdconf --auto=md $md_dev || /sbin/mdadm -Ac partitions $mdarg --auto=md $md_dev fi sleep 1 echo change > /sys/block/md$md_minor/uevent wait_for_events fi Hope this will help you Petr until a real fix comes along. This is a better workaround than earlier, and it allows mine to boot right up. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User hare@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c21 --- Comment #21 from Hannes Reinecke 2009-01-07 01:59:51 MST --- It looks as if either md doesn't generate change events for when it's ready or that the udev rules need to be modified to update ID_FS_XXX for md. Kay? Neil? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User bwalle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c22 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |kasievers@novell.com --- Comment #22 from Bernhard Walle 2009-01-07 05:40:18 MST --- Per comment 21 NEEDINFO. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User daved@windclimber.id.au added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c24 Dave Davey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daved@windclimber.id.au --- Comment #24 from Dave Davey 2009-01-07 14:56:52 MST --- I have had the same result. https://bugzilla.novell.com/show_bug.cgi?id=445490#19 fixed the problem. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 Michael McCarthy changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User bwalle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c27 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bwalle@novell.com |mmarek@novell.com Status|ASSIGNED |NEW --- Comment #27 from Bernhard Walle 2009-01-08 08:40:16 MST --- Michal, that needs changes in mkinitrd-boot.sh in mdadm package. You're listed as maintainer of that package. Can you help here? I'm not really familiar with md, so you're the better person here ... :) -- 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.

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#c29 --- Comment #29 from Joe Morris 2009-01-08 14:50:01 MST --- I do not believe so. For example, this is from my running system: joe@jmorris:~> ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 801c2029-6789-4117-a461-da745a19f062 -> ../../sda1 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 a2d3f2bf-eaec-45a0-b843-55b15f037d83 -> ../../md0 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 a97bf970-827c-458d-8d59-764fc0381da8 -> ../../sdb1 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 e3e86c6b-4445-4611-90a8-fb7b2df6e5af -> ../../sda7 Even though my home is on md1, as you can see above it is still absent in by-uuid. I believe md0 is only there because of the added sleep 1 echo change > /sys/block/md$md_minor/uevent that I added to boot-mount.sh See Comment #19. But, looking around at /dev/disk/by-id, I see: joe@jmorris:~> ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 ata-HDS722516VLAT20_VNR40AC4CMNT6S -> ../../sdb lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-HDS722516VLAT20_VNR40AC4CMNT6S-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-HDS722516VLAT20_VNR40AC4CMNT6S-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-HDS722516VLAT20_VNR40AC4CMNT6S-part5 -> ../../sdb5 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-HDS722516VLAT20_VNR40AC4CMNT6S-part6 -> ../../sdb6 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 ata-ST3200822A_3LJ07EHY -> ../../sda lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-ST3200822A_3LJ07EHY-part1 -> ./../sda1 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-ST3200822A_3LJ07EHY-part2 -> ./../sda2 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-ST3200822A_3LJ07EHY-part5 -> ./../sda5 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-ST3200822A_3LJ07EHY-part6 -> ./../sda6 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 ata-ST3200822A_3LJ07EHY-part7 -> ./../sda7 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 edd-int13_dev80 -> ../../sda lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev80-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev80-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev80-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev80-part6 -> ../../sda6 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev80-part7 -> ../../sda7 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 edd-int13_dev81 -> ../../sdb lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev81-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev81-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev81-part5 -> ../../sdb5 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 edd-int13_dev81-part6 -> ../../sdb6 lrwxrwxrwx 1 root root 9 2009-01-09 05:21 md-uuid-50317547:316ba81e:fc3a8342:011169ec -> ../../md1 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 md-uuid-ffb096e5:5d1a78ab:71771454:6b84c526 -> ../../md0 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 scsi-SATA_HDS722516VLAT20_VNR40AC4CMNT6S -> ../../sdb lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_HDS722516VLAT20_VNR40AC4CMNT6S-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_HDS722516VLAT20_VNR40AC4CMNT6S-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_HDS722516VLAT20_VNR40AC4CMNT6S-part5 -> ../../sdb5 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_HDS722516VLAT20_VNR40AC4CMNT6S-part6 -> ../../sdb6 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 scsi-SATA_ST3200822A_3LJ07EHY -> ./../sda lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_ST3200822A_3LJ07EHY-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_ST3200822A_3LJ07EHY-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_ST3200822A_3LJ07EHY-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_ST3200822A_3LJ07EHY-part6 -> ../../sda6 lrwxrwxrwx 1 root root 10 2009-01-09 13:20 scsi-SATA_ST3200822A_3LJ07EHY-part7 -> ../../sda7 lrwxrwxrwx 1 root root 9 2009-01-09 13:20 usb-IC_USB_Storage-CFC_20020509145305401-0:0 -> ../../sdc lrwxrwxrwx 1 root root 9 2009-01-09 13:20 usb-IC_USB_Storage-MMC_20020509145305401-0:2 -> ../../sde lrwxrwxrwx 1 root root 9 2009-01-09 13:20 usb-IC_USB_Storage-MSC_20020509145305401-0:3 -> ../../sdf lrwxrwxrwx 1 root root 9 2009-01-09 13:20 usb-IC_USB_Storage-SMC_20020509145305401-0:1 -> ../../sdd Which at least recognizes md1 as well as md0, though I am not sure how that would change the fact that the file system info is still not output, which is what is causing this part to fail, i.e. jmorris:/home/joe # udevadm info -q env -n /dev/md0 MD_LEVEL=raid1 MD_DEVICES=2 MD_METADATA=0.90 MD_UUID=ffb096e5:5d1a78ab:71771454:6b84c526 ID_FS_USAGE=filesystem ID_FS_TYPE=ext3 ID_FS_VERSION=1.0 ID_FS_UUID=a2d3f2bf-eaec-45a0-b843-55b15f037d83 ID_FS_UUID_ENC=a2d3f2bf-eaec-45a0-b843-55b15f037d83 ID_FS_LABEL=root ID_FS_LABEL_ENC=root ID_FS_LABEL_SAFE=root jmorris:/home/joe # udevadm info -q env -n /dev/md1 MD_LEVEL=raid1 MD_DEVICES=2 MD_METADATA=0.90 MD_UUID=50317547:316ba81e:fc3a8342:011169ec MD_DEVNAME=1 Without the ID_FS_TYPE info the fsck cannot work and stops booting. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Priority|P5 - None |P2 - High -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User hpj@urpla.net added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c32 --- Comment #32 from Hans-Peter Jansen 2009-01-12 15:30:50 MST --- Michal, I bet that installing 10.2 involving a md and than upgrading to 11.1 will suffice. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User crrodriguez@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c34 Cristian Rodríguez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crrodriguez@novell.com --- Comment #34 from Cristian Rodríguez 2009-01-15 11:33:41 MST --- got bitten by this one recently.. comment19 seems to help. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User braendle@morphosys.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c36 Gerhard Braendle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |braendle@morphosys.com --- Comment #36 from Gerhard Braendle 2009-01-24 06:59:51 MST --- The same here with my DELL Dimension 8200. The relevant lines in my boot.msg read as follows: Trying manual resume from /dev/md0 resume device /dev/md0 not found (ignoring) Trying manual resume from /dev/md0 resume device /dev/md0 not found (ignoring) Waiting for device /dev/md1 to appear: ok invalid root filesystem -- exiting to /bin/sh $ Here I have to hit Ctrl+D (or type "exit" followed by <ENTER>) to continue booting. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User hpj@urpla.net added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c38 --- Comment #38 from Hans-Peter Jansen 2009-01-27 13:55:33 MST --- Joe, it escapes me, why this glitch holds you back from doing anything with 11.1? Well yes, it's nagging to boot into the rescue system, mount the devices by hand, edit the offender, call mkinitrd, and reboot.. Even a newly created RAID 1 will fail without the fix. But being as alarmed as you are, how about doing the upgrade, wait for the "will reboot in 10s" message, cancel it, apply attached patch, call mkinitrd, and all should be well. OTOH, you will only circumvent this issue, even if a fix is committed and rolled out, if you manually add the correct update repo during the upgrade/install.. Thus the former approach is still more appealing in my book. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c40 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mmarek@novell.com |kasievers@novell.com --- Comment #40 from Michal Marek 2009-01-28 09:05:48 MST --- Kay, I'm probably not the right person for this bug :(. Could you have a look? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c42 --- Comment #42 from Kay Sievers 2009-01-28 12:10:45 MST --- It needs to be checked, that the kernel md code sends the "change" event at the proper time, when device is ready to read from userspace, if we are not sure that is correct already. Also, the initramfs needs special handling of md devices, loop until the device is readable to investigate it, it can not just wait for the device to appear. -- 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.

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 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |whiplash@pobox.com --- Comment #45 from Gordon Schumacher 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.

https://bugzilla.novell.com/show_bug.cgi?id=445490 User petr.m@seznam.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=445490#c47 --- Comment #47 from Petr Matula 2009-03-25 08:35:35 MST --- New SLES/SLED 11 : the same problem -- 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.