SCSI Decoder

Updated -

About

SCSI error messages appearing in log files can many times be convoluted and non-trivial to understand. This tool is designed to help decode SCSI error messages and provide solutions to resolve issues more quickly and easily.

Usage

The user has the ability to parse SCSI error messages from both log files and/or a log file snippets. The app will parse all SCSI error messages and marshall each into the following fields:

SD: SCSI Device
SCSI Error Code: Hexadecimal error code
ASC: Additional Sense Code
ASCQ: Additional Sense Code Qualifier
Found: Number of times error was found

The user then has the ability to individually diagnose each SCSI error message. This diagnose action will return solutions that when clicked will open in a new browser tab.

Was this helpful?

We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Get notified when this content is updated

Follow

Comments

Subscriber exclusive content

An active Red Hat subscription is required to participate.

Log In

Failed to load page..

Failed to load resource: net::ERR_CONNECTION_TIMED_OUT https://ajax.googleapis.com/ajax/libs/angularjs/1.2.0/angular.min.js
Uncaught ReferenceError: angular is not defined redhat_access_search.js:23
GET https://www.google.com/ads/user-lists/990030321/?label=rxV4CN_35QQQ8dOK2AM&script=0&random=3225744493 net::ERR_TIMED_OUT google_remarketing.js?v=2.0.8:29
add_tag google_remarketing.js?v=2.0.8:29
(anonymous function) VM322:8
context.execCb require.js:1636
Module.check require.js:871
(anonymous function)

I posted the following log, but there seems no response.
Jun 17 19:53:12 datacenter kernel: sd 1:0:0:0: [sda] Unhandled error code
Jun 17 19:53:12 datacenter kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 17 19:53:12 datacenter kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 25 84 de 04 00 00 08 00
Jun 17 19:53:14 datacenter kernel: sd 1:0:0:0: [sda] Unhandled error code
Jun 17 19:53:14 datacenter kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 17 19:53:14 datacenter kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 25 84 de 04 00 00 08 00
Jun 17 19:53:16 datacenter kernel: sd 1:0:0:0: [sda] Unhandled error code
Jun 17 19:53:16 datacenter kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 17 19:53:16 datacenter kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 25 84 de 04 00 00 08 00

Gengsheng,

This tool is looking for a "SCSI error: return code" which the text you posted does not contain. This error code is the most important in identifying an appropriate solution. Below is an example:

Dec 31 18:14:40 n118277vaps2015 kernel: sd 1:0:0:0: SCSI error: return code = 0x08000002
Dec 31 18:14:40 n118277vaps2015 kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Dec 31 18:14:40 n118277vaps2015 kernel: sdc: Current: sense key: Illegal Request
Dec 31 18:14:40 n118277vaps2015 kernel: ASC=0x2 ASCQ=0x10