All of a sudden HDS is reporting an imminent failure on a hard drive that has no reallocated sectors, but HDS says the number of reallocated sectors mean it's going to fail soon. I've attached screenshots showing the worst and last values are perfect 100's, but the Threshold for the value is reporting 140. On other similar drives it's only 10. You said before this isn't a problem with HDS, as far as the Total LBA Written, which can't be true. It's off your chart. But how can I fix the threshold for this value because setting an offset won't work there? I don't want to see the red circle flashing unless I have a hard drive that actually WILL fail soon.
Also, the H/W RAID0 (Striping) drive has returned instead of displaying the 4 individual drives. I've sent a bug report.
> I've attached screenshots showing the worst and last values are perfect 100's, but the Threshold for the value is reporting 140.
> On other similar drives it's only 10.
Yes, I'm afraid in some rare situations, this is possible: when thresholds detected, somehow Hard Disk Sentinel got incorrect thresholds.
Sometimes all thresholds are zeroes and in very rare situations, the thresholds may be related to a completely different disk drive. 140 is related to WD drives, so I suspect the thresholds of an other WD drive provided when Hard Disk Sentinel detects the thresholds for this disk drive.
This issue generally happened with older drivers for Intel SATA controllers where both disk drives connected to SATA channel.
In such situations, updating the SATA controller driver helped in all cases.
Now as both disk drives are USB drives, I suspect there may be a compatibility issue of the USB controller (or similarly its driver) itself.
Do you have USB hub for these devices? In theory that should be no problem, but sometimes may cause troubles.
Personally I'd try to verify if there is an updated driver available for the USB controller and/or chipset in general.
Hopefully by that, the proper thresholds can be detected, so then the health will be 100% again.
The health graph on the bottom will today show the low value (as it shows the daily lowest health) but from the following day, 100% should be displayed there too.
If this does not help, I'd try to connect the disks differently, swapping cables, connections and without USB hub (if now used).
Maybe for a test, I'd try to connect one or more drives to USB 2.0 connection also, just to verify if things may happen there or not.
> You said before this isn't a problem with HDS, as far as the Total LBA Written, which can't be true. It's off your chart.
Sorry, but I do not really understand ....
> But how can I fix the threshold for this value because setting an offset won't work there?
Yes of course. The Thresholds need to be fixed outside the software, by the way where all information could be properly detected.
Incorrect drivers may sometimes provide incorrect values and can causes false alarms.
Sorry for that, generally Hard Disk Sentinel has filters against such invalid response but sometimes things can happen... Maybe in this case, additional filters need to be used.
The Offsets generally designed to correct/modify the Data field. These have no effect on Threshold/Value fields. You may disable the attribute checking at the "Enable" column if you prefer to ignore it completely. But this is not the best solution in this case: the change of the USB controller / or driver update is the preferred method to fix.
> I don't want to see the red circle flashing unless I have a hard drive that actually WILL fail soon.
I completely agree, this is the purpose.
> Also, the H/W RAID0 (Striping) drive has returned instead of displaying the 4 individual drives. I've sent a bug report.
Thanks. Just examined the report and yes, now I see that the RAID controller chip does not respond to the detection at all.
I'm afraid this is out of my control: I suspect this is also related to the USB controller (or its driver). It may be confused and can cause improper operation after some time.
If I'm correct, after complete restart, things will work again without problems: the RAID controller will work again and the status of the drives can be accessed again.
I'm examining the report with more details and comparing with the previous "good" state, both related to the Thresholds and the RAID detection.
