Perhaps related to Robert's comment, but the ddrescue man page says:

The format for running ddrescue is:
     ddrescue [options] infile outfile [mapfile]

so your specifying --force at the end rather than at the beginning as indicated (quite aside from the redundancy) may be throwing off the command line parser's interpretation of what is supposed to be infile, outfile and mapfile. You'd think there'd be an error message in that case, by why don't you try again with just
        ddrescue -f /dev/sda /dev/sdb logfile
just to eliminate that possibility (and the redundant option --force)?


On 2021-09-29 11:04 AM, Robert Trevellyan wrote:
Is there space on the device where the map file 'logfile' is to be written?

Is there a reason you're specifying '-f' *and* '--force' (same thing).

Robert Trevellyan

On Wed, Sep 29, 2021 at 9:53 AM a p <> wrote:

Is this a good place to ask a question regarding a bug regarding ddrescue?

IF so my output from running ddrescue to clone a HDD
(ddrescue -f /dev/sda /dev/sdb logfile --force) errors out and says"no
space of device"..

The corrupt drive (320GB) hdd is attached to a desktop tower and cloning to
a 1TB hdd attached to the desktop (both directly on the mb).

Any help would be appreciated.

Thank you.

All the best

Reply via email to