http://bugzilla.novell.com/show_bug.cgi?id=599885 http://bugzilla.novell.com/show_bug.cgi?id=599885#c6 --- Comment #6 from Dan Williams <dan.j.williams@intel.com> 2010-05-07 18:01:14 UTC --- (In reply to comment #3)
At first I changed to the console before yast started anything raid related. mdadm -Esvvv: /dev/sde: Magic : Intel Raid ISM Cfg Sig. Version : 1.2.02 Orig Family : f5301bd5 Family : f5301bd5 Generation : 00143187 UUID : 7d149a87:a33f3f14:9b5655b2:2e1d1490 Checksum : bdd84f90 correct MPB Sectors : 2 Disks : 4 RAID Devices : 1 Disk01 Serial : WD-WMASY2708759 State : active Id : 00040000 Usable Size : 1250259214 (596.17 GiB 640.13 GB) [Raid5]: UUID : 3d4409ed:21143660:bda67464:b6c5a60b RAID Level : 5 Members : 4 This Slot : 1 Array Size : 3750776832 (1788.51 GiB 1920.40 GB) Per Dev Size : 1250259208 (596.17 GiB 640.13 GB) Sector Offset : 0 Num Stripes : 9767648 Chunk Size : 64 KiB Reserved : 0 Migrate State : idle Map State : normal Dirty State : clean Disk00 Serial : WD-WMASY2694410 State : active Id : 00020000 Usable Size : 1250259214 (596.17 GiB 640.13 GB) Disk02 Serial : WD-WMASY6437503 State : active Id : 00010000 Usable Size : 1250259214 (596.17 GiB 640.13 GB) Disk03 Serial : WD-WCASY5619508 State : active Id : 00030000 Usable Size : 1250259214 (596.17 GiB 640.13 GB) /dev/sdc2:
This might be part of the problem. We are picking up Intel metadata on a partition which should never happen. I'll attach a patch to address this. Can you get dmraid out of the picture and see if mdadm can assemble the array? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.