How to recover corrupted files on an SSD with TestDisk

Why SSDs corrupt and how TestDisk steps in

When a solid-state drive suddenly stops recognizing the operating system, panic is usually immediate. In the vast majority of cases, the issue is not a physical burnout of the flash memory chips, but rather a corruption in the partition table — the logical index that tells the computer where each block of files begins and ends. To make matters worse, the TRIM technology, designed to optimize SSD speed and lifespan by erasing idle blocks, can turn a logical glitch into a permanent data loss event if triggered incorrectly. It is precisely in this apparent catastrophe scenario that TestDisk comes into play, serving as an extremely powerful open-source utility for low-level scanning and storage structure reconstruction.

Before plugging in any cables or executing destructive commands, it is essential to understand metadata-based recovery. When we delete a partition or the primary table becomes corrupted, the files remain physically recorded on the SSD's flash memory cells; the system merely loses the map pointing to their location. Common file recovery software often fails because it searches for known extensions in a disorganized manner, whereas TestDisk goes straight to the root of the problem: it searches for signatures of old file systems, such as Microsoft backup boot sectors, ext4 superblocks, or exFAT descriptors, allowing you to rebuild the original table with surgical precision in the terminal, much like what happens when we clone corrupted NVMe drives on Linux with ddrescue to preserve media integrity.

Initial precautions and workspace preparation

The most common mistake made by professionals and enthusiasts when dealing with a corrupted SSD is attempting to run automated repair tools directly from the affected operating system, or worse, continuing to write new data to the same drive. In practice, this means every new file downloaded or system opened can occupy the exact physical space where your lost documents still reside, destroying any chance of recovery. Therefore, the golden rule of data recovery is to isolate the corrupted media: if possible, remove the SSD from the main machine and connect it to another computer as a secondary drive via a USB adapter or SATA cable, ensuring no operating system process attempts to write logs or temporary files to it during analysis.

Beyond isolating the hardware, choosing the environment where TestDisk runs makes all the difference in the success of the procedure. Although the utility has native Windows versions, running the tool from a live environment (such as a bootable USB stick with a lightweight Linux distribution) offers absolute control over disk access permissions and avoids interference from security software like antiviruses that block direct reads of physical sectors. If you need to handle related issues in other storage infrastructure layers, it is worth consulting complementary guidelines on how to test switched-mode power supplies with a series lamp to rule out electrical instabilities that might have corrupted the SSD originally.

Step-by-step guide to starting the scan in TestDisk

With the SSD properly isolated and connected to a support machine, the first practical step is to launch TestDisk with administrative privileges (root on Linux or Administrator on Windows) to guarantee unrestricted access to the disk blocks. Upon launching the program via the terminal using the testdisk command, the text-based user interface (TUI) appears, allowing you to navigate using the keyboard arrow keys. The software will ask whether you want to create a log file to record operations performed, which is highly recommended for auditing and tracking analyzed sectors.

Next, TestDisk lists all physical storage units detected by the operating system. Here, you must pay close attention to select the correct SSD based on the reported storage capacity (for example, 500GB or 1TB), avoiding the drive running your current operating system. After choosing the target unit, the program asks you to indicate the partition table type used — such as Intel/PC partition for traditional MBR partitions, EFI GPT for modern UEFI systems, or None if the drive uses a raw volume without a formal table. If in doubt, the tool features an intelligent auto-detection mechanism that suggests the most appropriate option based on signatures found in the first sectors.

# On Linux, start TestDisk with superuser privileges to unlock raw block access: sudo testdisk # In the interactive menu, select 'Proceed', choose the correct SSD, and pick the partition table type (usually 'EFI GPT' for modern hardware). 

Analysis of lost partitions and deep search

Once the partition table type is defined, TestDisk's main menu reveals the Analyse option, which performs a quick scan of the current disk structure to identify damaged, overlapping, or missing partitions. The result of this first scan shows what the program managed to deduce from remaining data. If the lost partition appears in the list in green or marked with a valid status, you are halfway home. However, if the result is inconclusive or displays incorrect partitions, you must trigger the Deeper Search option, an intensive feature that scans the SSD sector by sector for traces of old file systems that were deleted or partially overwritten over time.

The deep search may take a few minutes depending on the read speed and total capacity of the SSD, displaying found blocks in real time. It is important to look at the labels next to each finding: partitions marked with the letter 'P' indicate they can be listed and recovered with intact files, while 'D' indicates the partition was deleted. If you view your correct directories and folders by pressing the letter 'P' to list the contents of a found partition, you have confirmation that the data is sound and ready to be restored to a safe folder on another storage disk.

Table reconstruction and raw data recovery

The most critical moment of the entire process occurs during the writing phase of the new logical structure. After locating the lost partition through the deep search and confirming files are accessible, TestDisk offers the Write option to save the recovered partition table directly to the SSD's boot sector area. Before confirming this action, double-check that you are writing to the correct SSD and that the listed partitions make logical sense. Writing an incorrect partition table can further scramble logical indices, though complementary file rescue tools can help if anything goes wrong, similarly to how we handle corrupted files in Git directly from the terminal via recovery procedures.

If the partition table is completely unrecoverable and the goal is solely to extract specific files (such as documents, photos, or source code), you can use TestDisk's sibling utility called PhotoRec, included in the installation package. While TestDisk fixes the logical structure, PhotoRec completely ignores the partition table and performs a scan based on file signature stamps (file carving), rescuing raw content and saving it to an external folder. Although it loses original filenames and the directory tree, PhotoRec ensures no recoverable byte is left behind on the corrupted SSD.

# If you prefer to extract raw files without attempting partition repair, use PhotoRec included in the package: photorec # Select the corrupted SSD, choose the file system (usually [Other] for ext4, NTFS, or exFAT), and point to a destination folder on a healthy disk. 

Final considerations on data integrity and prevention

Recovering a corrupted SSD using TestDisk demonstrates the resilience of modern data when approached with appropriate technical tools, but it also serves as a definitive warning about the unpredictability of hardware and software failures. Solid-state drives have finite write cycles and complex controllers that can fail due to power surges, firmware bugs, or abrupt interruptions during OS updates. For this reason, no lab recovery procedure replaces a robust, automated off-site or cloud backup strategy.

Maintaining the discipline to periodically check drive health using smart monitoring attributes ensures you are warned before a catastrophe occurs, allowing you to proactively replace worn-out components. By mastering TestDisk and understanding the logical limits of partitioning, you turn a potential total loss situation into a controllable incident, ensuring technical knowledge remains your best line of defense against IT infrastructure surprises.