SSD corrupted during reboots, any idea if this is recoverable?

How to use TestDisk to recover lost partition
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Post Reply
Message
Author
MrGroggle
Posts: 1
Joined: 24 Apr 2025, 08:04

SSD corrupted during reboots, any idea if this is recoverable?

#1 Post by MrGroggle »

Good morning,
I was checking my Win10 PCs settings to see if it was possible to upgrade to Win11. This involved BIOS UEFI checks with some reboots to see how to enable Secure Boot. After some of these reboots, my main data storage drive (thankfully not OS) was flagged as needing a disk check on startup. The PC was running incredibly slowly, because this drive was running at 100% active time with occasional > 50KB/s read transfers. In disk management the drive shows as RAW, and cannot be accessed by Windows or any disk info software (e.g. CrystalDiskInfo).
I ran TestDisk and was able to review the files during the investigations, and have started to move the most important of these to a new drive just in case. However, I cannot repair the drive, as it emits a "Partition: write error" with no apparent reason. I selected the drive, selected GPT as that was the original format, then Analyze. I did a quick search and a deeper search. I cancelled the deeper search after a time, then went to attempt the repair. Can anyone shed some light on what might need to be done to fix the drive, or whether it's best to just recover the data?

Code: Select all

Tue Apr 22 23:02:34 2025
Command line: TestDisk

TestDisk 7.2, Data Recovery Utility, February 2024
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 11.2, Cygwin 3001.4
ext2fs lib: 1.45.3, ntfs lib: available, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.1
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=480103981056
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=512110190592
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive4)=15376318464
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=211956946432
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=2000397795328
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=1000202043392
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\F:)=267217010688
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\G:)=512107741184
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\H:)=15376302080
Hard disk list
Disk \\.\PhysicalDrive0 - 480 GB / 447 GiB - CHS 58369 255 63, sector size=512 - SanDisk SDSSDHII480G, S/N:154307406252, FW:X31200RL
Disk \\.\PhysicalDrive1 - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - Samsung SSD 870 EVO 2TB, S/N:S621NF0R201126E, FW:SVT01B6Q
Disk \\.\PhysicalDrive2 - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - Hitachi HDS721010CLA332, S/N:JP2911J82B7LTV, FW:JP4OA3MA
Disk \\.\PhysicalDrive3 - 512 GB / 476 GiB - CHS 62260 255 63, sector size=512 - ADATA SX8200PNP, S/N:2J3620033546        _00000001., FW:S0118C
Disk \\.\PhysicalDrive4 - 15 GB / 14 GiB - CHS 1869 255 63, sector size=512 - SanDisk Cruzer Blade, S/N:4C530000091108102234, FW:1.00

Partition table type (auto): EFI GPT
Disk \\.\PhysicalDrive1 - 2000 GB / 1863 GiB - Samsung SSD 870 EVO 2TB
Partition table type: EFI GPT

Analyse Disk \\.\PhysicalDrive1 - 2000 GB / 1863 GiB - CHS 243201 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=3907029167 (expected 3907029167)
hdr_lba_start=34
hdr_lba_end=3907029134
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
Current partition structure:
 1 P MS Data                     2048 3907028991 3907026944 [Basic data partition] [SSD Data]

search_part()
Disk \\.\PhysicalDrive1 - 2000 GB / 1863 GiB - CHS 243201 255 63
NTFS at 0/32/33
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
NTFS part_offset=1048576, part_size=2000397791744, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
NTFS at 0/32/33
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
     MS Data                     2048 3907028984 3907026937 [SSD Data]
     NTFS, blocksize=4096, 2000 GB / 1863 GiB
NTFS at 243201/78/13
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
     MS Data                     2055 3907028991 3907026937
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1863 GiB
NTFS at 243201/78/13
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
NTFS: Can't read MFT
     MS Data               3907028991 7814055927 3907026937
     NTFS, blocksize=4096, 2000 GB / 1863 GiB
This partition ends after the disk limits. (start=3907028991, size=3907026937, end=7814055927, disk end=3907029168)
file_win32_pread(544,11,buffer,3907029162(243201/80/58)) read err: read after end of file
file_win32_pread(544,8,buffer,3907029165(243201/80/61)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029156(243201/80/52)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029157(243201/80/53)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029158(243201/80/54)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029159(243201/80/55)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029160(243201/80/56)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029162(243201/80/58)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029164(243201/80/60)) read err: read after end of file
file_win32_pread(544,14,buffer,3907029166(243201/80/62)) read err: read after end of file
Disk \\.\PhysicalDrive1 - 2000 GB / 1863 GiB - CHS 243201 255 63
Check the hard disk size: HD jumper settings, BIOS detection...
The hard disk (2000 GB / 1863 GiB) seems too small! (< 4000 GB / 3726 GiB)
The following partition can't be recovered:
     MS Data               3907028991 7814055927 3907026937
     NTFS, blocksize=4096, 2000 GB / 1863 GiB

Results
     MS Data                     2048 3907028984 3907026937 [SSD Data]
     NTFS, blocksize=4096, 2000 GB / 1863 GiB
     MS Data                     2055 3907028991 3907026937
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1863 GiB

interface_write()
 
No partition found or selected for recovery

search_part()
Disk \\.\PhysicalDrive1 - 2000 GB / 1863 GiB - CHS 243201 255 63
NTFS at 0/32/33
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
NTFS part_offset=1048576, part_size=2000397791744, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
NTFS at 0/32/33
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
     MS Data                     2048 3907028984 3907026937 [SSD Data]
     NTFS, blocksize=4096, 2000 GB / 1863 GiB
file_win32_pread(544,16,buffer,382034(23/199/3)) read err: read after end of file
[..] REMOVED FOR BREVITY
file_win32_pread(544,16,buffer,2935462(182/184/41)) read err: read after end of file
NTFS at 243201/78/13
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
     MS Data                     2055 3907028991 3907026937
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1863 GiB
NTFS at 243201/78/13
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
NTFS: Can't read MFT
     MS Data               3907028991 7814055927 3907026937
     NTFS, blocksize=4096, 2000 GB / 1863 GiB
This partition ends after the disk limits. (start=3907028991, size=3907026937, end=7814055927, disk end=3907029168)
NTFS at 0/32/33
filesystem size           3907026937
sectors_per_cluster       8
mft_lcn                   39164790
mftmirr_lcn               10770
clusters_per_mft_record   -10
clusters_per_index_record 1
Search for partition aborted
Disk \\.\PhysicalDrive1 - 2000 GB / 1863 GiB - CHS 243201 255 63
Check the hard disk size: HD jumper settings, BIOS detection...
The hard disk (2000 GB / 1863 GiB) seems too small! (< 4000 GB / 3726 GiB)
The following partition can't be recovered:
     MS Data               3907028991 7814055927 3907026937
     NTFS, blocksize=4096, 2000 GB / 1863 GiB

Results
     MS Data                     2048 3907028984 3907026937 [SSD Data]
     NTFS, blocksize=4096, 2000 GB / 1863 GiB
     MS Data                     2055 3907028991 3907026937
     NTFS found using backup sector, blocksize=4096, 2000 GB / 1863 GiB

interface_write()
 1 P MS Data                     2048 3907028984 3907026937 [SSD Data]

interface_write()
 1 P MS Data                     2048 3907028984 3907026937 [SSD Data]
write!
file_win32_pwrite(544,32,buffer,2(0/0/3)) write err

Partition: Write error

TestDisk exited normally.
Top
recuperation
Posts: 3008
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: SSD corrupted during reboots, any idea if this is recoverable?

#2 Post by recuperation »

MrGroggle wrote: 24 Apr 2025, 08:16 Good morning,
I was checking my Win10 PCs settings to see if it was possible to upgrade to Win11. This involved BIOS UEFI checks with some reboots to see how to enable Secure Boot. After some of these reboots, my main data storage drive (thankfully not OS) was flagged as needing a disk check on startup. The PC was running incredibly slowly, because this drive was running at 100% active time with occasional > 50KB/s read transfers. In disk management the drive shows as RAW, and cannot be accessed by Windows
Disk management IS a part of windows. Therefore your disk can be accessed by Windows.
or any disk info software (e.g. CrystalDiskInfo).
I ran TestDisk and was able to review the files during the investigations, and have started to move the most important of these to a new drive just in case. However, I cannot repair the drive, as it emits a "Partition: write error" with no apparent reason.
Better SSD products that have reached the maximum writable amount of data remain readable and do not allow write operations. Unfortunately the TestDisk log file shows write errors as well.
I selected the drive, selected GPT as that was the original format, then Analyze. I did a quick search and a deeper search. I cancelled the deeper search after a time, then went to attempt the repair. Can anyone shed some light on what might need to be done to fix the drive, or whether it's best to just recover the data?
Given your description and the TestDisk logfile you should not use this SSD anymore.
Top
Post Reply

Return to “Partition Recovery”