[Bug-ddrescue] Better alternative switches

[John]

​I have never needed more than a basic invocation of ddrescue to do a
recovery. That's good but it's also bad since I don't know the tool as well
as I would like to.

Generally I have used:
/ddrescue -v /dev/disk1s3  MyDriveRecovery.dmg MyDriveRecovery.log
and I have been able to get most stuff back.

It was suggested I could get stuff off the drive faster if I used the raw
method so I used:

mac:ddrescue1.8
​me​
$ sudo ./ddrescue -v /dev/rdisk2s3  /Volumes/My\ Passport\ Air/
​Data​
.dmg
​Data​
.log



About to copy an undefined number of Bytes from /dev/rdisk2s3 to
/Volumes/My Passport Air/
​Data​
.dmg

    Starting positions: infile = 0 B,  outfile = 0 B

    Copy block size: 128 hard blocks

Hard block size: 512 bytes

Max_retries: 0

Direct: no    Sparse: no    Split: yes    Truncate: no


Press Ctrl-C to interrupt

Initial status (read from logfile)

rescued:    16555 MB,  errsize:    983 GB,  errors:       6

Current status

rescued:    18391 MB,  errsize:    981 GB,  current rate:     4608 B/s

   ipos:    18420 MB,   errors:   28137,    average rate:     5027 B/s

   opos:    18420 MB
​This has been running for almost a week now without much more success. (It
kicked off with an error at 16.1Gb so I restarted it and it's just been
running).

Can anyone suggest a better approach. If I stop ddrescue the drive will
mount again and I can see a list of folders and the files within. I have
been looking for a controller card for the drive and have not been able to
locate one so I am just moving forward but very concerned about data
integrity by plowing forward. Any suggestions?

Thanks,
John