#Read error testdisk how to#
#Read error testdisk install#
#Read error testdisk software#

>Disk /dev/sdb - 640 GB / 596 GiB - WDC WD6401AALS-00J7B1ĭisk /dev/sdc - 32 GB / 29 GiB - SanDisk CF Extreme USB2ĭisk /dev/sr0 - 366 MB / 349 MiB (RO) - ATAPI iHAS424 B Select a media (use Arrow keys, then press Enter):ĭisk /dev/sda - 2000 GB / 1863 GiB - ST2000DM001-1CH164 In the next screen select the disk you want to repair. Use arrow keys to select, then press Enter key: Outputs including any folder/file names TestDisk was used to find and Will contain TestDisk options, technical information and various If you choose to create the text file, testdisk.log, it Information gathered during TestDisk use can be recorded for later It can also be used to repair some filesystem errors. Partitions and/or make non-booting disks bootable again when these symptomsĪre caused by faulty software, certain types of viruses or human error.

#Read error testdisk software#

TestDisk is free data recovery software designed to help recover lost This e-mail address is being protected from spambots. TestDisk 6.14, Data Recovery Utility, July 2013

TestDisk is in most Linux repos, and on SystemRescueCD. TestDisk operates on both the legacy MBR and the newfangled GPT (see Using the New GUID Partition Table in Linux (Goodbye Ancient MBR)). TestDiskĪ good tool for repairing partition tables and recovering files is TestDisk. So, as always, your first and best line of defense is good backups. If the partition table is unrecoverable you may not be able to recover your data. There are no guarantees- you may be able to repair the problem, or you may have to reinstall your operating system.

#Read error testdisk install#

Any *buntu live system also makes a great rescue distro, especially on a USB stick with persistent storage, because then it remembers your settings, you can install apps, and store documents. SystemRescueCD on a USB stick is my fave. When your partition table is damaged to the point that your Linux will not boot, you have to fix it from the outside of the damaged system via bootable rescue media, or another Linux in a multi-boot installation.

#Read error testdisk how to#

I booted into a different Linux installation and pondered how to make repairs. I make sure that it is enabled and that it reboots the system. Fortunately, I always foil the desires of certain distros that disable ctrl+alt+delete, or make it behave like Windows and open a services manager. “Press any key to exit” landed at a blinking cursor on a black screen.

I don’t know exactly which operations gummed up /dev/sdb, which would be good to know. How did this happen? I was installing Voyage Linux on a compact flash card, and while I was messing around with GParted and other filesystem tools I accidentally ran some commands on /dev/sdb, my main hard disk, instead of /dev/sdc, the compact flash card. Figure 1 (above) shows the cheery message that greeted me at boot. Well there I was, rebuilding a router and having a good time when I accidentally damaged the partition table on my main Linux installation, which is a GUID partition table, or GPT.