https://bugzilla.novell.com/show_bug.cgi?id=784171 https://bugzilla.novell.com/show_bug.cgi?id=784171#c0 Summary: openSUSE:12.2:Update/patchinfo.949: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other URL: http://forums.opensuse.org/english/get-technical-help- here/tumbleweed/479250-tumbleweed-mdadm-upgrade-now-wo nt-boot.html OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: dmueller@suse.com ReportedBy: valentin@isim.ro QAContact: opensuse-communityscreening@forge.provo.novell.com CC: nfbrown@suse.com Found By: Community User Blocker: --- Seems that the latest mdadm update related to better suspend does make systems with RAID unbootable, see http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/479250... My case: / on RAID10 (fake RAID from intel with IMSM), boot from / After applying the update, the system can not boot, the error messages are related to: mdadm: bad uuid: UUID=<UUID>\nARRAY mdadm: only give one device per ARRAY line /dev/md/imsm0 and /dev/md126 Than the booting hangs while trying to resume from the / partition (in my case md126p2). This is rather a drawback after fixing https://bugzilla.novell.com/show_bug.cgi?id=752107 and the one similar to it. The update: 3.2.5-3.13.1|x86_64||repo-12.2-update|624c659a413a3830b3fd5dad53cd71e5d077e27a979d78fac3799b06139a4067 -- 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.