Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Some rescue help please

Help
boonie
2012-08-27
2012-09-10
  • boonie
    boonie
    2012-08-27

    I have a 250 gig drive that has errors on it. I used the rescue option of G4L
    to copy the drive to a good one. This is the first time I've used the software
    so I'm not sure how long it's supposed to take. The step it's currently on is
    "Splitting Failed Blocks." The "time from last successful read" is "2.3d" It
    says that it has rescued 249941MB. Since I"m not familiar with the program I'm
    not sure if the copy has failed or if I should keep waiting it out. Any
    suggestions?

     
  • Have not done many rescues using the ddrescue, but it would depend on how many
    errors and were they are located on the drive. A couple years ago, I had a co-
    worker with a failing drive, and ran spinrite on it to repair and it took 3
    full days.

    What OS is on the disks. Sometimes ntfsclone option can backup the data if it
    is not in used files. Also, the fsarchiver is a file level backup, but don't
    know how it handles hard errors in files.

     
  • boonie
    boonie
    2012-08-28

    Thanks for the reply. According to the info the # of errors were 1230 with a
    total size of 118MB. The average rate fluctuates so it looks like it is doing
    something but it has been running for almost a week straight. Also, if you
    know, what do the fields "ipos" and "opos" mean?