help decoding aacraid errors (3.10.40 kernel)

Hello.

I'm using 3.10.40 kernel with adaptec 3405 and unfortunately I'm getting I/O errors and dmesg errors like below. Is there a howto how to decode these errors or what these actually mean?

Some details, including full dmesg output at
http://ixion.pld-linux.org/~arekm/p2/web3-adaptec-problem/
eg
http://ixion.pld-linux.org/~arekm/p2/web3-adaptec-problem/dmesg.txt

That doesn't seem to be hard disk error (at least I don't see any bad errors from arcconf tool).

[3757350.671843] sd 0:0:2:0: [sdc] CDB: 
[3757350.671844] cdb[0]=0x28: 28 00 00 a0 2c a8 00 00 08 00
[3757350.671856] sd 0:0:2:0: [sdc] Unhandled sense code
[3757350.671858] sd 0:0:2:0: [sdc]  
[3757350.671860] Result: hostbyte=0x00 driverbyte=0x08
[3757350.671862] sd 0:0:2:0: [sdc]  
[3757350.671863] Sense Key : 0x4 [current] 
[3757350.671866] sd 0:0:2:0: [sdc]  
[3757350.671868] ASC=0x44 ASCQ=0x0
[3757350.671870] sd 0:0:2:0: [sdc] CDB: 
[3757350.671872] cdb[0]=0x28: 28 00 00 a0 2c b0 00 00 08 00
[3757350.671884] sd 0:0:2:0: [sdc] Unhandled sense code
[3757350.671886] sd 0:0:2:0: [sdc]  
[3757350.671888] Result: hostbyte=0x00 driverbyte=0x08
[3757350.671890] sd 0:0:2:0: [sdc]  
[3757350.671892] Sense Key : 0x4 [current] 
[3757350.671894] sd 0:0:2:0: [sdc]  
[3757350.671896] ASC=0x44 ASCQ=0x0
[3757350.671899] sd 0:0:2:0: [sdc] CDB: 
[3757350.671900] cdb[0]=0x28: 28 00 00 a0 2c b8 00 00 08 00
[3757350.671912] sd 0:0:2:0: [sdc] Unhandled sense code
[3757350.671914] sd 0:0:2:0: [sdc]  
[3757350.671916] Result: hostbyte=0x00 driverbyte=0x08
[3757350.671918] sd 0:0:2:0: [sdc]  
[3757350.671920] Sense Key : 0x4 [current] 
[3757350.671923] sd 0:0:2:0: [sdc]  
[3757350.671924] ASC=0x44 ASCQ=0x0
[3757350.671927] sd 0:0:2:0: [sdc] CDB: 
[3757350.671928] cdb[0]=0x28: 28 00 00 a0 2c c0 00 00 08 00
[3757350.671939] sd 0:0:2:0: [sdc] Unhandled sense code
[3757350.671941] sd 0:0:2:0: [sdc]  
[3757350.671943] Result: hostbyte=0x00 driverbyte=0x08
[3757350.671945] sd 0:0:2:0: [sdc]  
[3757350.671947] Sense Key : 0x4 [current] 
[3757350.671950] sd 0:0:2:0: [sdc]  
[3757350.671951] ASC=0x44 ASCQ=0x0
[3757350.671954] sd 0:0:2:0: [sdc] CDB: 
[3757350.671955] cdb[0]=0x28: 28 00 00 a0 2c c8 00 00 08 00

Arkadiusz Miśkiewicz, arekm / maven.pl

Q: vger.kernel.org postmasters - always rude and impolite, hmm?
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

http://www.t10.org/lists/2sensekey.htm

0x4 is "hardware error".

http://www.t10.org/lists/asc-num.htm

0x44/0x00 is "internal target failure".

Regards,
Bryn.

Thanks for links. I wonder why kernel doesn't decode these to be actually readable without a need for asking on ml - was decoding considered?

Anyway Adaptec support helped with details:

http://ask.adaptec.com/app/answers/detail/a_id/14947/track/AvOF~QqxDv8S~TbvGmIW~yLb_fsq5C75Mv~s~zj~PP8l

Basically this controller finds "bad stripes" and blocks any access to these areas resulting in errors :-/ What's more interesting there is no recovery procedure beside recreation. Fun :-)

Arkadiusz Miśkiewicz, arekm / maven.pl

Q: vger.kernel.org postmasters - always rude and impolite, hmm?
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Normally it does; I was a bit surprised to see numbers printed with such a recent kernel.

Sense key decoding to text has been around almost forever (the 'snstext' table of sense strings pre-dates git, i.e. 2.6.12ish).

Is it possible your kernel was built without CONFIG_SCSI_CONSTANTS?

Regards,
Bryn.

Bingo! Thanks for your help.

Arkadiusz Miśkiewicz, arekm / maven.pl

Q: vger.kernel.org postmasters - always rude and impolite, hmm?
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html