Re: [Bug-ddrescue] ddrescue input/output error (Xaeonios)

[Seth Baker]

Sounds like the drive disconnects from the system after it repetitive failed reads when it hits a certain area of the drive. Make sure you have the log file stored in place it won't disappear when you reboot and then power cycle the system and try again with the reverse copy command -R Also make sure to reuse the previous log file. I've had some success freezing drives, but I only do that if I don't have success with a room temperature recover.

--- On Tue, 6/11/13, address@hidden <address@hidden> wrote:

From: address@hidden <address@hidden>
Subject: Bug-ddrescue Digest, Vol 89, Issue 5
To: address@hidden
Date: Tuesday, June 11, 2013, 10:00 AM

Send Bug-ddrescue mailing list submissions to
    address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.gnu.org/mailman/listinfo/bug-ddrescue
or, via email, send a message with subject or body 'help' to
    address@hidden

You can reach the person managing the list at
    address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bug-ddrescue digest..."


Today's Topics:

   1.  ddrescue input/output error (Xaeonios)


----------------------------------------------------------------------

Message: 1
Date: Mon, 10 Jun 2013 16:25:34 -0700 (PDT)
From: Xaeonios <address@hidden>
To: address@hidden
Subject: [Bug-ddrescue]  ddrescue input/output error
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii


So I have a failing 500gb seagate drive.  SMART is reporting bad, and its
time to get the files off.  Nothing SUPER important, but things I wouldnt
rather not have to hunt down and find again.

I try to copy it through windows, it freezes up on a bunch of different
files, no luck.

So I get into ubuntu remix with ddrescue built in, follow the instructions
and start the backup.

500gb seagate > 1tb WD

At some point in the copying, it errors out with the input/output error and
just stops.  I ran the command again (not at my computer at home, so I cant
find the exact command that I used), and it picks up where it left off - but
then eventually errors out again.  I assume this is because the drive is
just taking a massive dump and cant handle being connected.

Is there some command arguement that I can put in that will allow it to just
KEEP trying or ignore it and move on?  Ive looked around but nothing seems
to be pointing in that direction.

If you dont feel like spoonfeeding me info, find me a website that has how
to fix the error and link me - that way I can read and learn.  I dont like
just having people TELL me answer unless I cant find them.

Thanks to all!  Heres to a successful recovery!
--
View this message in context: http://old.nabble.com/ddrescue-input-output-error-tp35610796p35610796.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.




------------------------------

_______________________________________________
Bug-ddrescue mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-ddrescue


End of Bug-ddrescue Digest, Vol 89, Issue 5
*******************************************