https://bugzilla.novell.com/show_bug.cgi?id=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c3 Richard Bos <richard.bos@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.bos@xs4all.nl --- Comment #3 from Richard Bos <richard.bos@xs4all.nl> 2012-09-23 20:37:12 UTC --- I ran into this bugreport, because I've something similar after I upgraded my openSUSE_11.4 system to openSUSE_12.2 On OS_11.4 I did not have any problems related to mdadm at all, it worked just fine. On OS_12.2 I run already sometimes into this problem, although the system is only on OS_12.2 for about a day. At the moment when it happens, the system goes into the mode during initializing that one has to the the root password to be able to enter "<ctrl> - D" or just type reboot. The second time the raid is working fine. For me this is fine to execute, but the same machine is just by my children and they will be stuck, especially when I'm not at home.... Just after the boot started, after the boot login screen, that states the mdadm failed for /dev/sdb, /dev/sdc, /dev/sdb1 and /dev/sdc1. # mdadm -V mdadm - v3.2.5 - 18th May 2012 I've only 1 raid. # uname -a Linux selene 3.4.6-2.10-default Just is just by heart when more details are appreciated I can look it up. Hmm, the output of "mdadm --examine --scan", is different compared to the info in the /etc/mdadm.conf file: # mdadm --examine --scan ARRAY metadata=imsm spares=2 ARRAY /dev/md/0 metadata=1.0 UUID=<some ID> name=selene:0 # cat /etc/mdadm.conf DEVICE partitions ARRAY /dev/md0 level=raid1 UUID=<some ID> ---------------------- <some ID> is in both cases the same -- 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.