Groups > comp.os.linux.misc > #13209 > 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:13 +0100
Articles	15 on this page of 55 — 11 participants

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

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

#13407

From	Ant <ant@zimage.comANT>
Date	2015-01-11 10:20 -0800
Message-ID	<HeudndgXhPt6Iy_JnZ2dnUU7-V-dnZ2d@earthlink.com>
In reply to	#13406

On 1/11/2015 10:14 AM, Ant wrote:
> ...
>> FAT32 can't hold a 74GB file. The maximum file size for FAT32 is 4GB
>> minus 1 byte. /dev/sdg1 *might* be large enough for the image if you
>> unmounted it and went straight to the raw partition, but that's going to
>> destroy the current contents of /dev/sdg1. I can't tell from the above
>> info. Compare the two sizes when you run "grep -E 'sda5|sdg1'
>> /proc/partitions" or the sizes you see when you run "fdisk -lu /dev/sda
>> /dev/sdg".
>
> $ df | grep -E 'sda5|sdg1'
> /dev/sdg1                                               76921888 184068
> 72830340   1% /media/storage2
> /dev/sda5                                               76637568
> 31256040  41488692  43% /media/_others
>
>
> # fdisk -lu /dev/sda /dev/sdg
>
> Disk /dev/sda: 80.0 GB, 80026361856 bytes
> 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x6a3a6846
>
>     Device Boot      Start         End      Blocks   Id  System
> /dev/sda2          578340   156296384    77859022+   5  Extended
> /dev/sda5          581632   156295167    77856768   83  Linux
>
> Disk /dev/sdg: 80.0 GB, 80026361856 bytes
> 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x1c7391d2
>
>     Device Boot      Start         End      Blocks   Id  System
> /dev/sdg1            2048   156301311    78149632   83  Linux
>
>
> As for ummounted sdg1, I think I did that when I tried to copy sda5
> partition into it (was an ext4, but turned into ext3), but not as an
> image. It failed as shown in
> http://pastie.org/pastes/9813433/text?key=y5rqiou5fsukcgvngnamw ... I'll
> try again as an image file this time and follow-up. :)

It failed quickly when I tried it:

# time ddrescue -r -1 /dev/sda5 /dev/sdg1/CopiedDyingSDA5 ImageFileLog
ddrescue: Can't open output file: Not a directory

real    0m0.002s
user    0m0.000s
sys     0m0.000s


# ls -all /dev/sdg1
brw-rw---T 1 root floppy 8, 97 Jan 11 10:10 /dev/sdg1


$ df
Filesystem                                             1K-blocks 
Used Available Use% Mounted on
rootfs                                                    960504 
733700    178012  81% /
udev                                                       10240 
0     10240   0% /dev
tmpfs                                                     206056 
7484    198572   4% /run
/dev/disk/by-uuid/242d81f2-8a0d-48e1-a144-22ab4d2b9407    960504 
733700    178012  81% /
tmpfs                                                       5120 
4      5116   1% /run/lock
tmpfs                                                    1193200 
80   1193120   1% /run/shm
/dev/sdb9                                               50013916 
16660140  30813184  36% /home
/dev/sdb5                                                 960504 
24068    887644   3% /tmp
/dev/sdb8                                               49982172 
6445300  40997864  14% /usr
/dev/sdb6                                                4804736 
1821408   2739260  40% /var


Both source internal drive and external USB2 destination drives were 
unmounted. Did I do this wrong? :(
-- 
    /\___/\ +1 Year 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]

#13409

From	Robert Nichols <SEE_SIGNATURE@localhost.localdomain.invalid>
Date	2015-01-11 19:23 -0600
Message-ID	<m8v7mi$ff4$1@omega-3a.local>
In reply to	#13407

On 01/11/2015 12:20 PM, Ant wrote:
> On 1/11/2015 10:14 AM, Ant wrote:
>>     Device Boot      Start         End      Blocks   Id  System
>> /dev/sda2          578340   156296384    77859022+   5  Extended
>> /dev/sda5          581632   156295167    77856768   83  Linux
>>
>> Disk /dev/sdg: 80.0 GB, 80026361856 bytes
>> 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
>> Units = sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x1c7391d2
>>
>>     Device Boot      Start         End      Blocks   Id  System
>> /dev/sdg1            2048   156301311    78149632   83  Linux
>>
>>
>> As for ummounted sdg1, I think I did that when I tried to copy sda5
>> partition into it (was an ext4, but turned into ext3), but not as an
>> image. It failed as shown in
>> http://pastie.org/pastes/9813433/text?key=y5rqiou5fsukcgvngnamw ... I'll
>> try again as an image file this time and follow-up. :)
>
> It failed quickly when I tried it:
>
> # time ddrescue -r -1 /dev/sda5 /dev/sdg1/CopiedDyingSDA5 ImageFileLog
> ddrescue: Can't open output file: Not a directory

You want just

     time ddrescue -r -1 /dev/sda5 /dev/sdg1 ImageFileLog

You don't get to add a name. When it's done, sdg1 will be a mountable
filesystem identical to however much of sda5 could be recovered. Even the
filesystem label (if any) and the UUID will be the same, so you might
want to use /tune2fs/ to change those afterward. There should be enough
space, as sdg1 is slightly larger than sda5.

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

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

#13416

From	Ant <ant@zimage.comANT>
Date	2015-01-12 22:44 -0800
Message-ID	<kcadnYBoDOVYIynJnZ2dnUU7-bGdnZ2d@earthlink.com>
In reply to	#13409

On 1/11/2015 5:23 PM, Robert Nichols wrote:
...
>> It failed quickly when I tried it:
>>
>> # time ddrescue -r -1 /dev/sda5 /dev/sdg1/CopiedDyingSDA5 ImageFileLog
>> ddrescue: Can't open output file: Not a directory
>
> You want just
>
>      time ddrescue -r -1 /dev/sda5 /dev/sdg1 ImageFileLog
>
> You don't get to add a name. When it's done, sdg1 will be a mountable
> filesystem identical to however much of sda5 could be recovered. Even the
> filesystem label (if any) and the UUID will be the same, so you might
> want to use /tune2fs/ to change those afterward. There should be enough
> space, as sdg1 is slightly larger than sda5.

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 saw "-rwxrwxrwx 1 root root 8.2G Jan 12 22:34 CopiedDyingStorage". It 
is still going.

$ df
Filesystem                                             1K-blocks 
Used Available Use% Mounted on
rootfs                                                    960504 
733704    178008  81% /
udev                                                       10240 
  0     10240   0% /dev
tmpfs                                                     206056 
5936    200120   3% /run
/dev/disk/by-uuid/242d81f2-8a0d-48e1-a144-22ab4d2b9407    960504 
733704    178008  81% /
tmpfs                                                       5120 
  8      5112   1% /run/lock
tmpfs                                                    1193200 
80   1193120   1% /run/shm
/dev/sda9                                               50013916 
2123204  45350120   5% /home
/dev/sda5                                                 960504 
24568    887144   3% /tmp
/dev/sda8                                               49982172 
6442520  41000644  14% /usr
/dev/sda6                                                4804736 
1801296   2759372  40% /var
/dev/sdb2                                              961428808 
23414852 889176120   3% /media/Storage2b
/dev/sdb1                                              961428808 
351230000 561360972  39% /media/Storage2a

I am surprised the dying HDD still works ever since it went crazy. :P
-- 
"Is it for pleasure you were made? Not for doing, and for action? Look 
at the plants, the sparrows, the ants, spiders, bees, all doing their 
business, helping to weld the order of the world. And will you refuse 
man's part? And not run the way of nature's ordering?" --Marcus Aurelius
    /\___/\         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]

#13417

From	Robert Nichols <SEE_SIGNATURE@localhost.localdomain.invalid>
Date	2015-01-13 08:39 -0600
Message-ID	<m93ani$vp6$1@omega-3a.local>
In reply to	#13416

On 01/13/2015 12:44 AM, Ant 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 saw "-rwxrwxrwx 1 root root 8.2G Jan 12 22:34 CopiedDyingStorage". It is still going.
>
> $ df
> Filesystem                                             1K-blocks Used Available Use% Mounted on
> rootfs                                                    960504 733704    178008  81% /
> udev                                                       10240  0     10240   0% /dev
> tmpfs                                                     206056 5936    200120   3% /run
> /dev/disk/by-uuid/242d81f2-8a0d-48e1-a144-22ab4d2b9407    960504 733704    178008  81% /
> tmpfs                                                       5120  8      5112   1% /run/lock
> tmpfs                                                    1193200 80   1193120   1% /run/shm
> /dev/sda9                                               50013916 2123204  45350120   5% /home
> /dev/sda5                                                 960504 24568    887144   3% /tmp
> /dev/sda8                                               49982172 6442520  41000644  14% /usr
> /dev/sda6                                                4804736 1801296   2759372  40% /var
> /dev/sdb2                                              961428808 23414852 889176120   3% /media/Storage2b
> /dev/sdb1                                              961428808 351230000 561360972  39% /media/Storage2a
>
> I am surprised the dying HDD still works ever since it went crazy. :P

I certainly hope it gets past the bad section and speeds up. At 16384 B/s
it's going to take about 55 days to finish.

Yes, 1TB is more than enough. You should need about 80GB.

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

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

#13425

From	Ant <ant@zimage.comANT>
Date	2015-01-14 08:33 -0800
Message-ID	<cvmdnYJ2QMfvByvJnZ2dnUU7-VOdnZ2d@earthlink.com>
In reply to	#13417

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 saw "-rwxrwxrwx 1 root root 8.2G Jan 12 22:34 CopiedDyingStorage".
>> It is still going.
>>
>> $ df
>> Filesystem                                             1K-blocks Used
>> Available Use% Mounted on
>> rootfs                                                    960504
>> 733704    178008  81% /
>> udev                                                       10240
>> 0     10240   0% /dev
>> tmpfs                                                     206056
>> 5936    200120   3% /run
>> /dev/disk/by-uuid/242d81f2-8a0d-48e1-a144-22ab4d2b9407    960504
>> 733704    178008  81% /
>> tmpfs                                                       5120
>> 8      5112   1% /run/lock
>> tmpfs                                                    1193200 80
>> 1193120   1% /run/shm
>> /dev/sda9                                               50013916
>> 2123204  45350120   5% /home
>> /dev/sda5                                                 960504
>> 24568    887144   3% /tmp
>> /dev/sda8                                               49982172
>> 6442520  41000644  14% /usr
>> /dev/sda6                                                4804736
>> 1801296   2759372  40% /var
>> /dev/sdb2                                              961428808
>> 23414852 889176120   3% /media/Storage2b
>> /dev/sdb1                                              961428808
>> 351230000 561360972  39% /media/Storage2a
>>
>> I am surprised the dying HDD still works ever since it went crazy. :P
>
> I certainly hope it gets past the bad section and speeds up. At 16384 B/s
> it's going to take about 55 days to finish.
>
> Yes, 1TB is more than enough. You should need about 80GB.

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. :(

# 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
rescued:     8719 MB,  errsize:  71006 MB,  current rate:        0 B/s
rescued:     8719 MB,  errsize:  71006 MB,  current rate:        0 B/s
rescued:     8720 MB,  errsize:  71004 MB,  current rate:        0 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    32157 MB,   errors:     159,    average rate:     120 kB/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    32159 MB,   errors:     159,    average rate:     118 kB/s
    opos:    32159 MB,     time since last successful read:     3.4 h
Splitting failed blocks...


pydemsg:
...
[2015-01-14 08:24:41] sd 14:0:0:0: [sdg]  Sense Key : Not Ready [current]
[2015-01-14 08:24:41] sd 14:0:0:0: [sdg]  Add. Sense: Medium not present
[2015-01-14 08:24:41] sd 14:0:0:0: [sdg] CDB: Read(10): 28 00 03 c7 4e 
c8 00 00 08 00
[2015-01-14 08:24:41] end_request: I/O error, dev sdg, sector 63393480
[2015-01-14 08:24:41] Buffer I/O error on device sdg5, logical block 7851481
[2015-01-14 08:25:12] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:25:43] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:26:13] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:26:44] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:27:15] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:27:47] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:27:47] sd 14:0:0:0: [sdg] Device not ready
[2015-01-14 08:27:47] sd 14:0:0:0: [sdg]  Result: hostbyte=DID_ABORT 
driverbyte=DRIVER_SENSE
[2015-01-14 08:27:47] sd 14:0:0:0: [sdg]  Sense Key : Not Ready [current]
[2015-01-14 08:27:47] sd 14:0:0:0: [sdg]  Add. Sense: Medium not present
[2015-01-14 08:27:47] sd 14:0:0:0: [sdg] CDB: Read(10): 28 00 03 c7 4e 
c8 00 00 08 00
[2015-01-14 08:27:47] end_request: I/O error, dev sdg, sector 63393480
[2015-01-14 08:27:47] Buffer I/O error on device sdg5, logical block 7851481
[2015-01-14 08:28:18] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:28:48] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:29:19] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:29:50] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:30:21] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:30:53] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
[2015-01-14 08:30:53] sd 14:0:0:0: [sdg] Device not ready
[2015-01-14 08:30:53] sd 14:0:0:0: [sdg]  Result: hostbyte=DID_ABORT 
driverbyte=DRIVER_SENSE
[2015-01-14 08:30:53] sd 14:0:0:0: [sdg]  Sense Key : Not Ready [current]
[2015-01-14 08:30:53] sd 14:0:0:0: [sdg]  Add. Sense: Medium not present
[2015-01-14 08:30:53] sd 14:0:0:0: [sdg] CDB: Read(10): 28 00 03 c7 4e 
c8 00 00 08 00
[2015-01-14 08:30:53] end_request: I/O error, dev sdg, sector 63393480
[2015-01-14 08:30:53] Buffer I/O error on device sdg5, logical block 7851481
[2015-01-14 08:31:23] usb 2-2: reset high-speed USB device number 6 
using ehci_hcd
...
-- 
"Ants can attack with a grain of rice." --a Malagasy Proverb
    /\___/\         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]

#13426

From	William Unruh <unruh@invalid.ca>
Date	2015-01-14 17:20 +0000
Message-ID	<m968gb$ng5$1@dont-email.me>
In reply to	#13425

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.

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

#13441

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

On 1/14/2015 9:20 AM, William Unruh 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.

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 
GB. This would be a good practice for me anyways. Either way, I need to 
destroy this old HDD. ;)
-- 
"Ants can lift up to 50 times their own weight. And your monitor is 
missing. Time to bring out the bugspray." --BBspot's Geek Horoscopes 
(2/28/2003)
    /\___/\         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]

#13456

From	Ant <ant@zimage.comANT>
Date	2015-01-17 17:59 -0800
Message-ID	<4r2dnZSkraQHjibJnZ2dnUU7-WWdnZ2d@earthlink.com>
In reply to	#13426

On 1/15/2015 12:46 AM, Ant 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.
 >
 > 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
 > GB. This would be a good practice for me anyways. Either way, I need to
 > destroy this old HDD. ;)

OK, I think it is officially dead:

# 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
rescued:     8719 MB,  errsize:  71006 MB,  current rate:        0 B/s
rescued:     8719 MB,  errsize:  71006 MB,  current rate:        0 B/s
rescued:     8720 MB,  errsize:  71004 MB,  current rate:        0 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    32157 MB,   errors:     159,    average rate:     120 kB/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    34550 MB,   errors:     159,    average rate:    90752 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    35348 MB,   errors:     159,    average rate:    82342 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    35348 MB,   errors:     159,    average rate:    82288 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    38008 MB,   errors:     159,    average rate:    47700 B/s
rescued:    31944 MB,  errsize:  47780 MB,  current rate:        0 B/s
    ipos:    38008 MB,   errors:     159,    average rate:    47682 B/s
    opos:    38008 MB,     time since last successful read:     3.5 d
Splitting failed blocks...
Interrupted by user

real    8145m19.830s
user    0m35.534s
sys     4m24.917s

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.
-- 
"Your parents were killed by ants?" --Idle Hands movie
    /\___/\         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]

#13457

From	Robert Nichols <SEE_SIGNATURE@localhost.localdomain.invalid>
Date	2015-01-18 08:45 -0600
Message-ID	<m9ggtl$ofj$1@omega-3a.local>
In reply to	#13456

On 01/17/2015 07:59 PM, Ant 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.

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

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

#13459

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

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]

#13706

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

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]

#13714

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

>>>>> 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]

#13438

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	#13425

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]

#13440

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

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]

#13261

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	#13239

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] | [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

#13407

#13409

#13416

#13417

#13425

#13426

#13441

#13456

#13457

#13459

#13706

#13714

#13438

#13440

#13261