Jump to content
Covecube Inc.
  • Announcements

    • Christopher (Drashna)

      Login issues   11/07/17

      If you have issues with logging in, make sure you use your display name and not the "username" or email.  Or head here for more info.   http://community.covecube.com/index.php?/topic/3252-login-issues/  
    • Christopher (Drashna)

      Getting Help   11/07/17

      If you're experiencing problems with the software, the best way to get ahold of us is to head to https://stablebit.com/Contact, especially if this is a licensing issue.    Issues submitted there are checked first, and handled more aggressively. So, especially if the problem is urgent, please head over there first. 
  • 0
xazz

Errors reported by Scanner, but not found by ChkDsk

Question

Hi

 

I'm evaluating scanner and disk pool. I have created a file server with six external drives connected by USB.

 

Scanner has reported for one of my drives: "Damaged"
 
Hard disk is unable to read 2822530 sectors
 
It did not complete the scan, because I cancelled it and ran:
 

chkdsk r: /f


Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

The surface scan checks to see if the sector is readable.  CHKDSK looks to see if there is file system damage.  These are not the same thing, and are VERY different.   You can have a disk with a lot of unreadable data, but the file system is still intact.  

 

In fact, you'd have better luck compare this if you ran "chkdsk R: /b", as this is closer to the surface scan.

 

 

 

That said, in the StableBit Scanner UI, right click on the disk in question and run the "Burst test".  if this comes back with issues, then you may have a controller or cable issue, rather than actual damage. 

But if this comes back clean, the disk is probably having severe problems and should be replaced.  

Share this post


Link to post
Share on other sites
  • 0

I forced it to recheck, and the errors seems to have gone away. At this stage, the drive is only 12% checked, and none of the others at all. I expect this is because it is avoiding scanning while DrivePool gets fully balanced and duped for the first time.

 

Will let you know if I see any other quirks.

Share this post


Link to post
Share on other sites
  • 0

If the errors are intermittent, then this may be a communication problem with the drive.  It may be worth running a burst test overnight, and see if that comes back with any issues.

 

Otherwise, if this continues to occur, let me know.

 

 

As for the scanning, by default, it only scans a single disk per controller.  this is to prevent the program from saturating the controller and causing performance issues. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×