https://bugzilla.novell.com/show_bug.cgi?id=760859 https://bugzilla.novell.com/show_bug.cgi?id=760859#c14 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|volker3204@paradise.net.nz | --- Comment #14 from Volker Kuhlmann <volker3204@paradise.net.nz> 2012-10-09 00:00:58 NZDT --- Thanks for outlining the procedure! I removed that one line and ran mkinitrd. After the first boot all was well. After the second boot: md125 : active raid1 sdb6[3] 99546668 blocks super 1.0 [2/1] [U_] md127 : inactive sda6[2](S) 99546668 blocks super 1.0 Taking the initrd apart with gunzip/cpio shows that the 64-md-raid.rules file was indeed gone. Both times when booting, the screen log said that md126 was started, then there's some resuming, then a 30s wait for timeout for one disk by uuid coming online, then a prompt asking whether to fall back on /dev/md126, with default yes - I pressed enter. The UUID it was waiting for belongs to md126. Next time I pressed n<return> - seems to make no difference. Restoring original initrd behaviour resolves the boot timeout. Is it possible something gets confused with the actual device name of the disks? Sometimes it's sd[ab], sometimes sd[af], sort of randomly for each boot. The 4 device names in between are taken up by an internal USB flash card reader. -- 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.