Re: help decoding aacraid errors (3.10.40 kernel)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 27 of June 2014, Bryn M. Reeves wrote:
> On Fri, Jun 27, 2014 at 10:55:08AM +0200, Arkadiusz Miskiewicz wrote:
> > [3757350.671860] Result: hostbyte=0x00 driverbyte=0x08
> > [3757350.671862] sd 0:0:2:0: [sdc]
> > [3757350.671863] Sense Key : 0x4 [current]
> 
> http://www.t10.org/lists/2sensekey.htm
> 
> 0x4 is "hardware error".
> 
> > [3757350.671866] sd 0:0:2:0: [sdc]
> > [3757350.671868] ASC=0x44 ASCQ=0x0
> 
> http://www.t10.org/lists/asc-num.htm
> 
> 0x44/0x00 is "internal target failure".

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 :-)

> Regards,
> Bryn.


-- 
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux