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

Bug#625922: Failures with ST2000DL003-9VT166



I'm seeing the same sort of failure with a pair of these same drives:

  [ 3.570733] ata3.00: ATA-8: ST2000DL003-9VT166, CC32, max UDMA/133

wired into a rather old (2007ish) motherboard:

    http://www.intel.com/p/pt_BR/support/highlights/dsktpboards/dg31pr

    Base Board Information
            Manufacturer: Intel Corporation
            Product Name: DG31PR
            Version: AAD97573-203
            Serial Number: BTPR741000Y3

    BIOS Information
        Vendor: Intel Corp.
        Version: PRG3110H.86A.0071.2010.0318.1704
        Release Date: 03/18/2010

I've upgraded the BIOS in the motherboard and it didn't fix the issue
(nor were any SATA interop fixes listed in the BIOS ChangeLog). I had
also replaced the power supply and both cables before that.

I encountered these problems running an amd64 2.6.35-28 Ubuntu kernel
(the current Maverick kernel). I just upgraded yesterday to the Natty
kernel, which is 2.6.38-8 to see if it addressed the problem, and I
haven't seen it occur since, but given that this bug report reports it's
happening in Debian's 2.6.38-8, I'm not very hopeful.

I think this is probably something broken in either the drives or in the
drive-to-motherboard interaction. In looking at the motherboards which
are appearing here:

    Gigabyte P35-DS3R
    Supermicro X7SPA-H

All these boards are specified as supporting SATA 3.0Bps, but at least
mine and the P35-DS3R are pretty old; I'm not sure about the Supermicro.
So I am thinking there may just be a motherboard interoperability issue.

If this kernel upgrade doesn't address the problem, then I'm considering
replacing one drive at a time, and then the motherboard. (I would switch
drive vendor but it won't be easy to get a refund, so I'm willing to
give this a bit more effort.)
-- 
Christian Robottom Reis   | [+55 16] 3376 0125 | http://launchpad.net/~kiko
Canonical Ltd.            | [+55 16] 9112 6430 | http://async.com.br/~kiko



Reply to: