ddrescue seems to get stuck
I'm trying to rescue a hard drive that seems flaky. Ddrescue goes along fine for while then seems to stop making progress. Moreover, it's not uninterruptible by ^C despite the message saying it can be. I can however interrupt it by pulling the USB cable. When I restart it, it goes along for a while then stops again. After 24 hours and multiple restarts, my image file is only 28G while the original device is 1T.
Below is output from ddrescue after it got stuck for many hours. I was out and when I came back, the screen hadn't changed. However after I pull the USB cable, some numbers do change. When The drive seems to be being accessed continually even when ddrescue isn't reporting progress. Does anyone have any ideas on what is going on? Code:
root@transponder:/home/garydale# ddrescue /dev/sdl ./.data/rescue.img ./.data/mapfile |
I had an issue on an older atom laptop (CMOOV issue???). Using dd under ubuntu basically crashed on me (July-ish 2015). Using dd under debian worked just fine. Perhaps a place to start.
|
Sounds like some badblocks or such giving extended iowaits ...
Just leave it running - that’s what ddrescue was designed to cope with. Starting from the other end of the drive might help too, or skip the problematic sectors and come back to them later. |
Quote:
|
Quote:
Does ddrescue have any issues with USB drives (as opposed to SATA) that you know of? If the drive is failing, the last thing I need is for a program to pound it trying to read. I just tried the reverse run and this happened: Code:
root@transponder:/home/garydale# ddrescue -R /dev/sdl ./.data/rescue.img ./.data/mapfile |
If the device node is disappearing, you probably have hardware issues - maybe the port isn't up to the job. Do you have external power ?.
|
Looks like it might be more serious trouble with that drive then.
If the drive won’t supply any data, not much ddrescue can do. |
Quote:
The external USB case is powered. I'm working with the theory that the drive electronics are flaky. The computer I took the drive from would take 30 minutes or longer to boot. It wasn't always successful and when it did, it would be slow to respond. To make matters worse, I couldn't get into the BIOS which prevented me from booting from a CD or USB stick. I put the drive in a USB case to try to recover the data on it, which led to the current problem. I first tried to run smartctl -H on it, but that never returned a result so I figured better try to make an image of the drive ASAP. ------------ Wonderful - after a reboot, Linux rearranged the drive letters so the drive I was trying to recover switched with a working drive and overwrote the data I'd recovered. Back to square 1. |
All times are GMT -5. The time now is 09:50 PM. |