<p dir="ltr">your next best bet is ddrescue on the damaged drive. </p>
<p dir="ltr">Sent from my mobile. Please excuse the brevity, spelling, and punctuation. </p>
<div class="gmail_quote">On Mar 13, 2014 2:04 AM, "Dustin Strickland" <<a href="mailto:dustin.h.strickland@gmail.com">dustin.h.strickland@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jesus, I've been short of time lately... I didn't realize that it's<br>
been a whole week since I was able to check up on this. Anyway, I can't<br>
try anything else as it's out of my hands now, but I tried everything I<br>
could think of. Unfortunately, I couldn't recover anything.<br>
<br>
As per Jim's suggestion, I tried swapping out the logic board in the<br>
bad drive, which had no effect. Before and after, it would only read<br>
153MB of data from the drive - I thought it to be a bad head, which I<br>
confirmed by spinning up the drive with the top cover off(mostly for my<br>
amusement; I wouldn't have done it if I wasn't totally sure the drive<br>
was bad).<br>
<br>
Raidextract failed to produce anything useful. When I ran it,<br>
regardless of the settings I used it only produced errors about parity<br>
mismatches. After looking into it a bit more, it seemed like the array<br>
had been running in degraded mode for several months before anyone<br>
noticed a problem, and that my client(a Windows IT admin) had tried to<br>
fix it previously and neglected to inform me of what he had done. This<br>
was the worst-case scenario.<br>
<br>
On Thu, 6 Mar 2014 14:15:36 -0500<br>
dev null zero two <<a href="mailto:dev.null.02@gmail.com">dev.null.02@gmail.com</a>> wrote:<br>
<br>
> Also <a href="http://www.freeraidrecovery.com/" target="_blank">http://www.freeraidrecovery.com/</a> works really well for being<br>
> free. Windows only but you just connect your two good drives, point<br>
> the software at them, it detects the RAID parameters and then lets<br>
> you save a dd image of the resulting reconstructed array that you can<br>
> then mount or access however you want.<br>
><br>
><br>
> On Thu, Mar 6, 2014 at 2:09 PM, Jim Kinney <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>><br>
> wrote:<br>
><br>
> > If all 3 drives are the same make and model, dd the working 2 drives<br>
> > first. Then try replacing the failed drives board with one from a<br>
> > good drive.<br>
> ><br>
> > with 2 drives out of 3 in a raid5, you're still OK data-wise.<br>
> > raidextract may be able to rebuild the data from the 2 drives.<br>
> ><br>
> > I used a tool a zillion years ago that I can't find right now that<br>
> > did exactly this: from a dd image of all the available drives,<br>
> > extract all the file possible to a new location.<br>
> ><br>
> ><br>
> > On Thu, Mar 6, 2014 at 1:29 PM, Dustin Strickland <<br>
> > <a href="mailto:dustin.h.strickland@gmail.com">dustin.h.strickland@gmail.com</a>> wrote:<br>
> ><br>
> >> Sorry, let me give you guys a better idea of the hardware - this<br>
> >> appears to be a custom build. Some Asrock motherboard as far as I<br>
> >> can tell with a VIA chipset and an Athlon XP something... an<br>
> >> unbranded SATA2 RAID card(which doesn't work), and the 3 80GB hard<br>
> >> drives.<br>
> >><br>
> >> Jim,<br>
> >><br>
> >> That's what I was afraid of. Only 2 of the drives still work. I<br>
> >> couldn't get any data off the third drive. Do you think raidextract<br>
> >> might still work in this case?<br>
> >><br>
> >> On Thu, 6 Mar 2014 12:12:53<br>
> >> -0500 Benjie <<a href="mailto:benjie.godfrey@gmail.com">benjie.godfrey@gmail.com</a>> wrote:<br>
> >><br>
> >> > Is this a SATA or a SCSI HBA? Is the HBA a card, or is it built<br>
> >> > into the motherboard? Is it a software raid using the<br>
> >> > mainboard's SATA interfaces? Can you answer those questions?<br>
> >> ><br>
> >> ><br>
> >> > On Thu, Mar 6, 2014 at 11:18 AM, Dustin Strickland <<br>
> >> > <a href="mailto:dustin.h.strickland@gmail.com">dustin.h.strickland@gmail.com</a>> wrote:<br>
> >> ><br>
> >> > > I just want to put this out there: I'm not *very* familiar with<br>
> >> > > RAID, but I get by. I have a unique situation and I'm not sure<br>
> >> > > how to handle it -- suggestions would be appreciated.<br>
> >> > ><br>
> >> > > So, my client has a machine - an *old* machine - that was<br>
> >> > > running an ancient version of Redhat, acting as a Samba<br>
> >> > > server. I'm not too clear on the details of what happened, but<br>
> >> > > the result: the motherboard in the server is apparently bad.<br>
> >> > > So is the RAID card that was installed. Also one of the disks<br>
> >> > > of the three that were installed. The other two work fine.<br>
> >> > > This machine will not boot, I tried everything. We've made the<br>
> >> > > decision to set up another machine to run Samba. Now here's<br>
> >> > > the hitch. The only available machine has only two SATA ports<br>
> >> > > and we still need to grab his old data.<br>
> >> > ><br>
> >> > > Yesterday I used a Live USB stick to dd the data from both of<br>
> >> > > the good drives, one at a time, on to a third. Now, I don't<br>
> >> > > even know if the data is recoverable - after we started<br>
> >> > > copying the second disk, we left it to run overnight so I<br>
> >> > > haven't been able to check it out. If it *is*, how would I go<br>
> >> > > about it? I've never encountered hardware RAID before, either<br>
> >> > > - would this even be possible to fix in software?<br>
> >> > > _______________________________________________ Ale mailing<br>
> >> > > list <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> >> > > <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> >> > > See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> >> > > <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
> >> > ><br>
> >> _______________________________________________<br>
> >> Ale mailing list<br>
> >> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> >> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> >> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> >> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
> >><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > --<br>
> > James P. Kinney III<br>
> ><br>
> > Every time you stop a school, you will have to build a jail. What<br>
> > you gain at one end you lose at the other. It's like feeding a dog<br>
> > on his own tail. It won't fatten the dog.<br>
> > - Speech 11/23/1900 Mark Twain<br>
> ><br>
> ><br>
> > *<a href="http://heretothereideas.blogspot.com/" target="_blank">http://heretothereideas.blogspot.com/</a><br>
> > <<a href="http://heretothereideas.blogspot.com/" target="_blank">http://heretothereideas.blogspot.com/</a>>*<br>
> ><br>
> > _______________________________________________<br>
> > Ale mailing list<br>
> > <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> > <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> > See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> > <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
> ><br>
> ><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>