RE: recovering from a controller failure
From: Leslie Rhorer <hidden>
Date: 2010-05-30 03:33:34
On Sun, May 30, 2010 at 09:50:26AM +1200, Richard wrote:quoted
How about adding entries to your mdadm.conf file containing the UUID of /dev/md0, eg: ARRAY /dev/md8 level=raid6 num-devices=16 UUID=38a06a50:ce3fc204:728edfb7:4f4cdd43 note this should be all one line.I'll be happy to do that.quoted
mdadm -D /dev/md0 should get you the UUID.root@00144ff2a334:/# mdadm -D /dev/md0 mdadm: md device /dev/md0 does not appear to be active. So...how do I get the UUIDs? I tried blkid and got this. http://lairds.us/temp/ucmeng_md/uuids Those UUIDs are far from unique.
After all your drives are visible, of course: `mdadm --examine /dev/sd* /dev/hd* > <filename>` `more <filename>` Make note of the array UUID for each drive. When done, `mdadm --assemble --assume-clean /dev/mdX /dev/<drive0> /dev/<drive1> /dev/<drive2> ...etc` where <drive0>, <drive1>, etc are all members of the same array UUID. Mount the file system, and fsck it. Once everything is verified good, `echo repair > /sys/block/mdX/md/sync_action` `mdadm --examine --scan >> /etc/mdadm/mdadm.conf`