Thanks for the file you sent. I examined, looks quite interesting.
It seems it is possible to get the list of the disk drives on the controller and the communication with the first drive started - but then the controller issued numerous errors, so then accessing any further disk is not possible (both for reading or status detection).
I suspect the controller stuck in a bad state as then it is no longer working correctly, no longer provides any access to disks - and this results that it does not work correctly again until a complete restart.
Not 100% sure if the issue is related to the disk model (you mentioned in your email) or the controller itself. Would be nice to investigate further.
If possible, please try (after deleting the created text files every time, just to have fresh clean start) create and send some similar reports in different situations, for example
- once immediately after bootup, when everything seems working
- then later, eg. after 10-15 minutes (when things may be still working too or problems started)
- then when things no longer working
as comparing them may give some additional thoughts, ideas about what happened. From those, I can check the response of the other disks and possible errors generated by the RAID controller and verify if the communication always stop at the very same disk and very same detection step (or different disk / different step).
This may give further ideas to investigate the situation.
> I can't simlply run it and It needs to be killed from task manager
Generally Hard Disk Sentnel (during startup and during periodic detection) waits for the disk controllers and drives to respond. If there is no response from the RAID controller (if it "stuck" somehow) then yes, this can happen: then the software seems "not responding" (or even does not show up when started) because it never receive answer from the hardware. I'm afraid this is "normal" in this situation.
Yes, inspecting some more situations, reports generated in different conditions would help in investigating this really weird situation and hopefully there could be a workaround. Sorry for the troubles and thanks for increasing attention to this case.