Jump to content

ata9.00: failed command: READ FPDMA QUEUED error


Recommended Posts

I occasionally get a error that says ata9.00: failed command with the below messages in the syslog:

May 28 08:19:14 Unraid kernel: sas: sas_scsi_find_task: task 0x00000000728b3cab is done
May 28 08:19:14 Unraid kernel: sas: sas_eh_handle_sas_errors: task 0x00000000728b3cab is done
May 28 08:19:14 Unraid kernel: sas: trying to find task 0x00000000357ec383
May 28 08:19:14 Unraid kernel: sas: sas_scsi_find_task: aborting task 0x00000000357ec383
May 28 08:19:14 Unraid kernel: isci 0000:02:00.0: isci_task_abort_task: dev = 000000005c2760bc (STP/SATA), task = 00000000357ec383, old_request == 00000000bafa4ef5
May 28 08:19:14 Unraid kernel: isci 0000:02:00.0: isci_task_abort_task: SATA/STP request or complete_in_target (1), or IDEV_GONE (0), thus no TMF
May 28 08:19:14 Unraid kernel: isci 0000:02:00.0: isci_task_abort_task: Done; dev = 000000005c2760bc, task = 00000000357ec383 , old_request == 00000000bafa4ef5
May 28 08:19:14 Unraid kernel: sas: sas_scsi_find_task: task 0x00000000357ec383 is done
May 28 08:19:14 Unraid kernel: sas: sas_eh_handle_sas_errors: task 0x00000000357ec383 is done
May 28 08:19:14 Unraid kernel: sas: trying to find task 0x0000000049f81fab
May 28 08:19:14 Unraid kernel: sas: sas_scsi_find_task: aborting task 0x0000000049f81fab
May 28 08:19:14 Unraid kernel: isci 0000:02:00.0: isci_task_abort_task: dev = 000000005c2760bc (STP/SATA), task = 0000000049f81fab, old_request == 00000000e30f14fc
May 28 08:19:14 Unraid kernel: isci 0000:02:00.0: isci_task_abort_task: SATA/STP request or complete_in_target (1), or IDEV_GONE (0), thus no TMF
May 28 08:19:14 Unraid kernel: isci 0000:02:00.0: isci_task_abort_task: Done; dev = 000000005c2760bc, task = 0000000049f81fab , old_request == 00000000e30f14fc
May 28 08:19:14 Unraid kernel: sas: sas_scsi_find_task: task 0x0000000049f81fab is done
May 28 08:19:14 Unraid kernel: sas: sas_eh_handle_sas_errors: task 0x0000000049f81fab is done
May 28 08:19:14 Unraid kernel: sas: ata9: end_device-7:2: cmd error handler
May 28 08:19:14 Unraid kernel: sas: ata7: end_device-7:0: dev error handler
May 28 08:19:14 Unraid kernel: sas: ata8: end_device-7:1: dev error handler
May 28 08:19:14 Unraid kernel: sas: ata9: end_device-7:2: dev error handler
May 28 08:19:14 Unraid kernel: sas: ata10: end_device-7:3: dev error handler
May 28 08:19:14 Unraid kernel: ata9.00: exception Emask 0x0 SAct 0xf8000416 SErr 0x0 action 0x6 frozen
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/f0:00:70:0d:46/02:00:1c:00:00/40 tag 1 ncq dma 385024 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/80:00:60:10:46/02:00:1c:00:00/40 tag 2 ncq dma 327680 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/00:00:88:be:3e/01:00:82:02:00/40 tag 4 ncq dma 131072 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/20:00:20:74:3b/00:00:01:00:00/40 tag 10 ncq dma 16384 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/08:00:20:0d:46/00:00:1c:00:00/40 tag 27 ncq dma 4096 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/08:00:28:0d:46/00:00:1c:00:00/40 tag 28 ncq dma 4096 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/10:00:30:0d:46/00:00:1c:00:00/40 tag 29 ncq dma 8192 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/10:00:40:0d:46/00:00:1c:00:00/40 tag 30 ncq dma 8192 in
May 28 08:19:14 Unraid kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9.00: failed command: READ FPDMA QUEUED
May 28 08:19:14 Unraid kernel: ata9.00: cmd 60/20:00:50:0d:46/00:00:1c:00:00/40 tag 31 ncq dma 16384 in
May 28 08:19:14 Unraid kernel:         res 40/00:ff:ff:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
May 28 08:19:14 Unraid kernel: ata9.00: status: { DRDY }
May 28 08:19:14 Unraid kernel: ata9: hard resetting link
May 28 08:19:14 Unraid kernel: ata9.00: configured for UDMA/133
May 28 08:19:14 Unraid kernel: ata9: EH complete
May 28 08:19:14 Unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 9 tries: 1

 

I am able to use unraid but find the error concerning. It usually happens when I do a parity check or a big read operation.

Link to comment
1 hour ago, doobyns said:

take a look at this thread :

https://forums.unraid.net/topic/26050-idenitifying-which-drive-is-quotata9quot-throwing-errors-into-syslog/

 

I ran the script from that thread but I get, my motherboard has 4 ports that run at 3gb/s and 2 ports that run at 6/gbs. I am guessing it doesn't show the 4 ports ata for some reason even through its the mothboard port.

Any ideas what I can do to find the ata9?

root@Unraid:/boot# bash ata_devices.sh
(Device sda is not an ATA device, but a USB device [e. g. a pen drive])
sdb: ata1.00
sdc: ata2.00
cat: '/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/host7/port-7:0/end_device-7:0/target7:0:0/hostsdd/scsi_host/hostsdd/unique_id': No such file or directory
: ata.
cat: '/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/host7/port-7:1/end_device-7:1/target7:0:1/hostsde/scsi_host/hostsde/unique_id': No such file or directory
: ata.
cat: '/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/host7/port-7:2/end_device-7:2/target7:0:2/hostsdf/scsi_host/hostsdf/unique_id': No such file or directory
: ata.
cat: '/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/host7/port-7:3/end_device-7:3/target7:0:3/hostsdg/scsi_host/hostsdg/unique_id': No such file or directory
: ata.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...