AHCI Hard Drive constantly erroring

[Ryan DeShone]

After a clean install of Ubuntu 9.04 on a brand new laptop, running kernel 2.6.28-11-generic x86_64 my hard drive is constantly working. Checking dmesg reveals the following errors repeating continuously.

[ 3052.081075] ata2.00: qc timeout (cmd 0xa0)
[ 3052.081108] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3052.081119] ata2.00: irq_stat 0x40000001
[ 3052.081142] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3052.081147] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3052.081151] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 3052.081163] ata2.00: status: { DRDY ERR }
[ 3052.081179] ata2: hard resetting link
[ 3052.565083] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 3052.593207] ata2.00: configured for PIO0
[ 3052.593762] ata2: EH complete
[ 3058.676066] ata2.00: qc timeout (cmd 0xa0)
[ 3058.676100] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3058.676113] ata2.00: irq_stat 0x40000001
[ 3058.676137] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3058.676141] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3058.676146] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 3058.676158] ata2.00: status: { DRDY ERR }
[ 3058.676175] ata2: hard resetting link
[ 3059.160058] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 3059.188051] ata2.00: configured for PIO0
[ 3059.188623] ata2: EH complete
[ 3065.768195] ata2.00: qc timeout (cmd 0xa0)
[ 3065.768209] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3065.768213] ata2.00: irq_stat 0x40000001
[ 3065.768220] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3065.768221] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 3065.768222] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 3065.768225] ata2.00: status: { DRDY ERR }
[ 3065.768231] ata2: hard resetting link
[ 3066.252063] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 3066.279892] ata2.00: configured for PIO0
[ 3066.280456] ata2: EH complete

I'm worried that this is going to end up burning out my drive at this rate. While I've found a number of other similar bugs posted, none of them seem to match this problem 100%. Also, none of the fixes I've found posted have worked. I'm fairly certain this problem has to do with the AHCI driver however.

from lshw:
     *-storage
          description: SATA controller
          product: nVidia Corporation
          vendor: nVidia Corporation
          physical id: 9
          bus info: pci@0000:00:09.0
          logical name: scsi0
          logical name: scsi1
          version: a2
          width: 32 bits
          clock: 66MHz
          capabilities: storage pm msi ht bus_master cap_list emulated
          configuration: driver=ahci latency=0 maxlatency=1 mingnt=3 module=ahci
        *-disk
             description: ATA Disk
             product: WDC WD2500BEVT-2
             vendor: Western Digital
             physical id: 0
             bus info: scsi@0:0.0.0
             logical name: /dev/sda
             version: 11.0
             serial: WD-WXEZ08V74428
             size: 232GiB (250GB)
             capabilities: partitioned partitioned:dos
             configuration: ansiversion=5 signature=6dfd59f0

lspci
00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation Device 075e (rev a2)
00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor (rev a2)
00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP78S [GeForce 8200] High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:09.0 SATA controller: nVidia Corporation Device 0ad5 (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:13.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:14.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:15.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:16.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:17.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 11h HyperTransport Configuration (rev 40)
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 11h DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 11h Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 11h Link Control
02:00.0 VGA compatible controller: nVidia Corporation GeForce 9100M G (rev a2)
03:00.0 VGA compatible controller: nVidia Corporation GeForce 9300M GS (rev a1)
06:00.0 Network controller: RaLink RT2860
07:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. IEEE 1394 Host Controller
07:00.1 System peripheral: JMicron Technologies, Inc. SD/MMC Host Controller
07:00.2 SD Host controller: JMicron Technologies, Inc. Standard SD Host Controller
07:00.3 System peripheral: JMicron Technologies, Inc. MS Host Controller
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

I've run full fscks on all partitions. I've run smart tests. Everything tells me that the drive is fine. I've tried the a number of kernel flags which I found posted on similar bugs, none of which helped (noapic, acpi=off, pci=nomsi).

[Jeff Enns (cyberpenguinks)]

Thank you for sending in your bug report. I'd like you to try something. Could you run this in a terminal, please:
  sudo /sbin/badblocks -v /dev/sda
This might take a while to do the scan. Please, post the results. Also, what were you results with the fsck? Thank you.

[Ryan DeShone (rfdeshon)]

sudo /sbin/badblocks -v /dev/sda
Checking blocks 0 to 244198583
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found.

When I ran fsck, it finished clean and didn't make any alterations. Considering this laptop is a day old, I'd say that's as expected. Let me know if you need any further information to help diagnose this.

[Jeff Enns (cyberpenguinks)]

Thank you for the additional information. I agree, one would expect clean results from a brand new piece of hardware. However, the only time I've seen these errors has been when a hard drive or the controller failed. That's not to say that is always the case, but that has been my experience in the past. I just want to be really sure that everything is fine with the hardware.

One last question I have is how did you check on SMART? Did you use a BIOS/firmware utility or smartmontools? What kind of tests did you run?

Thanks again.

[Ryan DeShone (rfdeshon)]

I ran smartctl -t short on the drive. After that test ran, I checked the results with smartctl --all and everything reported as good. I'll run a long test here and post the results once they are done.

[Ryan DeShone (rfdeshon)]

I used smartctl to run a long test on the drive. After it was complete, I checked smartctl -a on the drive and it reported that the drive had passed. I attached the output. If there's anything else I can provide to help, let me know.

[Jeff Enns (cyberpenguinks)]

Thank you for the additional information. That's all the questions I have. I'll pass this on. Thank you.

[Ryan DeShone (rfdeshon)]

I have additional information on this, courtesy the Ubuntu forums. Someone else with the exact same laptop did some experimenting and found that this bug is related in some way to the optical drive. Here is what he has to say:

"Well I am happy to report that this is not my harddrive.

I have isolated it to the dvd drive which makes me feel better. If I pop in a cd or keep the drive bay open the messages stop. If I close the dvd drive bay (without a cd in the drive) the message appear.

Still trying to figure this one out, but I am glad I won't be experiencing any corruption of my harddrive."

I am unable to confirm this currently as I'm in the process of replacing my standard Ubuntu install with CrunchBang...

[Ryan DeShone (rfdeshon)]

I can confirm that the errors do appear to cease when there is media in the DVD burner... I continue to get the errors when the drive is open however. Don't know if that helps at all or not.

[KÁDÁR Balázs (balazs-kadar)]

I'm experiencing a similar problem on completely different hardware. It's an Intel-based ASUS notebook with PATA drives. The error occurs repeatedly unless there is a disk in the DVD drive.

OS: a freshly installed and updated Jaunty:
Linux tol-sirion 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux

The error message:
[21536.000080] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[21536.000098] ata1.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0
[21536.000100] cdb 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[21536.000103] res 40/00:02:00:08:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
[21536.000109] ata1.01: status: { DRDY }
[21541.040058] ata1: link is slow to respond, please be patient (ready=0)
[21546.024046] ata1: device not ready (errno=-16), forcing hardreset
[21546.024061] ata1: soft resetting link
[21546.230280] ata1.00: configured for UDMA/100
[21546.268463] ata1.01: configured for UDMA/33
[21546.276769] ata1: EH complete
[21546.293376] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
[21546.308475] sd 0:0:0:0: [sda] Write Protect is off
[21546.308480] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[21546.340524] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[21546.372794] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
[21546.388483] sd 0:0:0:0: [sda] Write Protect is off
[21546.388488] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[21546.408450] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

I've attached the IDE part of lshw.
SMART and chkdsk don't show any problems.
Tell me if I should run some more extensive tests or add more information.

[richard (auto741526)]

I confirm the boot problems. I've the same sort of problems with a brand new laptop after installation of Ubuntu 9.04. The DRDY errors not only occur when booting from hard disk. They also occur, when booting the Ubuntu 9.04 life CD. However, the boot process does not get stuck here. After 27 seconds, the system boots normally.

When booting from hard disk:
- The workaround "insert a CD" works.
- The workaround "leave CD tray open" does not work for me.
See the attached error messages and hardware configuration.

uname -a:
Linux abarti 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

[Marco Alfonso (maop)]

Same problem here,

Everything seems fine until first message of this appears all system go veeeeery slow.

Is there any workaround?

[Juaco (kankito)]

i also have this problem on a MSI VR630 bought on january 2009. Can't recall if i had problems when first installed Ubuntu back then (was Intrepid 64 bits). Now with Jaunty 64 bits:

Aug 6 22:19:47 juaco kernel: [16106.996056] ata2.00: qc timeout (cmd 0xa0)
Aug 6 22:19:47 juaco kernel: [16106.996078] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Aug 6 22:19:47 juaco kernel: [16106.996084] ata2.00: irq_stat 0x40000001
Aug 6 22:19:47 juaco kernel: [16106.996078] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Aug 6 22:19:47 juaco kernel: [16106.996084] ata2.00: irq_stat 0x40000001
Aug 6 22:19:47 juaco kernel: [16106.996097] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Aug 6 22:19:47 juaco kernel: [16106.996100] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Aug 6 22:19:47 juaco kernel: [16106.996102] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
Aug 6 22:19:47 juaco kernel: [16106.996108] ata2.00: status: { DRDY ERR }
Aug 6 22:19:47 juaco kernel: [16106.996118] ata2: hard resetting link
Aug 6 22:19:48 juaco kernel: [16107.481052] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 6 22:19:48 juaco kernel: [16107.508985] ata2.00: configured for PIO0
Aug 6 22:19:48 juaco kernel: [16107.509549] ata2: EH complete

At an approx. rate of 1 sec. As the original HD started reporting SMART errors i took it to RMA in May, now with the new drive and fresh install the errors continue. Haven't tested yet other distros, but can confirm in Windows does not happen.

The "insert DVD workaround" WORKS. The errors are gone (pfeeuhh!), but i really need to find a solution. Dropping Linux is not an option for me, so i'll keep trying and reporting any advance or relevant data found.

Maybe is an error in libata? How can i trace this? Places to look?

[Floris (fdirkzwager)]

I also have this problem and confirmed workaround....

 You will find the error at the end of the attached log and it looks like this:

ata3.00: status: { DRDY ERR }
[ 2444.768392] ata3: hard resetting link
[ 2445.252019] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2445.280061] ata3.00: configured for UDMA/100
[ 2445.280598] ata3: EH complete
[ 2866.980021] ata3.00: qc timeout (cmd 0xa0)
[ 2866.980033] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 2866.980093] ata3.00: irq_stat 0x40000001
[ 2866.980152] ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 2866.980153] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2866.980155] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)

From the log ata3 refers to the cdrom drive:
[ 2.698013] ata3.00: ATAPI: Optiarc DVD RW AD-7640S, HX04, max UDMA/100, ATAPI AN.

 The " leave cd in cdrom player " works!!!! ..yesss finally....but I would love a real solution......

(I tried 9.10 but the same error is also there)

[Juaco (kankito)]

After upgrading to 9.10, the problem was gone on my machine, at least
initially. But after an upgrade i did in 2009/11/09 (which upgraded udev
among other stuff, dunno if it upgraded libata too), the problem is back.
So, i went and grabbed a CD again :S. Anyway, udev works better with the
upgrades, it would be great if this gets solved for once! It's been almost a
year now with this bug.

2009/11/9 Floris <email address hidden>

> I also have this problem and confirmed workaround....
>
> You will find the error at the end of the attached log and it looks like
> this:
>
> ata3.00: status: { DRDY ERR }
> [ 2444.768392] ata3: hard resetting link
> [ 2445.252019] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> [ 2445.280061] ata3.00: configured for UDMA/100
> [ 2445.280598] ata3: EH complete
> [ 2866.980021] ata3.00: qc timeout (cmd 0xa0)
> [ 2866.980033] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> frozen
> [ 2866.980093] ata3.00: irq_stat 0x40000001
> [ 2866.980152] ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> [ 2866.980153] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00
> [ 2866.980155] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5
> (timeout)
>
> >From the log ata3 refers to the cdrom drive:
> [ 2.698013] ata3.00: ATAPI: Optiarc DVD RW AD-7640S, HX04, max UDMA/100,
> ATAPI AN.
>
> The " leave cd in cdrom player " works!!!! ..yesss finally....but I
> would love a real solution......
>
> (I tried 9.10 but the same error is also there)
>
>
> ** Attachment added: "msg-dmesg.pdf"
> http://launchpadlibrarian.net/35433047/msg_dmesg.pdf
>
> --
> AHCI Hard Drive constantly erroring
> https://bugs.launchpad.net/bugs/383632
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Ecker Sandor (esanya)]

It seems to me that the following fixes the wrong behaviour...

I will add it to root's crontab:

sudo /etc/init.d/udev stop
sudo /etc/init.d/udev start

I had this issue on ubuntu 9.04, now on 9.10 it appears again. My HW is: MSI vr630x (bios still not upgraded).

[Ecker Sandor (esanya)]

I have created a file file /root/udevrestart.sh the content:

#/bin/bash

sleep 70
kill -9 `ps -ef|grep udev|grep -v restart|grep -v grep|cut -c10-15|xargs`

And I have added the following to crontab:

root@ubi-laptop:~# crontab -l
# m h dom mon dow command
@reboot /root/udevrestart.sh

This seems to fix the bug after each reboot.

[Gaetan Cambier (gaetan-cambier)]

I Have the same error with Fedora 12 64 bit

# lspci | grep SATA
00:09.0 SATA controller: nVidia Corporation MCP78S [GeForce 8200] AHCI Controller (rev a2)

# uname -r
2.6.32.11-99.fc12.x86_64

[startling (mark-starling)]

I have the same error with Ubuntu 10.04 on my brand new laptop:

[ 86.983162] ata1.00: failed command: READ FPDMA QUEUED
[ 86.983168] ata1.00: cmd 60/20:00:e0:63:87/00:00:18:00:00/40 tag 0 ncq 16384 in
[ 86.983169] res 41/40:00:ec:63:87/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[ 86.983172] ata1.00: status: { DRDY ERR }
[ 86.983175] ata1.00: error: { UNC }
[ 87.002792] ata1.00: configured for UDMA/133
[ 87.002805] ata1: EH complete
[ 87.796141] pwrdown, 0x6(BIT6)=71
[ 88.981841] ata1.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
[ 88.981845] ata1.00: irq_stat 0x40000008
[ 88.981849] ata1.00: failed command: READ FPDMA QUEUED
[ 88.981855] ata1.00: cmd 60/20:08:e0:63:87/00:00:18:00:00/40 tag 1 ncq 16384 in
[ 88.981856] res 41/40:00:ec:63:87/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[ 88.981859] ata1.00: status: { DRDY ERR }
[ 88.981862] ata1.00: error: { UNC }
[ 89.001502] ata1.00: configured for UDMA/133
[ 89.001514] ata1: EH complete
[ 89.796094] pwrdown, 0x6(BIT6)=71
[ 90.947153] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[ 90.947158] ata1.00: irq_stat 0x40000008
[ 90.947162] ata1.00: failed command: READ FPDMA QUEUED
[ 90.947168] ata1.00: cmd 60/20:00:e0:63:87/00:00:18:00:00/40 tag 0 ncq 16384 in
[ 90.947169] res 41/40:00:ec:63:87/00:00:18:00:00/40 Emask 0x409 (media error) <F>

Over the past few days to get Ubuntu to boot, from Grub I have to choose the older version of the kernel (wireless doesn't work with that kernel version or I'd stay with it) which then runs a disk check and fix, and then reboot with the new kernel.

I must say I've problems with various releases of Ubuntu on a couple of new laptops (one Toshiba, one Advent) and different replacement hard drives.

[Juaco (kankito)]

I'm sorry for not reporting this before, i'm on 10.04 too and a from a few
months age i have been able to solve this by using a 2.6.35 kernel from the
Kernel PPA.

uname -r is:

2.6.35-15-generic

Whenever i get back to the official Ubuntu kernel, i get back to the same
(too old i must say) issues.

2010/11/30 startling <email address hidden>

> I have the same error with Ubuntu 10.04 on my brand new laptop:
>
> [ 86.983162] ata1.00: failed command: READ FPDMA QUEUED
> [ 86.983168] ata1.00: cmd 60/20:00:e0:63:87/00:00:18:00:00/40 tag 0 ncq
> 16384 in
> [ 86.983169] res 41/40:00:ec:63:87/00:00:18:00:00/40 Emask 0x409
> (media error) <F>
> [ 86.983172] ata1.00: status: { DRDY ERR }
> [ 86.983175] ata1.00: error: { UNC }
> [ 87.002792] ata1.00: configured for UDMA/133
> [ 87.002805] ata1: EH complete
> [ 87.796141] pwrdown, 0x6(BIT6)=71
> [ 88.981841] ata1.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
> [ 88.981845] ata1.00: irq_stat 0x40000008
> [ 88.981849] ata1.00: failed command: READ FPDMA QUEUED
> [ 88.981855] ata1.00: cmd 60/20:08:e0:63:87/00:00:18:00:00/40 tag 1 ncq
> 16384 in
> [ 88.981856] res 41/40:00:ec:63:87/00:00:18:00:00/40 Emask 0x409
> (media error) <F>
> [ 88.981859] ata1.00: status: { DRDY ERR }
> [ 88.981862] ata1.00: error: { UNC }
> [ 89.001502] ata1.00: configured for UDMA/133
> [ 89.001514] ata1: EH complete
> [ 89.796094] pwrdown, 0x6(BIT6)=71
> [ 90.947153] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [ 90.947158] ata1.00: irq_stat 0x40000008
> [ 90.947162] ata1.00: failed command: READ FPDMA QUEUED
> [ 90.947168] ata1.00: cmd 60/20:00:e0:63:87/00:00:18:00:00/40 tag 0 ncq
> 16384 in
> [ 90.947169] res 41/40:00:ec:63:87/00:00:18:00:00/40 Emask 0x409
> (media error) <F>
>
>
> Over the past few days to get Ubuntu to boot, from Grub I have to choose
> the older version of the kernel (wireless doesn't work with that kernel
> version or I'd stay with it) which then runs a disk check and fix, and then
> reboot with the new kernel.
>
> I must say I've problems with various releases of Ubuntu on a couple of
> new laptops (one Toshiba, one Advent) and different replacement hard
> drives.
>
> --
> AHCI Hard Drive constantly erroring
> https://bugs.launchpad.net/bugs/383632
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[tallthom (tallthom)]

I'm getting similar errors in an Atom powered DIY machine w/4 cores. 2GB RAM with a 1TB hdd. (I used to have 2 TB but removed 1 drive when the errors were compounded):

[58854.080065] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[58854.080207] ata4.00: failed command: FLUSH CACHE EXT
[58854.080307] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[58854.080310] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[58854.080545] ata4.00: status: { DRDY }
[58859.120033] ata4: link is slow to respond, please be patient (ready=0)
[58864.100033] ata4: device not ready (errno=-16), forcing hardreset
[58864.100047] ata4: soft resetting link
[58869.300032] ata4: link is slow to respond, please be patient (ready=0)
[58874.162534] ata4: SRST failed (errno=-16)
[58874.162623] ata4: soft resetting link
[58879.370033] ata4: link is slow to respond, please be patient (ready=0)
[58884.170033] ata4: SRST failed (errno=-16)
[58884.170122] ata4: soft resetting link
[58889.382532] ata4: link is slow to respond, please be patient (ready=0)
[58893.980420] ata4.00: configured for UDMA/133
[58893.980430] ata4.00: retrying FLUSH 0xea Emask 0x4
[58893.980632] ata4.00: device reported invalid CHS sector 0
[58893.980655] ata4: EH complete

Seems like a power to the drive issue when the machine is kind of idle for a while. It isn't a notebook computer, but maybe Ubuntu thinks it is because of the Atom processor? What other information can I provide to help troubleshoot?

[tallthom (tallthom)]

Forgot to add that I'm running 10.10 with all the latest updates and kernel version: 2.6.35-25-server

[Jarek T. (ulvhedin)]

Same situation on kernel 2.6.38. System is freezing after few minutes for few seconds. Some bug in libata?

[Juaco (kankito)]

I have stopped experimenting the bug on the laptop mentioned in my FP, at
least since 2.6.35. Couldn't test yet my new desktop environment in the lap
(Ubuntu 10.10 + 2.6.38 debs from kernel.ubuntu.org, soon to be
hand-compiled), but when i do i'll report back.

2011/3/21 Jarek T. <email address hidden>

> Same situation on kernel 2.6.38. System is freezing after few minutes
> for few seconds. Some bug in libata?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/383632
>
> Title:
> AHCI Hard Drive constantly erroring
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/383632/+subscribe
>

[drey (inhuman-irk)]

Experiencing desktop freezes (2-20secs)with low la and cpu, mem consumption.
messages:
 ata4.00: qc timeout (cmd 0xa0)
 ata4: soft resetting link
 ata4.00: configured for UDMA/33
 ata4: EH complete

my ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x60e0 irq 14

$ uname -r
2.6.31-23-generic
$ lspci | grep SATA
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.