Hi,
Looking through the forums and this seems to be closest to what I am facing.
https://www.hdsentinel.com/forum/viewto ... 32&t=12048
My system in running on Win Server 2016 with Raid 1 on both drives using AVAGO MR9361-8i.
Drive C: (Disk 0 & 1) is where windows is installed
Drive D: (Disk 2 & 3) It is a SEAGATE ST1200MM0009 and has no system files but only for file storage.
When I performed Short self-test on Drive D it will show a response of 0xFFFFFFFF and estimated time remaining will just stay at 1 minute and it never completes.
Next I tried Extended self-test and it still shows response of 0xFFFFFFFF but estimated time remaining is blank. I left it running and came back and check when elapsed time at around 11 hours. Left it and came checking an hour later and notice that my system has stopped responding and needed to reboot it manually.
Another thing I notice is that it shows lifetime writes of only about 289MB despite there is at least 200GB of data already written on the drive.
Short Self-test / Extended Self-test not completing
Short Self-test / Extended Self-test not completing
- Attachments
-
- overview.png (133.54 KiB) Viewed 3865 times
- hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Short Self-test / Extended Self-test not completing
Hi,
Thanks for the information.
Yes, as the Help describes:
https://www.hdsentinel.com/help/en/62_testfaq.html
"In some cases, these hardware tests (Disk -> Short self test, Disk -> Extended self test) are not available, not supported or they result in an error quickly even in relatively low number of problems. No further information is returned about the result, for example it is not possible to list the sector(s) which are damaged. In such case, an appropriate software testing method is required."
While we expect that if the hard disk / SSD suggests that the short/extended self test function is available, supported - sometimes it is not really working as should. For example, yes, as you can see the internal test-progress indicator may never changes so the test seems never advancing.
As suggested, in this case, it is better to use the Disk menu -> Surface test -> Read test function instead.
> Another thing I notice is that it shows lifetime writes of only about 289MB despite
> there is at least 200GB of data already written on the drive.
From the image, I do not see which Hard Disk Sentinel version you use. Some SAS SSDs provide the lifetime writes differently than should and require special attention to provide the real value. Many of such SAS SSDs have improved support in newer versions, so not sure if an update may immediately help in this case too.
If you use the latest version, I'd suggest to please use Report menu -> Send test report to developer option. Maybe you can use it multiple times, eg. once for a "base" and then a 2nd report after writing 10-20 GB data and waiting some time (eg. an hour to be sure) to allow the counters to update.
Checking the developer reports (and especially comparing them) can help to verify how the internal counters changed and if there is anything to modify/improve for this particular model too.
The report(s) also help in checking possibilities for the hardware self test too.
Thanks for the information.
Yes, as the Help describes:
https://www.hdsentinel.com/help/en/62_testfaq.html
"In some cases, these hardware tests (Disk -> Short self test, Disk -> Extended self test) are not available, not supported or they result in an error quickly even in relatively low number of problems. No further information is returned about the result, for example it is not possible to list the sector(s) which are damaged. In such case, an appropriate software testing method is required."
While we expect that if the hard disk / SSD suggests that the short/extended self test function is available, supported - sometimes it is not really working as should. For example, yes, as you can see the internal test-progress indicator may never changes so the test seems never advancing.
As suggested, in this case, it is better to use the Disk menu -> Surface test -> Read test function instead.
> Another thing I notice is that it shows lifetime writes of only about 289MB despite
> there is at least 200GB of data already written on the drive.
From the image, I do not see which Hard Disk Sentinel version you use. Some SAS SSDs provide the lifetime writes differently than should and require special attention to provide the real value. Many of such SAS SSDs have improved support in newer versions, so not sure if an update may immediately help in this case too.
If you use the latest version, I'd suggest to please use Report menu -> Send test report to developer option. Maybe you can use it multiple times, eg. once for a "base" and then a 2nd report after writing 10-20 GB data and waiting some time (eg. an hour to be sure) to allow the counters to update.
Checking the developer reports (and especially comparing them) can help to verify how the internal counters changed and if there is anything to modify/improve for this particular model too.
The report(s) also help in checking possibilities for the hardware self test too.