Find the answer to your Linux question:
Results 1 to 2 of 2
I've got a raid array, I'm not getting any raid errors, but I'm getting some errors in /var/log/messages (fedora) that appear to be disk/controller related. Most of the errors don't ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    May 2014
    Posts
    1

    kernel ata errors


    I've got a raid array, I'm not getting any raid errors, but I'm getting some errors in /var/log/messages (fedora) that appear to be disk/controller related. Most of the errors don't indicate a specific drive, but occaisionally indicate sdd. Can anyone give me some more specific on the errors? I am thinking I'll fault/remove/replace sdd and see if the errors go away. Still, strange to me raid doesn't fault/remove the drive automatically, no? Errors below. Thanks for any advice. - Mike

    use=00000084 pp_flags=00000001, dev error, EDMA self-disable
    May 15 21:25:22 ash kernel: [125334.509114] ata5.00: failed command: READ DMA
    May 15 21:25:22 ash kernel: [125334.516975] ata5.00: cmd c8/00:d0:60:e6:27/00:00:00:00:00/e0 tag 0 dma 106496 in
    May 15 21:25:22 ash kernel: [125334.516977] res 51/40:58:d8:e6:27/40:00:8d:00:00/00 Emask 0x9 (media error)
    May 15 21:25:22 ash kernel: [125334.532679] ata5.00: status: { DRDY ERR }
    May 15 21:25:22 ash kernel: [125334.540500] ata5.00: error: { UNC }
    May 15 21:25:22 ash kernel: [125334.548272] ata5: hard resetting link
    May 15 21:25:23 ash kernel: [125335.004044] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 15 21:25:23 ash kernel: [125335.019053] ata5.00: configured for UDMA/33
    May 15 21:25:23 ash kernel: [125335.019064] ata5: EH complete
    May 15 21:25:29 ash kernel: [125341.442345] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
    May 15 21:25:29 ash kernel: [125341.450140] ata5.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
    May 15 21:25:29 ash kernel: [125341.457942] ata5.00: failed command: READ DMA
    May 15 21:25:29 ash kernel: [125341.465682] ata5.00: cmd c8/00:d0:60:e6:27/00:00:00:00:00/e0 tag 0 dma 106496 in
    May 15 21:25:29 ash kernel: [125341.465684] res 51/40:58:d8:e6:27/40:00:8d:00:00/00 Emask 0x9 (media error)
    May 15 21:25:29 ash kernel: [125341.481243] ata5.00: status: { DRDY ERR }
    May 15 21:25:29 ash kernel: [125341.488990] ata5.00: error: { UNC }
    May 15 21:25:29 ash kernel: [125341.496659] ata5: hard resetting link
    May 15 21:25:30 ash kernel: [125341.953036] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 15 21:25:30 ash kernel: [125341.968052] ata5.00: configured for UDMA/33
    May 15 21:25:30 ash kernel: [125341.968061] ata5: EH complete
    May 15 21:25:40 ash kernel: [125351.916170] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
    May 15 21:25:40 ash kernel: [125351.923847] ata5.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
    May 15 21:25:40 ash kernel: [125351.931559] ata5.00: failed command: READ DMA
    May 15 21:25:40 ash kernel: [125351.939242] ata5.00: cmd c8/00:d0:60:e6:27/00:00:00:00:00/e0 tag 0 dma 106496 in
    May 15 21:25:40 ash kernel: [125351.939244] res 51/40:47:e9:e6:27/40:00:8d:00:00/00 Emask 0x9 (media error)
    May 15 21:25:40 ash kernel: [125351.954674] ata5.00: status: { DRDY ERR }
    May 15 21:25:40 ash kernel: [125351.962409] ata5.00: error: { UNC }
    May 15 21:25:40 ash kernel: [125351.970080] ata5: hard resetting link
    May 15 21:25:40 ash kernel: [125352.426046] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 15 21:25:40 ash kernel: [125352.441052] ata5.00: configured for UDMA/33
    May 15 21:25:40 ash kernel: [125352.441061] ata5: EH complete

    May 15 21:25:49 ash kernel: [125361.511374] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
    May 15 21:25:49 ash kernel: [125361.519074] ata5.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
    May 15 21:25:49 ash kernel: [125361.526780] ata5.00: failed command: READ DMA
    May 15 21:25:49 ash kernel: [125361.534467] ata5.00: cmd c8/00:d0:60:e6:27/00:00:00:00:00/e0 tag 0 dma 106496 in
    May 15 21:25:49 ash kernel: [125361.534469] res 51/40:47:e9:e6:27/40:00:8d:00:00/00 Emask 0x9 (media error)
    May 15 21:25:49 ash kernel: [125361.549916] ata5.00: status: { DRDY ERR }
    May 15 21:25:49 ash kernel: [125361.557657] ata5.00: error: { UNC }
    May 15 21:25:49 ash kernel: [125361.565342] ata5: hard resetting link
    May 15 21:25:50 ash kernel: [125362.021049] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 15 21:25:50 ash kernel: [125362.036055] ata5.00: configured for UDMA/33
    May 15 21:25:50 ash kernel: [125362.036091] sd 4:0:0:0: [sdd] Unhandled sense code
    May 15 21:25:50 ash kernel: [125362.036094] sd 4:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    May 15 21:25:50 ash kernel: [125362.036098] sd 4:0:0:0: [sdd] Sense Key : Medium Error [current] [descriptor]
    May 15 21:25:50 ash kernel: [125362.036104] Descriptor sense data with sense descriptors (in hex):
    May 15 21:25:50 ash kernel: [125362.036107] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
    May 15 21:25:50 ash kernel: [125362.036117] 00 27 e6 e9
    May 15 21:25:50 ash kernel: [125362.036121] sd 4:0:0:0: [sdd] Add. Sense: Unrecovered read error - auto reallocate failed
    May 15 21:25:50 ash kernel: [125362.036128] sd 4:0:0:0: [sdd] CDB: Read(10): 28 00 00 27 e6 60 00 00 d0 00
    May 15 21:25:50 ash kernel: [125362.036137] end_request: I/O error, dev sdd, sector 2615017
    May 15 21:25:50 ash kernel: [125362.043863] ata5: EH complete
    May 15 21:26:09 ash kernel: [125381.085774] raid5_end_read_request: 1 callbacks suppressed
    May 15 21:26:09 ash kernel: [125381.085779] md/raid:md0: read error corrected (8 sectors at 2615160 on sdd)
    May 15 21:26:28 ash kernel: [125400.548423] md/raid:md0: read error corrected (8 sectors at 2615016 on sdd)
    May 15 21:26:28 ash kernel: [125400.548429] md/raid:md0: read error corrected (8 sectors at 2615024 on sdd)
    May 15 21:26:28 ash kernel: [125400.548432] md/raid:md0: read error corrected (8 sectors at 2615032 on sdd)
    May 15 21:26:28 ash kernel: [125400.548436] md/raid:md0: read error corrected (8 sectors at 2615040 on sdd)
    May 15 21:26:28 ash kernel: [125400.548439] md/raid:md0: read error corrected (8 sectors at 2615048 on sdd)
    May 15 21:26:28 ash kernel: [125400.548442] md/raid:md0: read error corrected (8 sectors at 2615056 on sdd)
    May 15 21:26:28 ash kernel: [125400.548446] md/raid:md0: read error corrected (8 sectors at 2615064 on sdd)
    May 15 21:26:28 ash kernel: [125400.548449] md/raid:md0: read error corrected (8 sectors at 2615072 on sdd)
    May 15 21:26:28 ash kernel: [125400.548453] md/raid:md0: read error corrected (8 sectors at 2615080 on sdd)
    May 15 21:28:58 ash kernel: [125550.868752] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
    May 15 21:28:58 ash kernel: [125550.876430] ata5.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
    May 15 21:28:59 ash kernel: [125550.884155] ata5.00: failed command: READ DMA
    May 15 21:28:59 ash kernel: [125550.891858] ata5.00: cmd c8/00:10:b0:a5:09/00:00:00:00:00/e0 tag 0 dma 8192 in
    May 15 21:28:59 ash kernel: [125550.891860] res 51/40:0a:b6:a5:09/40:00:8d:00:00/00 Emask 0x9 (media error)
    May 15 21:28:59 ash kernel: [125550.907293] ata5.00: status: { DRDY ERR }
    May 15 21:28:59 ash kernel: [125550.915012] ata5.00: error: { UNC }
    May 15 21:28:59 ash kernel: [125550.922655] ata5: hard resetting link
    May 15 21:28:59 ash kernel: [125551.379050] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 15 21:28:59 ash kernel: [125551.429053] ata5.00: configured for UDMA/33
    May 15 21:28:59 ash kernel: [125551.429062] ata5: EH complete
    May 15 21:29:30 ash kernel: [125582.704205] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
    May 15 21:29:30 ash kernel: [125582.711876] ata5.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
    May 15 21:29:30 ash kernel: [125582.719598] ata5.00: failed command: READ DMA
    May 15 21:29:30 ash kernel: [125582.727308] ata5.00: cmd c8/00:10:00:ae:09/00:00:00:00:00/e0 tag 0 dma 8192 in
    May 15 21:29:30 ash kernel: [125582.727309] res 51/40:05:0b:ae:09/40:00:8d:00:00/00 Emask 0x9 (media error)
    May 15 21:29:30 ash kernel: [125582.742759] ata5.00: status: { DRDY ERR }
    May 15 21:29:30 ash kernel: [125582.750480] ata5.00: error: { UNC }
    May 15 21:29:30 ash kernel: [125582.758124] ata5: hard resetting link
    May 15 21:29:31 ash kernel: [125583.214036] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 15 21:29:31 ash kernel: [125583.264052] ata5.00: configured for UDMA/33
    May 15 21:29:31 ash kernel: [125583.264063] ata5: EH complete
    May 15 21:29:36 ash kernel: [125588.087563] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
    May 15 21:29:36 ash kernel: [125588.095216] ata5.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
    May 15 21:29:36 ash kernel: [125588.102935] ata5.00: failed command: READ DMA
    May 15 21:29:36 ash kernel: [125588.110642] ata5.00: cmd c8/00:10:00:ae:09/00:00:00:00:00/e0 tag 0 dma 8192 in
    May 15 21:29:36 ash kernel: [125588.110645] res 51/40:04:0c:ae:09/40:00:8d:00:00/00 Emask 0x9 (media error)
    May 15 21:29:36 ash kernel: [125588.126113] ata5.00: status: { DRDY ERR }
    May 15 21:29:36 ash kernel: [125588.133849] ata5.00: error: { UNC }
    May 15 21:29:36 ash kernel: [125588.141545] ata5: hard resetting link
    May 15 21:29:36 ash kernel: [125588.597031] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 15 21:29:36 ash kernel: [125588.612052] ata5.00: configured for UDMA/33
    May 15 21:29:36 ash kernel: [125588.612060] ata5: EH complete

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,578
    What does the disk utility say, with regarding to the S.M.A.R.T. data? That may give you some better indications as to what is going on with the device.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •