Bug 549290 – sys-kernel/gentoo-sources-3.19.3 - Error Read DMA EXT

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Lagu 2015-05-12 17:52:03 UTC]

Created attachment 403144 [details]
lspci -- emerge

Hi all, well here  ugly bug, log:

may 12 14:31:16 TWVWOJRFUYN kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
may 12 14:31:16 TWVWOJRFUYN kernel: ata1.00: irq_stat 0x40000001
may 12 14:31:16 TWVWOJRFUYN kernel: ata1.00: failed command: READ DMA EXT
may 12 14:31:16 TWVWOJRFUYN kernel: ata1.00: cmd 25/00:08:18:08:ec/00:00:3f:00:00/e0 tag 30 dma 4096 in
                                             res 51/40:08:18:08:ec/00:00:3f:00:00/e0 Emask 0x9 (media error)
may 12 14:31:16 TWVWOJRFUYN kernel: ata1.00: status: { DRDY ERR }
may 12 14:31:16 TWVWOJRFUYN kernel: ata1.00: error: { UNC }
may 12 14:31:16 TWVWOJRFUYN kernel: blk_update_request: I/O error, dev sda, sector 1072433176
may 12 14:31:16 TWVWOJRFUYN kernel: EXT4-fs error (device sda5): ext4_wait_block_bitmap:494: comm kworker/u16:5: Cannot read block bitmap - block_grou
may 12 14:31:16 TWVWOJRFUYN kernel: Aborting journal on device sda5-8.
may 12 14:31:16 TWVWOJRFUYN kernel: EXT4-fs (sda5): Remounting filesystem read-only
may 12 14:31:16 TWVWOJRFUYN kernel: EXT4-fs error (device sda5) in ext4_writepages:2395: IO failure

i don't have how reproduce it, well i run a test of smartctl and i get no error on the hdd, logs:

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       450
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   089   079   025    Pre-fail  Always       -       3451
  4 Start_Stop_Count        0x0032   089   089   000    Old_age   Always       -       11815
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       10108
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1682
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       1164
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   063   032   000    Old_age   Always       -       37 (Min/Max 11/70)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       1
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       31531
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       211
225 Load_Cycle_Count        0x0032   070   070   000    Old_age   Always       -       307264

SMART Error Log Version: 1
No Errors Logged


in any case i don't lose data, with fsck can fix the broken data, checking other forums i saw its a kernel problem.

Thx.

[Comment 1 Mike Pagano 2015-06-24 19:13:11 UTC]

I'm about to drop 3.19 from gentoo-sources. Does this still happen with 4.1 ?

[Comment 2 Lagu 2015-06-26 18:10:40 UTC]

Hi, now i'm using 4.0.5 and works fine, but some time letter of this report my hdd dead, so i really can't confirm it, and i can't say is for the hdd because existe this issue in others distros, if happend again i'll notify it.

Thx.

[Comment 3 Mike Pagano 2015-06-26 22:49:48 UTC]

Ok, thanks for replying, just post back here and I'll reopen if it happens again.