The LSI log info code decodes to say that this is an IO Aborted issue, the error is most likely by a bad cable but can also be due to a bad port. I suggest checking the cables first as they are cheaper to replace
If it's a SAS disk you can look at the SAS counters (depending on the OS how you look at them) and see on which cable/port/phy the issue exists.
I've written a tool to decode the LSI log info codes to help troubleshoot such problems, you can see relevant links to the log info at:
LSI SAS controller timeout issues with 5.2-5592.2
in Archives
Posted
The LSI log info code decodes to say that this is an IO Aborted issue, the error is most likely by a bad cable but can also be due to a bad port. I suggest checking the cables first as they are cheaper to replace
If it's a SAS disk you can look at the SAS counters (depending on the OS how you look at them) and see on which cable/port/phy the issue exists.
I've written a tool to decode the LSI log info codes to help troubleshoot such problems, you can see relevant links to the log info at:
* http://blog.disksurvey.org/knowledge-base/lsi-loginfo/ -- pre decoded list
* https://github.com/baruch/lsi_decode_loginfo -- command line toool that essentially generated that list and can help with the unknown codes
LSI never fully documented openly all the codes so the list I have is incomplete.
Hope this helps and let me know if you need some more help figuring it out.