3rd party alternate to chkdsk

[Aree Soothsayer]

I am asking because the 2 times it has been used on my pc it has left behind 0kb files. First on my internal drive where I lost almost 300gb of my shows. Then last night I found it had turned 3 of my backup image files after scanning the other day to fix some file irregularities on my external drive.

[AbydosOne]

2 minutes ago, Aree Soothsayer said:

I am asking because the 2 times it has been used on my pc it has left behind 0kb files. First on my internal drive where I lost almost 300gb of my shows. Then last night I found it had turned 3 of my backup image files after scanning the other day to fix some file irregularities on my external drive.

You should be blaming your drives, not chkdsk. If chkdsk wasn't able to restore the files, they were gone already (apart from cyber-sleuthing them manually).

[Dujith]

chkdsk wont do anything without you giving the order, besides it wont do anything when nothing is wrong. 

Like @AbydosOne said, check your drives. 

There are just 2 states for a HDD:

 

1. Its working and its fine.

2. Its starting to act up - IT WILL DIE, replace as soon as possible.

[Aree Soothsayer]

6 minutes ago, AbydosOne said:

You should be blaming your drives, not chkdsk. If chkdsk wasn't able to restore the files, they were gone already (apart from cyber-sleuthing them manually).

 

3 minutes ago, Dujith said:

chkdsk wont do anything without you giving the order, besides it wont do anything is nothing is wrong. 

Like @AbydosOne said, check your drives. 

There are just 2 states for a HDD:

 

1. Its working and its fine.

2. Its starting to act up - IT WILL DIE, replace as soon as possible.

 

I used a couple of tools to check my HDD health and neither showed any problems. I regulary monitor with Crystaldisk, My external drive is pretty new. Having to replace both would be difficult.

[Radium_Angel]

6 minutes ago, Aree Soothsayer said:

 

 

I used a couple of tools to check my HDD health and neither showed any problems. I regulary monitor with Crystaldisk, My external drive is pretty new. Having to replace both would be difficult.

Doesn't change the fact that chkdsk is working as it is supposed to.

 

Have you tested the drives with the manufacturer's software? Seagate, for example, makes Seatools, WD makes WDDiags, and so forth

[Aree Soothsayer]

9 minutes ago, Radium_Angel said:

Doesn't change the fact that chkdsk is working as it is supposed to.

 

Have you tested the drives with the manufacturer's software? Seagate, for example, makes Seatools, WD makes WDDiags, and so forth

My external is hp but the tools would not see it. My internal drive is Seagate and it's working right now and it could see the external one. Should I use it on the hp drive instead?

[Radium_Angel]

49 minutes ago, Aree Soothsayer said:

My external is hp but the tools would not see it.

Probably because it's connected by USB. That tends to interfere with things.

50 minutes ago, Aree Soothsayer said:

Should I use it on the hp drive instead?

As your main drive?

I can't say, since we can't determine the health of the drive.

Is it easily removable from the enclosure? In other words, can you attach it internally to your PC?

[Aree Soothsayer]

1 minute ago, Radium_Angel said:

Probably because it's connected by USB. That tends to interfere with things.

As your main drive?

I can't say, since we can't determine the health of the drive.

Is it easily removable from the enclosure? In other words, can you attach it internally to your PC?

I don't use an enclosure. I use a hub. So I can stick it in the pc. I just didn't want the hassle. I did some googling and others have had windows 10 do these things to their data,

[narrdarr]

did you run both chkdsk /f and /r?

[Aree Soothsayer]

3 minutes ago, narrdarr said:

did you run both chkdsk /f and /r?

Windows did it on it's own in a reboot the first time.

The second time I did it in the disk properties.

[narrdarr]

Run it yourself using cmd as admin

type chkdsk /f/r

y(yes) for reboot

 

If you want to run chkdsk on a specific drive here is an example

chkdsk d: /f/r

 

 

Maybe also want to run sfc /scannow if your having issues with your boot drive

[Aree Soothsayer]

2 minutes ago, narrdarr said:

Run it yourself using cmd as admin

type chkdsk /f/r

y(yes) for reboot

 

If you want to run chkdsk on a specific drive here is an example

chkdsk d: /f/r

 

 

Maybe also want to run sfc /scannow if your having issues with your boot drive

I do NOT want to use the damned thing.

 

So no.

[narrdarr]

1 minute ago, Aree Soothsayer said:

I do NOT want to use the damned thing.

 

So no.

well have a good time with that

guess you can format your drive and start over

[Aree Soothsayer]

Well Seagate came up with 100% on all tests on my internal drive. Just like it did when chkdsk destroyed my data. 

 

That time happened when I cloned my windows drive from HDD to SSD. Windows event had errors and while fixing those errors the chkdsk happened during a reboot. 

 

This time the errors showed up AFTER a reinstall of windows 10 where I upgraded from 1809, all my cpu could handle then, to the 19xx version.

 

In researching it seems windows causes problems when looking at stuff made from older versions of itself.

[AbydosOne]

41 minutes ago, Aree Soothsayer said:

Well Seagate came up with 100% on all tests on my internal drive

All that's doing is checking the HDD-reported SMART information and running a benchmark or two. It really doesn't have any bearing on data integrity; it's more a metric for the drive's physical state. Sometimes degraded drives go on for quite a while (I have unimportant disks that are "technically failed" but still work fine) and others (especially SSDs) will just die without any SMART indication.

 

42 minutes ago, Aree Soothsayer said:

That time happened when I cloned my windows drive from HDD to SSD. Windows event had errors and while fixing those errors the chkdsk happened during a reboot. 

 

This time the errors showed up AFTER a reinstall of windows 10 where I upgraded from 1809, all my cpu could handle then, to the 19xx version.

 

In researching it seems windows causes problems when looking at stuff made from older versions of itself.

The only times I've ever had to deal with actual chkdsk issues have been where there was an underlying hardware issue. My first SSD had a buggy firmware that constantly lost blocks (until I updated it). I've had cheap flash drive with worn flash also loose/corrupt blocks. In pinning down some RAM related bugs on my desktop, occasionally there would be a file system issue too.

 

Cloning Windows, unless done very carefully, has never worked particularly well for me, especially if (as I mentioned above) there's any amount of hardware issues going on at the same time.

 

I've literally gone from Win7 (c.2011) to Win10 1909 (restoring an old laptop) with all the Windows updates and such along the way, and didn't have these issues.

 

1 hour ago, Aree Soothsayer said:

I do NOT want to use the damned thing.

 

So no.

Running from the command line will give you a listing of what blocks it has lost, so you at least have an idea what's missing. Running it from the Windows GUI doesn't recover blocks by default.

 

chkdsk [X:] /f /r will attempt recovery, and if that fails, there wasn't any way you were getting at that data to begin with. chkdsk doesn't delete data; it's telling you somewhere between the file listing and the actual data, something isn't right (e.g. there isn't any data at the target, or the target isn't accessible).

[Aree Soothsayer]

1 minute ago, AbydosOne said:

All that's doing is checking the HDD-reported SMART information and running a benchmark or two. It really doesn't have any bearing on data integrity; it's more a metric for the drive's physical state. Sometimes degraded drives go on for quite a while (I have unimportant disks that are "technically failed" but still work fine) and others (especially SSDs) will just die without any SMART indication.

 

The only times I've ever had to deal with actual chkdsk issues have been where there was an underlying hardware issue. My first SSD had a buggy firmware that constantly lost blocks (until I updated it). I've had cheap flash drive with worn flash also loose/corrupt blocks. In pinning down some RAM related bugs on my desktop, occasionally there would be a file system issue too.

 

Cloning Windows, unless done very carefully, has never worked particularly well for me, especially if (as I mentioned above) there's any amount of hardware issues going on at the same time.

 

I've literally gone from Win7 (c.2011) to Win10 1909 (restoring an old laptop) with all the Windows updates and such along the way, and didn't have these issues.

 

Running from the command line will give you a listing of what blocks it has lost, so you at least have an idea what's missing. Running it from the Windows GUI doesn't recover blocks by default.

 

chkdsk [X:] /f /r will attempt recovery, and if that fails, there wasn't any way you were getting at that data to begin with. chkdsk doesn't delete data; it's telling you somewhere between the file listing and the actual data, something isn't right (e.g. there isn't any data at the target, or the target isn't accessible).

Thank you. You actually explained things to me. I'll look into things.

 

[Aree Soothsayer]

Well here are the results.

 

https://imgur.com/UPKVed1

[narrdarr]

That looks good.

But I think you need to run the c drive

So write it as

Chkdsk /f/r

Or chkdsk c : /f/r

[narrdarr]

Can't stop my phone from auto correcting to emoji

No space between the c and :

[Aree Soothsayer]

Checking file system on
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  335360 file records processed.                                                         
File verification completed.
  5951 large file records processed.                                    
  0 bad file records processed.                                      

Stage 2: Examining file name linkage ...
  202 reparse records processed.                                       
  436408 index entries processed.                                                        
Index verification completed.
  0 unindexed files scanned.                                         
  0 unindexed files recovered to lost and found.                     
  202 reparse records processed.                                       

Stage 3: Examining security descriptors ...
Cleaning up 838 unused index entries from index $SII of file 0x9.
Cleaning up 838 unused index entries from index $SDH of file 0x9.
Cleaning up 838 unused security descriptors.
Security descriptor verification completed.
  50525 data files processed.                                            
CHKDSK is verifying Usn Journal...
  35340648 USN bytes processed.                                                            
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  335344 files processed.                                                                
File data verification completed.

Stage 5: Looking for bad, free clusters ...
  49081268 free clusters processed.                                                        
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

 244198551 KB total disk space.
  47298492 KB in 196397 files.
    128724 KB in 50526 indexes.
         0 KB in bad sectors.
    446259 KB in use by the system.
     65536 KB occupied by the log file.
 196325076 KB available on disk.

      4096 bytes in each allocation unit.
  61049637 total allocation units on disk.
  49081269 allocation units available on disk.
 

[narrdarr]

Stage 3 looks like it cleaned up your issues.

 

If you want I would now run

sfc /scannow

Just to make sure your previous errors didn't affect windows file

[Aree Soothsayer]

5 minutes ago, narrdarr said:

Stage 3 looks like it cleaned up your issues.

 

If you want I would now run

sfc /scannow

Just to make sure your previous errors didn't affect windows file

I did and this was the results... so much I am lost.

 

CBS.log

[narrdarr]

47 minutes ago, Aree Soothsayer said:

I did and this was the results... so much I am lost.

 

CBS.log 5.87 MB · 1 download

I scrub through your log

It looks good

there were 2 errors pointed to  onedrive and windows store, but they have been repaired.

and

a couple warnings regarding overlapping permission, but they don't matter

you should be all set now

 

If you have other drives you can

chkdsk  (insert drive letter here): /r

 

now would also be a good time to defrag hdd(s) or trim/optimize sdd(s)

and

do windows updates and windows store app updates

 

anyways you should be all good now

[Aree Soothsayer]

22 minutes ago, narrdarr said:

I scrub through your log

It looks good

there were 2 errors pointed to  onedrive and windows store, but they have been repaired.

and

a couple warnings regarding overlapping permission, but they don't matter

you should be all set now

 

If you have other drives you can

chkdsk  (insert drive letter here): /r

 

now would also be a good time to defrag hdd(s) or trim/optimize sdd(s)

and

do windows updates and windows store app updates

 

anyways you should be all good now

Thanks, I had to look up what Trim means. Then more stuff to finally find out my windows is set to trim already.