Yes, in case of hard disk problems, this is completely normal.
Chkdsk usually does not find or repair problems with the hard disk, but finds and "repairs" problem only with the logical volume / partition. Even if sounds surprising, this may be independent form the actual hard disk status:
chkdsk may never find problems (with the logical volume/partition) even if the hard disk is dying - and may find problems on completely perfect hard disk.
The Support -> Knowledge Base -> Hard Disk Cases -> Hard disk case: weak sectors (
http://www.hdsentinel.com/hard_disk_cas ... ectors.php ) page shows exactly a such situation: if weak sectors reported, chkdsk may try to "fix" them by isolating the sectors.
But this is not a real fix, as (for example)
- if you re-partition the hard disk / re-install the system, the problematic sectors will be used again and may cause data corruption / data loss
- if you backup/restore (mirror) the drive to a new one, the "bad sectors" created by chkdsk will be also mirrored to the new, perfect hard disk, even if that shows 100% health with no problems.
So chkdsk should not be used on a hard disk drive with problems. Data recovery companies may also not recommend this - as this may cause even more corruption of the logical volume / partition, resulting more loss of data.
> I initiated a Disk Check from within Windows Explorer, checking both boxes (Automatically fix errors and Attempt recovery of bad sectors).
This is 100% same as chkdsk does, so there is no difference in the results as well.
> Last night I ran HD Sentinel's READ test, it reported no errors.
This sounds good. Then it seems the hard disk already found the problematic sectors, reallocated them (if required) and now the hard disk status seems stable. Even if it's not perfect, the drive may still be used, but if it's health is low, then I'd recommend only for secondary storage (to not store important data on it) and immediate backup upon any, even minor new problem(s).
> Confuses me that CHKDSK (after finally completing) reported no further errors,
Yes. This is completely normal.
Bad sectors found and "fixed" by chkdsk are still used by the hard disk and can cause problems.
In contrast "real" bad sectors (if these reported in the text description in Hard Disk Sentinel) are no longer used by the hard disk: they are already reallocated. So the spare area is used for all reads and writes targeting those bad sectors. This means that no software access those sectors: so chkdsk should show no problems - and also the READ test in Hard Disk Sentinel should show no problems (if all such sectors already fixed this way).
This is good, as this way you can be sure that the original (bad) area does not contain important data and can't risk data loss.
This is why the detected and reported bad sectors can NEVER cause problems, regardless of their position because that problematic area is never used any more.
This is why manufacturers (really shame but work this way) "allow" some bad sectors and may not offer warrantly replacement, just if the amount of bad sectors reach a (usually very high) threshold level.
Also when there are high number of bad sectors on the hard disk and its health is low, there is high chance that new and new problems will occur, new and new bad sectors will be reported. These (and the reallocation procedure) may cause performance decrease (in best case), system instability - but can cause system freezes/sudden restarts/data corruption or data loss.
> and HD Sentinel's READ test reported no errors, so why does the Overview tab report the errors mentioned above,
> but if there are indeed bad sectors I'd like to mark them to not be used (HD Sentinel can do that, right?
Exactly for this situation, if you confirm that all previous bad sectors are already fixed, Hard Disk Sentinel has a mechanism to clear the error-counters.
Hard disk drives record problems found in their lifetime and these are not cleared by default.
But if you used the test, verified that the status is stable, it is possible to "acknowledge" the errors detected and reported. This way the problems will be removed from the text description and the health also restores (ideally to even 100%) until no new problems detected.
So then Hard Disk Sentinel shows only such new problems / degradations.
See Support -> Frequently Asked Questions ->
How to repair hard disk drive? How to eliminate displayed hard disk problems?
(
http://www.hdsentinel.com/faq_repair_ha ... _drive.php )
which exactly describes this.
> But HOW?, if I can't get the read+WRITE+read test to run???
For write tests, it is required to lock the hard disk for exclusive use.
But if any other software has one (or more) open files / folders on the hard disk, then it is not possible to lock the hard disk for exclusive use.
Please try to close other software which may use the affected hard disk.
While Hard Disk Sentinel works differently (performs disk low-level testing instead of testing only partitions) this is slightly similar to chkdsk: if you enter chkdsk D: /F (assuming D: is on the affected hard disk) chkdsk will show that it can't perform the test as the drive can't be locked/unmounted.
This is also caused by an other software / tool which has open file(s) or folders on that drive.
This can be antivirus software, Windows indexing software - or even a hidden malware.