Generally, the issue may be related to the actual disk (RAID) controller where the hard disks are connected.
Some of such controllers (more precisely the drivers) may not provide real, accurate information when the hardware self test started.
This can cause that
- the disk test seem stuck at a point (seem no advance), the test seem not completes, the progress bar seem stuck at center
- the disk test seem complete very quickly
- the disk test can be started, but when Hard Disk Sentinel sends the cancel command, the test may still seems running.
These are not rare issues, especially when drives configured as RAID, as then some RAID controllers may not allow these kind of special tests (which test the drives indepependently in the array, not together as an array).
Generally, in such situations (as described in the Help), it may be better to perform the Disk menu -> Surface test -> Read test, which will perform complete testing of the array.
If you use Report menu -> Send test report to developer option, I can check the actual disk controller, the driver version, the "raw" details provided when Hard Disk Sentinel detects the self test status.
You may even use Report menu -> Send test report to developer option two-three times, eg. in normal situation (when test is not running), some when drive(s) are being tested (and you click on the Background button to let it run) and after you try to cancel the test.
This way I can compare them, verify the reported information and check the possibiliies, for example if it's possible to improve anything (for example by a driver version update).