Disk Error: failed command: READ DMA EXT

General support questions including new installations
JamesBoard
Posts: 68
Joined: 2009/05/31 21:13:21

Disk Error: failed command: READ DMA EXT

Postby JamesBoard » 2017/03/17 13:25:03

I have an ASUS Sabertooth X58 system board (2010) and two newer hard drives (HGST 6-TB) running CentOS. After booting, the hard drives work well for some amount of time. Then, during heavy usage, I hear some loud clicking sounds, and after that access to the hard drives hangs for 20-30 seconds. When that happens, I see this error in the dmesg output for each hard drive:

Code: Select all

ata14: lost interrupt (Status 0x50)
ata14.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen
ata14: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
ata14.00: failed command: READ DMA EXT
ata14.00: cmd 25/00:08:a8:d9:30/00:00:46:02:00/e0 tag 0 dma 4096 in
ata14.00: status: { DRDY }
ata14: hard resetting link
ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata14.00: configured for UDMA/133
ata14.00: device reported invalid CHS sector 0
ata14: EH complete


What is causing this?

tunk
Posts: 298
Joined: 2017/02/22 15:08:17

Re: Disk Error: failed command: READ DMA EXT

Postby tunk » 2017/03/17 14:19:33

Clicking noises could be a hardware problem. Run smartctl -a on both disks and see if SMART reports any problems.

User avatar
TrevorH
Forum Moderator
Posts: 22590
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Disk Error: failed command: READ DMA EXT

Postby TrevorH » 2017/03/17 16:21:32

I'd be about 98% sure that that is a hardware error on your disks.

Are you really using CentOS 5? Look at my sig... :(
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

JamesBoard
Posts: 68
Joined: 2009/05/31 21:13:21

Re: Disk Error: failed command: READ DMA EXT

Postby JamesBoard » 2017/03/17 16:32:52

Thanks for your replies. I ran smartctl on the disks and no errors were reported. I also have another disk (same exact type) and it reports the same problems. Because three fairly new disks are all reporting the same problems, I'm somewhat reluctant to blame the hardware.

However, it could be a cable problem. I previously received these errors much more frequently. Then I switched to the SATA cable which came with the hard drives (I had previously used 7-year old cables), and these errors occurred much less frequently.

Could it be that I need higher quality SATA cables? Does such a thing exist?

ps. Yes, I know. CentOS 5. I'm trying to save myself the pain of upgrading as long as I can.

User avatar
TrevorH
Forum Moderator
Posts: 22590
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Disk Error: failed command: READ DMA EXT

Postby TrevorH » 2017/03/17 16:42:42

Yes, cables could be the cause too so definitely worth changing those since they're cheap.

March 31st is rapidly approaching... :( But seriously, if you're using this as a desktop then CentOS 7 with MATE will be a splendid upgrade from CentOS 5 plus gnome2.ancient and you'll wonder why you didn't do it before.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke