[SATLUG] 1st Q? - RAID5 quit working - Attempting recovery #2

David Labens adlabens at swbell.net
Fri Aug 21 15:27:51 CDT 2009

Freezing the drive?  Funny that should be mentioned.  I JUST NOW finished repairing DSL at a customer's home, and HE suggested that freezing the drive might make it work.  However, he explained that the read would need to be completed by the time the drive thaws out and before the moisture inside condenses.  Considering it's 250 gb, I'm inclined to think that it would thaw faster than it could be fully read.  HOWEVER, I would consider that as an option of last resort.  
I'd never heard of such a thing till today, then from two different sources!  
Freezing causes everything to shrink JUST ENOUGH to let it move freely.  However, I don't think moving components are the problem.  "I don't think." - which may be a problem!

David Labens
San Antonio, TX

--- On Fri, 8/21/09, Herb Cee <hc at lookcee.com> wrote:

From: Herb Cee <hc at lookcee.com>
Subject: Re: [SATLUG] 1st Q? - RAID5 quit working - Attempting recovery #2
To: "The San Antonio Linux User's Group Mailing List" <satlug at satlug.org>
Date: Friday, August 21, 2009, 2:37 PM

Samuel Leon wrote:
> David Labens wrote:
>> Sam,
>> Thank you.  I found this tutorial:
>> http://www.debianadmin.com/recover-data-from-a-dead-hard-drive-using-ddrescue.html 
>> and have done apt-get install ddrescue
>> I'll read more on it this evening, before I try to make it work.
>> Thanks,
>> David Labens
> I found this: http://www.forensicswiki.org/wiki/Ddrescue
> So:
> First you copy as much data as possible, without retrying or splitting sectors:
>     ddrescue --no-split /dev/sdc /dev/newdrive logfile
> Now let it retry previous errors 3 times, using uncached reads:
>     ddrescue --direct --max-retries=3 /dev/sdc /dev/newdrive logfile
> If that fails you can try again but retrimmed, so it tries to reread full sectors:
>     ddrescue --direct --retrim --max-retries=3 /dev/sdc /dev/newdrive logfile
> I don't know what gets written to logfile or where it gets written at (perhaps /root/logfile?) But if it is not too big please let us see it :)
> Also you might try putting the bad harddrive in different positions (ie, upside down, sideways) to see if that helps with getting the data off of it.
> Sam
Sam would freezing the drive maybe help since many have had success with that trick. I dunno, never had to use it
-- _______________________________________________
SATLUG mailing list
SATLUG at satlug.org
http://alamo.satlug.org/mailman/listinfo/satlug to manage/unsubscribe
Powered by Rackspace (www.rackspace.com)

More information about the SATLUG mailing list