![]() ![]() I prefer bringing the sick device to my good reliable Linux system and not hassling with bootloaders and strange hardware. For SATA and SDD drives, USB adapters are inexpensive and easy to use. One way is to mount the sick drive on your Linux system, which is easy if it’s an optical disk or USB device. There are a couple of ways to set this up. If you run out of room, even if it’s just a few bytes, GNU ddrescue will fail at the very end. You need a Linux system with GNU ddrescue (gddrescue on Ubuntu), the drive you are rescuing, and a device with an empty partition at least 1.5 times as large as the partition you are rescuing, so you have plenty of headroom. GNU ddrescue is fast and reliable: it skips bad blocks and copies the good blocks, and then comes back to try copying the bad blocks, tracking their location with a simple logfile. dd-rescue is older, and the design of GNU ddrescue probably benefited from it. These days most Linux distributions have live bootable versions so you can use whatever you are comfortable with, provided you add GNU ddrescue and any other rescue software you need.ĭon’t confuse GNU ddrescue with dd-rescue by Kurt Garloff. (Remember the bad old days before USB devices? However did we survive?) SystemRescueCD has a small footprint and is specialized for rescue operations. I like to keep a SystemRescueCD handy, and also on a USB stick. You can even copy Windows and Mac OS X storage devices because GNU ddrescue operates at the block level, rather than the filesystem level, so it doesn’t matter what filesystem is on the device.īefore you run any kind of file recovery or forensic tools on a damaged volume it is a best practice to first make a copy, and then operate on the copy. GNU ddrescue is the premium tool for copying dying hard drives, and any block device such as CDs, DVDs, USB sticks, Compact Flash, SD cards - anything that is recognized by your Linux system as /dev/ foo. ![]() The longer it takes to copy your data, the more you risk losing. The drive is in an internally mounted SATA dock.When you rescue your data from a dying hard drive, time is of the essence. I'm confused by this as I would expect lots of read errors for this very slow progress. Just before I captured this screen shot, the remaining time was 71 days, so it does look like some progress is being made, but it's really slow (less that 1% recovered after 5 1/2 hours). Pct rescued: 0.94%, read errors: 2, remaining time: 7d 17h 52mĬopying non-tried blocks. Rescued: 9472 MB, bad areas: 0, run time: 5h 33m 5s Non-tried: 990732 MB, bad-sector: 0 B, error rate: 0 B/s Opos: 9492 MB, non-scraped: 0 B, average rate: 473 kB/s Ipos: 9492 MB, non-trimmed: 131072 B, current rate: 0 B/s $ sudo ddrescue -d /dev/sde jennifer.img jennifer.logfile After 5 1/2 hours, the ddrescue info looks like this: So I decided to pull the drive and run ddrescue. Firmware version is 04.01A04, and I don't see a firmware update on the WD support site. This is a WD10SPZX-24Z10 drive (WD BLUE (EIDE)). And yes, I do know that SMART is not definitive in terms of drive health. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUEĪll other SMART values are OK. I booted it from an external drive, and SMART shows: Yet another broken hard drive question.Ĭustomer brought system to me with a "won't boot" issue. ![]()
0 Comments
Leave a Reply. |