hello friends! new(ish)!
Data recovery: Difference between revisions
>WubTheCaptain m (WubTheCaptain moved page Data Recovery to Data recovery: wikipedia:Wikipedia:Naming conventions (capitalization)) |
>Oitap (Added in headings, links to the tools mentioned in the drive recovery process, and a short explanation taken from the TestDisk wiki (sourced appropriately).) |
||
| Line 1: | Line 1: | ||
{{Cleanup}} | {{Cleanup}} | ||
== Data Recovery Tools == | |||
*[http://www.cgsecurity.org/wiki/TestDisk/ TestDisk] | |||
*[http://www.cgsecurity.org/wiki/PhotoRec/ PhotoRec] | |||
*[https://www.piriform.com/recuva/ Recuva] | |||
Note: TestDisk and PhotoRec come as a package, TestDisk is used to "help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software, certain types of viruses or human error (such as accidentally deleting a Partition Table)."[http://www.cgsecurity.org/wiki/TestDisk] Whereas PhotoRec is for recovering data, therefore depending on your needs either one may be appropriate. | |||
== An example of a drive recovery process== | |||
Here's what you have to do to save your data, if the hard drive still mounts. | Here's what you have to do to save your data, if the hard drive still mounts. | ||
| Line 8: | Line 22: | ||
Connect the failing hard drive to an internal SATA port on your computer, if it's in a USB enclosure open it up and remove the drive. | Connect the failing hard drive to an internal SATA port on your computer, if it's in a USB enclosure open it up and remove the drive. | ||
Next, boot from a [[GNU/Linux]] LiveCD and use an imaging program that doesn't retry I/O errors endlessly. Mount the failing drive Read-Only first. Use | Next, boot from a [[GNU/Linux]] LiveCD and use an imaging program that doesn't retry I/O errors endlessly. Mount the failing drive Read-Only first. Use [http://www.garloff.de/kurt/linux/ddrescue/ dd_rescue] or an equivalent so that it doesn't get stuck forever rereading one sector when it encounters read errors. | ||
Finally, if you are able to mount the disk image, do that. If not able to mount the copy, try Testdisk and Photorec or Recuva to recover data from the image. Recover the saved data to yet another separate partition. | Finally, if you are able to mount the disk image, do that. If not able to mount the copy, try Testdisk and Photorec or Recuva to recover data from the image. Recover the saved data to yet another separate partition. | ||
Revision as of 04:45, 23 February 2014
Data Recovery Tools
Note: TestDisk and PhotoRec come as a package, TestDisk is used to "help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software, certain types of viruses or human error (such as accidentally deleting a Partition Table)."[1] Whereas PhotoRec is for recovering data, therefore depending on your needs either one may be appropriate.
An example of a drive recovery process
Here's what you have to do to save your data, if the hard drive still mounts.
You can tell that your hard drive is failing if it causes your computer to hang in the BIOS when connected, if it has a "Current Pending Sector Count" > 0 in the SMART info, or if it's making unusual noises.
First, get another hard drive large enough to image the failing one onto.
Connect the failing hard drive to an internal SATA port on your computer, if it's in a USB enclosure open it up and remove the drive.
Next, boot from a GNU/Linux LiveCD and use an imaging program that doesn't retry I/O errors endlessly. Mount the failing drive Read-Only first. Use dd_rescue or an equivalent so that it doesn't get stuck forever rereading one sector when it encounters read errors.
Finally, if you are able to mount the disk image, do that. If not able to mount the copy, try Testdisk and Photorec or Recuva to recover data from the image. Recover the saved data to yet another separate partition.
If you had to use PhotoRec, you will probably want to disable recovery of plain text files unless there's something in that format you want to save since it produces a massive amount of tiny text files from most hard drives. Stick to photos and Office documents for most people. Fragmented files will probably be unrecoverable.