Use Up/Down Arrow keys to select partition. Press Enter to continue to the next screen. We can try to attempt to recover the lost partition by pressing >. If there’s nothing here it means neither it got delete or damage. Here it shows the current partitions available on the drive. > Analyse current partition structure and search for lost partitions > EFI GPT partition map (Mac i386, some x86_64.) Please select the partition table type, press Enter when done. TestDisk might also pre-selected with Auto detect. But if your computer is newer or has a very big drive(more then 2TB) it will most likely be EFI GPT. If you don’t know theres a good chance its Intel type if its like a usb stick. Once you pick your device, in the next menu choose the partition table type. Select a media (use Arrow keys, then press Enter): Then pick your disk device then press proceed to continue. Use arrow keys to select, then press Enter key: Just run “ sudo testdisk” in the terminal.
To install both Testdisk and Photorec on Debian or Ubuntu, open the terminal and use this command.
But these’s tools are available on are on other platforms too, even windows too! With This tutorial, you learn about using these tools on Debian-based Linux. The Other PhotoRec, is a great file recovery tool to help find deleted files. First I’ll talk about Testdisk, this tool can help find lost partitions that may have been damaged or deleted. ///// Only one HDD was attached on that day and the problematic disk is mapped as /dev/sdb now:ĭisk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - USB3.0 high speed, FW:2210ĭisk /dev/sdb - 1000 GB / 931 GiB - USB3.These’s two tools are great for basic file recovery and easy to use. Hint for advanced users: dmsetup may be used if you prefer to avoid rewriting the partition table for the moment:Įcho "0 4096 linear /dev/sdc 2048" | dmsetup create test0 LUKS 1 (Data size unknown), 2097 KB / 2048 KiB Image created successfully but read errors have occured.Īnalyse Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121601 255 63ĭisk /dev/sdc - 1000 GB / 931 GiB - CHS 121601 255 63 Warning: can't get size for Disk /dev/loop7 - 0 B - 0 sectors, sector size=512ĭisk /dev/sdc - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - USB3.0 high speed, FW:2210ĭisk /dev/sdc - 1000 GB / 931 GiB - USB3.0 high speed Warning: can't get size for Disk /dev/loop6 - 0 B - 0 sectors, sector size=512 Warning: can't get size for Disk /dev/loop5 - 0 B - 0 sectors, sector size=512 Warning: can't get size for Disk /dev/loop4 - 0 B - 0 sectors, sector size=512 Warning: can't get size for Disk /dev/loop3 - 0 B - 0 sectors, sector size=512 Warning: can't get size for Disk /dev/loop2 - 0 B - 0 sectors, sector size=512 Warning: can't get size for Disk /dev/loop1 - 0 B - 0 sectors, sector size=512 Warning: can't get size for Disk /dev/loop0 - 0 B - 0 sectors, sector size=512 Warning: can't get size for Disk /dev/mapper/control - 0 B - 0 sectors, sector size=512 OS: Linux, kernel 5.4.0-109-generic (#123-Ubuntu SMP Fri Apr 8 09:10:) x86_64Įxt2fs lib: 1.45.5, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.1
TestDisk 7.1, Data Recovery Utility, July 2019 Here's the output of testdisk runs (keep in mind that during the 1st run the drive was assigned /dev/sdc, and the next day/run it was mapped as /dev/sdb): Thu May 5 10:37:39 2022 I made some analyzes and Deep Search of partitions. I didn't create any LUKS header dump when the disk was fully operational. 140GB of size, so it apparently didn't take a backup of the whole drive, which is utilized in more than 90%. What I did so far, was creating an image with testdisk. However, it's discoverable by lsblk, although size of the partition is reported as only ca. Also, the device doesn't appear in the list of available devices in Linux Mint's GUI.
The HDD used to prompt for the password right after it was mounted, but now it doesn't mount automatically as before, and there's no password prompt anymore. It has only one partition and it's LUKS-encrypted, as far as I know. There's a 1TB HDD which is somehow corrupted.