Page 1 of 2

Try to find a unallocated partition and stuck at 99%

Posted: 18 Mar 2026, 06:50
by John123
Long story short, I am trying to use testdisk. After analyze the partition structure, and quick search, it stuck at 99% .
Any help will be appreciate.

Image

Re: Try to find a unallocated partition and stuck at 99%

Posted: 18 Mar 2026, 08:28
by recuperation
Please post your log file.

Re: Try to find a unallocated partition and stuck at 99%

Posted: 18 Mar 2026, 08:42
by John123
testdisk.log
(2.46 KiB) Downloaded 11033 times
recuperation wrote: 18 Mar 2026, 08:28 Please post your log file.
where can I find that log files? I just follow the step up to that point.
is it this one?

Re: Try to find a unallocated partition and stuck at 99%

Posted: 18 Mar 2026, 14:39
by recuperation
When using Windows operating systems the log file is typically written into the folder with the TestDisk executable.
The log file you provided looks like being cut off.

Based on the information given, I have no answer for you.
Obviously you are using TestDisk for a reason.

Please provide a smartmontools log file and a case description - hoping that this information provides some readable evidence.

viewtopic.php?f=5&t=10910

Re: Try to find a unallocated partition and stuck at 99%

Posted: 18 Mar 2026, 16:47
by John123
recuperation wrote: 18 Mar 2026, 14:39 When using Windows operating systems the log file is typically written into the folder with the TestDisk executable.
The log file you provided looks like being cut off.

Based on the information given, I have no answer for you.
Obviously you are using TestDisk for a reason.

Please provide a smartmontools log file and a case description - hoping that this information provides some readable evidence.

viewtopic.php?f=5&t=10910
Thanks for your time helping.
The cut off, it is because it stack at 99% and never finish. This is my guess here.
I used smartmontools as you suggested and follow those instruction, but in the log it show:

"Smartctl open device: /dev/sde [SAT] failed: \\.\PhysicalDrive4: Open failed, Error=5"

I used both command smartctl -a -d sat,12 /dev/sdx > myreport.txt and smartctl -a /dev/sde > myreport.txt

Re: Try to find a unallocated partition and stuck at 99%

Posted: 18 Mar 2026, 19:34
by recuperation
John123 wrote: 18 Mar 2026, 16:47 The cut off, it is because it stack at 99% and never finish. This is my guess here.
I used smartmontools as you suggested and follow those instruction, but in the log it show:

"Smartctl open device: /dev/sde [SAT] failed: \\.\PhysicalDrive4: Open failed, Error=5"

I used both command smartctl -a -d sat,12 /dev/sdx > myreport.txt and smartctl -a /dev/sde > myreport.txt
Please run your command prompt as admin.
If that fails use a designated location like
D:\myreport.txt instead of myreport.txt.

Re: Try to find a unallocated partition and stuck at 99%

Posted: 19 Mar 2026, 05:50
by John123
here the log

Re: Try to find a unallocated partition and stuck at 99%

Posted: 19 Mar 2026, 10:31
by recuperation
I don't see any indications for errors in your smartmontools log file. What surprises me, though, is that your TestDisk log file is refering to a disk labeled "Sabrent" whereas the smartmontools log file shows a Samsung 850 EVO.

Re: Try to find a unallocated partition and stuck at 99%

Posted: 19 Mar 2026, 17:49
by John123
recuperation wrote: 19 Mar 2026, 10:31 I don't see any indications for errors in your smartmontools log file. What surprises me, though, is that your TestDisk log file is refering to a disk labeled "Sabrent" whereas the smartmontools log file shows a Samsung 850 EVO.
I use a cable or adapter from Sabrent to connect to the SSD (Samsung). This SSD was the booster drive on my other PC.
I did try to leave my PC on the whole night to see if that 1% get finish, but it doesn't.

Re: Try to find a unallocated partition and stuck at 99%

Posted: 19 Mar 2026, 21:40
by recuperation
Out of despair I would recommend:
Try to connect your SSD internally.

Another possibility is to try and clone the SSD under Linux using ddrescue as described in the manual.
Afterwards you would run TestDisk against the clone. That would exclude any issue with the Samsung SSD.