I'm having a hard time finding others with the same error, and I'm trying to figure out the best path forward.
I have a hard drive that was unusably slow, and then stopped booting. The clonezilla clone failed, and I started a ddrescue, using the gnu rescue tool included with a clonezilla live cd. It is going unbelievably slow averaging about 400 kBps for a 2 TB drive, so I'm estimating almost 4 months! at this point. My last backup was sadly about 2 years ago, and there are a lot of pictures I'd like to get off of it. The surprising part is that its rescued about 50 GB, with no errors so far, even though its taken 3 days. I have a few questions on the best path forward, and why it would take so long but also not have any errors.
Is the drive just taking forever to succesfully read, but never actually failing, slowing down the copy time? Is the hard drive itself fine, but something like the control board the problem?
I'm very worried about where the logfile is likely going. I can't depend on my computer staying steady, and the command not erroring for four months. If I'm talking at all about keeping it running for even weeks, I'd like to get that logfile onto a flash drive. I originally thought it was going onto the new larger hard drive, but now I realize its likely on the RAM drive clonezilla_live is utilizing. Is it safe to insert a formatted USB drive, mount it, and copy over the log file, then restart the ddrescue? Will the clonezilla shell even recognize that I inserted the USB stick that wasn't there on boot, so I can mount it?
I'm assuming I'd try
sudo fdisk -l to list the disks, then make a directory?
sudo mkdir /logfile/usb then mount it?
sudo mount /dev/sdb1 /media/usb, then copy?
ANY feedback would be appreciated. I've screwed around in Unix shell a bit, setup a z-pool raid, but always when I knew exactly what I was doing, and not in linux, let alone a bare-bones version.