Jump to content
Covecube Inc.


  • Posts

  • Joined

  • Last visited

StablebitFan87's Achievements


Newbie (1/3)



  1. 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
  2. Unfortunately this issue cropped up again on a different drive. This with the Beta version. Any ideas what's up? And why didn't I receive an e-mail/text when this error occurred?
  3. 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.
  • Create New...