Chkdsk says "Free space verification is complete". What to do next?

[L0lig1]

My friend gave me his broken laptop to try to get the files from the HDD that's inside. The laptop didn't boot so I took out the drive and connected it to my laptop with a SATA to USB cable. I couldn't access the drive, error message: "E:\ is not accessible. The parameter is incorrect." After watching a few videos, i decided to do a chkdsk on cmd. It took like 12h and now it looks like it's complete but I still can't access the drive yet. What do I have to do?

 

Log:

 

 

C:\Users\User1>chkdsk E: /f /r
The type of the file system is NTFS.

CHKDSK is verifying files (stage 1 of 5)...
 0 percent complete. (6 of 256 file records processed)
Deleting corrupt attribute record (128, "")
from file record segment 6.
 5 percent complete. (131 of 256 file records processed)
File record segment 131 is unreadable.
 5 percent complete. (136 of 256 file records processed)
File record segment 136 is unreadable.
 5 percent complete. (137 of 256 file records processed)
File record segment 137 is unreadable.
 5 percent complete. (148 of 256 file records processed)
File record segment 148 is unreadable.
 5 percent complete. (152 of 256 file records processed)
File record segment 152 is unreadable.
 6 percent complete. (156 of 256 file records processed)
File record segment 156 is unreadable.
 6 percent complete. (157 of 256 file records processed)
File record segment 157 is unreadable.
 6 percent complete. (158 of 256 file records processed)
File record segment 158 is unreadable.
 6 percent complete. (159 of 256 file records processed)
File record segment 159 is unreadable.
 6 percent complete. (164 of 256 file records processed)
File record segment 164 is unreadable.
 6 percent complete. (165 of 256 file records processed)
File record segment 165 is unreadable.
 7 percent complete. (180 of 256 file records processed)
File record segment 180 is unreadable.
 7 percent complete. (184 of 256 file records processed)
File record segment 184 is unreadable.
 8 percent complete. (216 of 256 file records processed)
File record segment 216 is unreadable.
 8 percent complete. (224 of 256 file records processed)
File record segment 224 is unreadable.
 8 percent complete. (225 of 256 file records processed)
File record segment 225 is unreadable.
 8 percent complete. (228 of 256 file records processed)
File record segment 228 is unreadable.
 8 percent complete. (229 of 256 file records processed)
File record segment 229 is unreadable.
 8 percent complete. (230 of 256 file records processed)
File record segment 230 is unreadable.
 9 percent complete. (231 of 256 file records processed)
File record segment 231 is unreadable.
 9 percent complete. (232 of 256 file records processed)
File record segment 232 is unreadable.
 9 percent complete. (233 of 256 file records processed)
File record segment 233 is unreadable.
 9 percent complete. (234 of 256 file records processed)
File record segment 234 is unreadable.
 9 percent complete. (235 of 256 file records processed)
File record segment 235 is unreadable.
 9 percent complete. (236 of 256 file records processed)
File record segment 236 is unreadable.
 9 percent complete. (237 of 256 file records processed)
File record segment 237 is unreadable.
 9 percent complete. (238 of 256 file records processed)
File record segment 238 is unreadable.
 9 percent complete. (239 of 256 file records processed)
File record segment 239 is unreadable.
 9 percent complete. (240 of 256 file records processed)
File record segment 240 is unreadable.
 9 percent complete. (241 of 256 file records processed)
File record segment 241 is unreadable.
 9 percent complete. (242 of 256 file records processed)
File record segment 242 is unreadable.
  256 file records processed.
File verification completed.
  0 large file records processed.
  31 bad file records processed.
  0 EA records processed.
  0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
10 percent complete. (137 of 272 index entries processed)
File record segment 140 is unreadable.
10 percent complete. (142 of 272 index entries processed)
File record segment 141 is unreadable.
10 percent complete. (145 of 272 index entries processed)
File record segment 144 is unreadable.
10 percent complete. (146 of 272 index entries processed)
File record segment 145 is unreadable.
10 percent complete. (149 of 272 index entries processed)
File record segment 160 is unreadable.
10 percent complete. (165 of 272 index entries processed)
File record segment 168 is unreadable.
10 percent complete. (181 of 272 index entries processed)
File record segment 188 is unreadable.
10 percent complete. (201 of 272 index entries processed)
File record segment 200 is unreadable.
10 percent complete. (202 of 272 index entries processed)
File record segment 201 is unreadable.
10 percent complete. (205 of 272 index entries processed)
File record segment 204 is unreadable.
10 percent complete. (213 of 272 index entries processed)
File record segment 212 is unreadable.
10 percent complete. (214 of 272 index entries processed)
File record segment 213 is unreadable.
10 percent complete. (217 of 272 index entries processed)
File record segment 220 is unreadable.
10 percent complete. (249 of 272 index entries processed)
File record segment 248 is unreadable.
10 percent complete. (250 of 272 index entries processed)
File record segment 249 is unreadable.
10 percent complete. (251 of 272 index entries processed)
File record segment 250 is unreadable.
10 percent complete. (252 of 272 index entries processed)
File record segment 251 is unreadable.
  272 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
  256 file SDs/SIDs processed.
Security descriptor verification completed.
Inserting data attribute into file 6.
  9 data files processed.
CHKDSK is verifying file data (stage 4 of 5)...
  240 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  122077875 free clusters processed.
Free space verification is complete.

 

[Archer42]

3 minutes ago, L0lig1 said:

to try to get the files from the HDD that's inside

 

3 minutes ago, L0lig1 said:

i decided to do a chkdsk on cmd

Worst decision ever. A way to damage/destroy data even further, making it completely unrecoverable.

 

What you have to do each time you are trying to recover data is, first of all, create full hdd image. Then depending on circumstances you can either work with original hdd (if it is not broken/damaged) or create a copy and work with it (working with broken hdd makes no sense as it is huge waste of time).

There are different tools which can be used in such cases to try and fix partition table/filesystem or extract whatever files are there, like testdisk for example.

But again - you never write anything or run any tools on hdd before you've imaged it.

[L0lig1]

2 minutes ago, Archer42 said:

 

Worst decision ever. A way to damage/destroy data even further, making it completely unrecoverable.

 

What you have to do each time you are trying to recover data is, first of all, create full hdd image. Then depending on circumstances you can either work with original hdd (if it is not broken/damaged) or create a copy and work with it (working with broken hdd makes no sense as it is huge waste of time).

There are different tools which can be used in such cases to try and fix partition table/filesystem or extract whatever files are there, like testdisk for example.

But again - you never write anything or run any tools on hdd before you've imaged it.

Oh ok! It's my second time I do this. The first time the HDD just worked fine and I accessed the files with no problem. This time doesn't seem that good. I should've done my research, I guess watching some YT vids isn't a solution. Can you link any good videos or forums or guides on how to create a full hdd image? I don't trust myself anymore lul

[Kilrah]

And to image it you use something like ddrescue that's designed to not stress the drive too much by quickly skipping bad sectors on the first passes.

[Archer42]

11 minutes ago, L0lig1 said:

Oh ok! It's my second time I do this. The first time the HDD just worked fine and I accessed the files with no problem. This time doesn't seem that good. I should've done my research, I guess watching some YT vids isn't a solution. Can you link any good videos or forums or guides on how to create a full hdd image? I don't trust myself anymore lul

Multiple ways to do it, depends on your knowledge level. I cannot really recommend any videos, but what i'd do is boot into some live cd like clonezilla and use either dd or ddrescue to make an image. You should be able to google how to use either tool without issues.

Testdisk, a recovery tool also available there, can create images too.

To get basic understanding of how bad hdd state is you can read smart using smartctl, and then decide what tool to use based on that.

 

11 minutes ago, Kilrah said:

And to image it you use something like ddrescue that's designed to not stress the drive too much by quickly skipping bad sectors on the first passes.

Also one more trick to this - even on desktop hdd-s setting error recovery control timeout is often supported, and setting it as low as possible can greatly help with speeding things up and avoiding unneeded retries too.

[Chiyawa]

1 hour ago, Archer42 said:

Worst decision ever. A way to damage/destroy data even further, making it completely unrecoverable.

Hmm... Well, I guess that depends on the situation. For me, CHKDSK /f /r always works, unless the drive is heavily damage, but at that point, even Recuva couldn't read the HDD, and the cloned HDD had so many corrupted files.

[Archer42]

15 minutes ago, Chiyawa said:

Hmm... Well, I guess that depends on the situation. For me, CHKDSK /f /r always works, unless the drive is heavily damage, but at that point, even Recuva couldn't read the HDD, and the cloned HDD had so many corrupted files.

It can work, or it can make things worse. Depends on many things.

If the data is at least somewhat important making an image before trying is a must anyway, it is not hard and can save time too in many cases (if hdd is physically damaged working with image will be much faster).