Hard Drive Error : ata3.00: status: { DRDY ERR }

[z987k]

It's Kernel Bug on ata ACPI. I put "options libata noacpi=1" on /etc/modprobe.d/options and the ERROR is gone.

This solved it for me.

[fatmystic]

I agree that noapic is required as additional boot parameter to resolve the disk error. If using CD or other means, use following:

ubuntu acpi=off noapic

and all the kernel will boot.

[anjohnso]

It's Kernel Bug on ata ACPI. I put "options libata noacpi=1" on /etc/modprobe.d/options and the ERROR is gone.

I realize I may be showing what a noob I am, but how exactly do I do this? /etc/modprobe.d/options does not exist.

[thatmattbone]

I realize I may be showing what a noob I am, but how exactly do I do this? /etc/modprobe.d/options does not exist.

I think in 9.10, any file ending in ".conf" in /etc/modprobe.d is parsed. I created a new file, /etc/modprobe.d/options.conf and put the "options libata noacpi=1" in there. Seemed to fix the problem.

[sau_sage114]

I just got this on ubuntu 9.10.

was playing pokemon sapphire on gvba, then restarted to install the update. all I can get to is the kernel, but I can't put in a command without it just repeating the same error over and over again for about 3 minutes before going back to the command line.

I also get the error 'module' object has no attribute 'normalize_encoding'

EDIT: also, I know this isn't a hard drive error because I loaded a second version of ubuntu on a different partition and it works fine.

[tubezninja]

For what it's worth: I'm being driven mad by the same issue. Attempted to add "options libata noacpi=1" but the errors STILL popped up, and it even got to the point where one of my drives stopped reading with sector read errors.

There are two ahrd drives in this box. I've replaced both of them thinking it was hardware issues, and then had to do a fresh ubuntu OS install. And the error STILL pops up:

[ 1089.724114] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 1089.724163] ata3.00: BMDMA stat 0x66
[ 1089.724192] ata3.00: cmd 35/00:00:ef:3c:ff/00:04:00:00:00/e0 tag 0 dma 524288 out
[ 1089.724194]          res 51/84:31:be:3d:ff/84:03:00:00:00/e0 Emask 0x30 (host bus error)
[ 1089.724284] ata3.00: status: { DRDY ERR }
[ 1089.724309] ata3.00: error: { ICRC ABRT }
[ 1089.724342] ata3: soft resetting link
[ 1089.981561] ata3.00: configured for UDMA/133
[ 1090.048905] ata3.01: configured for UDMA/133
[ 1090.048924] ata3: EH complete

Over and over again!

[jaycakep]

For what it's worth: I'm being driven mad by the same issue. Attempted to add "options libata noacpi=1" but the errors STILL popped up, and it even got to the point where one of my drives stopped reading with sector read errors.

There are two ahrd drives in this box. I've replaced both of them thinking it was hardware issues, and then had to do a fresh ubuntu OS install. And the error STILL pops up:

[ 1089.724114] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 1089.724163] ata3.00: BMDMA stat 0x66
[ 1089.724192] ata3.00: cmd 35/00:00:ef:3c:ff/00:04:00:00:00/e0 tag 0 dma 524288 out
[ 1089.724194]          res 51/84:31:be:3d:ff/84:03:00:00:00/e0 Emask 0x30 (host bus error)
[ 1089.724284] ata3.00: status: { DRDY ERR }
[ 1089.724309] ata3.00: error: { ICRC ABRT }
[ 1089.724342] ata3: soft resetting link
[ 1089.981561] ata3.00: configured for UDMA/133
[ 1090.048905] ata3.01: configured for UDMA/133
[ 1090.048924] ata3: EH complete

Over and over again!

sir have you try to restart udev, it's work on my laptop
sudo /etc/init.d/udev stop
sudo /etc/init.d/udev start

here the reference https://bugs.launchpad.net/ubuntu/+s...ux/+bug/383632

[The Spy]

I can verify that this fix works, though, of course the command will have to be run again after a system reboot.

[startling]

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

[   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>

Ubuntu 10.04, after some errors for a while, eventually would not start at all on this new Advent laptop, so I re-installed from a live cd to a new partition. That worked fine for a week or so but now this is also throwing errors all the time and failing to boot.

I cannot believe it's a hard drive problem. A while ago, When I installed Ubuntu 8.10, on my then new Toshiba laptop, the hard drive died within a few months and needed replacement. Now I've installed Ubuntu 10.04 on a new hard drive and that is showing problems. Is this just bad luck? Or is there a problem with Ubuntu / Linux and laptop drives?

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 that) which then runs a disk check and fix, and then reboot with the new kernel.

[diazjavier]

I think in 9.10, any file ending in ".conf" in /etc/modprobe.d is parsed. I created a new file, /etc/modprobe.d/options.conf and put the "options libata noacpi=1" in there. Seemed to fix the problem.

Works in Ubuntu 10.04
Thank you