There's not a tool I'm aware of for that, however, I'm happy to share how we did it. We would export the PERC log directly from the PERC using OpenManage or the iDRAC. That log has all the relevant information. PD would mean physical disk, though PD20 would refer to the backplane. The log may have sense keys. I find the link below helpful for finding what the sense keys are reporting.
Thanks for the reply. I do not normally run OMSA on this machine, but I did so I could export the logs as you suggested. While doing so, I see OMSA actually logs slightly different messages to syslog:
Jan 1 11:06:16 linux Server_Administrator: 28975 2095 - Storage Service Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Enclosure 0:1 Controller 2, Connector 0
(this is not the same as the megaraid sas messages, as, if I am interpreting this correctly from the link you provided a sense key 5 code 24 is "Illegal Request - invalid field in CDB (Command Descriptor Block)" which is likely due to some uncertified drives in the enclosure and thus different from the other message I see periodically.)
Unfortunately the exported log was not much help. According to my syslog the last message today was thrown at midnight and my exported log doesn't go back that far (probably due to the 5/24's which although informational in nature still take up log space.
In the interim I guess I'll have to wait for another megaraid message to be thrown to see if OMSA interprets the sense code and qualifier differently to give me a clue.
Dell-DylanJ
4 Operator
•
2.9K Posts
0
January 1st, 2021 06:00
Hello,
There's not a tool I'm aware of for that, however, I'm happy to share how we did it. We would export the PERC log directly from the PERC using OpenManage or the iDRAC. That log has all the relevant information. PD would mean physical disk, though PD20 would refer to the backplane. The log may have sense keys. I find the link below helpful for finding what the sense keys are reporting.
https://dell.to/2L9nBQ3
Mike Deignan
1 Rookie
•
31 Posts
0
January 1st, 2021 15:00
Thanks for the reply. I do not normally run OMSA on this machine, but I did so I could export the logs as you suggested. While doing so, I see OMSA actually logs slightly different messages to syslog:
Jan 1 11:06:16 linux Server_Administrator: 28975 2095 - Storage Service Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Enclosure 0:1 Controller 2, Connector 0
(this is not the same as the megaraid sas messages, as, if I am interpreting this correctly from the link you provided a sense key 5 code 24 is "Illegal Request - invalid field in CDB (Command Descriptor Block)" which is likely due to some uncertified drives in the enclosure and thus different from the other message I see periodically.)
Unfortunately the exported log was not much help. According to my syslog the last message today was thrown at midnight and my exported log doesn't go back that far (probably due to the 5/24's which although informational in nature still take up log space.
In the interim I guess I'll have to wait for another megaraid message to be thrown to see if OMSA interprets the sense code and qualifier differently to give me a clue.