Groups > comp.os.linux.hardware > #2660 > unrolled thread

How to force copy retries until finally copied all due to a dying old HDD in Linux?

Started by	Ant <ant@zimage.comANT>
First post	2015-01-04 06:55 -0800
Last post	2015-01-05 14:15 +0100
Articles	8 on this page of 48 — 12 participants

Back to article view | Back to comp.os.linux.hardware

Page 3 of 3 — ← Prev page 1 2 [3]

#2710

From	Ant <ant@zimage.comANT>
Date	2015-01-18 14:04 -0800
Message-ID	<SJ6dnTqxkt9nsCHJnZ2dnUU7-TOdnZ2d@earthlink.com>
In reply to	#2709

On 1/18/2015 6:45 AM, Robert Nichols wrote:

>> 3.5 days it last read. I aborted it. It is not end of the world since
>> I do have
>> backups from other computers and drives. At least I learned how to use
>> ddrescue
>> in case I run into this again the future (use ddrescue to make an
>> image!)! ;)
>>
>> Actually, since I have an image. Does that mean I can still access the
>> data in
>> it even though it is only 30 GB out of 80 GB? I wonder how much can be
>> accessed
>> from it.
>
> Hard to say, but sounds doubtful. You'd need to make another copy of the
> image, run "fsck -y" on that, and then see what can be recovered. You
> could _try_ running /photorec/ on the current image, but between the loss
> of all the file names and the mass of corrupted files and fragments it
> would find, it strikes me a strictly an act of desperation.

Alright and thanks. Just wnated to see what it is like to a pretty bad 
dead drive that was recovered. Learning experiences. :)
-- 
This worker ant will be unemployed after Friday, the 23rd, as of 
1/15/2015 @ 11 AM PST. :(
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2736

From	ebenZEROONE@verizon.net (Hactar)
Date	2015-02-19 22:15 -0500
Message-ID	<dflirb-0ri.ln1@pc.home>
In reply to	#2704

In article <m968gb$ng5$1@dont-email.me>,
William Unruh  <unruh@invalid.ca> wrote:
> On 2015-01-14, Ant <ant@zimage.comANT> wrote:
> > On 1/13/2015 6:39 AM, Robert Nichols wrote:
> >
> >>> Ah. Well, I ended up with a brand new 2 TB WD HDD (partitioned in half
> >>> with EXT4 FS) and my hardware friend replaced the dying HDD in my PC.
> >>> Dying HDD is my
> >>> sdg(5 is the one I want to copy) and the new HDD partition I am making
> >>> an image is in /media/Storage2b/CopiedDyingStorage and 1 TB better be
> >>> enough. I hope
> >>> I am doing this correctly for over a day so far:
> >>>
> >>> # time ddrescue /dev/sdg5 /media/Storage2b/CopiedDyingStorage
> >>> ImageFileLog
> >>>
> >>> GNU ddrescue 1.16
> >>> Press Ctrl-C to interrupt
> >>> Initial status (read from logfile)
> >>> rescued:     8641 MB,  errsize:  29099 MB,  errors:      42
> >>> Current status
> >>> rescued:     8641 MB,  errsize:  29099 MB,  current rate:        0 B/s
> >>> rescued:     8718 MB,  errsize:  71006 MB,  current rate:    16384 B/s
> >>>     ipos:    18350 kB,   errors:      56,    average rate:     1041 B/s
> >>>     opos:    18350 kB,     time since last successful read:       0 s
> >>> Splitting failed blocks...
> 
> I think that the reason it is taking so long is taht your disk is really
> really borked-- ie loads of it is unreadable. It keeps trying a few
> times to reread each sector, and cannot. I think you will need to wave
> goodbye to all of the data on that disk. 
> If the disk were good, it would be reading it at many MB/sec. 

I recovered files from a "dead" HD for my friend.  I forget how big it
was but I used essentially this method.  It was slow reading the source
and there was lots of clicking, but mounting the image and copying from
it ran at normal speeds.

-- 
-eben    QebWenE01R@vTerYizUonI.nOetP    ebmanda.redirectme.net:81
LIBRA:  A big promotion is just around the corner for someone
much more talented than you.  Laughter is the very best medicine,
remember that when your appendix bursts next week.  -- Weird Al

[toc] | [prev] | [next] | [standalone]

#2742

From	Ant <ant@zimage.comANT>
Date	2015-02-20 22:47 -0800
Message-ID	<DIednWdOgJmAt3XJnZ2dnUU7-W2dnZ2d@earthlink.com>
In reply to	#2736

>>>>> Ah. Well, I ended up with a brand new 2 TB WD HDD (partitioned in half
>>>>> with EXT4 FS) and my hardware friend replaced the dying HDD in my PC.
>>>>> Dying HDD is my
>>>>> sdg(5 is the one I want to copy) and the new HDD partition I am making
>>>>> an image is in /media/Storage2b/CopiedDyingStorage and 1 TB better be
>>>>> enough. I hope
>>>>> I am doing this correctly for over a day so far:
>>>>>
>>>>> # time ddrescue /dev/sdg5 /media/Storage2b/CopiedDyingStorage
>>>>> ImageFileLog
>>>>>
>>>>> GNU ddrescue 1.16
>>>>> Press Ctrl-C to interrupt
>>>>> Initial status (read from logfile)
>>>>> rescued:     8641 MB,  errsize:  29099 MB,  errors:      42
>>>>> Current status
>>>>> rescued:     8641 MB,  errsize:  29099 MB,  current rate:        0 B/s
>>>>> rescued:     8718 MB,  errsize:  71006 MB,  current rate:    16384 B/s
>>>>>      ipos:    18350 kB,   errors:      56,    average rate:     1041 B/s
>>>>>      opos:    18350 kB,     time since last successful read:       0 s
>>>>> Splitting failed blocks...
>>
>> I think that the reason it is taking so long is taht your disk is really
>> really borked-- ie loads of it is unreadable. It keeps trying a few
>> times to reread each sector, and cannot. I think you will need to wave
>> goodbye to all of the data on that disk.
>> If the disk were good, it would be reading it at many MB/sec.
>
> I recovered files from a "dead" HD for my friend.  I forget how big it
> was but I used essentially this method.  It was slow reading the source
> and there was lots of clicking, but mounting the image and copying from
> it ran at normal speeds.

I somewhat gave up on it. It was too slow and not moving:

       22499 Jan 17 17:44 ImageFileLog
31987306496 Jan 14 05:03 CopiedDyingStorageImage

3 days of nothing! I still have the "dead" drive so I could retry if I 
wanted to.
-- 
"The ants are my friends, they're blowin' in the wind. The ant, sir, is 
blowin' in the wind." --the misheard lyrics to Bob Dylan's "Blowin' in 
the Wind"
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2705

From	Robert Nichols <SEE_SIGNATURE@localhost.localdomain.invalid>
Date	2015-01-14 23:05 -0600
Message-ID	<m97hqq$ii2$1@omega-3a.local>
In reply to	#2703

On 01/14/2015 10:33 AM, Ant wrote:
> Yeah, I am glad it is only a 80 GB HDD. I can't imagine people trying to recover
> from very big drives!! Too bad we can't recover some areas and not the whole
> drive which I wanted to do. :(

You have some control over it, but you have to have some idea of what's
where. <http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html#Algorithm>

-- 
Bob Nichols         AT comcast.net I am "RNichols42"

[toc] | [prev] | [next] | [standalone]

#2706

From	Ant <ant@zimage.comANT>
Date	2015-01-15 00:43 -0800
Message-ID	<rJmdnYZD6rxe4CrJnZ2dnUU7-I2dnZ2d@earthlink.com>
In reply to	#2705

On 1/14/2015 9:05 PM, Robert Nichols wrote:

>> Yeah, I am glad it is only a 80 GB HDD. I can't imagine people trying
>> to recover
>> from very big drives!! Too bad we can't recover some areas and not the
>> whole
>> drive which I wanted to do. :(
>
> You have some control over it, but you have to have some idea of what's
> where.
> <http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html#Algorithm>

Ah, interesting. Oh well, I'll let it keep going until the disk is 
completely dead or ddrescue is finally done. So far, it 
(finish/complete)d 30 GB out of 80.
-- 
"Above ground I shall be food for kites; below I shall be food for 
mole-crickets and ants. Why rob one to feed the other?" --Juang-zu (4th 
Century B.C.)
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )         If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[toc] | [prev] | [next] | [standalone]

#2690

From	Marc Haber <mh+usenetspam1118@zugschl.us>
Date	2015-01-05 14:13 +0100
Message-ID	<m8e2lg$kg4$1@news1.tnib.de>
In reply to	#2684

Ant <ant@zimage.comANT> wrote:
>On 1/4/2015 2:12 PM, Rich wrote:
>
>>> Even with ddrescue? I thought it retries until it finally copies.
>>
>> If the disk sector is corrupted, no amount of retries will make it
>> "finally copy".  It is simply gone.  Retries are only useful when there
>> is an intermittent issue that occurs sometimes, but not other times.
>
>Ah, so http://www.kalysto.org/utilities/dd_rhelp/index.en.html is 
>useless in this scenario. Interesting. Thanks.

It might help you to get the undestroyed data off the drive before it
will eventually fail completely. Destroyed data is, well, destroyed.
You might get back parts of them, but don't expect them to be remotely
intact.

Greetings
Marc
-- 
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber         |   " Questions are the         | Mailadresse im Header
Mannheim, Germany  |     Beginning of Wisdom "     | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

[toc] | [prev] | [next] | [standalone]

#2672

From	andrew.williams@t-online.de
Date	2015-01-04 10:28 -0800
Message-ID	<3af3edff-b933-4978-b792-647dabfbfdd3@googlegroups.com>
In reply to	#2660

The way I do backups, even on a running system is:

cd source
tar cf - . | (cd /target ; tar xf - )

Doing that as root preserves all permissions, assuming the filesystems are vaguely compatible.
I have never done this on a dying disk, but I have done this on a "dynamic" partition where some of the files on the source were being deleted during the copy by another process.

[toc] | [prev] | [next] | [standalone]

#2691

From	Marc Haber <mh+usenetspam1118@zugschl.us>
Date	2015-01-05 14:15 +0100
Message-ID	<m8e2ol$knv$1@news1.tnib.de>
In reply to	#2672

andrew.williams@t-online.de wrote:
>The way I do backups, even on a running system is:
>
>cd source
>tar cf - . | (cd /target ; tar xf - )
>
>Doing that as root preserves all permissions, assuming the filesystems are vaguely compatible.
>I have never done this on a dying disk

Obviously, because it won't work. It's likely to abort on the first
defective file.

Greetings
Marc
-- 
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber         |   " Questions are the         | Mailadresse im Header
Mannheim, Germany  |     Beginning of Wisdom "     | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

csiph-web

How to force copy retries until finally copied all due to a dying old HDD in Linux?

Contents

#2710

#2736

#2742

#2705

#2706

#2690

#2672

#2691