Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

ATA command failure: worthy of concern?

Need help with peripherals or devices?
Post Reply
Message
Author
wirawan0
Posts: 33
Joined: 2011-09-09 15:59

ATA command failure: worthy of concern?

#1 Post by wirawan0 »

I have a Lenovo T450s running Debian 8 (Jessie) stable. Standard Linux kernel 3.16.0-4-amd64, version 3.16.7-ckt11-1+deb8u2.

Today I found quite a bit of error messages about the ata2 drive (29 total over the period of 30-31 days, from June 28-July 29):

Code: Select all

$ zgrep -E 'ata.*(exception|failed)' $(ls -tr /var/log/syslog* )
/var/log/syslog.18.gz:Jun 28 23:59:57 wirawan2 kernel: [33628.965877] ata2.00: exception Emask 0x10 SAct 0x2000 SErr 0x50000 action 0xe frozen
/var/log/syslog.18.gz:Jun 28 23:59:57 wirawan2 kernel: [33628.965884] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.17.gz:Jun 29 12:03:13 wirawan2 kernel: [37860.027993] ata2.00: exception Emask 0x10 SAct 0x7800 SErr 0x50000 action 0xe frozen
/var/log/syslog.17.gz:Jun 29 12:03:13 wirawan2 kernel: [37860.028000] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.17.gz:Jun 29 12:03:13 wirawan2 kernel: [37860.028006] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.17.gz:Jun 29 12:03:13 wirawan2 kernel: [37860.028010] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.17.gz:Jun 29 12:03:13 wirawan2 kernel: [37860.028015] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.15.gz:Jul 11 03:03:20 wirawan2 kernel: [24653.971903] ata2.00: exception Emask 0x10 SAct 0x10000 SErr 0x50000 action 0xe frozen
/var/log/syslog.15.gz:Jul 11 03:03:20 wirawan2 kernel: [24653.971916] ata2.00: failed command: READ FPDMA QUEUED
/var/log/syslog.13.gz:Jul 13 13:38:53 wirawan2 kernel: [66850.074433] ata2.00: exception Emask 0x10 SAct 0x3 SErr 0x50000 action 0xe frozen
/var/log/syslog.13.gz:Jul 13 13:38:53 wirawan2 kernel: [66850.074440] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.13.gz:Jul 13 13:38:53 wirawan2 kernel: [66850.074445] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.12.gz:Jul 14 22:19:30 wirawan2 kernel: [87149.162642] ata2.00: exception Emask 0x10 SAct 0x20000 SErr 0x50000 action 0xe frozen
/var/log/syslog.12.gz:Jul 14 22:19:30 wirawan2 kernel: [87149.162649] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.12.gz:Jul 15 00:00:04 wirawan2 kernel: [90176.255608] ata2.00: exception Emask 0x10 SAct 0x400000 SErr 0x50000 action 0xe frozen
/var/log/syslog.12.gz:Jul 15 00:00:04 wirawan2 kernel: [90176.255627] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.12.gz:Jul 15 15:52:42 wirawan2 kernel: [96336.876379] ata2.00: exception Emask 0x10 SAct 0x2 SErr 0x50000 action 0xe frozen
/var/log/syslog.12.gz:Jul 15 15:52:42 wirawan2 kernel: [96336.876388] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.10.gz:Jul 16 11:33:26 wirawan2 kernel: [158026.385099] ata2.00: exception Emask 0x10 SAct 0x40 SErr 0x50000 action 0xe frozen
/var/log/syslog.10.gz:Jul 16 11:33:26 wirawan2 kernel: [158026.385109] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.10.gz:Jul 16 14:06:14 wirawan2 kernel: [163375.078729] ata2.00: exception Emask 0x10 SAct 0x1000000 SErr 0x50000 action 0xe frozen
/var/log/syslog.10.gz:Jul 16 14:06:14 wirawan2 kernel: [163375.078741] ata2.00: failed command: READ FPDMA QUEUED
/var/log/syslog.10.gz:Jul 18 09:36:22 wirawan2 kernel: [195725.074455] ata2.00: exception Emask 0x10 SAct 0xc000 SErr 0x50000 action 0xe frozen
/var/log/syslog.10.gz:Jul 18 09:36:22 wirawan2 kernel: [195725.074473] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.10.gz:Jul 18 09:36:22 wirawan2 kernel: [195725.074478] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.8.gz:Jul 20 08:39:26 wirawan2 kernel: [220798.350181] ata2.00: exception Emask 0x10 SAct 0x18000 SErr 0x50000 action 0xe frozen
/var/log/syslog.8.gz:Jul 20 08:39:26 wirawan2 kernel: [220798.350188] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.8.gz:Jul 20 08:39:26 wirawan2 kernel: [220798.350194] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.7.gz:Jul 20 16:06:31 wirawan2 kernel: [225680.073942] ata2.00: exception Emask 0x10 SAct 0x10000000 SErr 0x50000 action 0xe frozen
/var/log/syslog.7.gz:Jul 20 16:06:31 wirawan2 kernel: [225680.073956] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.7.gz:Jul 20 21:54:30 wirawan2 kernel: [246580.305356] ata2.00: exception Emask 0x10 SAct 0x2000000 SErr 0x50000 action 0xe frozen
/var/log/syslog.7.gz:Jul 20 21:54:30 wirawan2 kernel: [246580.305370] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.7.gz:Jul 21 07:20:24 wirawan2 kernel: [249863.503574] ata2.00: exception Emask 0x10 SAct 0x8000000 SErr 0x50000 action 0xe frozen
/var/log/syslog.7.gz:Jul 21 07:20:24 wirawan2 kernel: [249863.503581] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.6.gz:Jul 21 16:33:05 wirawan2 kernel: [258652.084042] ata2.00: exception Emask 0x10 SAct 0x80 SErr 0x50000 action 0xe frozen
/var/log/syslog.6.gz:Jul 21 16:33:05 wirawan2 kernel: [258652.084059] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.6.gz:Jul 21 18:11:53 wirawan2 kernel: [264584.170719] ata2.00: exception Emask 0x10 SAct 0x300 SErr 0x50000 action 0xe frozen
/var/log/syslog.6.gz:Jul 21 18:11:53 wirawan2 kernel: [264584.170726] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.6.gz:Jul 21 18:11:53 wirawan2 kernel: [264584.170732] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.6.gz:Jul 21 22:56:01 wirawan2 kernel: [281649.387503] ata2.00: exception Emask 0x10 SAct 0x6000 SErr 0x50000 action 0xe frozen
/var/log/syslog.6.gz:Jul 21 22:56:01 wirawan2 kernel: [281649.387511] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.6.gz:Jul 21 22:56:01 wirawan2 kernel: [281649.387527] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.6.gz:Jul 22 00:00:17 wirawan2 kernel: [285509.785405] ata2.00: exception Emask 0x10 SAct 0x3 SErr 0x50000 action 0xe frozen
/var/log/syslog.6.gz:Jul 22 00:00:17 wirawan2 kernel: [285509.785412] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.6.gz:Jul 22 00:00:17 wirawan2 kernel: [285509.785419] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.5.gz:Jul 23 00:26:35 wirawan2 kernel: [316654.652003] ata2.00: exception Emask 0x10 SAct 0x3 SErr 0x50000 action 0xe frozen
/var/log/syslog.5.gz:Jul 23 00:26:35 wirawan2 kernel: [316654.652013] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.5.gz:Jul 23 00:26:35 wirawan2 kernel: [316654.652024] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.4.gz:Jul 23 09:56:45 wirawan2 kernel: [327916.070870] ata2.00: exception Emask 0x10 SAct 0x1800 SErr 0x50000 action 0xe frozen
/var/log/syslog.4.gz:Jul 23 09:56:45 wirawan2 kernel: [327916.070878] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.4.gz:Jul 23 09:56:45 wirawan2 kernel: [327916.070896] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.4.gz:Jul 23 23:02:23 wirawan2 kernel: [12525.291414] ata2.00: exception Emask 0x10 SAct 0x1 SErr 0x50000 action 0xe frozen
/var/log/syslog.4.gz:Jul 23 23:02:23 wirawan2 kernel: [12525.291423] ata2.00: failed command: READ FPDMA QUEUED
/var/log/syslog.4.gz:Jul 24 00:57:22 wirawan2 kernel: [19145.817322] ata2.00: exception Emask 0x10 SAct 0x20000 SErr 0x50000 action 0xe frozen
/var/log/syslog.4.gz:Jul 24 00:57:22 wirawan2 kernel: [19145.817342] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.4.gz:Jul 25 22:57:58 wirawan2 kernel: [15094.645681] ata2.00: exception Emask 0x10 SAct 0x8000000 SErr 0x50000 action 0xe frozen
/var/log/syslog.4.gz:Jul 25 22:57:58 wirawan2 kernel: [15094.645697] ata2.00: failed command: READ FPDMA QUEUED
/var/log/syslog.2.gz:Jul 27 14:38:52 wirawan2 kernel: [19407.186930] ata2.00: exception Emask 0x10 SAct 0x6000 SErr 0x50000 action 0xe frozen
/var/log/syslog.2.gz:Jul 27 14:38:52 wirawan2 kernel: [19407.186938] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.2.gz:Jul 27 14:38:52 wirawan2 kernel: [19407.186944] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.2.gz:Jul 27 21:40:10 wirawan2 kernel: [34305.454163] ata2.00: exception Emask 0x10 SAct 0x20000 SErr 0x50000 action 0xe frozen
/var/log/syslog.2.gz:Jul 27 21:40:10 wirawan2 kernel: [34305.454172] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.2.gz:Jul 28 10:15:02 wirawan2 kernel: [43988.057244] ata2.00: exception Emask 0x10 SAct 0x6000 SErr 0x50000 action 0xe frozen
/var/log/syslog.2.gz:Jul 28 10:15:02 wirawan2 kernel: [43988.057272] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.2.gz:Jul 28 10:15:02 wirawan2 kernel: [43988.057277] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.1:Jul 28 14:10:56 wirawan2 kernel: [57243.884382] ata2.00: exception Emask 0x10 SAct 0x8 SErr 0x50000 action 0xe frozen
/var/log/syslog.1:Jul 28 14:10:56 wirawan2 kernel: [57243.884398] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.1:Jul 28 22:47:00 wirawan2 kernel: [71149.883999] ata2.00: exception Emask 0x10 SAct 0x300000 SErr 0x50000 action 0xe frozen
/var/log/syslog.1:Jul 28 22:47:00 wirawan2 kernel: [71149.884019] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.1:Jul 28 22:47:00 wirawan2 kernel: [71149.884029] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.1:Jul 29 11:52:40 wirawan2 kernel: [77786.606148] ata2.00: exception Emask 0x10 SAct 0x30 SErr 0x50000 action 0xe frozen
/var/log/syslog.1:Jul 29 11:52:40 wirawan2 kernel: [77786.606157] ata2.00: failed command: WRITE FPDMA QUEUED
/var/log/syslog.1:Jul 29 11:52:40 wirawan2 kernel: [77786.606163] ata2.00: failed command: WRITE FPDMA QUEUED
Examining a few block of errors like this, it seems to coincide with laptop mode change (I used laptop-mode-tools). Is this a cause of worry? The drive is "MyDigitalSSD 128GB (120GB) Super Boot Eco Drive 42mm SATA III 6G M.2 NGFF 2242 SSD Solid State Drive - MDM242-SBe-128", see here:

http://www.amazon.com/gp/product/B00LNF1RVM

Overall I did not detect anomaly on the drive operation, but just wonder if I should be concerned with this issue. Here is a complete block of error message:

Code: Select all

Jul 18 09:36:21 wirawan2 kernel: [195724.499953] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:21 wirawan2 kernel: [195724.509396] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:21 wirawan2 kernel: [195724.520893] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:21 wirawan2 kernel: [195724.530049] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:21 wirawan2 kernel: [195724.543559] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:21 wirawan2 kernel: [195724.554380] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:21 wirawan2 kernel: [195724.565385] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:21 wirawan2 kernel: [195724.574727] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
Jul 18 09:36:22 wirawan2 kernel: [195725.074455] ata2.00: exception Emask 0x10 SAct 0xc000 SErr 0x50000 action 0xe frozen
Jul 18 09:36:22 wirawan2 kernel: [195725.074469] ata2.00: irq_stat 0x00400000, PHY RDY changed
Jul 18 09:36:22 wirawan2 kernel: [195725.074470] ata2: SError: { PHYRdyChg CommWake }
Jul 18 09:36:22 wirawan2 kernel: [195725.074473] ata2.00: failed command: WRITE FPDMA QUEUED
Jul 18 09:36:22 wirawan2 kernel: [195725.074476] ata2.00: cmd 61/00:70:b8:d6:da/04:00:02:00:00/40 tag 14 ncq 524288 out
Jul 18 09:36:22 wirawan2 kernel: [195725.074476]          res 40/00:78:b8:da:da/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
Jul 18 09:36:22 wirawan2 kernel: [195725.074477] ata2.00: status: { DRDY }
Jul 18 09:36:22 wirawan2 kernel: [195725.074478] ata2.00: failed command: WRITE FPDMA QUEUED
Jul 18 09:36:22 wirawan2 kernel: [195725.074481] ata2.00: cmd 61/c8:78:b8:da:da/00:00:02:00:00/40 tag 15 ncq 102400 out
Jul 18 09:36:22 wirawan2 kernel: [195725.074481]          res 40/00:78:b8:da:da/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
Jul 18 09:36:22 wirawan2 kernel: [195725.074482] ata2.00: status: { DRDY }
Jul 18 09:36:22 wirawan2 kernel: [195725.074485] ata2: hard resetting link
Jul 18 09:36:22 wirawan2 kernel: [195725.422868] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 18 09:36:22 wirawan2 kernel: [195725.424825] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jul 18 09:36:22 wirawan2 kernel: [195725.424829] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jul 18 09:36:22 wirawan2 kernel: [195725.428370] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jul 18 09:36:22 wirawan2 kernel: [195725.428373] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jul 18 09:36:22 wirawan2 kernel: [195725.430004] ata1.00: configured for UDMA/133
Jul 18 09:36:22 wirawan2 kernel: [195725.799251] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 18 09:36:22 wirawan2 kernel: [195725.799491] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jul 18 09:36:22 wirawan2 kernel: [195725.799495] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jul 18 09:36:22 wirawan2 kernel: [195725.799839] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jul 18 09:36:22 wirawan2 kernel: [195725.799841] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jul 18 09:36:22 wirawan2 kernel: [195725.799926] ata2.00: configured for UDMA/133
Jul 18 09:36:22 wirawan2 kernel: [195725.815210] ata2: EH complete
Jul 18 09:36:23 wirawan2 laptop-mode: Laptop mode
Jul 18 09:36:23 wirawan2 laptop-mode: enabled, not active
Smartcl -x on this drive did not show anything suspect, except the last few lines showing some numbers:

Code: Select all

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
...deleted...
0x0009  4            6  Transition from drive PhyRdy to drive PhyNRdy
0x000a  4            3  Device-to-host register FISes sent due to a COMRESET
...deleted...
Any clue on what happening?

Thanks,
Wirawan


FWIW, here is the full `smartctl -x` output:

Code: Select all

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SBe M2 SSD
Serial Number:    
Firmware Version: S9FM02.2
User Capacity:    120,034,123,776 bytes [120 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      M.2
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-3 (minor revision not indicated)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jul 29 12:35:13 2015 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unavailable

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		(   30) 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: 	 (   2) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     -O-R--   100   100   000    -    0
  9 Power_On_Hours          -O--C-   100   100   000    -    143
 12 Power_Cycle_Count       -O--C-   100   100   000    -    133
168 Unknown_Attribute       -O--C-   100   100   000    -    0
170 Unknown_Attribute       PO--C-   100   100   010    -    25
173 Unknown_Attribute       ------   100   100   000    -    9895937
192 Power-Off_Retract_Count -O--C-   100   100   000    -    0
194 Temperature_Celsius     PO---K   070   070   000    -    30
196 Reallocated_Event_Count ------   100   100   000    -    0
218 Unknown_Attribute       ------   100   100   000    -    0
241 Total_LBAs_Written      -O--C-   100   100   000    -    39206
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O     51  Comprehensive SMART error log
0x03       GPL     R/O     64  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O      8  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log

SMART Extended Comprehensive Error Log Version: 1 (64 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 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.

SCT Commands not supported

Device Statistics (GP Log 0x04)
Page Offset Size         Value  Description
  7  =====  =                =  == Solid State Device Statistics (rev 1) ==
  7  0x008  1                0  Percentage Used Endurance Indicator

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  4            6  Transition from drive PhyRdy to drive PhyNRdy
0x000a  4            3  Device-to-host register FISes sent due to a COMRESET
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0010  2            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  2            0  R_ERR response for host-to-device non-data FIS, non-CRC
Top
User avatar
powder
Posts: 17
Joined: 2013-08-23 22:22

Re: ATA command failure: worthy of concern?

#2 Post by powder »

Logs are showing failed write commands leading up to a hard reset of the SATA link. The failed write commands should retry until they complete, which might explain why you haven't noticed any problems.

I would recommend you avoid whatever is causing this though, if you value your data. :)
Top
wirawan0
Posts: 33
Joined: 2011-09-09 15:59

Re: ATA command failure: worthy of concern?

#3 Post by wirawan0 »

Hi,

Thanks for your reply. I am still not clear with what you said: "whatever causing this". What are the possible factors?

Those errors were generated when I was using stock kernel 3.16 from Debian. I switched to LIquorix kernel 4.1-3 now and the frequency of the ata2 errors were much, much lower. So far after 7 days of uptime, only two "WRITE FPDMA QUEUED" failures were recorded--and occuring only in 2 days. The other two failures involved the "CHECK POWER MODE" command. As of now this should be a good temporary solution. But I suspect that kernel bug could have something to do with it?

Wirawan
Top
User avatar
powder
Posts: 17
Joined: 2013-08-23 22:22

Re: ATA command failure: worthy of concern?

#4 Post by powder »

Oh, I thought it was something to do with laptop mode change? I am not familiar with laptop-mode-tools...

My best guess it could be a compatibility issue with your hardware and the SSD or the SSD might be faulty. I doubt it's a kernel issue since libata is pretty robust.
Top
Post Reply

Return to “Hardware”