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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 02 Dec 2008 15:05:53 +0100
From:	Soeren Sonnenburg <kernel@....de>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linux-ide <linux-ide@...r.kernel.org>
Subject: Re: ST31500341AS vs ICH10, exception Emask 0x50 SAct 0x1 SErr
	0x280900 action 0x6 frozen

On Tue, 2008-12-02 at 04:49 -0500, Justin Piszcz wrote:
> 
> On Tue, 2 Dec 2008, Soeren Sonnenburg wrote:
> 
> > Dear all,
> >
> > I just purchased a seagate 1.5TB drive ST31500341AS, with firmware
> > revision CC1G (which according to seagate is not affected by the cache
> > flush bug) and I am getting the errors below (after almost a day of
> > uptime without problems). The drive is replacing a 750G variant from
> > seagate with which I had months of uptime and no errors whatsoever.
> >
> > I hope anyone has an idea?
> >
> > - relevant part of hdparm -I and lspci
> >
> > ATA device, with non-removable media
> > 	Model Number:       ST31500341AS
> > 	Firmware Revision:  CC1G
> > 	Transport:          Serial
> >
> > 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA
> > AHCI Controller
> >
> > - the error(tm)
> 
> A few items:
> 
>           res 40/00:00:48:19:67/00:00:1e:00:00/40 Emask 0x50 (ATA bus error)
>           ata3: SError: { UnrecovData HostInt 10B8B BadCRC }
> 
> These are usually realted to a bad cable or connector.

OK, if this happens again I will try a new cable. However, the backplane
(it is this one:
http://www.raidsonic.de/en/pages/products/backplanes.php?we_objectID=4251 ) was working nicely with another disk in the same slot (but maybe I did not perfectly insert the disk...)

> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> 
> Did you remove the 1.5 Gbps jumper so it can run at 3.0 Gbps?

Yes. This is actually the only difference to the drive before (which was
1.5 Gbps).

For now it is all running nicely and I did a full dd if= ... read of the
disk:

ata3: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 510
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: HPA detected: current 2930277168, native 18446744072344861488
ata3.00: ATA-8: ST31500341AS, CC1G, max UDMA/133
ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133

Thank you very much!!
Soeren
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ