Hello,
This is my first post and I want to say thank you to all of you that help others to solve his problems. I'm having some troubles with the HD Sentinel 5.20 version. I have a server G8 360 with windows 2012 R2 server with 32Gb of ram a disk controller P822 and a disk enclousure D2700. The problem I have is that I can't run a surface test for more than 2 disks at the same time. I have 23 disks that hd sentinel recognize perfectly but when I run the surface test for the 23 disks the program opens the windows but It says that no response. Do you know where can be the problem?
Regards
Surface Test problem
-
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Surface Test problem
Thanks for your message and excuse me for the possible troubles.
However, I'm afraid I can confirm that this is possible.
Generally Hard Disk Sentinel (during the periodic disk status detection and accessing the disks) needs to wait for the controller(s) and disks to respond. While the detection is usually very quick (question of milliseconds only) sometimes such response (especially if the controller is busy and/or depending on the amount and model of hard disks, their connection) may take long time, even minutes.
Yes, when a controller is busy with processing many disks and performing multiple tests at the same time, it may respond even slower. Then further disk access and test selection may take longer time.
I'd recommend to try to select Disk menu -> Surface test and in that window, select multiple drives to test with the same type of test (for example read test). I'd recommend to do not select too many disks in this case.
If you use Report menu -> Send test report to developer option, I can check the actual response of the controller and configuration.
It may give ideas about how to optimize, improve the situation further.
However, I'm afraid I can confirm that this is possible.
Generally Hard Disk Sentinel (during the periodic disk status detection and accessing the disks) needs to wait for the controller(s) and disks to respond. While the detection is usually very quick (question of milliseconds only) sometimes such response (especially if the controller is busy and/or depending on the amount and model of hard disks, their connection) may take long time, even minutes.
Yes, when a controller is busy with processing many disks and performing multiple tests at the same time, it may respond even slower. Then further disk access and test selection may take longer time.
I'd recommend to try to select Disk menu -> Surface test and in that window, select multiple drives to test with the same type of test (for example read test). I'd recommend to do not select too many disks in this case.
If you use Report menu -> Send test report to developer option, I can check the actual response of the controller and configuration.
It may give ideas about how to optimize, improve the situation further.