linux-kernel - Re: SATA repeated failure (command 0x35 timeout, status 0xd8)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 03 Oct 2006 15:54:53 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Molle Bestefich <molle.bestefich@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: SATA repeated failure (command 0x35 timeout, status 0xd8)

Molle Bestefich wrote:
[--snip--]
> The above repeats itself thru modes UDMA/66, UDMA/44, UDMA/33,
> UDMA/25, UDMA/16, PIO4, PIO3, PIO1 and PIO0.

Can you full dmesg for this?  Preferably w/ timestamp?

> At which point /dev/sdb disappears completely, only to reappear as 
> /dev/sdh:
> ===============
> SCSI device sdh: 398297088 512-byte hdwr sectors (203928 MB)
> sdh: Write Protect is off
> sdh: Mode Sense: 00 3a 00 00
> SCSI device sdh: drive cache: write back
> SCSI device sdh: 398297088 512-byte hdwr sectors (203928 MB)
> sdh: Write Protect is off
> sdh: Mode Sense: 00 3a 00 00
> SCSI device sdh: drive cache: write back
> ===============
> 
> (Odd.)
> 
> I don't get why PowerMax works this drive just fine while Linux
> doesn't.  Perhaps because PowerMax only uses SMART commands and
> doesn't transfer data over the SATA bus?
> 
> Anyway, with the device now failing fairly consistently, I guess I
> should begin moving around cables, controllers, disks etc. again.  I'm
> very worried about doing this though, since I'm pretty sure that it'll
> break the MD array on the disks very quickly..

Your problem seems to be hardware transmission error.  I don't know what 
a powermax is and doesn't know what it does, so you'll have to play the 
swap-and-see-what-breaks game to figure out the problematic part.

Thanks.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/