ata7.00: failed command: SEND FPDMA QUEUEDHow do you fix “failed command: IDENTIFY DEVICE” showing up in dmesg?SSD: Support for SATA 3.1 and “queued TRIM”VMware Player - Failed to build vmnet. Failed to execute the build commandRecovery action for reserved kernel page: FailedBuild failed mainlineReplacing Failed Boot Disk

Translate "Everything burns" into classical Latin

Magento2 :How To Use Form Key In Frontend Grid Using Ui Component

Can there be an atomic nucleus where there are more protons than neutrons?

What do you call a document which has no content?

Is any one against the rational teachings of Maimonides?

How can I turn on Adventure Sync?

Are Snap and Flatpack apps safe to install? Are they "official", approved or tested for a particular distro version?

"inuendo" in a piano score

The travel to a friend

Usefulness of Nash embedding theorem

What does すきすき mean here?

I got this nail stuck in my tire, should I plug or replace?

How can demon technology be prevented from surpassing humans?

"Table" method for expanding brackets vs "each term in the first bracket gets multiplied by each term in the second bracket"

When did 5 foot squares become standard in D&D?

Why does Sonny say they call Michael "Giogali"?

Why is beatboxing called 「ヒューマンビートボックス」?

What is this game with a red cricket pushing a ball?

Text on old-fashioned differential geometry

Can digital computers understand infinity?

How to protect my Wi-Fi password from being displayed by Android phones when sharing it with QR code?

A fast aquatic predator with multiple eyes and pupils. Would these eyes be possible?

'Pound' meaning in this context

Why was the wedding ring missing during the twist of The Sixth Sense



ata7.00: failed command: SEND FPDMA QUEUED


How do you fix “failed command: IDENTIFY DEVICE” showing up in dmesg?SSD: Support for SATA 3.1 and “queued TRIM”VMware Player - Failed to build vmnet. Failed to execute the build commandRecovery action for reserved kernel page: FailedBuild failed mainlineReplacing Failed Boot Disk






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









0

















I regularly get the following error on my Ubuntu Server 18.10:



00:00:30 systemd[1]: Starting Discard unused blocks...
00:00:30 systemd[1]: Starting Rotate log files...
00:00:30 systemd[1]: Started Rotate log files.
00:01:01 kernel: ata7.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x6 frozen
00:01:01 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:01 kernel: ata7.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:01 kernel: ata7.00: status: DRDY 
00:01:01 kernel: ata7: hard resetting link
00:01:01 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:01 kernel: ata7.00: configured for UDMA/133
00:01:01 kernel: ata7.00: device reported invalid CHS sector 0
00:01:01 kernel: ata7: EH complete
00:01:32 kernel: ata7.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6 frozen
00:01:32 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:32 kernel: ata7.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:32 kernel: ata7.00: status: DRDY 
00:01:32 kernel: ata7: hard resetting link
00:01:32 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:32 kernel: ata7.00: configured for UDMA/133
00:01:32 kernel: ata7.00: device reported invalid CHS sector 0
00:01:32 kernel: ata7: EH complete
00:02:04 kernel: ata7.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6 frozen
00:02:04 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:37 kernel: io_schedule_timeout+0x1e/0x50
00:02:37 kernel: wait_for_completion_io+0xb7/0x140
00:02:37 kernel: ? wake_up_q+0x80/0x80
00:02:37 kernel: submit_bio_wait+0x61/0x90
00:02:37 kernel: blkdev_issue_discard+0x7a/0xd0
00:02:37 kernel: ext4_trim_fs+0x5a9/0x8b0
00:02:37 kernel: ? security_file_open+0x86/0x90
00:02:37 kernel: ext4_ioctl+0xd81/0x14a0
00:02:37 kernel: ? _copy_to_user+0x2b/0x40
00:02:37 kernel: ? cp_new_stat+0x152/0x180
00:02:37 kernel: do_vfs_ioctl+0xa8/0x620
00:02:37 kernel: ? __do_sys_newfstat+0x5f/0x70
00:02:37 kernel: ksys_ioctl+0x67/0x90
00:02:37 kernel: __x64_sys_ioctl+0x1a/0x20
00:02:37 kernel: do_syscall_64+0x5a/0x110
00:02:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
00:02:37 kernel: RIP: 0033:0x7faba5a9e3c7
00:02:37 kernel: Code: Bad RIP value.
00:02:37 kernel: RSP: 002b:00007ffec09ede88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
00:02:37 kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007faba5a9e3c7
00:02:37 kernel: RDX: 00007ffec09ede90 RSI: 00000000c0185879 RDI: 0000000000000004
00:02:37 kernel: RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
00:02:37 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000561d21106dd0
00:02:37 kernel: R13: 00007faba5663ff8 R14: 00007ffec09edfc8 R15: 0000561d21106dd0
00:02:37 kernel: ata7.00: NCQ disabled due to excessive errors
00:02:37 kernel: ata7.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6 frozen
00:02:37 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:37 kernel: ata7.00: cmd 64/01:c0:00:00:00/00:00:00:00:00/a0 tag 24 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:37 kernel: ata7.00: status: DRDY 
00:02:37 kernel: ata7: hard resetting link
00:02:38 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:38 kernel: ata7.00: configured for UDMA/133
00:02:38 kernel: ata7.00: device reported invalid CHS sector 0
00:02:38 kernel: ata7: EH complete
00:03:02 fstrim[29514]: /home/caillou/downloads: 891.5 GiB (957190782976 bytes) trimmed
00:03:02 fstrim[29514]: /: 212.4 GiB (228063428608 bytes) trimmed
00:03:02 systemd[1]: Started Discard unused blocks.


Unfortunately I don't understand what it tries to tell me.



  1. What is ata7.00?

  2. What does failed command: SEND FPDMA QUEUED mean? What is this FPDMA?

  3. What does device reported invalid CHS sector 0 mean?

I suspect it has something to do with a drive, but I have no idea how to debug nor how to fix this issue.



Here is the output of lsblk:



sda 8:0 0 7.3T 0 disk
|-sda1 8:1 0 2G 0 part
`-sda2 8:2 0 7.3T 0 part
sdb 8:16 0 7.3T 0 disk
|-sdb1 8:17 0 2G 0 part
`-sdb2 8:18 0 7.3T 0 part
sdc 8:32 0 7.3T 0 disk
|-sdc1 8:33 0 2G 0 part
`-sdc2 8:34 0 7.3T 0 part
sdd 8:48 0 7.3T 0 disk
|-sdd1 8:49 0 2G 0 part
`-sdd2 8:50 0 7.3T 0 part
sde 8:64 0 3.7T 0 disk
|-sde1 8:65 0 2G 0 part
`-sde2 8:66 0 3.7T 0 part
sdf 8:80 0 7.3T 0 disk
|-sdf1 8:81 0 2G 0 part
`-sdf2 8:82 0 7.3T 0 part
sdg 8:96 0 931.5G 0 disk
`-sdg1 8:97 0 931.5G 0 part /home/caillou/downloads
nvme0n1 259:0 0 232.9G 0 disk
nvme1n1 259:1 0 232.9G 0 disk
|-nvme1n1p1 259:2 0 512M 0 part /boot/efi
`-nvme1n1p2 259:3 0 232.4G 0 part /



  • sdg is an mSATA SSD connected through a PCIe card.


  • sda - sdf are SATA HDDs with ZFS.

Detail of the drives:




  • sda WD Red 8T, mainboard SATA connector.


  • sdb WD Red 8T, mainboard SATA connector.


  • sdc WD Red 8T, mainboard SATA connector.


  • sdd WD Red 8T, mainboard SATA connector.


  • sde WD Red 4T, mainboard SATA connector.


  • sdf WD Red 8T, mainboard SATA connector.


  • sdg Samsung mSATA 1T, shuked from Samsung Portable SSD T5, connected through a PCIe card.


  • nvme0n1 and nvme1n1 Samsung 970 EVO, connected to the mainboard m.2 connector.

The system does not show other signs of errors. Also, everything seems to function as intended, with the exception of these errors in the logs.






kernel drive







share|improve this question




























  • As I do not really understand the problem, I find it difficult to correctly tag the question, or to choose an adequate title. Please edit to your liking, if you understand more than I do.

    – Pierre Spring
    May 1 at 14:25











  • Is this a SSD or HDD? Is the ONLY problem seen in syslog, or does the system exhibit operational problems? Do you have a GUI on this server? Are you able to view SMART data using the Disks app (or smartctl)? 1. ata7.00 identifies which SATA drive, 2. FPDMA = First-Party Direct Memory Access, 3. CHS sector 0 means cylinder/head/sector... an outdated form of identifying a location on disk. I have a possible solution, pending your answers.

    – heynnema
    May 1 at 14:54












  • @heynnema I edited the question with responses as good as I could. You say ata7.00 identifies the SATA drive, does that mean it is sdg, as g is the 7th letter?

    – Pierre Spring
    May 1 at 15:11






  • 1





    I've added a quick answer that should probably take care of the problem. Report back.

    – heynnema
    May 1 at 16:31






  • 1





    Status please...

    – heynnema
    May 2 at 15:36

















0

















I regularly get the following error on my Ubuntu Server 18.10:



00:00:30 systemd[1]: Starting Discard unused blocks...
00:00:30 systemd[1]: Starting Rotate log files...
00:00:30 systemd[1]: Started Rotate log files.
00:01:01 kernel: ata7.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x6 frozen
00:01:01 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:01 kernel: ata7.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:01 kernel: ata7.00: status: DRDY 
00:01:01 kernel: ata7: hard resetting link
00:01:01 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:01 kernel: ata7.00: configured for UDMA/133
00:01:01 kernel: ata7.00: device reported invalid CHS sector 0
00:01:01 kernel: ata7: EH complete
00:01:32 kernel: ata7.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6 frozen
00:01:32 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:32 kernel: ata7.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:32 kernel: ata7.00: status: DRDY 
00:01:32 kernel: ata7: hard resetting link
00:01:32 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:32 kernel: ata7.00: configured for UDMA/133
00:01:32 kernel: ata7.00: device reported invalid CHS sector 0
00:01:32 kernel: ata7: EH complete
00:02:04 kernel: ata7.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6 frozen
00:02:04 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:37 kernel: io_schedule_timeout+0x1e/0x50
00:02:37 kernel: wait_for_completion_io+0xb7/0x140
00:02:37 kernel: ? wake_up_q+0x80/0x80
00:02:37 kernel: submit_bio_wait+0x61/0x90
00:02:37 kernel: blkdev_issue_discard+0x7a/0xd0
00:02:37 kernel: ext4_trim_fs+0x5a9/0x8b0
00:02:37 kernel: ? security_file_open+0x86/0x90
00:02:37 kernel: ext4_ioctl+0xd81/0x14a0
00:02:37 kernel: ? _copy_to_user+0x2b/0x40
00:02:37 kernel: ? cp_new_stat+0x152/0x180
00:02:37 kernel: do_vfs_ioctl+0xa8/0x620
00:02:37 kernel: ? __do_sys_newfstat+0x5f/0x70
00:02:37 kernel: ksys_ioctl+0x67/0x90
00:02:37 kernel: __x64_sys_ioctl+0x1a/0x20
00:02:37 kernel: do_syscall_64+0x5a/0x110
00:02:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
00:02:37 kernel: RIP: 0033:0x7faba5a9e3c7
00:02:37 kernel: Code: Bad RIP value.
00:02:37 kernel: RSP: 002b:00007ffec09ede88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
00:02:37 kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007faba5a9e3c7
00:02:37 kernel: RDX: 00007ffec09ede90 RSI: 00000000c0185879 RDI: 0000000000000004
00:02:37 kernel: RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
00:02:37 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000561d21106dd0
00:02:37 kernel: R13: 00007faba5663ff8 R14: 00007ffec09edfc8 R15: 0000561d21106dd0
00:02:37 kernel: ata7.00: NCQ disabled due to excessive errors
00:02:37 kernel: ata7.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6 frozen
00:02:37 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:37 kernel: ata7.00: cmd 64/01:c0:00:00:00/00:00:00:00:00/a0 tag 24 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:37 kernel: ata7.00: status: DRDY 
00:02:37 kernel: ata7: hard resetting link
00:02:38 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:38 kernel: ata7.00: configured for UDMA/133
00:02:38 kernel: ata7.00: device reported invalid CHS sector 0
00:02:38 kernel: ata7: EH complete
00:03:02 fstrim[29514]: /home/caillou/downloads: 891.5 GiB (957190782976 bytes) trimmed
00:03:02 fstrim[29514]: /: 212.4 GiB (228063428608 bytes) trimmed
00:03:02 systemd[1]: Started Discard unused blocks.


Unfortunately I don't understand what it tries to tell me.



  1. What is ata7.00?

  2. What does failed command: SEND FPDMA QUEUED mean? What is this FPDMA?

  3. What does device reported invalid CHS sector 0 mean?

I suspect it has something to do with a drive, but I have no idea how to debug nor how to fix this issue.



Here is the output of lsblk:



sda 8:0 0 7.3T 0 disk
|-sda1 8:1 0 2G 0 part
`-sda2 8:2 0 7.3T 0 part
sdb 8:16 0 7.3T 0 disk
|-sdb1 8:17 0 2G 0 part
`-sdb2 8:18 0 7.3T 0 part
sdc 8:32 0 7.3T 0 disk
|-sdc1 8:33 0 2G 0 part
`-sdc2 8:34 0 7.3T 0 part
sdd 8:48 0 7.3T 0 disk
|-sdd1 8:49 0 2G 0 part
`-sdd2 8:50 0 7.3T 0 part
sde 8:64 0 3.7T 0 disk
|-sde1 8:65 0 2G 0 part
`-sde2 8:66 0 3.7T 0 part
sdf 8:80 0 7.3T 0 disk
|-sdf1 8:81 0 2G 0 part
`-sdf2 8:82 0 7.3T 0 part
sdg 8:96 0 931.5G 0 disk
`-sdg1 8:97 0 931.5G 0 part /home/caillou/downloads
nvme0n1 259:0 0 232.9G 0 disk
nvme1n1 259:1 0 232.9G 0 disk
|-nvme1n1p1 259:2 0 512M 0 part /boot/efi
`-nvme1n1p2 259:3 0 232.4G 0 part /



  • sdg is an mSATA SSD connected through a PCIe card.


  • sda - sdf are SATA HDDs with ZFS.

Detail of the drives:




  • sda WD Red 8T, mainboard SATA connector.


  • sdb WD Red 8T, mainboard SATA connector.


  • sdc WD Red 8T, mainboard SATA connector.


  • sdd WD Red 8T, mainboard SATA connector.


  • sde WD Red 4T, mainboard SATA connector.


  • sdf WD Red 8T, mainboard SATA connector.


  • sdg Samsung mSATA 1T, shuked from Samsung Portable SSD T5, connected through a PCIe card.


  • nvme0n1 and nvme1n1 Samsung 970 EVO, connected to the mainboard m.2 connector.

The system does not show other signs of errors. Also, everything seems to function as intended, with the exception of these errors in the logs.






kernel drive







share|improve this question




























  • As I do not really understand the problem, I find it difficult to correctly tag the question, or to choose an adequate title. Please edit to your liking, if you understand more than I do.

    – Pierre Spring
    May 1 at 14:25











  • Is this a SSD or HDD? Is the ONLY problem seen in syslog, or does the system exhibit operational problems? Do you have a GUI on this server? Are you able to view SMART data using the Disks app (or smartctl)? 1. ata7.00 identifies which SATA drive, 2. FPDMA = First-Party Direct Memory Access, 3. CHS sector 0 means cylinder/head/sector... an outdated form of identifying a location on disk. I have a possible solution, pending your answers.

    – heynnema
    May 1 at 14:54












  • @heynnema I edited the question with responses as good as I could. You say ata7.00 identifies the SATA drive, does that mean it is sdg, as g is the 7th letter?

    – Pierre Spring
    May 1 at 15:11






  • 1





    I've added a quick answer that should probably take care of the problem. Report back.

    – heynnema
    May 1 at 16:31






  • 1





    Status please...

    – heynnema
    May 2 at 15:36













0












0








0








I regularly get the following error on my Ubuntu Server 18.10:



00:00:30 systemd[1]: Starting Discard unused blocks...
00:00:30 systemd[1]: Starting Rotate log files...
00:00:30 systemd[1]: Started Rotate log files.
00:01:01 kernel: ata7.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x6 frozen
00:01:01 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:01 kernel: ata7.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:01 kernel: ata7.00: status: DRDY 
00:01:01 kernel: ata7: hard resetting link
00:01:01 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:01 kernel: ata7.00: configured for UDMA/133
00:01:01 kernel: ata7.00: device reported invalid CHS sector 0
00:01:01 kernel: ata7: EH complete
00:01:32 kernel: ata7.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6 frozen
00:01:32 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:32 kernel: ata7.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:32 kernel: ata7.00: status: DRDY 
00:01:32 kernel: ata7: hard resetting link
00:01:32 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:32 kernel: ata7.00: configured for UDMA/133
00:01:32 kernel: ata7.00: device reported invalid CHS sector 0
00:01:32 kernel: ata7: EH complete
00:02:04 kernel: ata7.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6 frozen
00:02:04 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:37 kernel: io_schedule_timeout+0x1e/0x50
00:02:37 kernel: wait_for_completion_io+0xb7/0x140
00:02:37 kernel: ? wake_up_q+0x80/0x80
00:02:37 kernel: submit_bio_wait+0x61/0x90
00:02:37 kernel: blkdev_issue_discard+0x7a/0xd0
00:02:37 kernel: ext4_trim_fs+0x5a9/0x8b0
00:02:37 kernel: ? security_file_open+0x86/0x90
00:02:37 kernel: ext4_ioctl+0xd81/0x14a0
00:02:37 kernel: ? _copy_to_user+0x2b/0x40
00:02:37 kernel: ? cp_new_stat+0x152/0x180
00:02:37 kernel: do_vfs_ioctl+0xa8/0x620
00:02:37 kernel: ? __do_sys_newfstat+0x5f/0x70
00:02:37 kernel: ksys_ioctl+0x67/0x90
00:02:37 kernel: __x64_sys_ioctl+0x1a/0x20
00:02:37 kernel: do_syscall_64+0x5a/0x110
00:02:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
00:02:37 kernel: RIP: 0033:0x7faba5a9e3c7
00:02:37 kernel: Code: Bad RIP value.
00:02:37 kernel: RSP: 002b:00007ffec09ede88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
00:02:37 kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007faba5a9e3c7
00:02:37 kernel: RDX: 00007ffec09ede90 RSI: 00000000c0185879 RDI: 0000000000000004
00:02:37 kernel: RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
00:02:37 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000561d21106dd0
00:02:37 kernel: R13: 00007faba5663ff8 R14: 00007ffec09edfc8 R15: 0000561d21106dd0
00:02:37 kernel: ata7.00: NCQ disabled due to excessive errors
00:02:37 kernel: ata7.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6 frozen
00:02:37 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:37 kernel: ata7.00: cmd 64/01:c0:00:00:00/00:00:00:00:00/a0 tag 24 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:37 kernel: ata7.00: status: DRDY 
00:02:37 kernel: ata7: hard resetting link
00:02:38 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:38 kernel: ata7.00: configured for UDMA/133
00:02:38 kernel: ata7.00: device reported invalid CHS sector 0
00:02:38 kernel: ata7: EH complete
00:03:02 fstrim[29514]: /home/caillou/downloads: 891.5 GiB (957190782976 bytes) trimmed
00:03:02 fstrim[29514]: /: 212.4 GiB (228063428608 bytes) trimmed
00:03:02 systemd[1]: Started Discard unused blocks.


Unfortunately I don't understand what it tries to tell me.



  1. What is ata7.00?

  2. What does failed command: SEND FPDMA QUEUED mean? What is this FPDMA?

  3. What does device reported invalid CHS sector 0 mean?

I suspect it has something to do with a drive, but I have no idea how to debug nor how to fix this issue.



Here is the output of lsblk:



sda 8:0 0 7.3T 0 disk
|-sda1 8:1 0 2G 0 part
`-sda2 8:2 0 7.3T 0 part
sdb 8:16 0 7.3T 0 disk
|-sdb1 8:17 0 2G 0 part
`-sdb2 8:18 0 7.3T 0 part
sdc 8:32 0 7.3T 0 disk
|-sdc1 8:33 0 2G 0 part
`-sdc2 8:34 0 7.3T 0 part
sdd 8:48 0 7.3T 0 disk
|-sdd1 8:49 0 2G 0 part
`-sdd2 8:50 0 7.3T 0 part
sde 8:64 0 3.7T 0 disk
|-sde1 8:65 0 2G 0 part
`-sde2 8:66 0 3.7T 0 part
sdf 8:80 0 7.3T 0 disk
|-sdf1 8:81 0 2G 0 part
`-sdf2 8:82 0 7.3T 0 part
sdg 8:96 0 931.5G 0 disk
`-sdg1 8:97 0 931.5G 0 part /home/caillou/downloads
nvme0n1 259:0 0 232.9G 0 disk
nvme1n1 259:1 0 232.9G 0 disk
|-nvme1n1p1 259:2 0 512M 0 part /boot/efi
`-nvme1n1p2 259:3 0 232.4G 0 part /



  • sdg is an mSATA SSD connected through a PCIe card.


  • sda - sdf are SATA HDDs with ZFS.

Detail of the drives:




  • sda WD Red 8T, mainboard SATA connector.


  • sdb WD Red 8T, mainboard SATA connector.


  • sdc WD Red 8T, mainboard SATA connector.


  • sdd WD Red 8T, mainboard SATA connector.


  • sde WD Red 4T, mainboard SATA connector.


  • sdf WD Red 8T, mainboard SATA connector.


  • sdg Samsung mSATA 1T, shuked from Samsung Portable SSD T5, connected through a PCIe card.


  • nvme0n1 and nvme1n1 Samsung 970 EVO, connected to the mainboard m.2 connector.

The system does not show other signs of errors. Also, everything seems to function as intended, with the exception of these errors in the logs.






kernel drive







share|improve this question
















I regularly get the following error on my Ubuntu Server 18.10:



00:00:30 systemd[1]: Starting Discard unused blocks...
00:00:30 systemd[1]: Starting Rotate log files...
00:00:30 systemd[1]: Started Rotate log files.
00:01:01 kernel: ata7.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x6 frozen
00:01:01 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:01 kernel: ata7.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:01 kernel: ata7.00: status: DRDY 
00:01:01 kernel: ata7: hard resetting link
00:01:01 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:01 kernel: ata7.00: configured for UDMA/133
00:01:01 kernel: ata7.00: device reported invalid CHS sector 0
00:01:01 kernel: ata7: EH complete
00:01:32 kernel: ata7.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6 frozen
00:01:32 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:01:32 kernel: ata7.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:01:32 kernel: ata7.00: status: DRDY 
00:01:32 kernel: ata7: hard resetting link
00:01:32 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:01:32 kernel: ata7.00: configured for UDMA/133
00:01:32 kernel: ata7.00: device reported invalid CHS sector 0
00:01:32 kernel: ata7: EH complete
00:02:04 kernel: ata7.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6 frozen
00:02:04 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:04 kernel: ata7.00: cmd 64/01:28:00:00:00/00:00:00:00:00/a0 tag 5 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:04 kernel: ata7.00: status: DRDY 
00:02:04 kernel: ata7: hard resetting link
00:02:05 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:05 kernel: ata7.00: configured for UDMA/133
00:02:05 kernel: ata7.00: device reported invalid CHS sector 0
00:02:05 kernel: ata7: EH complete
00:02:37 kernel: INFO: task fstrim:29514 blocked for more than 120 seconds.
00:02:37 kernel: Tainted: P O 4.18.0-17-generic #18-Ubuntu
00:02:37 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
00:02:37 kernel: fstrim D 0 29514 1 0x00000000
00:02:37 kernel: Call Trace:
00:02:37 kernel: __schedule+0x29e/0x840
00:02:37 kernel: schedule+0x2c/0x80
00:02:37 kernel: schedule_timeout+0x258/0x360
00:02:37 kernel: io_schedule_timeout+0x1e/0x50
00:02:37 kernel: wait_for_completion_io+0xb7/0x140
00:02:37 kernel: ? wake_up_q+0x80/0x80
00:02:37 kernel: submit_bio_wait+0x61/0x90
00:02:37 kernel: blkdev_issue_discard+0x7a/0xd0
00:02:37 kernel: ext4_trim_fs+0x5a9/0x8b0
00:02:37 kernel: ? security_file_open+0x86/0x90
00:02:37 kernel: ext4_ioctl+0xd81/0x14a0
00:02:37 kernel: ? _copy_to_user+0x2b/0x40
00:02:37 kernel: ? cp_new_stat+0x152/0x180
00:02:37 kernel: do_vfs_ioctl+0xa8/0x620
00:02:37 kernel: ? __do_sys_newfstat+0x5f/0x70
00:02:37 kernel: ksys_ioctl+0x67/0x90
00:02:37 kernel: __x64_sys_ioctl+0x1a/0x20
00:02:37 kernel: do_syscall_64+0x5a/0x110
00:02:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
00:02:37 kernel: RIP: 0033:0x7faba5a9e3c7
00:02:37 kernel: Code: Bad RIP value.
00:02:37 kernel: RSP: 002b:00007ffec09ede88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
00:02:37 kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007faba5a9e3c7
00:02:37 kernel: RDX: 00007ffec09ede90 RSI: 00000000c0185879 RDI: 0000000000000004
00:02:37 kernel: RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
00:02:37 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000561d21106dd0
00:02:37 kernel: R13: 00007faba5663ff8 R14: 00007ffec09edfc8 R15: 0000561d21106dd0
00:02:37 kernel: ata7.00: NCQ disabled due to excessive errors
00:02:37 kernel: ata7.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6 frozen
00:02:37 kernel: ata7.00: failed command: SEND FPDMA QUEUED
00:02:37 kernel: ata7.00: cmd 64/01:c0:00:00:00/00:00:00:00:00/a0 tag 24 ncq dma 512 out
 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
00:02:37 kernel: ata7.00: status: DRDY 
00:02:37 kernel: ata7: hard resetting link
00:02:38 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
00:02:38 kernel: ata7.00: configured for UDMA/133
00:02:38 kernel: ata7.00: device reported invalid CHS sector 0
00:02:38 kernel: ata7: EH complete
00:03:02 fstrim[29514]: /home/caillou/downloads: 891.5 GiB (957190782976 bytes) trimmed
00:03:02 fstrim[29514]: /: 212.4 GiB (228063428608 bytes) trimmed
00:03:02 systemd[1]: Started Discard unused blocks.


Unfortunately I don't understand what it tries to tell me.



  1. What is ata7.00?

  2. What does failed command: SEND FPDMA QUEUED mean? What is this FPDMA?

  3. What does device reported invalid CHS sector 0 mean?

I suspect it has something to do with a drive, but I have no idea how to debug nor how to fix this issue.



Here is the output of lsblk:



sda 8:0 0 7.3T 0 disk
|-sda1 8:1 0 2G 0 part
`-sda2 8:2 0 7.3T 0 part
sdb 8:16 0 7.3T 0 disk
|-sdb1 8:17 0 2G 0 part
`-sdb2 8:18 0 7.3T 0 part
sdc 8:32 0 7.3T 0 disk
|-sdc1 8:33 0 2G 0 part
`-sdc2 8:34 0 7.3T 0 part
sdd 8:48 0 7.3T 0 disk
|-sdd1 8:49 0 2G 0 part
`-sdd2 8:50 0 7.3T 0 part
sde 8:64 0 3.7T 0 disk
|-sde1 8:65 0 2G 0 part
`-sde2 8:66 0 3.7T 0 part
sdf 8:80 0 7.3T 0 disk
|-sdf1 8:81 0 2G 0 part
`-sdf2 8:82 0 7.3T 0 part
sdg 8:96 0 931.5G 0 disk
`-sdg1 8:97 0 931.5G 0 part /home/caillou/downloads
nvme0n1 259:0 0 232.9G 0 disk
nvme1n1 259:1 0 232.9G 0 disk
|-nvme1n1p1 259:2 0 512M 0 part /boot/efi
`-nvme1n1p2 259:3 0 232.4G 0 part /



  • sdg is an mSATA SSD connected through a PCIe card.


  • sda - sdf are SATA HDDs with ZFS.

Detail of the drives:




  • sda WD Red 8T, mainboard SATA connector.


  • sdb WD Red 8T, mainboard SATA connector.


  • sdc WD Red 8T, mainboard SATA connector.


  • sdd WD Red 8T, mainboard SATA connector.


  • sde WD Red 4T, mainboard SATA connector.


  • sdf WD Red 8T, mainboard SATA connector.


  • sdg Samsung mSATA 1T, shuked from Samsung Portable SSD T5, connected through a PCIe card.


  • nvme0n1 and nvme1n1 Samsung 970 EVO, connected to the mainboard m.2 connector.

The system does not show other signs of errors. Also, everything seems to function as intended, with the exception of these errors in the logs.






kernel drive




kernel drive






share|improve this question















share|improve this question













share|improve this question




share|improve this question



share|improve this question








edited May 1 at 15:35







Pierre Spring

















asked May 1 at 14:24









Pierre SpringPierre Spring

1115 bronze badges




1115 bronze badges















  • As I do not really understand the problem, I find it difficult to correctly tag the question, or to choose an adequate title. Please edit to your liking, if you understand more than I do.

    – Pierre Spring
    May 1 at 14:25











  • Is this a SSD or HDD? Is the ONLY problem seen in syslog, or does the system exhibit operational problems? Do you have a GUI on this server? Are you able to view SMART data using the Disks app (or smartctl)? 1. ata7.00 identifies which SATA drive, 2. FPDMA = First-Party Direct Memory Access, 3. CHS sector 0 means cylinder/head/sector... an outdated form of identifying a location on disk. I have a possible solution, pending your answers.

    – heynnema
    May 1 at 14:54












  • @heynnema I edited the question with responses as good as I could. You say ata7.00 identifies the SATA drive, does that mean it is sdg, as g is the 7th letter?

    – Pierre Spring
    May 1 at 15:11






  • 1





    I've added a quick answer that should probably take care of the problem. Report back.

    – heynnema
    May 1 at 16:31






  • 1





    Status please...

    – heynnema
    May 2 at 15:36

















  • As I do not really understand the problem, I find it difficult to correctly tag the question, or to choose an adequate title. Please edit to your liking, if you understand more than I do.

    – Pierre Spring
    May 1 at 14:25











  • Is this a SSD or HDD? Is the ONLY problem seen in syslog, or does the system exhibit operational problems? Do you have a GUI on this server? Are you able to view SMART data using the Disks app (or smartctl)? 1. ata7.00 identifies which SATA drive, 2. FPDMA = First-Party Direct Memory Access, 3. CHS sector 0 means cylinder/head/sector... an outdated form of identifying a location on disk. I have a possible solution, pending your answers.

    – heynnema
    May 1 at 14:54












  • @heynnema I edited the question with responses as good as I could. You say ata7.00 identifies the SATA drive, does that mean it is sdg, as g is the 7th letter?

    – Pierre Spring
    May 1 at 15:11






  • 1





    I've added a quick answer that should probably take care of the problem. Report back.

    – heynnema
    May 1 at 16:31






  • 1





    Status please...

    – heynnema
    May 2 at 15:36
















As I do not really understand the problem, I find it difficult to correctly tag the question, or to choose an adequate title. Please edit to your liking, if you understand more than I do.

– Pierre Spring
May 1 at 14:25





As I do not really understand the problem, I find it difficult to correctly tag the question, or to choose an adequate title. Please edit to your liking, if you understand more than I do.

– Pierre Spring
May 1 at 14:25













Is this a SSD or HDD? Is the ONLY problem seen in syslog, or does the system exhibit operational problems? Do you have a GUI on this server? Are you able to view SMART data using the Disks app (or smartctl)? 1. ata7.00 identifies which SATA drive, 2. FPDMA = First-Party Direct Memory Access, 3. CHS sector 0 means cylinder/head/sector... an outdated form of identifying a location on disk. I have a possible solution, pending your answers.

– heynnema
May 1 at 14:54






Is this a SSD or HDD? Is the ONLY problem seen in syslog, or does the system exhibit operational problems? Do you have a GUI on this server? Are you able to view SMART data using the Disks app (or smartctl)? 1. ata7.00 identifies which SATA drive, 2. FPDMA = First-Party Direct Memory Access, 3. CHS sector 0 means cylinder/head/sector... an outdated form of identifying a location on disk. I have a possible solution, pending your answers.

– heynnema
May 1 at 14:54














@heynnema I edited the question with responses as good as I could. You say ata7.00 identifies the SATA drive, does that mean it is sdg, as g is the 7th letter?

– Pierre Spring
May 1 at 15:11





@heynnema I edited the question with responses as good as I could. You say ata7.00 identifies the SATA drive, does that mean it is sdg, as g is the 7th letter?

– Pierre Spring
May 1 at 15:11




1




1





I've added a quick answer that should probably take care of the problem. Report back.

– heynnema
May 1 at 16:31





I've added a quick answer that should probably take care of the problem. Report back.

– heynnema
May 1 at 16:31




1




1





Status please...

– heynnema
May 2 at 15:36





Status please...

– heynnema
May 2 at 15:36










1 Answer
1






active

oldest

votes


















1


















Note: It's a good idea to have good backups first.



You need to check/upgrade the firmware on the Samsung SSD's for sdg and nvme*.



Go to Samsung's download page here and download their Samsung Magician software tool to help with the firmware upgrade. Other software updates are also available there.



Also check for a firmware upgrade for the sdg PCIe card.



Check your motherboard BIOS with sudo dmidecode -s bios-version. Then go to the manufacturor's web site and check for a newer BIOS. If there is one, download and install it.



Note: later, if there are still problems, we'll discuss a ncq patch.






share|improve this answer





























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );














    draft saved

    draft discarded
















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1139719%2fata7-00-failed-command-send-fpdma-queued%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown


























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1


















    Note: It's a good idea to have good backups first.



    You need to check/upgrade the firmware on the Samsung SSD's for sdg and nvme*.



    Go to Samsung's download page here and download their Samsung Magician software tool to help with the firmware upgrade. Other software updates are also available there.



    Also check for a firmware upgrade for the sdg PCIe card.



    Check your motherboard BIOS with sudo dmidecode -s bios-version. Then go to the manufacturor's web site and check for a newer BIOS. If there is one, download and install it.



    Note: later, if there are still problems, we'll discuss a ncq patch.






    share|improve this answer
































      1


















      Note: It's a good idea to have good backups first.



      You need to check/upgrade the firmware on the Samsung SSD's for sdg and nvme*.



      Go to Samsung's download page here and download their Samsung Magician software tool to help with the firmware upgrade. Other software updates are also available there.



      Also check for a firmware upgrade for the sdg PCIe card.



      Check your motherboard BIOS with sudo dmidecode -s bios-version. Then go to the manufacturor's web site and check for a newer BIOS. If there is one, download and install it.



      Note: later, if there are still problems, we'll discuss a ncq patch.






      share|improve this answer






























        1














        1










        1









        Note: It's a good idea to have good backups first.



        You need to check/upgrade the firmware on the Samsung SSD's for sdg and nvme*.



        Go to Samsung's download page here and download their Samsung Magician software tool to help with the firmware upgrade. Other software updates are also available there.



        Also check for a firmware upgrade for the sdg PCIe card.



        Check your motherboard BIOS with sudo dmidecode -s bios-version. Then go to the manufacturor's web site and check for a newer BIOS. If there is one, download and install it.



        Note: later, if there are still problems, we'll discuss a ncq patch.






        share|improve this answer
















        Note: It's a good idea to have good backups first.



        You need to check/upgrade the firmware on the Samsung SSD's for sdg and nvme*.



        Go to Samsung's download page here and download their Samsung Magician software tool to help with the firmware upgrade. Other software updates are also available there.



        Also check for a firmware upgrade for the sdg PCIe card.



        Check your motherboard BIOS with sudo dmidecode -s bios-version. Then go to the manufacturor's web site and check for a newer BIOS. If there is one, download and install it.



        Note: later, if there are still problems, we'll discuss a ncq patch.







        share|improve this answer















        share|improve this answer




        share|improve this answer



        share|improve this answer








        edited May 2 at 21:45

























        answered May 1 at 16:30









        heynnemaheynnema

        27.2k3 gold badges29 silver badges73 bronze badges




        27.2k3 gold badges29 silver badges73 bronze badges































            draft saved

            draft discarded















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid …


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1139719%2fata7-00-failed-command-send-fpdma-queued%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown









            -

            Popular posts from this blog

            Distance measures on a map of a game The 2019 Stack Overflow Developer Survey Results Are Inmin distance in a graphShortest distance path on contour plotHow to plot a tilted map?Finding points outside of a diskDelaunay link distanceAnnulus from GeoDisks: drawing a ring on a mapNegative Correlation DistanceFind distance along a path (GPS coordinates)Finding position at given distance in a GeoPathMathematics behind distance estimation using camera

            Image
            Delete all lines which don't have n characters before delimiter How to manage monthly salary Deal with toxic manager when you can't quit Button changing it's text & action. Good or terrible? For what reasons would an animal species NOT cross a *horizontal* land bridge? Why do some words that are not inflected have an umlaut? Are there any other methods to apply to solving simultaneous equations? Does a dangling wire really electrocute me if I'm standing in water? Right tool to dig six foot holes? Is there a symbol for a right arrow with a square in the middle? Can a rogue use sneak attack with weapons that have the thrown property even if they are not thrown? What is the motivation for a law requiring 2 parties to consent for recording a conversation What is the accessibility of a package's `Private` context variables? Is "plugging out" electronic devices an American expression? Is there any way to tell whether the shot is g...
            Read more

            How to get a smooth, uniform ParametricPlot of a 2D Region?How to plot a complicated Region?How to exclude a region from ParametricPlotHow discretize a region placing vertices on a specific non-uniform gridHow to transform a Plot or a ParametricPlot into a RegionHow can I get a smooth plot of a bounded region?Smooth ParametricPlot3D with RegionFunction?Smooth border of a region ParametricPlotSmooth region boundarySmooth region plot from list of pointsGet minimum y of a certain x in a region

            Image
            Did "2001: A Space Odyssey" make any reference to the names of companies, or show any evidence of the existence of advertisements? Pros and cons of playing correspondence chess How do professors and lecturers learn to teach? Is it OK for a Buddhist teacher to charge their students an hourly rate for their time? Do insurance rates depend on credit scores? Why does California seem to have much more aggressive Consumer Protection and Safety Legislation? Query more than 50000 records Is this medieval picture of hanging 5 royals showing an historical event? Film about the USA being run by fake videos of the president after his kidnapping Is American Express widely accepted in Hong Kong? How many atoms in the hydrocarbon? How do you give spell casters xp? If a picture of a screen is a screenshot, what is a video of a screen? Is there any plausible in-between of Endotherms and Ectotherms? How can we save ourselves from large drops in stock price? How wo...
            Read more

            Genealogie vun de Merowenger Vum Merowech bis zum Chilperich I. | Navigatiounsmenü

            Image
            Merowenger MëttelalterFrankräich Genealogie vun de Merowenger Vu Wikipedia Op d'Navigatioun wiesselen Op d'Siche wiesselen D' Merowenger waren en Adelsgeschlecht, dat am fréie Mëttelalter a Frankräich geherrscht huet. Vum Merowech bis zum Chilperich I. | Merowech, ëm 451 Childerich I., † 482, als Kinnek vun de Franken 463 an 489 attestéiert, bei Tournai begruewen; ∞ Basina aus Thüringen Clovis I. (Chlodowech, Chlodwig), * 466, † 27. November 511, 482 Kinnek vun de Franken, begruewen an der Apostelkierch zu Paräis; ∞ I NN, eng adleg Fränkin; ∞ II 492/494 Chlothilde (Chrodihild), † 544, Duechter vum Chilperich II., Kinnek vun de Burgunder, begruewen an der Apostelkierch zu Paräis (I) Theuderich I. (Thierry I.), * géint 484, † Enn 533, Kinnek zu Reims 511-533; ∞ I Suavegotta, † virun 566; ∞ II ëm 517 NN, Duechter vum Sigismund...
            Read more