https://bugzilla.novell.com/show_bug.cgi?id=656217 https://bugzilla.novell.com/show_bug.cgi?id=656217#c2 --- Comment #2 from Malvern Star 2010-11-29 07:39:16 UTC --- Created an attachment (id=402394) --> (http://bugzilla.novell.com/attachment.cgi?id=402394) File system table for unbootable system. Altering the final line of the attached fstab to use /dev/md0 functions as a workaround. The system boots normally. -- 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=656217 https://bugzilla.novell.com/show_bug.cgi?id=656217#c3 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |malv_star@hotmail.com --- Comment #3 from Neil Brown 2010-11-29 09:56:01 UTC --- Thanks for the report. Based on your description there seems to be some sort of race with device names appearing in /dev, particularly as it doesn't always fail, but does often. The script /etc/init.d/boot.localfs is responsible for getting this right. It is the script that causes the "repair filesystem" prompt to appear. That script has a function 'wait_for_udev' which should wait for the link to appear. You should see a message like: Waiting for /dev/disk/by-id/md-uuid-d87fe1ec:5ddde35d:eab631e5:c6c4a0ad ... After 30 '.'s it should should say 'timeout!', otherwise it should succeed. Do you see anything like that during boot. These messages don't appear in any logs unfortunately, only on the console. A digital photo of the screen when it stops and gives you a prompt might be quite useful. -- 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=656217 https://bugzilla.novell.com/show_bug.cgi?id=656217#c5 Malvern Star changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|malv_star@hotmail.com | --- Comment #5 from Malvern Star 2010-12-13 17:43:59 UTC --- OK, I can't reproduce this in 11.4 M4, but I have some further information for 11.3 Final. I don't think the problem is a race condition, because when the RAID holds /, GRUB reports that it is unable to find the root partition using /dev/disk/by-id. So we don't even get that far. The problem with recognising MD devices on AHCI seems to be much more fundamental. -- 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=656217 https://bugzilla.novell.com/show_bug.cgi?id=656217#c7 --- Comment #7 from Malvern Star 2011-04-03 04:52:05 UTC --- I can confirm your findings for 11.4 final. It has been suggested that 11.3 has "device enumeration issues", but beyond that I can't say much more. I'm inclined to agree with closing this bug as it is hopefully no longer a problem. Thanks, Solaris. -- 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.