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

Bug#731120: marked as done (Seeing ATA failed command WRITE FPDMA QUEUED after upgrade kernel 3.2.46-1+deb7u1 -> 3.2.51-1)

Your message dated Wed, 11 Dec 2013 14:31:53 +0000
with message-id <1386772313.12186.77.camel@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#731120: Seeing ATA failed command WRITE FPDMA QUEUED after upgrade kernel 3.2.46-1+deb7u1 -> 3.2.51-1
has caused the Debian Bug report #731120,
regarding Seeing ATA failed command WRITE FPDMA QUEUED after upgrade kernel 3.2.46-1+deb7u1 -> 3.2.51-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
731120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731120
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.2.0-4-amd64
Version: 3.2.51-1

After a recent kernel upgrade, going from a kernel that on boot
identifies itself as:

Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1+deb7u1

to a kernel that identifies itself as:

Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.51-1

I have started seeing fairly regular "WRITE FPDMA QUEUED" ATA command
failed errors in my system logs. These never showed up before (I have
checked system logs going back several months and the first error
logged showed up approximately 25 ½ hours after the first boot into
the new kernel) and are now showing up approximately once a day. I see
no clear connection to what would be high disk usage. Here is an
example of a logged failure:

Dec  2 04:27:01 yeono kernel: [459438.816058] ata2.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
Dec  2 04:27:01 yeono kernel: [459438.816071] ata2.00: failed command: WRITE FPDMA QUEUED
Dec  2 04:27:01 yeono kernel: [459438.816085] ata2.00: cmd 61/08:00:70:0d:ca/00:00:08:00:00/40 tag 0 ncq 4096 out
Dec  2 04:27:01 yeono kernel: [459438.816088]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Dec  2 04:27:01 yeono kernel: [459438.816095] ata2.00: status: { DRDY }
Dec  2 04:27:01 yeono kernel: [459438.816101] ata2.00: failed command: WRITE FPDMA QUEUED
Dec  2 04:27:01 yeono kernel: [459438.816113] ata2.00: cmd 61/08:08:48:0f:ca/00:00:08:00:00/40 tag 1 ncq 4096 out
Dec  2 04:27:01 yeono kernel: [459438.816116]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  2 04:27:01 yeono kernel: [459438.816122] ata2.00: status: { DRDY }
Dec  2 04:27:01 yeono kernel: [459438.816127] ata2.00: failed command: READ FPDMA QUEUED
Dec  2 04:27:01 yeono kernel: [459438.816139] ata2.00: cmd 60/01:10:62:99:62/00:00:39:00:00/40 tag 2 ncq 512 in
Dec  2 04:27:01 yeono kernel: [459438.816142]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  2 04:27:01 yeono kernel: [459438.816148] ata2.00: status: { DRDY }
Dec  2 04:27:01 yeono kernel: [459438.816154] ata2.00: failed command: READ FPDMA QUEUED
Dec  2 04:27:01 yeono kernel: [459438.816165] ata2.00: cmd 60/02:18:ba:3b:a0/00:00:39:00:00/40 tag 3 ncq 1024 in
Dec  2 04:27:01 yeono kernel: [459438.816167]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  2 04:27:01 yeono kernel: [459438.816172] ata2.00: status: { DRDY }
Dec  2 04:27:01 yeono kernel: [459438.816181] ata2: hard resetting link
Dec  2 04:27:02 yeono kernel: [459439.920055] ata2: SATA link down (SStatus 0 SControl 300)
Dec  2 04:27:02 yeono kernel: [459439.932977] ata2: hard resetting link
Dec  2 04:27:09 yeono kernel: [459446.100050] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec  2 04:27:09 yeono kernel: [459446.314509] ata2.00: configured for UDMA/133
Dec  2 04:27:09 yeono kernel: [459446.328037] ata2.00: device reported invalid CHS sector 0
Dec  2 04:27:09 yeono kernel: [459446.328045] ata2.00: device reported invalid CHS sector 0
Dec  2 04:27:09 yeono kernel: [459446.328051] ata2.00: device reported invalid CHS sector 0
Dec  2 04:27:09 yeono kernel: [459446.328055] ata2.00: device reported invalid CHS sector 0

I have two internal SATA-connected drives on the host in question, and
according to dmesg output, the drive having problems is the main
system drive. Here is smartctl output for that drive:

smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda ES.2
Device Model:     ST31000340NS
Serial Number:    9QJ26FT9
LU WWN Device Id: 5 000c50 00dccec6a
Firmware Version: SN05
User Capacity:    1 000 204 886 016 bytes [1,00 TB]
Sector Size:      512 bytes logical/physical
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:    Mon Dec  2 10:38:38 2013 CET

==> WARNING: There are known problems with these drives,
see the following Seagate web pages:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207963

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  642) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 234) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   080   063   044    Pre-fail  Always       -       224044516
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       387
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       2
  7 Seek_Error_Rate         0x000f   069   064   030    Pre-fail  Always       -       129124330141
  9 Power_On_Hours          0x0032   052   052   000    Old_age   Always       -       42199
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   037   020    Old_age   Always       -       388
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   097   000    Old_age   Always       -       7
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   075   038   045    Old_age   Always   In_the_past 25 (0 255 27 25)
194 Temperature_Celsius     0x0022   025   062   000    Old_age   Always       -       25 (0 11 0 0)
195 Hardware_ECC_Recovered  0x001a   029   018   000    Old_age   Always       -       224044516
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     42193         -
# 2  Extended offline    Interrupted (host reset)      00%     42193         -
# 3  Short offline       Interrupted (host reset)      00%     42169         -
# 4  Short offline       Interrupted (host reset)      00%     42145         -
# 5  Short offline       Interrupted (host reset)      00%     42121         -
# 6  Short offline       Interrupted (host reset)      00%     42097         -
# 7  Short offline       Interrupted (host reset)      00%     42072         -
# 8  Short offline       Interrupted (host reset)      00%     42066         -
# 9  Short offline       Interrupted (host reset)      00%     42066         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

** end of smartctl output **

-- 
Michael Kjörling • http://michael.kjorling.se • michael@kjorling.se
                “People who think they know everything really annoy
                those of us who know we don’t.” (Bjarne Stroustrup)

--- End Message ---
--- Begin Message --- 
On Wed, 2013-12-11 at 10:21 +0000, Michael Kjörling wrote:
> Control: tag = unreproducible wontfix
> 
> It turns out the logged errors were most likely caused by actual
> hardware problems, meaning that the observed behavior was desirable.
> After physically replacing the relevant hard disk, the system has been
> running without any similar issues.
> 
> This bug report can be considered invalid.

Thanks, closing.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that there are so many of them.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: