<br><br><div><span class="gmail_quote">On 9/17/07, <b class="gmail_sendername">John Drescher</b> <<a href="mailto:drescherjm@gmail.com">drescherjm@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;">
> Because /dev/md0 no loger exists, any attempts I have made to mount or<br>> diagnose the status of the raid5 array have been futile. Does anyone with<br>> software raid experience have any suggestions on how I could go about
<br>> recovering the data on the array? What would cause mdadm to segfault?<br>><br>I have never seen mdadm segfault. I assume it is segfaulting when you<br>are trying to diagnose the problem as well. Have you tried running it
<br>from a livecd?<br><br>John<br><br></blockquote></div>
Unfortunately, I don't get very far trying to diagnose with mdadm - it simply complains that /dev/md0 does not exist whether booted from the live CD or not...<br><br>fdisk -l says that the raid drives are "Linux raid autodetect"; I'm assuming that the md error message I'm seeing on boot has somehting to do with this "autodetect" feature failing...
<br>