HDS Flooding System Log with Failures on OCZ NVME

[Mr_Resistor]

Upgraded to the 4.71.10 (8128) Beta to get monitoring of my OCZ (Toshbia) RD400 NVME drives. I did not see these errors before loading this so I'm pretty sure HDS is the source.

QTY 2 Toshiba OCZ RD400 512 GB (RVD400-M22280-512G-A)

System is running Win10 Pro, 64GB Ram, Dual octocore Xeons.

1/21/2017 8-00-29 AM Warning ocznvme Request failed on \Device\0000006c
1/21/2017 8-00-29 AM Warning ocznvme Request failed on \Device\0000006b
1/21/2017 7-55-23 AM Warning ocznvme Request failed on \Device\0000006c
1/21/2017 7-55-23 AM Warning ocznvme Request failed on \Device\0000006b
1/21/2017 7-50-20 AM Warning ocznvme Request failed on \Device\0000006c
1/21/2017 7-50-19 AM Warning ocznvme Request failed on \Device\0000006b
1/21/2017 7-45-16 AM Warning ocznvme Request failed on \Device\0000006c
1/21/2017 7-45-16 AM Warning ocznvme Request failed on \Device\0000006b
1/21/2017 7-40-11 AM Warning ocznvme Request failed on \Device\0000006c
1/21/2017 7-40-10 AM Warning ocznvme Request failed on \Device\0000006b
1/21/2017 7-35-08 AM Warning ocznvme Request failed on \Device\0000006c
1/21/2017 7-35-08 AM Warning ocznvme Request failed on \Device\0000006b
1/21/2017 7-30-02 AM Warning ocznvme Request failed on \Device\0000006c
1/21/2017 7-30-02 AM Warning ocznvme Request failed on \Device\0000006b

[hdsentinel]

Thanks for your attention and excuse me for the possible issue.
Generally there should be no problem with the detection, it should not cause any performance or compatibility issues. I wonder why the driver logs such during the detection cycles.

Can you pleas use Report menu -> Send test report to developer option? Then I can examine the current NVMe driver, its "raw" response and investigate the situation, examine the possibilities.

You may adjust the detection frequeny at Configuration -> Advanced options page, so then there should be less frequent detections (less entries - if they are really and surely related to accessing the NVMe SSD).

Just to be 100%, sure, can you please check:

1) start a command prompt (CMD.EXE)
2) enter

wmic path Win32_PnPSignedDriver where "pdo like '%0000006b" get devicename,friendlyname,pdo

and

wmic path Win32_PnPSignedDriver where "pdo like '%0000006c" get devicename,friendlyname,pdo

just to confirm that these devices are really, surely related to the NVMe SSD - or maybe different device(s).

Thanks!

[Mr_Resistor]

Logs uploaded. Updated to 5.00 pro and still doing it. I'll slow down the detection frequency to eliminate some of the "noise"

Thanks, for investigating.

[hdsentinel]

Thanks for the report you just sent.

Excuse me for the troubles. As I did not receive update / report in the past weeks, I can confirm that in version 5.00 nothing changed here, so it may be normal that things working similarly.

I examined the report and I saw that RAID controller card is also used. Not sure, but it is possible that the combination of that card and the NVMe SSD is causing the troubles as with the single SSD, could not reproduce and I did not receive information / message about similar from other users.

I'll perform detailed investigation and attempt tests. I'll also send information about what to check - just to verify, examine the situation and try to improve in all possible ways.