ATA bus error

techbob

Limp Gawd
Joined
Jun 26, 2009
Messages
364
The PC is a 4 year old, specs as follows:
  • CPU - AMD Phenom II X4 955
  • Motherboard - GIGABYTE GA-880GA-UD3H AM3 AMD 880G SATA 6Gb/s USB 3.0 HDMI ATX AMD Motherboard
  • PSU - 500W Corsair Bronze - not sure of model #
  • Memory - G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333
  • Drives SATA mechanical, (not SSD)
  • No separate GPU
  • OS - Linux Mint

I was doing a backup with Clonezilla a few days ago and able to complete but got messages that were also found in an Kernal Log - same errors as from Clonezilla:

Kern.log.1 -​

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121375] ata7.00: failed command: WRITE FPDMA QUEUED

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121387] ata7.00: cmd 61/08:10:e8:3c:26/00:00:94:00:00/40 tag 2 ncq 4096 out

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121387] res 40/00:50:e8:41:26/00:00:94:00:00/40 Emask 0x10 (ATA bus error)

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121393] ata7.00: status: { DRDY }

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121399] ata7.00: failed command: WRITE FPDMA QUEUED

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121410] ata7.00: cmd 61/08:18:38:3d:26/00:00:94:00:00/40 tag 3 ncq 4096 out

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121410] res 40/00:50:e8:41:26/00:00:94:00:00/40 Emask 0x10 (ATA bus error)

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121417] ata7.00: status: { DRDY }

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121422] ata7.00: failed command: WRITE FPDMA QUEUED

Feb 15 18:00:00 mint17-GA-880GA-UD3H kernel: [2024357.121434] ata7.00: cmd 61/10:20:68:3d:26/00:00:94:00:00/40 tag 4 ncq 8192 out


This happened a few days ago, and since then the log is clean and no other problems. I'm checking the kern.log daily.
I ran MEM86 test overnight and no errors. No SMART errors on the two hard drives.

Any ideas what could be wrong? My guess, the mother board or PSU failing? There are no other symptoms. Clonezilla was able to complete backup. The next day tried again and no errors. Fsck is always turned on during backup.

Thanks!
 
30+ views and no comments or suggestions? Any ideas on what is going on would be appreciated! One more thing, the PC is usually on 24x7. But the Clonezilla errors occured after the required reboot. Clonezilla works by booting their live cd.
 
maybe bad spots on the hdd that got corrected so not enough to trip smart. run a full test on the hdd, memtest and a smart check arent gonna show anything.
 
maybe bad spots on the hdd that got corrected so not enough to trip smart. run a full test on the hdd, memtest and a smart check arent gonna show anything.

Good idea. I did a "quick" test on the drives but not the full test. Since my original post the logs still clean.
 
When I saw the problem I assumed that "ATA bus error" indicated bad controller, or motherboard. One of the drives has some errors - but not failing:





The problem s-
-Seek Error Rate
-UDMA CRC Error Rate

Is this 2 year old 3TB drive already going south?
 
it looks like its had some issues that were corrected so that might have been the problem during copying. the drive isnt bad yet but i'd keep an eye on it, leave nothing critical on it. what test was that that you ran? i dont recognize the window. if possible i would get the test software from the drive manufacturer and see what it says.
 
The disk software - It's a package that came with Mint Linux. Not sure of the name off hand. Nothing critical is on that drive. I have a 3TB extra drive unused, but I think I'll continue to use this until the errors got worse. Based on that test I can rule out a bad SATA cable or other things? I don't like swapping things out unless it's necessary. Thanks!

it looks like its had some issues that were corrected so that might have been the problem during copying. the drive isnt bad yet but i'd keep an eye on it, leave nothing critical on it. what test was that that you ran? i dont recognize the window. if possible i would get the test software from the drive manufacturer and see what it says.
 
yeah i doubt its the cable as you'd still be getting errors. id keep using it but keep an eye on it. i dont know linux but if there is one, installing a hdd monitor program would be a good idea too.
 
I used The Seagate for DOS, boot disk, and no errors found. I think that disk manufacturers don't like to find disk errors. I'll keep an eye on it and so far no other ATA Bus Error.
Thanks for the replies.
 
good good then whatever was wrong got corrected. just check on it once in a while to be safe.
 
Back
Top