You are not logged in.

Pages: 1

#1 2015-07-31 19:40:46

Scriptor
Member
Registered: 2011-01-16
Posts: 144

[SOLVED]SSD failed read fdpma queued

Hello,

I recently had a freeze problem. From the look of dmesg, it seemed to come from this :

[35130.646345] ata7.00: exception Emask 0x10 SAct 0xffe000 SErr 0x280100 action 0x6 frozen
[35130.646351] ata7: SError: { UnrecovData 10B8B BadCRC }
[35130.646356] ata7.00: failed command: READ FPDMA QUEUED
[35130.646363] ata7.00: cmd 60/00:68:f0:51:80/01:00:11:00:00/40 tag 13 ncq 131072 in
[35130.646366] ata7.00: status: { DRDY }
[35130.646369] ata7.00: failed command: READ FPDMA QUEUED
[35130.646375] ata7.00: cmd 60/08:70:58:a6:46/00:00:10:00:00/40 tag 14 ncq 4096 in
[35130.646378] ata7.00: status: { DRDY }
[35130.646380] ata7.00: failed command: READ FPDMA QUEUED
[35130.646385] ata7.00: cmd 60/08:78:68:a6:46/00:00:10:00:00/40 tag 15 ncq 4096 in
[35130.646388] ata7.00: status: { DRDY }
[35130.646390] ata7.00: failed command: READ FPDMA QUEUED
[35130.646396] ata7.00: cmd 60/98:80:b0:a6:46/00:00:10:00:00/40 tag 16 ncq 77824 in
[35130.646399] ata7.00: status: { DRDY }
[35130.646401] ata7.00: failed command: READ FPDMA QUEUED
[35130.646406] ata7.00: cmd 60/28:88:40:82:9b/00:00:10:00:00/40 tag 17 ncq 20480 in
[35130.646409] ata7.00: status: { DRDY }
[35130.646411] ata7.00: failed command: READ FPDMA QUEUED
[35130.646416] ata7.00: cmd 60/18:90:70:82:9b/00:00:10:00:00/40 tag 18 ncq 12288 in
[35130.646419] ata7.00: status: { DRDY }
[35130.646421] ata7.00: failed command: READ FPDMA QUEUED
[35130.646426] ata7.00: cmd 60/08:98:c0:82:9b/00:00:10:00:00/40 tag 19 ncq 4096 in
[35130.646429] ata7.00: status: { DRDY }
[35130.646431] ata7.00: failed command: READ FPDMA QUEUED
[35130.646436] ata7.00: cmd 60/20:a0:e0:ee:6c/00:00:11:00:00/40 tag 20 ncq 16384 in
[35130.646439] ata7.00: status: { DRDY }
[35130.646441] ata7.00: failed command: READ FPDMA QUEUED
[35130.646446] ata7.00: cmd 60/18:a8:28:ef:6c/00:00:11:00:00/40 tag 21 ncq 12288 in
[35130.646449] ata7.00: status: { DRDY }
[35130.646452] ata7.00: failed command: READ FPDMA QUEUED
[35130.646457] ata7.00: cmd 60/08:b0:60:ef:6c/00:00:11:00:00/40 tag 22 ncq 4096 in
[35130.646460] ata7.00: status: { DRDY }
[35130.646462] ata7.00: failed command: READ FPDMA QUEUED
[35130.646467] ata7.00: cmd 60/20:b8:78:ef:6c/00:00:11:00:00/40 tag 23 ncq 16384 in
[35130.646470] ata7.00: status: { DRDY }
[35130.646474] ata7: hard resetting link
[35131.133737] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[35131.135658] ata7.00: supports DRM functions and may not be fully accessible
[35131.135706] ata7.00: failed to get NCQ Send/Recv Log Emask 0x1
[35131.135919] ata7.00: supports DRM functions and may not be fully accessible
[35131.135965] ata7.00: failed to get NCQ Send/Recv Log Emask 0x1
[35131.136018] ata7.00: configured for UDMA/133
[35131.136020] ata7.00: device reported invalid CHS sector 0
[35131.136021] ata7.00: device reported invalid CHS sector 0
[35131.136021] ata7.00: device reported invalid CHS sector 0
[35131.136023] ata7.00: device reported invalid CHS sector 0
[35131.136023] ata7.00: device reported invalid CHS sector 0
[35131.136024] ata7.00: device reported invalid CHS sector 0
[35131.136025] ata7.00: device reported invalid CHS sector 0
[35131.136026] ata7.00: device reported invalid CHS sector 0
[35131.136027] ata7.00: device reported invalid CHS sector 0
[35131.136028] ata7.00: device reported invalid CHS sector 0
[35131.136029] ata7.00: device reported invalid CHS sector 0
[35131.136053] ata7: EH complete

So, I ran a smartctl -a, which output this:

smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.1.2-2-ARCH] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 850 PRO 256GB
Serial Number:    S1SUNSAFC09391B
LU WWN Device Id: 5 002538 8a088dc33
Firmware Version: EXM01B6Q
User Capacity:    256 060 514 304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Jul 31 21:38:56 2015 CEST
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

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: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  17) 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: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       2265
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       296
177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       4
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   073   061   000    Old_age   Always       -       27
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   099   099   000    Old_age   Always       -       3
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       22
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       2352479966

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%         0         -

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.

So is my ssd failing ?

[EDIT]
So I did some research on the web, and I may have found a solution. But is it safe to disable ncq ? (discard is not in my fstab)
From what I have read it may have an impact on the performance, but in my case it seems faster. So is it a bug ?

Also what bothers me is this line: 

[35130.646351] ata7: SError: { UnrecovData 10B8B BadCRC }

[/EDIT]

[EDIT2]
So, I think I solved the problem by replacing the power cable/adding a power cable connected to the ssd. The inital power cable was connected to my ssd and my hdd, so I don't know if the problem came from here or if it is because the power cable was damaged.
[/EDIT2]
Thank you very much for any answer smile

Last edited by Scriptor (2015-08-04 15:04:25)

Offline

#2 2015-08-01 13:00:40

Scriptor
Member
Registered: 2011-01-16
Posts: 144

Re: [SOLVED]SSD failed read fdpma queued

So I tried to change the sata cable with another one, but I don't know if that works. The problem seems to come with a high I/O.

What I would really like to know is if it is a serious problem or not ?

Thank you very much smile

Offline

#3 2015-08-01 13:08:08

frostschutz
Member
Registered: 2013-11-15
Posts: 1,480

Re: [SOLVED]SSD failed read fdpma queued

I have NCQ disabled everywhere (libata.force=noncq). Too many bugs in that area and too little performance improvements to show for it. In fact I get better performance w/o NCQ.

Worth a try, but your SSD seems to have a different issue. Maybe it just went bad, it happens...

Run a long selftest (smarctl -t long ...)

Last edited by frostschutz (2015-08-01 13:08:55)

Offline

#4 2015-08-01 15:11:11

Scriptor
Member
Registered: 2011-01-16
Posts: 144

Re: [SOLVED]SSD failed read fdpma queued

Thank you very much smile

So I ran a smartctl -t long and had this result:

smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.1.3-1-ARCH] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%         2         -
# 2  Short offline       Completed without error       00%         0         -

Thank you again smile

Offline

#5 2015-08-01 15:29:16

Scriptor
Member
Registered: 2011-01-16
Posts: 144

Re: [SOLVED]SSD failed read fdpma queued

Okay, so I got another error again:

[    0.506749] ata7: SATA max UDMA/133 abar m512@0xdf600000 port 0xdf600100 irq 32
[    0.992449] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.994358] ata7.00: FORCE: horkage modified (noncq)
[    0.994402] ata7.00: supports DRM functions and may not be fully accessible
[    0.994404] ata7.00: ATA-9: Samsung SSD 850 PRO 256GB, EXM01B6Q, max UDMA/133
[    0.994405] ata7.00: 500118192 sectors, multi 1: LBA48 NCQ (not used)
[    0.994709] ata7.00: supports DRM functions and may not be fully accessible
[    0.994790] ata7.00: configured for UDMA/133
[    4.831390] ata7.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
[    4.831392] ata7.00: irq_stat 0x48000001, interface fatal error
[    4.831393] ata7: SError: { UnrecovData 10B8B BadCRC }
[    4.831395] ata7.00: failed command: READ DMA EXT
[    4.831397] ata7.00: cmd 25/00:00:c0:5c:70/00:01:11:00:00/e0 tag 19 dma 131072 in
[    4.831399] ata7.00: status: { DRDY ERR }
[    4.831399] ata7.00: error: { ICRC ABRT }
[    4.831401] ata7: hard resetting link
[    5.318774] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    5.318955] ata7.00: supports DRM functions and may not be fully accessible
[    5.319180] ata7.00: supports DRM functions and may not be fully accessible
[    5.319235] ata7.00: configured for UDMA/133
[    5.319240] ata7: EH complete

Thank you again smile

Offline

#6 2015-08-01 16:31:27

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

Re: [SOLVED]SSD failed read fdpma queued

Did you somehow reset your smart values or something?
Your output indicates that the test were run at lifetime hour 2. But I guess you are using this drive a little longer..at least:

  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       2265

suggests that it should be more than two hours.

Last edited by dice (2015-08-01 16:31:47)

I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do.  (Gune | Titan A.E.)

Offline

#7 2015-08-01 16:34:00

Scriptor
Member
Registered: 2011-01-16
Posts: 144

Re: [SOLVED]SSD failed read fdpma queued

In fact, it intrigued me as well, and no I didn't reset the values hmm

Thank you again smile

Offline

#8 2015-08-01 16:53:39

frostschutz
Member
Registered: 2013-11-15
Posts: 1,480

Re: [SOLVED]SSD failed read fdpma queued

Well, not sure what's wrong with this device. Have you another PC, does it work there? Just to rule out issues with PSU / cabling / controllers / ..., another PC would change all these, if it still fails you might just have to replace it.

Offline

#9 2015-08-01 17:14:34

Scriptor
Member
Registered: 2011-01-16
Posts: 144

Re: [SOLVED]SSD failed read fdpma queued

Okay, thank you I'll try that, but according to you, from the look of the smartctl selftest, did it reveal something wrong ?

thank you again for all your help smile

Offline

#10 2015-08-01 17:46:09

frostschutz
Member
Registered: 2013-11-15
Posts: 1,480

Re: [SOLVED]SSD failed read fdpma queued

In a serious issue the self test should have reported read error on LBA 123456. Not sure what to make of the Power on Hours - it's strange but should not be related to CRC errors you're seeing.

Offline

#11 2015-08-01 19:58:17

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED]SSD failed read fdpma queued

A quick google search comes up with this[1]. It seems to point to a problem with the cable and/or power. Also make sure you are using the latest available firmware for your ssd and motherboard.

[1] https://lime-technology.com/wiki/index. … ive_Issues

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#12 2015-08-01 21:50:43

Scriptor
Member
Registered: 2011-01-16
Posts: 144

Re: [SOLVED]SSD failed read fdpma queued

Okay, thank you smile I'll take a look. To start with, I'll update my mainboard firmware. Concerning the ssd I can't since it hasn't got any updates.

Thank you very much for your time smile

Offline

#13 2015-08-02 08:25:43

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

Re: [SOLVED]SSD failed read fdpma queued

Did you always have these errors since you use that ssd with that mainboard? If not it is unlikely that the firmware is the cause since it worked before.
Although it is trivial, did you already check/replace the SATA and power cable of the SSD? This would be the easiest to solve problems and are they are quite likely

I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do.  (Gune | Titan A.E.)

Offline

#14 2015-08-02 08:48:29

Scriptor
Member
Registered: 2011-01-16
Posts: 144

Re: [SOLVED]SSD failed read fdpma queued

Yes, I just replaced them, both. I even changed the ssd sata port on the mainboard. If I ever have another error, I'll post it.

Thank you again very much smile

Offline

Pages: 1

Board footer

Powered by FluxBB