<br><br><div><span class="gmail_quote">On 9/21/07, <b class="gmail_sendername">Steve MacLaren</b> <<a href="mailto:scram69@gmail.com">scram69@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span class="q"><br></span><br>But it looks like I will just have to ignore the obvious contradictions and forge ahead trying to mount and access a 3-drive array by messing with /sys/block/md0/md/array_state, then wiping and re-adding the fourth drive...
<br>
</blockquote></div><br>Finally, some good news. Before I went ahead picking 3 disks at random and assembling, I re-read through all of the posts on this thread. The one that caught my eye was in f-myth's PPS:<br>"for each drive, try dd if=/dev/sdaN of=/dev/null bs=1M count=1000 and see if you can read the first gig of the device"
<br>I hadn't yet tried that, so I gave it a try. Sure enough, /dev/sdd1 cause a reboot when I tried the read. Not being hardware-savvy enough to know which of my physical drives was _actually_ /dev/sdd, I ran through a process of elimination, removing power to one drive at a time until I could successfully read from the three remaining drives.
<br>Identifying the bad drive, I yanked it, replaced it with a brand new spare I had fortuitously purchased some months ago, and restarted.<br>Upon restart, in dmesg, mdadm gave the same complaints about "dirty" drives and the array status remained inactive. But I tried
<br>mdadm -S /dev/md0<br>mdadm -Af /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1<br>"mdadm: /dev/md0 has been started with 3 drives (out of 4)." - hey, that looks good!<br><br>So, next, <br>sudo mdadm --detail /dev/md0
<br>"...<br> State : clean, degraded"<br><br>I don't feel so dirty anymore...<br><br>Pushing my luck,<br>sudo mount -t xfs /dev/md0 /var/lib/mythtv<br>and all of my data was back, seemingly intact!<br><br>So I did an fdisk on the new disk, formatting it as "linux raid autodetect", then:
<br>steve@mediaserver:~$ sudo umount /dev/md0<br>steve@mediaserver:~$ sudo mdadm -a /dev/md0 /dev/sdd1mdadm: added /dev/sdd1<br>steve@mediaserver:~$ sudo mdadm --detail /dev/md0<br>/dev/md0:<br> Version : 00.90.03<br>
Creation Time : Mon May 7 21:31:55 2007<br> Raid Level : raid5<br> Array Size : 1465151616 (1397.28 GiB 1500.32 GB)<br> Device Size : 488383872 (465.76 GiB 500.11 GB)<br> Raid Devices : 4<br> Total Devices : 4
<br>Preferred Minor : 0<br> Persistence : Superblock is persistent<br><br> Update Time : Fri Sep 21 23:24:58 2007<br> State : clean, degraded, recovering<br> Active Devices : 3<br>Working Devices : 4<br> Failed Devices : 0
<br> Spare Devices : 1<br><br> Layout : left-symmetric<br> Chunk Size : 128K<br><br> Rebuild Status : 0% complete<br><br> UUID : bc7a4d90:bd286a91:c109596b:d7e29b7e (local to host mediaserver)<br> Events :
0.174<br><br> Number Major Minor RaidDevice State<br> 0 8 1 0 active sync /dev/sda1<br> 1 8 17 1 active sync /dev/sdb1<br> 2 8 33 2 active sync /dev/sdc1
<br> 4 8 49 3 spare rebuilding /dev/sdd1<br><br>Success! Thanks to everyone who helped me through this special hardware hell nightmare!<br>Now I can finally get back to troubleshooting my "ivtv driver has stopped responding" errors...
<br><br>