You are not logged in.
Pages: 1
I noticed this in my errors.log this morning. Is my SSD on it's way out.
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948843] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948845] ata1.00: cmd 61/00:e0:00:08:5f/04:00:14:01:00/40 tag 28 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948845] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948846] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948847] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948849] ata1.00: cmd 61/00:e8:00:04:5f/04:00:14:01:00/40 tag 29 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948849] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948851] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948852] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948854] ata1.00: cmd 61/00:f0:00:00:5f/04:00:14:01:00/40 tag 30 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948854] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948855] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486071] ata1.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x400000 action 0x6 frozen
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486075] ata1.00: irq_stat 0x08000000, interface fatal error
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486077] ata1: SError: { Handshk }
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486080] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486085] ata1.00: cmd 61/00:00:00:a4:5f/04:00:14:01:00/40 tag 0 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486085] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486087] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486089] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486092] ata1.00: cmd 61/00:08:00:a8:5f/04:00:14:01:00/40 tag 1 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486092] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486094] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486095] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486098] ata1.00: cmd 61/00:10:00:ac:5f/04:00:14:01:00/40 tag 2 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486098] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486100] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486102] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486105] ata1.00: cmd 61/00:18:00:b0:5f/04:00:14:01:00/40 tag 3 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486105] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486107] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486108] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486111] ata1.00: cmd 61/00:20:00:b4:5f/04:00:14:01:00/40 tag 4 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486111] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486113] ata1.00: status: { DRDY }
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486114] ata1.00: failed command: WRITE FPDMA QUEUED
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486117] ata1.00: cmd 61/00:28:00:b8:5f/04:00:14:01:00/40 tag 5 ncq 524288 out
Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486117] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
Last edited by z1lt0id (2013-08-23 10:35:22)
Offline
I noticed this in my errors.log this morning. Is my SSD on it's way out.
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948843] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948845] ata1.00: cmd 61/00:e0:00:08:5f/04:00:14:01:00/40 tag 28 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948845] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948846] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948847] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948849] ata1.00: cmd 61/00:e8:00:04:5f/04:00:14:01:00/40 tag 29 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948849] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948851] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948852] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948854] ata1.00: cmd 61/00:f0:00:00:5f/04:00:14:01:00/40 tag 30 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948854] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948855] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486071] ata1.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x400000 action 0x6 frozen Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486075] ata1.00: irq_stat 0x08000000, interface fatal error Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486077] ata1: SError: { Handshk } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486080] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486085] ata1.00: cmd 61/00:00:00:a4:5f/04:00:14:01:00/40 tag 0 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486085] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486087] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486089] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486092] ata1.00: cmd 61/00:08:00:a8:5f/04:00:14:01:00/40 tag 1 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486092] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486094] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486095] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486098] ata1.00: cmd 61/00:10:00:ac:5f/04:00:14:01:00/40 tag 2 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486098] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486100] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486102] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486105] ata1.00: cmd 61/00:18:00:b0:5f/04:00:14:01:00/40 tag 3 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486105] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486107] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486108] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486111] ata1.00: cmd 61/00:20:00:b4:5f/04:00:14:01:00/40 tag 4 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486111] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486113] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486114] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486117] ata1.00: cmd 61/00:28:00:b8:5f/04:00:14:01:00/40 tag 5 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486117] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
look at http://ubuntuforums.org/archive/index.p … 31070.html & https://bugs.launchpad.net/ubuntu/+sour … bug/550559
Offline
IMO, it's something other than your drive. A few observations:
1) FPDMA is a NCQ function. NCQ requires the SATA controller to be in AHCI mode or RAID mode. If you have an old mobo, it's possible that there are 'issues' with the AHCI implementation. It may even be possible that your controller isn't in AHCI/RAID mode at all, and the commands were sent due to a bug.
2) A mobo of mine has issues when the controller is in AHCI mode. When I put the controller in RAID mode the problem disappears. RAID mode includes all the features/functions of AHCI, and Intel recommends using RAID mode rather than AHCI (Source), if only because 'you might want to use it at some point'.
3) On the Ubuntu bug report linked by cpatrick08, post 126 recommended disabling NCQ on SSDs because "SSD drives don't need to optimze the order of disk operationsm apparently it causes some errors". FWIW, Wikipedia disagrees. Still, it could be a good work-around if the errors are causing performance issues.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
z1lt0id wrote:I noticed this in my errors.log this morning. Is my SSD on it's way out.
Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948843] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948845] ata1.00: cmd 61/00:e0:00:08:5f/04:00:14:01:00/40 tag 28 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948845] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948846] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948847] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948849] ata1.00: cmd 61/00:e8:00:04:5f/04:00:14:01:00/40 tag 29 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948849] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948851] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948852] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948854] ata1.00: cmd 61/00:f0:00:00:5f/04:00:14:01:00/40 tag 30 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948854] res 40/00:00:00:24:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 398.948855] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486071] ata1.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x400000 action 0x6 frozen Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486075] ata1.00: irq_stat 0x08000000, interface fatal error Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486077] ata1: SError: { Handshk } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486080] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486085] ata1.00: cmd 61/00:00:00:a4:5f/04:00:14:01:00/40 tag 0 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486085] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486087] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486089] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486092] ata1.00: cmd 61/00:08:00:a8:5f/04:00:14:01:00/40 tag 1 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486092] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486094] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486095] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486098] ata1.00: cmd 61/00:10:00:ac:5f/04:00:14:01:00/40 tag 2 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486098] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486100] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486102] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486105] ata1.00: cmd 61/00:18:00:b0:5f/04:00:14:01:00/40 tag 3 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486105] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486107] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486108] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486111] ata1.00: cmd 61/00:20:00:b4:5f/04:00:14:01:00/40 tag 4 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486111] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error) Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486113] ata1.00: status: { DRDY } Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486114] ata1.00: failed command: WRITE FPDMA QUEUED Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486117] ata1.00: cmd 61/00:28:00:b8:5f/04:00:14:01:00/40 tag 5 ncq 524288 out Aug 15 21:17:25 ziltoid-pc kernel: [ 399.486117] res 40/00:60:00:d4:5f/00:00:14:01:00/40 Emask 0x10 (ATA bus error)
look at http://ubuntuforums.org/archive/index.p … 31070.html & https://bugs.launchpad.net/ubuntu/+sour … bug/550559
Look at these links I found on arch wiki for SSDs https://sites.google.com/site/easylinux … te-actions https://wiki.archlinux.org/index.php/Solid_State_Drives https://wiki.archlinux.org/index.php/SS … l_Clearing https://wiki.archlinux.org/index.php/SSD_Benchmarking
Offline
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
This bug is so elusive, I can't believe it. I also have this problem for 2 or 3 years. I bought an asus u3s6 controller card (sata3+usb3 card) 2 or 3 years ago. After I connected my Crucial RealSSD 128gb to the marvell 9123 controller, the same thing happend. The sata3 controller is useless to me due to this bug . And no, disabling NCQ didn't help either. Maybe in a few years the kernel devs say .. oops ..our mistake (like the usb-stack timing problem they admitted ..after years).
I always thought that this is due to marvells shitty 88SE9123 controller, they had to pull back their first revision due to some PATA compatibility issues http://www.pcper.com/news/Storage/UPDAT … P55-boards, but now I'm not so sure that it's marvell's fault.
RiP, Jeff http://www.slayer.net/at/jeff-hanneman
Offline
@frostbittenking: I came across this old problem with my old AM3 motherboard due to the controller. My new motherboard uses a different controller and has stopped making that error. I realised the error I posted was due to the SATA cables having the slightest kink in them and not being in the socket fully. I was using the old red cables and changed them with the clipped ones and it has since resolved the issue... For now
Offline
Yeah, btdt. I have one of those black ones in the box in which the card was packaged. Tried it with it.... didn't help either. Have read others success stories where this helped. Unfortunately in my case, it didn't. I just can't figure out if it's a problem with the controller or if it's an issue with the ahci subsystem. But thanks for the tip anyway.
RiP, Jeff http://www.slayer.net/at/jeff-hanneman
Offline
Pages: 1