failed command: READ FPDMA QUEUED and interface fatal errors

[Shinji]

I have installed Ubuntu 12.10 server on my Zotac IONITX Board but I am getting a lot of errors related to my SATA controller. Sometimes the system partition is remounted read-only after a reboot.

I replaced my "OCZ Onyx" SSD with a new "Crucial 64GB M4" and reinstalled the system again. But the errors are still there.

Errors like " failed command: READ FPDMA QUEUED", " I/O error, dev sdb", "SError: { Dispar BadCRC }"... are not restricted to the SSD. The also appear at the SATA port where my Seagate hard disk is connected to.

One of the last errors is: "end_request: I/O error, dev sdb, sector 355383583" but if I run "sudo e2fsck -f /dev/sdb1" everythings seems to be ok.

Just now all was fine. Then I did a "sudo apt-get install iasl acpidump" and after that the root file systems was remounted read only and the syslog is filled with:

======================
[...]
Dec 29 11:39:48 nas kernel: [32061.259230] Buffer I/O error on device sda1, logical block 253944
Dec 29 11:39:48 nas kernel: [32061.259661] Buffer I/O error on device sda1, logical block 253945
Dec 29 11:39:48 nas kernel: [32061.260134] Buffer I/O error on device sda1, logical block 253946
Dec 29 11:39:48 nas kernel: [32061.260576] Buffer I/O error on device sda1, logical block 253947
Dec 29 11:39:48 nas kernel: [32061.261006] Buffer I/O error on device sda1, logical block 253948
Dec 29 11:39:48 nas kernel: [32061.261438] Buffer I/O error on device sda1, logical block 253949
Dec 29 11:39:48 nas kernel: [32061.261864] Buffer I/O error on device sda1, logical block 253950
Dec 29 11:39:48 nas kernel: [32061.262297] Buffer I/O error on device sda1, logical block 253951
Dec 29 11:39:48 nas kernel: [32061.262731] EXT4-fs warning (device sda1): ext4_end_bio:250: I/O error writing to inode 2102075 (offset 16252928 size 524288 starting block 254208)
=======================

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-21-generic 3.5.0-21.32
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Sat Dec 29 11:16:21 2012
HibernationDevice: RESUME=UUID=aa80fc57-83e6-4840-aeca-fc9f61f7706c
InstallationDate: Installed on 2012-12-28 (0 days ago)
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=5570eedc-78bb-431f-b202-b8c61423927b ro
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-21-generic N/A
 linux-backports-modules-3.5.0-21-generic N/A
 linux-firmware 1.95
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd08/13/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Dave Gilbert (ubuntu-treblig)]

To me that looks like a SATA link error - are you sure you've not got a bad cable or similar?

[ 7927.477839] ata2: SError: { 10B8B Dispar BadCRC }
[ 7927.478874] ata2.00: failed command: READ FPDMA QUEUED
[ 7927.479914] ata2.00: cmd 60/08:00:a7:03:e0/00:00:14:00:00/40 tag 0 ncq 4096 in
[ 7927.479914] res 40/00:00:a7:03:e0/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
[ 7927.482025] ata2.00: status: { DRDY }

smartctl -a might show you some diagnostics if you are lucky in the error log.

[Shinji (thorsten-reichelt)]

I replaced the cables but the error was still there. Then I restricted the SATA speed to 3.0Gb/s by adding

GRUB_CMDLINE_LINUX="libata.force=3.0"

to my "/etc/default/grub" file and the error was gone!

Both drives are SATA 6Gb/s capable.
Maybe it is a driver or a hardware issue with the NVIDIA MCP79 chip.

[Dave Gilbert (ubuntu-treblig)]

Huh ok, weird, since as far as I can read from your logs it was only running it at 3Gb/s anyway.

OK, so the next thing to try is to see if the latest upstream kernel has the same problem exists if you don't add the libata.force.

From: https://wiki.ubuntu.com/Kernel/BugTriage/Responses#Please_Test_Latest_Upstream :

Could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.8-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Dave Gilbert (ubuntu-treblig)]

Medium: It's a problem with a required hardware component (high) but has an easy workaround (low) - so I went for medium.

[Shinji (thorsten-reichelt)]

Sorry to bother again, but the bug seems to be still there. After two month without any problems I am getting the same errors again. So I have to withdraw my statement that the problem has been solved with the 3.8 upstream kernel!

After a restart/Reset my systems says "Read error" after POST... nothing more! :(

[...]
[ 10.782056] [drm] Initialized nouveau 1.1.0 20120801 for 0000:03:00.0 on minor 0
[ 12.225065] ata1.00: exception Emask 0x10 SAct 0x2 SErr 0x400000 action 0x6 frozen
[ 12.225124] ata1.00: irq_stat 0x08000000, interface fatal error
[ 12.225151] ata1: SError: { Handshk }
[ 12.225169] ata1.00: failed command: WRITE FPDMA QUEUED
[ 12.225196] ata1.00: cmd 61/08:08:58:86:04/00:00:04:00:00/40 tag 1 ncq 4096 out
[ 12.225196] res 40/00:0c:58:86:04/00:00:04:00:00/40 Emask 0x10 (ATA bus error)
[ 12.225230] ata1.00: status: { DRDY }
[ 12.225252] ata1: hard resetting link
[ 12.544038] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 12.544838] ata1.00: configured for UDMA/100
[ 12.544862] ata1: EH complete
[ 12.545530] ata1.00: exception Emask 0x10 SAct 0x3 SErr 0x400000 action 0x6 frozen
[ 12.545588] ata1.00: irq_stat 0x08000000, interface fatal error
[ 12.545619] ata1: SError: { Handshk }
[ 12.545648] ata1.00: failed command: WRITE FPDMA QUEUED
[ 12.545688] ata1.00: cmd 61/98:00:10:55:c5/00:00:02:00:00/40 tag 0 ncq 77824 out
[ 12.545688] res 40/00:04:10:55:c5/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[ 12.545744] ata1.00: status: { DRDY }
[ 12.545770] ata1.00: failed command: WRITE FPDMA QUEUED
[ 12.545808] ata1.00: cmd 61/08:08:00:08:84/00:00:03:00:00/40 tag 1 ncq 4096 out
[ 12.545808] res 40/00:04:10:55:c5/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[ 12.545858] ata1.00: status: { DRDY }
[ 12.545882] ata1: hard resetting link
[ 12.864036] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 12.864814] ata1.00: configured for UDMA/100
[ 12.864843] ata1: EH complete
[ 12.865010] ata1: limiting SATA link speed to 1.5 Gbps
[ 12.865023] ata1.00: exception Emask 0x10 SAct 0xf SErr 0x400000 action 0x6 frozen
[ 12.865066] ata1.00: irq_stat 0x08000000, interface fatal error
[ 12.865086] ata1: SError: { Handshk }
[ 12.865104] ata1.00: failed command: WRITE FPDMA QUEUED
[ 12.865130] ata1.00: cmd 61/20:00:60:38:0c/02:00:04:00:00/40 tag 0 ncq 278528 out
[ 12.865130] res 40/00:0c:10:55:c5/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[ 12.865165] ata1.00: status: { DRDY }
[ 12.865181] ata1.00: failed command: WRITE FPDMA QUEUED
[ 12.865205] ata1.00: cmd 61/98:08:10:55:c5/00:00:02:00:00/40 tag 1 ncq 77824 out
[ 12.865205] res 40/00:0c:10:55:c5/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[ 12.865241] ata1.00: status: { DRDY }
[ 12.865256] ata1.00: failed command: WRITE FPDMA QUEUED
[ 12.865281] ata1.00: cmd 61/98:10:20:50:c4/00:00:02:00:00/40 tag 2 ncq 77824 out
[ 12.865281] res 40/00:0c:10:55:c5/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[ 12.865315] ata1.00: status: { DRDY }
[ 12.865331] ata1.00: failed command: WRITE FPDMA QUEUED
[ 12.865356] ata1.00: cmd 61/08:18:b0:0d:5c/00:00:00:00:00/40...

[Shinji (thorsten-reichelt)]

Ok... from today it seems not to work with forcing to 1.5GBit any longer .... :(

============================
Mar 23 18:00:01 nas CRON[12386]: (shinji) CMD (/usr/bin/imapfilter)
Mar 23 18:00:56 nas kernel: [73823.079958] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe frozen
Mar 23 18:00:56 nas kernel: [73823.080000] ata1: irq_stat 0x00400000, PHY RDY changed
Mar 23 18:00:56 nas kernel: [73823.080065] ata1: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
Mar 23 18:00:56 nas kernel: [73823.080109] ata1: hard resetting link
Mar 23 18:00:56 nas kernel: [73823.804066] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 23 18:00:56 nas kernel: [73823.804878] ata1.00: configured for UDMA/100
Mar 23 18:00:56 nas kernel: [73823.804891] ata1: EH complete
Mar 23 18:00:59 nas kernel: [73826.260721] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1910000 action 0xe frozen
Mar 23 18:00:59 nas kernel: [73826.260753] ata1: irq_stat 0x00400000, PHY RDY changed
Mar 23 18:00:59 nas kernel: [73826.260771] ata1: SError: { PHYRdyChg Dispar LinkSeq TrStaTrns }
Mar 23 18:00:59 nas kernel: [73826.260795] ata1: hard resetting link
Mar 23 18:00:59 nas kernel: [73826.984052] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 23 18:00:59 nas kernel: [73826.984868] ata1.00: configured for UDMA/100
Mar 23 18:00:59 nas kernel: [73826.984880] ata1: EH complete
Mar 23 18:09:01 nas CRON[12426]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 23 18:17:01 nas CRON[12464]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 23 18:30:01 nas CRON[12505]: (shinji) CMD (/usr/bin/imapfilter)
Mar 23 18:39:01 nas CRON[12543]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 23 19:00:01 nas CRON[12621]: (shinji) CMD (/usr/bin/imapfilter)
Mar 23 19:09:01 nas CRON[12659]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 23 19:17:01 nas CRON[12696]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 23 19:21:53 nas kernel: [78680.832393] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen
Mar 23 19:21:53 nas kernel: [78680.832426] ata1.00: irq_stat 0x08000000, interface fatal error
Mar 23 19:21:53 nas kernel: [78680.832445] ata1: SError: { Handshk }
Mar 23 19:21:53 nas kernel: [78680.832461] ata1.00: failed command: WRITE DMA
Mar 23 19:21:53 nas kernel: [78680.833119] ata1.00: cmd ca/00:58:40:d9:86/00:00:00:00:00/e3 tag 0 dma 45056 out
Mar 23 19:21:53 nas kernel: [78680.833119] res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
Mar 23 19:21:53 nas kernel: [78680.834400] ata1.00: status: { DRDY }
Mar 23 19:21:53 nas kernel: [78680.835036] ata1: hard resetting link
Mar 23 19:21:54 nas kernel: [78681.152053] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 23 19:21:54 nas kernel: ...

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[penalvch (penalvch)]

Shinji, could you please provide the full model of your motherboard (ex. IONITX R Series IONITX-R-E)?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]