Thank you for the correction:) Sorry about my misunderstanding/giving wrong advice, which was just from old faulty memory anyway.
On 9/6/16, Antonio Diaz Diaz <anto...@gnu.org> wrote: > Zeniff Martineau wrote: >> "The format for running ddrescue is: >> ddrescue [options] infile outfile [mapfile]" > > This is true, but ddrescue uses Arg_parser and allows the options to be > placed anywhere in the command line: > > http://www.nongnu.org/arg-parser/manual/arg_parser_manual.html#Argument-syntax > > >> Otherwise, I think it's taking "/media/(user)/recoverylogfile.txt" as >> the outfile name and "--force" as the log/mapfile name (just my >> guess). > > There is no way for ddrescue to take "--force" as the mapfile unless you > precede it with "--" or type it as "./--force". > > >> Maybe ddrescue could do a command format check before running (it does >> already show "while" it's running), or maybe output what it thinks are >> the options used were even on an error like that? > > Ddrescue checks the command line before running it. Maybe you mean "--ask"? > > --ask > Ask for user confirmation before starting the copy. If the first > letter of the answer is 'y', ddrescue starts copying. Else it exits > with status 1. > If they can be obtained, ddrescue shows the model and serial number > of the input and output devices. Else it shows the size in bytes of > the corresponding file or device. > > > AFAICT, this problem is just a lack of read permission on /dev/sdb3. > > > Best reagrds, > Antonio. > > _______________________________________________ > Bug-ddrescue mailing list > Bug-ddrescue@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-ddrescue > _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org https://lists.gnu.org/mailman/listinfo/bug-ddrescue