False Numbers in Reallocated Sectors Count

[voyager62]

I thought this was a one time fluke on a single drive, but now every Seagate drive reports imminent failure and zero health because of this bug.

HDS reports that the Reallocated Sectors Count Attribute has failed even though no sectors have even been reallocated. HDS used to show 10 100 100 for Seagate Drives, but now it shows 140 100 100. Sometimes it will show the proper value, but most of the time it shows that SMART has failed without 1 single sector being reallocated.

I've verified that this bug only exists in HDS by using HD Tune Pro. It properly reports 10 100 100 for the same drives HDS says have failed.

I'm tired of seeing flashing red circles when there's absolutely nothing wrong with my drives.

[hdsentinel]

If I'm correct, we discussed that the issue is NOT really related to the hard disk itself or Hard Disk Sentinel at all.

The problem is that on your system somehow the THRESHOLD value Hard Disk Sentinel got come from a different hard disk: Threshold = 140 for this attribute is related to WD drives.
So somehow when Hard Disk Sentinel detects the Thresholds of the attributes, it got the Threshold for the other, WD drive, instead of the correct Seagate drive.

This may be a driver issue or similar, depending on the actual configuration.

Generally Hard Disk Sentinel has filters for such issues (as this may happen, independently from hard disk drives or used software) but it seems somehow it got the wrong error-level threshold, which caused the confusion.

Please use Report menu -> Send test report to developer option now, when you see similar, as then I can check the current situation.

[hdsentinel]

> I'm tired of seeing flashing red circles when there's absolutely nothing wrong with my drives.

From the developer report, I can check which detection provides false thresholds and how to avoid that particular detection in your case to improve the situation.

Until that, there are two different ways to stop the "flashing red circles":

- open Configuration -> Thresholds/Tray Icon page. On that page, you can see "Display hard disk health sign on tray icon" and you may notice that the "Bad: Below xx%" is enabled (this is the default, to increase attention about a disk with low health). Uncheck that box - and there will be no more "flashing" (alternating display of disk status symbol and temperature)

OR

- open S.M.A.R.T. page of the hard disk and in the line of the Reallocated Sectors Count attribute, unselect the "Enable" checkbox. This way that particular attribute will not be used in determining health, so the drive health will be reported as 100% so there will be no flashing icon (the bottom graph on the Overview page still shows the lower value (as it displays the daily lowest value) but then, from tomorrow it will show higher value).

And from the developer report, things can be checked and improved, hopefully sooner.

[voyager62]

If I'm correct, we discussed that the issue is NOT really related to the hard disk itself or Hard Disk Sentinel at all.

I just checked the questions section and you did reply about the threshold, but for some reason I didn't get an email back in May that there was a new post.

I just started up HDS and everything is green and 100% health. The problem started before I was attaching other drives and the drive letters changed. One thing I've had to do twice that I've never had to do before is erase all the drive mount registry setting using mountvol. Sometimes I'd attach a drive and the letter would never show up and there were strange things happening.

I've been attaching EXT4 formatted drives from my NAS and have Paragon's Linux File System for Windows installed and am using that to read the EXT4 drives, but since Netgear uses BTRFS, I also have WinBTRFS installed for those drives. It seems to only work for a short period before the drive stops responding.

What is the compatibility level between HDS and these Linux drivers? Could this be causing some of the problems?

[voyager62]

I just attached the RAID box and everything is back to my initial post. Drive letters haven't changed. the RAID box was assign letter J, the last letter for my physical drives. I do have U-Z mapped as virtual drives from my NAS though.

Everything was fine, like the problem didn't exist until I attached my RAID box and now 3 of the 5 Seagate drives (1 Seagate Desktop Expansion, 1 Seagate Backup Plus and 1 Samsung D3 Station) are displaying red circles with zero health. It happen that fast, no reboot nothing detached, just attached the RAID box (which is correctly showing the 4 internal drives).

[voyager62]

I sent another developer report. I realize that one of the drives in my RAID box has pending sectors. I'm trying to empty it so I can replace the drive.

[hdsentinel]

> What is the compatibility level between HDS and these Linux drivers? Could this be causing some of the problems?

I can confirm that Linux drives causes absolutely no problems at all.
Generally Hard Disk Sentinel works independently from the current file system, so can diagnose, monitor, detect / reveal / fix status on hard disks formatted under Linux (or MAC) or even unformatted / unpartitioned drives.

As Windows do not recognise these partitions, no drive letter assigned and files could not be read/written, but as Hard Disk Sentinel works at lower (sector) level, it can analyse those drives and also the surface test functions can be used on such drives.