Page 1 of 1

Scheduled short self test results reported as long self test

Posted: 2016.08.20. 11:53
by Tiiazllm
If I create an operation to perform a short self test on all HDDs - and then click "start now" the results of that short test will be shown under the "Information" tab of any HDD as being the results of "Last Extended Self-test" with 3 fields of "successfully completed", date/time, and "2 minutes" as the duration (it normally take 6+hrs to perform)

This is on 4.71.3 Pro, registered

Regards

Re: Scheduled short self test results reported as long self

Posted: 2016.08.21. 19:52
by hdsentinel
Thanks for increasing attention about this situation and sorry for the troubles.

Is Hard Disk Sentinel Pro running (active) when you start the self test by that project?
What happens if you simply start Disk menu -> Short self test on any hard disk from the software, do you see similar - or then the result is recorded to the proper (short self test) field?

Generally when short / extended self test started, hard disks only provide a progress indicator and result (success or fail) but no nformation about WHICH test actually started. Hard Disk Sentinel (when the test starts) saves which test started and the test result is saved to the appropriate test type when the test finished.
It seems somehow when you start short self test (maybe only if you start by a project) the results saved as it would be an extended self test.

As these self tests (how they run and their results) may be affected by the current disk controller / motherboard and its chipset, it is possible that the current combination may cause this behaviour.

The best would be if you can
1) use Disk menu -> Short self test to run a short self test on one of the affected drives
2) use the Background button in the small window to send the test to background
3) use Report menu -> Send test report to developer option while the test is still running.

This way it is possble to check the actual situation, verify the controller / driver / hard disk combination and also I'll try to reproduce the issue, investigate it with more details and improve in all possible ways.