Page 1 of 1
Programm hangs very often
Posted: 2022.03.09. 09:41
by righter
Hi
I've created the following server for testing hard disks:
Windows Server 2019
LSI SAS 9240-4i controller with a SATA SSD on a RAID0 volume as system disk
Adaptec 5405 controller in JBOD mode for testing Hard Disks
registered HDS Pro 6.00 12540
now the program hangs very often.
In Example if I have inserted 4 Disks and I start the surface test on all these disk I have to wait 15 minutes until all test windows appears and start.
Also the app hangs very often -> windows reports then, app not responding.
Is there a way to fix that?
Re: Programm hangs very often
Posted: 2022.03.09. 15:19
by hdsentinel
Hi,
Thanks for your message and sorry for the possible troubles. However, I can confirm that there is absolutely no "hangs" or similar: Hard Disk Sentinel is simply waiting for the disk drives and storage devices to respond when Hard Disk Sentinel attempts to identify them and check basic information first (disk model, manufacturer, capacity) and if supported, then health/temperature and further details.
The detection happens more quickly/more frequent if you start test(s) - and especially if you attempt to run multiple tests: the Hard Disk Sentinel can't do anything else just constantly discussing the drives and the RAID controllers.
While the status detection is generally quick, depending on the number of disks (and their connection) it may take longer time. For example SAS drives usually provide status information much slower than SATA/IDE drives or NVMe SSDs. Some other hardware (eg. SAS backplanes) can also affect the detection too.
Also some RAID controllers (and especially if you attempt multiple tests at the same time on them) can cause that their response become very slow - and while Hard Disk Sentinel performs the detection, it seems "not responding" as it is waiting for the hardware. However, it does not mean that it "hangs" or so.
I recommend to please try to
- adjust the detection frequency on Configuration -> Advanced Options page to perform less frequent status detections
- try to start disk tests one by one and observe how many drives could be safely tested. This is more related to the bandwidth requirement of the controllers, not really related to CPU/RAM or other resources.
Also if you use Report menu -> Send test report to developer option, I can check the actual situation/configuration and verify the response time of the drive(s) / controller(s) and examine if there is anything to improve both in Hard Disk Sentinel and by general (for example by a driver update for the actual controller).