Never mind, user error, more coffee. Thanks for all that you do. On Mon, Mar 19, 2018 at 8:44 PM, Chris Combs <cco...@gmail.com> wrote:
> Greetings, > > Is it possible that ddrescue 1.22 could be unlinking the input file if the > user tries to output it to a block device? > > my steps--Ubuntu Bionic Beaver running ddrescue from gddrescue package: > > [ successfully captures img from /dev/sdd to sdd.img using ddrescue ] > [ swaps in new sd card to copy image onto ] > > root@pripyat:/media/combs ddrescue sdd.img /dev/sdd > ddrescue: Output file exists and is not a regular file. > ddrescue: Use '--force' if you really want to overwrite it, but be > aware that all existing data in the output file will be lost. > Try 'ddrescue --help' for more information. > root@pripyat:/media/combs# ddrescue sdd.img /dev/sdd --force > ddrescue: Can't open input file: No such file or directory > root@pripyat:/media/combs# ls -l sdd.img > ls: cannot access 'sdd.img': No such file or directory > > reasonably reliable root storage device, stable power supply, low quantum > fluctuations, good moon phase, etc. > > Thanks, > Chris > > -- > Chris Combs > Washington, D.C. > http://chriscombs.net > -- Chris Combs Washington, D.C. http://chriscombs.net _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org https://lists.gnu.org/mailman/listinfo/bug-ddrescue