I noticed these errors did not generate in HD Sentinel unless I started the Basic Tests in SeaTools. I discovered that there is some kind of conflict or anomaly between SeaTools and HD Sentinel and this model of Seagate drive. This would show clearly what "raw" information we got from the hard disk and how to avoid: both displaying that and also to make the storage system more stable. The best would be to "catch" an event and send developer report exactly when similar problems detected (which may result in temporarily lower health % too). Maybe updating the driver can help to prevent such issues in the future. This way it is possible to verify the "raw" response of the hard disk and check the disk controller (chipset) and its driver.
I'd recommend to use Report menu -> Send test report to developer option. Hard Disk Sentinel has special filters to prevent invalid status displayed when such problematic chipsets (and drivers) used - but sometimes it is possible that invalid status received from the driver and displayed (and errors logged according that). This may also cause degraded performance / stability too.Īlso in some cases, the disk controller (chipset) and its driver can cause that. It is possible that somehow the connections are now not perfect - and this result in the invalid status information which sometimes provided when the hard disk status accessed. You wrote that the configuration changed - and problems started after that. If the self tests (Disk menu -> Short self test, Extended self test) complete without errors, it confirms that - as these tests run "inside" the hard disk, without transferring higher amount of data between the hard disk and the computer. Many times the operating environment (cables, connections, disk controller, chipset, driver, etc.) are in the background - as these can affect how the hard disk is working and how its status can be detected. Usually such issues are not (or not completely) related to the hard disk itself. We can consider these as "false alarm" - but we can also consider these as signs of something wrong, something is not stable in the operation of the storage subsystem. page shows no such issues, it means that at the time of a detection, Hard Disk Sentinel may got incorrect status information. If the drive seems working correctly and the S.M.A.R.T. Generally such errors detected if the software gets those values (which may indicate errors) from the hard disk drive. Thanks for the information and the details !