https://bugzilla.novell.com/show_bug.cgi?id=760859 https://bugzilla.novell.com/show_bug.cgi?id=760859#c27 --- Comment #27 from Volker Kuhlmann <volker3204@paradise.net.nz> 2012-11-01 21:02:12 NZDT --- Installed the updates from yesterday including the dbus packages. Rebooted, failure to run md1 altogether - this is on the machine with 2 SATA disks in RAID1, and with the previous mdadm-3.2.2-4.4.1.x86_64 Rebooted again, md1 is started, but with only 1 disk. Rebooted some more, it appears md1 is started with only one disk, and it's random which one that is. I am guessing that the boot failure resulted from neither disk being available for md1. The previous mdadm package was needed to make md1 start with both disks, but it seems that's no longer the case. This whole thing smells like a race problem, and it seems irrelevant whether one of the disks is PATA. dbus may be involved, I don't see any other system-level package change since I last tested it 6 days ago. It also looks like that Linux md raid is currently severely broken :-( -- 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.