Jump to content
  • 0

File System damaged - yet there are no errors in chkdsk or windows chkdsk. I even ran >chkdsk t: /f /r for a week!


StablebitFan87

Question

Hello! I am running the latest version of Stablebit Scanner. I just purchased it two weeks ago, and I let it scan all my drives. The only drive that gave me an error is my brand new 10TB Western Digital drive. It is saying "File System Damaged". 

So I read another forum post here with someone who had the same issue. So I ran >chkdsk t: /f /r on the drive. It took over a week!  And here's what it said:

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

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

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  14 data files processed.

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

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

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

   9537533 MB total disk space.
     72796 KB in 10 files.
        76 KB in 16 indexes.
         0 KB in bad sectors.
    364251 KB in use by the system.
     65536 KB occupied by the log file.
   9537107 MB available on disk.

      4096 bytes in each allocation unit.
2441608703 total allocation units on disk.
2441499423 allocation units available on disk.

C:\WINDOWS\system32>

So after doing that, I forced Stablebit Scanner to re-scan the drive. And I got the exact same error. 

I even tried re-formatting the drive. Still the same error. 

This is driving me crazy. Any advice as to what I can do to fix this? Hopefully it does not require running chkdsk t: /f /r since that took over a week!
Thanks in advance for any help you can provide. 

Link to comment
Share on other sites

13 answers to this question

Recommended Posts

  • 0

To make sure, you're on the beta that I linked?  
If not, use that beta specifically, not the one linked on the stablebit.com site. 

As for an email, it wouldn't. It would basically have to send a notification for each new drive.   Etc. 
There are two issues that we've seen: 

  1. The settings files getting corrupted
  2. the Disk ID changing (it SHOULD NOT, but it has)

 

If this is still happening, then please head to https://stablebit.com/Contact

Link to comment
Share on other sites

  • 0
On 5/16/2019 at 9:52 PM, Christopher (Drashna) said:

To make sure, you're on the beta that I linked?  
If not, use that beta specifically, not the one linked on the stablebit.com site. 

As for an email, it wouldn't. It would basically have to send a notification for each new drive.   Etc. 
There are two issues that we've seen: 

  1. The settings files getting corrupted
  2. the Disk ID changing (it SHOULD NOT, but it has)

 

If this is still happening, then please head to https://stablebit.com/Contact

Yeah I am using the beta from your link. 

So you want me to contact you at the email? And do what, link this thread? 

Thanks in advance! Great program besides this glitch

Link to comment
Share on other sites

  • 0

I hope its OK to add on here? Or should I start a new thread?

I have this same problem. 24 disks and suddenly Scanner thinks half of them Windows has marked dirty. Chkdsked 4 and its clear Scanner is smoking crack, so I came here and found this topic.

If I don't want to use the beta, can I safely ignore the warnings? Are there any dangers to my data besides the obvious (that Scanner will not be able to tell me when my drives are dirty now)?

Link to comment
Share on other sites

  • 0

For anyone still seeing this, please update to the latest beta.  There is a bugfix for some ... very odd responses that we've seen lately.  It should fix this issue, even if it is to "not scan the drive for a while".

http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3259_BETA.exe

Link to comment
Share on other sites

  • 0
On 8/23/2019 at 11:23 AM, mr_yellow said:

Hi,  just wondering if there’s a newer beta to try?  I’m on 2.5.4.3216 and I have this damaged file system issue on two drives. 

Thanks

Linked right above your post, there is

http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3259_BETA.exe

 

6 hours ago, RONtiour said:

After drive scanner 3259 Beta continued to report damage and during a sync snapraid encoutered an error which implies certain files were corrupt (Unexpected Windows error 1392), I took the drives offline and ran another ChkDsk /R.

3 days later, 0k in bad sectors found

I'm sorry to hear that.  And ... well, it may not be a false positive then.  :(

Also, the CHKDSK pass doesn't run the same sort of check.  It looks for bad sectors, and attempts to remap then.  The surface scan is a block by block read of the disk, looking for any sectors that have issues reading.    If the surface scan comes back with the same sectors repeatedly, then you most likely do have a problem with the disk.

However, if you're not seeing it happen on the same sectors, it may be a communication problem.  In this case, running the "Burst test" from StableBit Scanner may identify that. 

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...