You are not logged in.

#1 2014-12-07 07:31:05

frig
Member
From: Thuringia - Germany
Registered: 2013-06-11
Posts: 12

[SOLVED] libata: status{DRDY ERR} failed command: READ DMA

Hello there,

acquired a new amd R7 SSD to boost up my asus 1000H experience (it quiet actually does the double of the rotating seagate integrated) and are watching those errormessages during boot.

[    2.263498] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[    2.420827] ata1.00: ATA-8: Radeon R7, 1.00, max UDMA/133
[    2.423824] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 0/32)
[    2.433962] ata1.00: configured for UDMA/133
[    2.480106] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    2.483457] ata1.00: BMDMA stat 0x24
[    2.486730] ata1.00: failed command: READ DMA
[    2.489985] ata1.00: cmd c8/00:08:a8:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.496697] ata1.00: status: { DRDY ERR }
[    2.500063] ata1.00: error: { ABRT }
[    2.510710] ata1.00: configured for UDMA/133
[    2.514043] ata1: EH complete
[    2.526934] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    2.530401] ata1.00: BMDMA stat 0x24
[    2.533724] ata1.00: failed command: READ DMA
[    2.537034] ata1.00: cmd c8/00:08:88:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.543709] ata1.00: status: { DRDY ERR }
[    2.546931] ata1.00: error: { ABRT }
[    2.557328] ata1.00: configured for UDMA/133
[    2.560569] ata1: EH complete
[    2.573579] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    2.576977] ata1.00: BMDMA stat 0x24
[    2.580177] ata1.00: failed command: READ DMA
[    2.583434] ata1.00: cmd c8/00:08:90:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.590086] ata1.00: status: { DRDY ERR }
[    2.593391] ata1.00: error: { ABRT }
[    2.603991] ata1.00: configured for UDMA/133
[    2.607257] ata1: EH complete
[    2.620245] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    2.623682] ata1.00: BMDMA stat 0x24
[    2.627010] ata1.00: failed command: READ DMA
[    2.630268] ata1.00: cmd c8/00:08:98:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.636873] ata1.00: status: { DRDY ERR }
[    2.640123] ata1.00: error: { ABRT }
[    2.650659] ata1.00: configured for UDMA/133
[    2.653825] ata1: EH complete
[    2.666904] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    2.670101] ata1.00: BMDMA stat 0x24
[    2.673076] ata1.00: failed command: READ DMA
[    2.676084] ata1.00: cmd c8/00:08:a0:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.682256] ata1.00: status: { DRDY ERR }
[    2.685253] ata1.00: error: { ABRT }
[    2.693994] ata1.00: configured for UDMA/133
[    2.697046] ata1: EH complete
[    2.726959] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    2.730130] ata1.00: BMDMA stat 0x24
[    2.736257] ata1.00: failed command: READ DMA
[    2.739324] ata1.00: cmd c8/00:08:00:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.745689] ata1.00: status: { DRDY ERR }
[    2.748865] ata1.00: error: { ABRT }
[    2.757231] ata1.00: configured for UDMA/133
[    2.760390] ata1: EH complete
[    2.773584] ata1.00: limiting speed to UDMA/100:PIO4
[    2.776803] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[    2.779847] ata1.00: BMDMA stat 0x24
[    2.782890] ata1.00: failed command: READ DMA
[    2.785980] ata1.00: cmd c8/00:08:a0:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.792354] ata1.00: status: { DRDY ERR }
[    2.795499] ata1.00: error: { ABRT }
[    2.798626] ata1: soft resetting link
[    2.960611] ata1.00: configured for UDMA/100
[    2.963739] ata1: EH complete
[    2.976877] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    2.980091] ata1.00: BMDMA stat 0x24
[    2.983144] ata1.00: failed command: READ DMA
[    2.986226] ata1.00: cmd c8/00:08:a8:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    2.992504] ata1.00: status: { DRDY ERR }
[    2.995652] ata1.00: error: { ABRT }
[    3.003925] ata1.00: configured for UDMA/100
[    3.007042] ata1: EH complete
[    3.020170] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.023399] ata1.00: BMDMA stat 0x24
[    3.026462] ata1.00: failed command: READ DMA
[    3.029549] ata1.00: cmd c8/00:08:a8:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.035927] ata1.00: status: { DRDY ERR }
[    3.039085] ata1.00: error: { ABRT }
[    3.047327] ata1.00: configured for UDMA/100
[    3.051577] ata1: EH complete
[    3.063562] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.066735] ata1.00: BMDMA stat 0x24
[    3.069694] ata1.00: failed command: READ DMA
[    3.072671] ata1.00: cmd c8/00:08:70:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.078680] ata1.00: status: { DRDY ERR }
[    3.082313] ata1.00: error: { ABRT }
[    3.090631] ata1.00: configured for UDMA/100
[    3.093767] ata1: EH complete
[    3.106937] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.110106] ata1.00: BMDMA stat 0x24
[    3.113094] ata1.00: failed command: READ DMA
[    3.116073] ata1.00: cmd c8/00:08:b0:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.122146] ata1.00: status: { DRDY ERR }
[    3.125194] ata1.00: error: { ABRT }
[    3.137418] ata1.00: configured for UDMA/100
[    3.140507] ata1: EH complete
[    3.153643] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.156823] ata1.00: BMDMA stat 0x24
[    3.159807] ata1.00: failed command: READ DMAlibata: status{DRDY ERR} failed command: READ DMA
[    3.162839] ata1.00: cmd c8/00:08:20:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.168998] ata1.00: status: { DRDY ERR }
[    3.172007] ata1.00: error: { ABRT }
[    3.180668] ata1.00: configured for UDMA/100
[    3.183723] ata1: EH complete
[    3.196959] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.200133] ata1.00: BMDMA stat 0x24
[    3.203119] ata1.00: failed command: READ DMA
[    3.206164] ata1.00: cmd c8/00:08:60:49:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.212299] ata1.00: status: { DRDY ERR }
[    3.215307] ata1.00: error: { ABRT }
[    3.223992] ata1.00: configured for UDMA/100
[    3.227045] ata1: EH complete
[    3.240272] ata1.00: limiting speed to UDMA/33:PIO4
[    3.243410] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[    3.246425] ata1.00: BMDMA stat 0x24
[    3.249432] ata1.00: failed command: READ DMA
[    3.252409] ata1.00: cmd c8/00:08:08:49:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.258466] ata1.00: status: { DRDY ERR }
[    3.261493] ata1.00: error: { ABRT }
[    3.264538] ata1: soft resetting link
[    3.427332] ata1.00: configured for UDMA/33
[    3.430433] ata1: EH complete
[    3.443595] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.446820] ata1.00: BMDMA stat 0x24
[    3.449852] ata1.00: failed command: READ DMA
[    3.452832] ata1.00: cmd c8/00:08:d0:48:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.459026] ata1.00: status: { DRDY ERR }
[    3.462171] ata1.00: error: { ABRT }
[    3.470657] ata1.00: configured for UDMA/33
[    3.473739] ata1: EH complete
[    3.486913] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.490139] ata1.00: BMDMA stat 0x24
[    3.493166] ata1.00: failed command: READ DMA
[    3.496142] ata1.00: cmd c8/00:08:20:48:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.502331] ata1.00: status: { DRDY ERR }
[    3.505461] ata1.00: error: { ABRT }
[    3.514007] ata1.00: configured for UDMA/33
[    3.517105] ata1: EH complete
[    3.530253] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.533492] ata1.00: BMDMA stat 0x24
[    3.536538] ata1.00: failed command: READ DMAlibata: status{DRDY ERR} failed command: READ DMA
[    3.539551] ata1.00: cmd c8/00:08:e0:47:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.545772] ata1.00: status: { DRDY ERR }
[    3.548906] ata1.00: error: { ABRT }
[    3.557336] ata1.00: configured for UDMA/33
[    3.560498] ata1: EH complete
[    3.576774] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.580911] ata1.00: BMDMA stat 0x24
[    3.584568] ata1.00: failed command: READ DMA
[    3.587701] ata1.00: cmd c8/00:08:d0:47:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.593924] ata1.00: status: { DRDY ERR }
[    3.598096] ata1.00: error: { ABRT }
[    3.607296] ata1.00: configured for UDMA/33
[    3.610368] ata1: EH complete
[    3.623605] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.626779] ata1.00: BMDMA stat 0x24
[    3.629744] ata1.00: failed command: READ DMA
[    3.632766] ata1.00: cmd c8/00:08:f8:47:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.638870] ata1.00: status: { DRDY ERR }
[    3.641872] ata1.00: error: { ABRT }
[    3.650611] ata1.00: configured for UDMA/33
[    3.653642] ata1: EH complete
[    3.683604] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.686772] ata1.00: BMDMA stat 0x24
[    3.689736] ata1.00: failed command: READ DMA
[    3.692743] ata1.00: cmd c8/00:08:00:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.698878] ata1.00: status: { DRDY ERR }
[    3.701864] ata1.00: error: { ABRT }
[    3.710673] ata1.00: configured for UDMA/33
[    3.713704] ata1: EH complete
[    3.726837] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.729990] ata1.00: BMDMA stat 0x24
[    3.732974] ata1.00: failed command: READ DMA
[    3.735978] ata1.00: cmd c8/00:08:78:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.742069] ata1.00: status: { DRDY ERR }
[    3.745055] ata1.00: error: { ABRT }
[    3.753991] ata1.00: configured for UDMA/33
[    3.757019] ata1: EH complete
[    3.773597] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.776769] ata1.00: BMDMA stat 0x24
[    3.779733] ata1.00: failed command: READ DMA
[    3.782731] ata1.00: cmd c8/00:07:88:4b:f9/00:00:00:00:00/ed tag 0 dma 3584 in
[    3.788819] ata1.00: status: { DRDY ERR }
[    3.791802] ata1.00: error: { ABRT }
[    3.800656] ata1.00: configured for UDMA/33
[    3.803685] ata1: EH complete
[    3.816836] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.819987] ata1.00: BMDMA stat 0x24
[    3.822972] ata1.00: failed command: READ DMA
[    3.825977] ata1.00: cmd c8/00:08:88:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.832062] ata1.00: status: { DRDY ERR }
[    3.835048] ata1.00: error: { ABRT }
[    3.843961] ata1.00: configured for UDMA/33
[    3.846993] ata1: EH complete
[    3.860289] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    3.863469] ata1.00: BMDMA stat 0x24
[    3.866447] ata1.00: failed command: READ DMA
[    3.869446] ata1.00: cmd c8/00:08:80:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    3.875548] ata1.00: status: { DRDY ERR }
[    3.878532] ata1.00: error: { ABRT }
[    3.887264] ata1.00: configured for UDMA/33
[    3.890287] ata1: EH complete
[    6.760125] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.760135] ata1.00: BMDMA stat 0x24
[    6.760145] ata1.00: failed command: READ DMA
[    6.760162] ata1.00: cmd c8/00:08:00:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.760171] ata1.00: status: { DRDY ERR }
[    6.760178] ata1.00: error: { ABRT }
[    6.767301] ata1.00: configured for UDMA/33
[    6.767364] ata1: EH complete
[    6.776800] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.776811] ata1.00: BMDMA stat 0x24
[    6.776819] ata1.00: failed command: READ DMA
[    6.776838] ata1.00: cmd c8/00:08:a0:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.776847] ata1.00: status: { DRDY ERR }
[    6.776854] ata1.00: error: { ABRT }
[    6.783957] ata1.00: configured for UDMA/33
[    6.784011] ata1: EH complete
[    6.800140] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.800152] ata1.00: BMDMA stat 0x24
[    6.800160] ata1.00: failed command: READ DMAlibata: status{DRDY ERR} failed command: READ DMA
[    6.800178] ata1.00: cmd c8/00:08:a8:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.800187] ata1.00: status: { DRDY ERR }
[    6.800194] ata1.00: error: { ABRT }
[    6.807270] ata1.00: configured for UDMA/33
[    6.807333] ata1: EH complete
[    6.816800] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.816811] ata1.00: BMDMA stat 0x24
[    6.816819] ata1.00: failed command: READ DMA
[    6.816838] ata1.00: cmd c8/00:08:a8:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.816848] ata1.00: status: { DRDY ERR }
[    6.816854] ata1.00: error: { ABRT }
[    6.823953] ata1.00: configured for UDMA/33
[    6.824006] ata1: EH complete
[    6.834673] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.834685] ata1.00: BMDMA stat 0x24
[    6.834693] ata1.00: failed command: READ DMA
[    6.834710] ata1.00: cmd c8/00:08:70:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.834720] ata1.00: status: { DRDY ERR }
[    6.834726] ata1.00: error: { ABRT }
[    6.841449] ata1.00: configured for UDMA/33
[    6.841504] ata1: EH complete
[    6.850112] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.850122] ata1.00: BMDMA stat 0x24
[    6.850131] ata1.00: failed command: READ DMA
[    6.850149] ata1.00: cmd c8/00:08:b0:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.850159] ata1.00: status: { DRDY ERR }
[    6.850166] ata1.00: error: { ABRT }
[    6.857270] ata1.00: configured for UDMA/33
[    6.857325] ata1: EH complete
[    6.866792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.866801] ata1.00: BMDMA stat 0x24
[    6.866810] ata1.00: failed command: READ DMA
[    6.866829] ata1.00: cmd c8/00:08:20:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.866838] ata1.00: status: { DRDY ERR }
[    6.866845] ata1.00: error: { ABRT }
[    6.873943] ata1.00: configured for UDMA/33
[    6.873998] ata1: EH complete
[    6.883475] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.883486] ata1.00: BMDMA stat 0x24
[    6.883495] ata1.00: failed command: READ DMA
[    6.883512] ata1.00: cmd c8/00:08:60:49:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.883521] ata1.00: status: { DRDY ERR }
[    6.883528] ata1.00: error: { ABRT }
[    6.890605] ata1.00: configured for UDMA/33
[    6.892878] ata1: EH complete
[    6.903459] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.903469] ata1.00: BMDMA stat 0x24
[    6.903478] ata1.00: failed command: READ DMA
[    6.903496] ata1.00: cmd c8/00:08:08:49:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.903506] ata1.00: status: { DRDY ERR }
[    6.903513] ata1.00: error: { ABRT }
[    6.910612] ata1.00: configured for UDMA/33
[    6.910675] ata1: EH complete
[    6.923479] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.923489] ata1.00: BMDMA stat 0x24
[    6.923498] ata1.00: failed command: READ DMA
[    6.923516] ata1.00: cmd c8/00:08:d0:48:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.923526] ata1.00: status: { DRDY ERR }
[    6.923532] ata1.00: error: { ABRT }
[    6.926080] ata1.00: configured for UDMA/33
[    6.926140] ata1: EH complete
[    6.936806] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.936816] ata1.00: BMDMA stat 0x24
[    6.936825] ata1.00: failed command: READ DMA
[    6.936842] ata1.00: cmd c8/00:08:20:48:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.936852] ata1.00: status: { DRDY ERR }
[    6.936859] ata1.00: error: { ABRT }
[    6.945210] ata1.00: configured for UDMA/33
[    6.945269] ata1: EH complete
[    6.953493] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.953503] ata1.00: BMDMA stat 0x24
[    6.953512] ata1.00: failed command: READ DMA
[    6.953531] ata1.00: cmd c8/00:08:e0:47:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.953541] ata1.00: status: { DRDY ERR }
[    6.953547] ata1.00: error: { ABRT }
[    6.960623] ata1.00: configured for UDMA/33
[    6.960685] ata1: EH complete
[    6.972021] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.972032] ata1.00: BMDMA stat 0x24
[    6.972041] ata1.00: failed command: READ DMA
[    6.972059] ata1.00: cmd c8/00:08:d0:47:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.972069] ata1.00: status: { DRDY ERR }
[    6.972076] ata1.00: error: { ABRT }
[    6.978496] ata1.00: configured for UDMA/33
[    6.978551] ata1: EH complete
[    6.987805] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    6.987816] ata1.00: BMDMA stat 0x24
[    6.987825] ata1.00: failed command: READ DMA
[    6.987844] ata1.00: cmd c8/00:08:f8:47:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    6.987855] ata1.00: status: { DRDY ERR }
[    6.987862] ata1.00: error: { ABRT }
[    6.994054] ata1.00: configured for UDMA/33
[    6.994112] ata1: EH complete
[    7.061253] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    7.061262] ata1.00: BMDMA stat 0x24
[    7.061269] ata1.00: failed command: READ DMA
[    7.061281] ata1.00: cmd c8/00:08:00:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    7.061288] ata1.00: status: { DRDY ERR }
[    7.061293] ata1.00: error: { ABRT }
[    7.067754] ata1.00: configured for UDMA/33
[    7.067793] ata1: EH complete
[    7.076833] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    7.076844] ata1.00: BMDMA stat 0x24
[    7.076853] ata1.00: failed command: READ DMA
[    7.076872] ata1.00: cmd c8/00:08:78:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    7.076882] ata1.00: status: { DRDY ERR }
[    7.076888] ata1.00: error: { ABRT }
[    7.084012] ata1.00: configured for UDMA/33
[    7.084060] ata1: EH complete
[    7.096775] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    7.096783] ata1.00: BMDMA stat 0x24
[    7.096790] ata1.00: failed command: READ DMA
[    7.096802] ata1.00: cmd c8/00:07:88:4b:f9/00:00:00:00:00/ed tag 0 dma 3584 in
[    7.096809] ata1.00: status: { DRDY ERR }
[    7.096813] ata1.00: error: { ABRT }
[    7.104009] ata1.00: configured for UDMA/33
[    7.104046] ata1: EH complete
[    7.113495] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    7.113509] ata1.00: BMDMA stat 0x24
[    7.113522] ata1.00: failed command: READ DMA
[    7.113547] ata1.00: cmd c8/00:08:88:4a:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    7.113560] ata1.00: status: { DRDY ERR }
[    7.113570] ata1.00: error: { ABRT }
[    7.120540] ata1.00: configured for UDMA/33
[    7.120578] ata1: EH complete
[    7.130188] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[    7.130203] ata1.00: BMDMA stat 0x24
[    7.130216] ata1.00: failed command: READ DMA
[    7.130242] ata1.00: cmd c8/00:08:80:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
[    7.130255] ata1.00: status: { DRDY ERR }
[    7.130264] ata1.00: error: { ABRT }
[    7.137317] ata1.00: configured for UDMA/33
[    7.137353] ata1: EH complete
[   10.733468] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   10.733482] ata1.00: BMDMA stat 0x24
[   10.733494] ata1.00: failed command: READ DMA
[   10.733513] ata1.00: cmd c8/00:01:87:4b:f9/00:00:00:00:00/ed tag 0 dma 512 in
[   10.733523] ata1.00: status: { DRDY ERR }
[   10.733531] ata1.00: error: { ABRT }
[   10.740782] ata1.00: configured for UDMA/33
[   10.740833] ata1: EH complete

#Produktbeschreibung
[    2.420827] ata1.00: ATA-8: Radeon R7, 1.00, max UDMA/133
[    2.437274] scsi 0:0:0:0: Direct-Access     ATA      Radeon R7        1.00 PQ: 0 ANSI: 5

The Last 3 Lines are for the support if i have to return the drive. (Nobody wants to know his car will explode for sure and ride it until it realy does)

No occasional Errors.
The drive doesn't spit out errors if plugged through multiple 2,5'' to usb adaptors (diversing brands also), it isn't affected by the actual kernel since i started with 3.16 and upgraded lately to 3.17 and the error-message persists in similar matters.
Using a different PC (wortmann/clevo 1547p) results in no error-messages (same procedure 3.16 and .17 kernel, internal SATA and external through the adaptors).
If i use the delivered HDD, the various other 2,5'' HDD's lying around my table or whatever doesn't result in error-messages either, thus i think the sata-port isn't damaged on the pc-side. Blowing dust from the connectors and ensuring the drive was in place [check!]

I tried both multiple times, with live and resident OS.
No bad sectors, last time trimmed: 05122014.


To conclude: the Error-messages do not impose a threat on the performance, they are simply annoying :s Googling did reveal similar problems and error messages but never {DRDY  ERR} as is, so i consider myself a postworthy case.

I'm using openrc.
P.S. on systemd it also spits out the errors above

Solution:
I read in the libata-sourcecode and greped the error messages in the ata part of the kernel sources and got some known issues with OCZ-SSD's in combination with DMA.
Disabling of DMA solved the problem and rendered the drive access ultra slow, so i searched anew, another read in the sources brought me to the assumption that something with AHCI could be wrong, i googled and revealed
https://www.bios-mods.com/forum/Thread- … eePC-1000H
which proposes a bios-mod which enables AHCI-capabilities already present on the ASUS1000H.
/*not encouraging to upgrade your bios, consider your case!*/

I changed the bios to the modded one and alas the error is gone, the speed is remarkably better.

Sadly i'm not able to explain the issue or the solution technically correct.

With kind regards, frig

Last edited by frig (2015-01-13 02:46:07)

Offline

#2 2014-12-07 15:16:26

alex.theoto
Member
From: Athens Greece
Registered: 2014-11-30
Posts: 307

Re: [SOLVED] libata: status{DRDY ERR} failed command: READ DMA

When I see these type of errors, the condition is critical.

If I understand right, the same hdd works fine on other internal connected computer and with usb connection.
If you installed another hdd on the 'problematic' pc and you see some errors then the pc's controller might dyeing.

One good solution to see what is going on is to install 'testdisk' and 'smartmontools'. Start the smartd daemon and do a deep search on the hdd with testdisk app. Look at the 'deep search' if the presses freezes on some sectors and at the same time on another terminal type 'dmesg |tail -n 20' to see kernels last log. You can use smartctl program to see the hdd's condition.

In any case, make sure you have a backup.

Offline

#3 2014-12-08 18:43:29

frig
Member
From: Thuringia - Germany
Registered: 2013-06-11
Posts: 12

Re: [SOLVED] libata: status{DRDY ERR} failed command: READ DMA

I run all your mentioned test, nothing revealed anything special, testdisk moaned about too big drive. smartd -d mentioned a missing database entry (which smartctl -P showall | grep R7 or anything relating the SSD did confirm) and an "invalid SMART checksum", which a quick internet-search revealed as not severe.

smartctl -a /dev/sda after a -t short:

smartctl 6.3 2014-07-26 r3976 [i686-linux-3.17.4-eeefrig] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Radeon R7
Serial Number:    A22MD061446000024
LU WWN Device Id: 5 e83a97 10001a041
Firmware Version: 1.00
User Capacity:    120,034,123,776 bytes [120 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Mon Dec  8 12:20:32 2014 UTC
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: 			 (0x1d) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Abort Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x00)	Error logging NOT supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   0) minutes.
Extended self-test routine
recommended polling time: 	 (   0) minutes.

SMART Attributes Data Structure revision number: 18
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0000   000   000   000    Old_age   Offline      -       0
  9 Power_On_Hours          0x0000   100   100   000    Old_age   Offline      -       41
 12 Power_Cycle_Count       0x0000   100   100   000    Old_age   Offline      -       28
171 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       38761552
174 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       9
195 Hardware_ECC_Recovered  0x0000   100   100   000    Old_age   Offline      -       0
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       0
197 Current_Pending_Sector  0x0000   100   100   000    Old_age   Offline      -       0
208 Unknown_SSD_Attribute   0x0000   100   100   000    Old_age   Offline      -       2
210 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
224 Unknown_SSD_Attribute   0x0000   100   100   000    Old_age   Offline      -       1
233 Media_Wearout_Indicator 0x0000   100   100   000    Old_age   Offline      -       100
241 Total_LBAs_Written      0x0000   100   100   000    Old_age   Offline      -       96
242 Total_LBAs_Read         0x0000   100   100   000    Old_age   Offline      -       154
249 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       5352170

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

Selective Self-tests/Logging not supported

The 'invalid SMART checksum' vanished after the test. As i had 'smartd -d' running alongside every check it stopped moaning about the missing database entry (which still is missing) and the invalid checksum (which the test cleared).

Here is a unique excerpt of dmesg which actually changed from the previous one:

[  582.906871] ata1.00: error: { ABRT }
[  582.914018] ata1.00: configured for UDMA/33
[  582.914060] ata1: EH complete
[  582.923514] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[  582.923522] ata1.00: BMDMA stat 0x24
[  582.923529] ata1.00: failed command: READ DMA
[  582.923542] ata1.00: cmd c8/00:08:98:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
         res 51/04:08:98:4b:f9/00:00:0d:00:00/ed Emask 0x1 (device error)
[  582.923549] ata1.00: status: { DRDY ERR }
[  582.923553] ata1.00: error: { ABRT }
[  582.930700] ata1.00: configured for UDMA/33
[  582.930747] ata1: EH complete

The changed part is in

[  582.923542] ata1.00: cmd c8/00:08:98:4b:f9/00:00:00:00:00/ed tag 0 dma 4096 in
         res 51/04:08:98:4b:f9/00:00:0d:00:00/ed Emask 0x1 (device error)

which probably is the resource tried to read ? (i don't actually know it's just a wild guess :p )
This is the exact error i encountered the first time, all subsequent times the error in the opening post appeared.

I forgot to testdisk /log but to answer your questions: no hangs at all. The strange part in the end showed something around 8+ partitions found, none recoverable. Since this was supposed to be a 'brand' new ssd and i only did 2 repartitionings (each of  max.2 gpt partitions), this assumption should be false!(?)

I do a smartctl -t long and a  testdisk /log today.

With kind regards, frig.

Last edited by frig (2014-12-09 11:45:08)

Offline

Board footer

Powered by FluxBB