linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Daniel Pocock <daniel@pocock.com.au>
Cc: linux-ide@vger.kernel.org
Subject: Re: very slow write to AHCI device
Date: Tue, 08 May 2012 10:21:46 +0200	[thread overview]
Message-ID: <4FA8D79A.7000500@fold.natur.cuni.cz> (raw)
In-Reply-To: <4FA85B25.8070500@pocock.com.au>

Daniel Pocock wrote:

> Not quite:
> 
> # smartctl -a /dev/sda
> smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
> Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
> 
> === START OF INFORMATION SECTION ===
> Model Family:     Seagate Barracuda 7200.12 family
> Device Model:     ST31000528AS
> Serial Number:    6VP0KWSF
> Firmware Version: CC49
> User Capacity:    1,000,204,886,016 bytes
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   8
> ATA Standard is:  ATA-8-ACS revision 4
> Local Time is:    Tue May  8 01:26:06 2012 CEST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
> 
> 
>> My disk catch up at 3Gbps:
>>
>> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata3.00: ATA-8: WDC WD1000FYPS-01ZKB0, 02.01B01, max UDMA/133
>> ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
>> ata3.00: configured for UDMA/133
>> scsi 2:0:0:0: Direct-Access     ATA      WDC WD1000FYPS-0 02.0 PQ: 0 ANSI: 5
>> sd 2:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
>> sd 2:0:0:0: Attached scsi generic sg2 type 0
>> sd 2:0:0:0: [sdc] Write Protect is off
>> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
>> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>>  sdc: sdc1
>> sd 2:0:0:0: [sdc] Attached SCSI disk
>>
>>   
> 
> 
> One of mine died as soon as I upgraded to the CC49 firmware today:
> 
> [ 2905.173593] sd 0:0:0:0: [sda] Unhandled error code
> [ 2905.173599] sd 0:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET
> driverbyte=DRIVER_OK
> [ 2905.173608] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 18 f7 aa c8 00 00
> 10 00
> [ 2905.173628] end_request: I/O error, dev sda, sector 418884296
> [ 2905.180214] sd 0:0:0:0: [sda] Unhandled error code
> [ 2905.180220] sd 0:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET
> driverbyte=DRIVER_OK
> [ 2905.180234] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 18 f7 aa b8 00 00
> 08 00
> [ 2905.180286] end_request: I/O error, dev sda, sector 418884280
> [ 2905.180496] md/raid1:md2: Disk failure on sda2, disabling device.
> [ 2905.180501] md/raid1:md2: Operation continuing on 1 devices.
> [ 2905.199738] sd 0:0:0:0: [sda] Unhandled error code
> 
> 

I use CC4C in my 3TB Seagates (ST3000DM001 disk, 4k sectors). Do you wnat to downgrade? ;-)

Martin

      reply	other threads:[~2012-05-08  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 16:16 very slow write to AHCI device Daniel Pocock
2012-05-07 18:10 ` Martin Mokrejs
2012-05-07 18:11   ` Daniel Pocock
2012-05-07 18:27     ` Martin Mokrejs
2012-05-07 23:30       ` Daniel Pocock
2012-05-08  8:21         ` Martin Mokrejs [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA8D79A.7000500@fold.natur.cuni.cz \
    --to=mmokrejs@fold.natur.cuni.cz \
    --cc=daniel@pocock.com.au \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).