ata2.00: exception emask 0x0 sact ...

[dreamerx2004]

i installed ubuntu 8.04 by wubi under vista home basic.
after the successful installation, i rebooted my pc and selected ubuntu.
then after the rooting page, it gave me a page of error message:

------------------------------------------------------------------------------------------------------
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: cmd a0/00:00:00:24...
ata2.00: status: {DRDY}
...
...
------------------------------------------------------------------------------------------------------

my HD is ST3250310AS

[warnec (maciekw5-o2)]

I've got the same issue.
My HDD is ST3320833AS.
When I used this HDD in my old computer, it ran Ubuntu 7.10 perfecty.
Now, i inserted it into my new PC (new motherboard, CPU, GPU, everything except for DVD and HDD) and after installing Ubuntu 7.10 on a new ext3 partition and rebooting I get very similar message (except for the 'status ; {DRDY}')
After that, I tried Ubuntu 8.04. I ran the CD and have chosen straight installataion. After about 2 minutes of the orange bar going left and right, i got the same message. Identical. It repeats - the same error appears after the previous one after about 6-7 seconds.

A friend of mine told me that updating the BIOS might help. It didn't. Neither with 7.10, nor 8.04.

The strange thing is that I am able to log in into Ubuntu 7.10 in recovery or normal mode once in about 5 tries. After reboot, mostly I still get the same error.

[warnec (maciekw5-o2)]

PS.: I must also add that Windows XP runs perfectly on the same computer.

[Tuukka Kataja (stuge-t)]

I also have the same issue, with 8.04 Live-cd (amd64).
My HDD is ST3320620AS.
For me no hardware changes, 6.10 has been running on the machine without problems for well over a year.

[Tuukka Kataja (stuge-t)]

I managed to boot from the LiveCD by adding 'all_generic_ide' to the boot parameters.
Not sure what exactly that does though, just picked it up from a thread in the ubuntu forums.

[schobes (schobes)]

I am also having the same issue with the Live CD / Server CD and 8.04 Desktop Alt CD. I have not been able to install a new version of Ubuntu on this PC since 6.06. From my googling it appears to be an issue with the Intel Chipset and my board supporting both IDE and SATA. I have tried many of the work around suggestions on several other bug reports and forums and all have failed. When running through the CD I get to the point where it tries to mount my cdrom drive and fails, but a copy Ubuntu 6.06 succeeds. I also have WinXP running on the same machine without problem.

MotherBoard: P4P800-VM
Primary IDE Master: Maxtor 6Y080L0
Primary IDE Slave: None
Secondary IDE Master: SAMSUNG CD-RW SW
Secondary IDE Slave: None
Third IDE Master (Sata1): WDC WD5000KS-00MNB
Forth IDE Master (Sata1): WDC WD5000KS-00MNB

The kernel options that i have tried are as follows:

all_generic_ide
nopaic
nolapic
combined_mode=ide
combined_mode=libata
enable_atapi=1

It appears to me that it is just failing to recognize the cdrom drive, because when I remove the quiet option I see it detect the Primary Master (maxtor drive) and then hangs when trying to detect the Secondary Master (samsung drive). After trying to detect for about 2+ minutes it will then detect both of my sata drives.

Let me know if anyone has any suggestions or needs any additional information to troubleshoot this bug.

[Tuukka Kataja (stuge-t)]

I went on and installed 8.04 on my box yesterday using the alternate cd. The installation didn't require the all_generic_ide option that I had to use with the LiveCD (instead I needed to use irqpoll). But after installation, all_generic_ide was again required to boot (no irqpoll though).

After investigating this further, it seems like a very similar (if not the same) problem was already reported in October 2007. See bug #153702 and duplicates for details. The duplicates include reports of the same ata2.00: Exception Emask... errors, as well as an error 'ata1.00: revalidation failed (errno=-5)', which I'm also experiencing. Sadly that bug has been marked as "Won't fix"...

After schobes' comment, I tried unplugging my two DVD-RW-drives (both SATA). This gets rid of the 'exception Emask...' errors, but the revalidation errors are still there so booting won't complete.

Here's my machine's hardware:
Motherboard: MSI P965Neo (P965 chipset and ICH8 chipset)
Primary Master: ST3320620AS
Secondary Master: TSSTcorpCD/DVDW SH-S
Third Master: TSSTcorpCD/DVDW SH-S
Fourth Master: WDC WD800JD-75MSA3

I can also help troubleshoot this further if needed.

[Gaurish Sharma (gslive)]

I also Confirm this.
i am getting this msg

ata2.00: status: {DRDY ERR}
ata2.00: error: {UNC}
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: DMDMA stat 0x5
ata2.00: cmd c8/00:08:06:fd:6e/00:00:00:00:/e2 tag 0 dma 4096 in

[HARJINDER SINGH (harjinder1988-gmail)]

i have got the same problem
cant access the hard disk which i upgraded to hardy heron..
cant get it to start...

heres d dmesg output

0+ processors (version 2.00.00)
[ 627.807833] powernow-k8: MP systems not supported by PSB BIOS structure
[ 627.808030] powernow-k8: MP systems not supported by PSB BIOS structure
[ 632.805760] lp0: using parport0 (interrupt-driven).
[ 633.958279] ppdev: user-space parallel port driver
[ 635.268101] eth0: no link during initialization.
[ 638.389465] Failure registering capabilities with primary security module.
[ 639.292524] Bluetooth: Core ver 2.11
[ 639.292683] NET: Registered protocol family 31
[ 639.292686] Bluetooth: HCI device and connection manager initialized
[ 639.292690] Bluetooth: HCI socket layer initialized
[ 639.376389] Bluetooth: L2CAP ver 2.8
[ 639.376393] Bluetooth: L2CAP socket layer initialized
[ 639.921649] Bluetooth: RFCOMM socket layer initialized
[ 639.921669] Bluetooth: RFCOMM TTY layer initialized
[ 639.921671] Bluetooth: RFCOMM ver 1.8
[ 788.594559] end_request: I/O error, dev fd0, sector 0
[ 800.775717] end_request: I/O error, dev fd0, sector 0
[ 812.957550] end_request: I/O error, dev fd0, sector 0
[ 825.132448] end_request: I/O error, dev fd0, sector 0
[ 837.306252] end_request: I/O error, dev fd0, sector 0
[ 837.306258] Buffer I/O error on device fd0, logical block 0
[ 849.479961] end_request: I/O error, dev fd0, sector 0
[ 849.479968] Buffer I/O error on device fd0, logical block 0
[ 861.641668] end_request: I/O error, dev fd0, sector 0
[ 861.641674] Buffer I/O error on device fd0, logical block 0
[ 873.887443] end_request: I/O error, dev fd0, sector 0
[ 873.887449] Buffer I/O error on device fd0, logical block 0
[ 886.133416] end_request: I/O error, dev fd0, sector 0
[ 886.133423] Buffer I/O error on device fd0, logical block 0
[ 898.367440] end_request: I/O error, dev fd0, sector 0
[ 898.367445] Buffer I/O error on device fd0, logical block 0
[ 910.590083] end_request: I/O error, dev fd0, sector 0
[ 910.590090] Buffer I/O error on device fd0, logical block 0
[ 922.811951] end_request: I/O error, dev fd0, sector 0
[ 922.811957] Buffer I/O error on device fd0, logical block 0
[ 935.025584] end_request: I/O error, dev fd0, sector 0
[ 935.025590] Buffer I/O error on device fd0, logical block 0
[ 947.231221] end_request: I/O error, dev fd0, sector 0
[ 947.231227] Buffer I/O error on device fd0, logical block 0
[ 959.429869] end_request: I/O error, dev fd0, sector 0
[ 959.429875] Buffer I/O error on device fd0, logical block 0
[ 971.611047] end_request: I/O error, dev fd0, sector 0
[ 971.611054] Buffer I/O error on device fd0, logical block 0
[ 983.797448] end_request: I/O error, dev fd0, sector 0
[ 983.797454] Buffer I/O error on device fd0, logical block 0
[ 995.983449] end_request: I/O error, dev fd0, sector 0
[ 995.983455] Buffer I/O error on device fd0, logical block 0
[ 1008.173065] end_request: I/O error, dev fd0, sector 0
[ 1008.173071] Buffer I/O error on device fd0, logical block 0
[ 1020.363258] end_request: I/O error, dev fd0, sector 0
[ 1020.363265] Buffer I/O error on device fd0, logical block 0
[ 1032.548839] end_request: I/O error, dev fd0, sector 0
[ 1044.7...

[wangyb (yibin-wang)]

same issue here.

[HARJINDER SINGH (harjinder1988-gmail)]

On Mon, May 26, 2008 at 8:11 AM, wangyb <email address hidden> wrote:

> same issue here.
>
> --
> ata2.00: exception emask 0x0 sact ...
> https://bugs.launchpad.net/bugs/223014
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Do get a solution.. i had to format my hard drive. n i lost all my data :((

[Michael Cullinan (cullinanm)]

Hmm ..

Me too. Very minor differences with new install on new Dell Vostro.

October 2007?! Looks like a "deal breaker" for 8.04.

[manno (manno78)]

Very similar issue but I came from an upgrade from ubuntu 7.10. After I upgraded to 8.04 if I boot using the 2.6.22-14 kernel instead of the 2.6.24-16, or the 2.6.24-17 kenels it boots fine. but if I use either of the newer kernels it crashes. my system is a dell vostro 400 desktop.

[alexroat (alexroat)]

The same here.
I have a Dell Inspiron with a 250 gb HD, Intel core 2 duo and 2 Gb of RAM.
Visa home premium as OS.
I decided to try wubi instead to resize the NTFS partition.
System does boot but it freezes on ubuntu progress bar and after some minutes screen becomes black and a series of error messages start to flow down.
Error messages are:

ata2.00: exception Emask 0x0 ........
ata2.00: cmd a0/00:00:00:24...
ata2.00: status: {DRDY}

After a while error messages changes to ata1.00 or ata3.00
There are also other errors like:
ata 2.00: revalidation failed (errno=-5)

It could be related to the SATA controller ? Is there a way to bypass the problem ?
Is there a way to pass some option to the kernel whrough wubi installation or do I need to use grubfordos shell directly ?
Is it related to a problem of contiguous-ness of the HD image file ? Can a defrag help ?

I'm waiting for some indication.

Thank you.

[alexroat (alexroat)]

PS: I used hardy henron 8.04 desktop CD image.

[Gaurish Sharma (gslive)]

i Found a Workaround of This

* Goto BIOS and disable floppy disk Controller

see if it works for you

[warnec (maciekw5-o2)]

I'm sorry to say that, but it was completely useless for me. It didn't change anything. The same message occurs all the time. I turned "Onboard FDC Controller" on "Disabled"

[Matt Schifter (schifterm)]

I've also experienced this issue. I have a Dell Vostro 400 (my config is mentioned in a related bug).

I've tried the live cd and etch. I've also tried Kubuntu 8.04, the latest Debian (4.0 r3 i3), and Fedora Core 9.

It seems the issue is related to something in common between Debian and K/Ubuntu.

Like others with this issue, I am going to punt back to 7.10.

[Lennart Hansen (lahansen)]

Same issue here using a Dell Inspioron 530, standard box.

[Lennart Hansen (lahansen)]

What I had to do so make Hardy run on this box was adding "irqpoll" boot parameter when running installation from CD and when running installed and upgraded version of Hardy.

Attached is output from # lspci -vvnn

[alexroat (alexroat)]

Hi guys,
I solved the problem re-installing Hardy (wubi installation under Vista).
After the copy the installer will ask you to reboot the machine in
order to proceed to the installation.
At the boot you have to choose "linux kernel-xxxx-xxx-xxx with ACPI
safe mode" (or something similar: ACPI compatible mode), because the
issue is caused by an incompatibility of ACPI manager of the SATA
controller.
Choosing this option you will workaround the problem and the installer
will keep your choice for the incoming installation.

If you don't want to reinstall ubuntu you can also try to attach some
options like "irqpoll" to the kernel line in grub configuration.
Someone could ask : "how can I access to grub configuration if I
cannot boot Ubuntu", and the answer is quite simple : after the first
bootloader, you can see something like "press ESC for more options",
the press ESC. You will arrive in the grub classical menu in which you
can directly edit the kernel boot command line (and so you can attach
these options).
Once you are logged on your ubuntu box, it is sufficient to attach the
same lines to the /boot/grub/menu.lst file in the right place to keep
the options.

I wish it will be useful.

Alessandro

2008/7/27 Lennart Hansen <email address hidden>:
> What I had to do so make Hardy run on this box was adding "irqpoll" boot
> parameter when running installation from CD and when running installed
> and upgraded version of Hardy.
>
> Attached is output from # lspci -vvnn
>
>
> ** Attachment added: "output from # lspci -vvnn"
> http://launchpadlibrarian.net/16346780/lspci.out
>
> --
> ata2.00: exception emask 0x0 sact ...
> https://bugs.launchpad.net/bugs/223014
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[warnec (maciekw5-o2)]

Strange. With 8.04 I just needed to add 'irqpoll' in the options when my PC booted from the CD, and then install Linux. After that, I didn't need to do everything and since then Ubuntu works fine (I didn't need to add 'irqpoll' in GRUB, just in the menu which is shown after booting from the CD)

And I am 200% sure that 'irqpoll' didn't help when i used 7.10. Fortunately it works now! ;)

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux the Launchpad package for the kernel.

[Guillaume Desmottes (cassidy)]

Priority of this bug should be raised as it makes Hardy installation impossible on lot of computers.

[alexroat (alexroat)]

Warnek,
the bug randomly appears.
For me was the same, without using irqpoll many times ubuntu starts without
any problem.
However, sometimes happed that ubuntu didn't start correctly and stops on
{DRDY} black screen.
Ok, it is less than 10% of the boots, but it happens and I don't like that
my system behaves in a random way, otherwise I had to chose another OS that
you probably know :D.
Without putting irqpoll option I experienced that also some freezes happen
during KDE session, accesing for example to the printer.
With irqpoll all these problems seemed to be vanished.

Alessandro

2008/7/29 warnec <email address hidden>

> Strange. With 8.04 I just needed to add 'irqpoll' in the options when my
> PC booted from the CD, and then install Linux. After that, I didn't need
> to do everything and since then Ubuntu works fine (I didn't need to add
> 'irqpoll' in GRUB, just in the menu which is shown after booting from
> the CD)
>
> And I am 200% sure that 'irqpoll' didn't help when i used 7.10.
> Fortunately it works now! ;)
>
> --
> ata2.00: exception emask 0x0 sact ...
> https://bugs.launchpad.net/bugs/223014
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Mark Joselli (mejoselli)]

I also had this problem in a dell vostro 200... and it was solved with the irqpoll option
thanks,
Mark Joselli

[Nicholas J Kreucher (kreucher)]

Ubuntu 8.04.1 on a Dell Inspiron 530s, same problem and the irqpoll boot option worked here as well. Added to kopt in /boot/grub/menu.lst to make it permanent.

Thanks!

[Andrei Z. (ateamrocks)]

Hey, same problem... I have a Dell Latitude D600, with ubuntu 8.04.1...

When I boot up it gives me the same problems... I tried all the fixes listed here, and nothing is working...

Please help!

az

[isayhelloyousaygoodbye (ihiubye)]

Sorry for not digging in deepter into related bugs, but I'll just add a comment hoping to give someone a hit on some keywords.
I had the same problem when installing Ubuntu 8.10 on an SiS 620 Mainboard with Intel Pentium III and P-ATA HDDs (8 and 13 GB). The Kernel option all_generic_ide solved the problem for me (add to kernel line in GRUB boot menu and /boot/grub/menu.lst). Unfortunately I could not find a description of this option online, maybe something in linux-doc can tell what this option does exactly.

[Paris Finley (ariostel)]

I used the fix posted here http://johnbokma.com/mexit/2008/08/05/fixing-the-vostro-hang-issue.html by John Bokma on my 8.04LTS, Dell Inspiron 530, and it worked.

[kernel-janitor (kernel-janitor)]

Hi dreamerx2004,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 223014

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Matt Schifter (schifterm)]

> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]

Matt Schifter
Senior Software Engineer
ProActive Technologies, L.L.C.
11825 High Tech Avenue, Suite 150
Orlando, FL 32817
321.319.0440 x119
fax [phone]
The information transmitted (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is intended only for the person(s) or entity/entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
> kernel-janitor
> Sent: Friday, July 10, 2009 7:37 PM
> To: Matt Schifter
> Subject: [Bug 223014] Re: ata2.00: exception emask 0x0 sact ...
>
> Hi dreamerx2004,
>
> This bug was reported a while ago and there hasn't been any activity in
> it recently. We were wondering if this is still an issue? Can you try
> with the latest development release of Ubuntu? ISO CD images are
> available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command from a
> Terminal (Applications->Accessories->Terminal). It will automatically
> gather and attach updated debug information to this report.
>
> apport-collect -p linux-image-`uname -r` 223014
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
> you've tested the upstream kernel, please remove the 'needs-upstream-
> testing' tag. This can be done by clicking on the yellow pencil icon
> next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text. Please let us know your
> results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> ata2.00: exception emask 0x0 sact ...
> https://bugs.launchpad.net/bugs/223014
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> i installed ubuntu 8.04 by wubi under vista home basic.
> after the successful installation, i rebooted my pc and selected ubuntu.
> then after the rooting page, it gave me a page of error message:
>
> ------------------------------------------------------------------------------------------------------
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action ...

[Lennart Hansen (lahansen)]

This issue seems to have been fixed in Ubuntu 9.10 Karmic, installing it worked without any problems for me on the same computer.

[SaintDanBert (saint-grillongroup)]

I have this same issue -- minor differences in error text -- running Hardy (v8.04.3 LTS).
My message text says "ata1.00 ..." or "ata3.00 ..." instead of the ata2.00 reported here.

Trouble started after install of update that added a new kernel as
[code]
vmlinuz-2.6.24-26-386
vmlinuz-2.6.24-26-generic
[/code]

along with
[code]
initrd.img-2.6.24-26-386
initrd.img-2.6.24-26-generic
[/code]

When all of this happened, my running initrd.img file ended up in the bit bucket (I think). The corresponding vmlinuz file
was not affected. Now when I boot, there is not a match between vmlinuz and initrd.img. Sadly, I'm having a whale of the time recovering the lost initrd.img from what I learn now are flawed save sets.

[PabloRQ (pablo-romeroquinteros)]

Fixed!

I used the Dell Vostro fix (http://johnbokma.com/mexit/2008/08/05/fixing-the-vostro-hang-issue.html) by John Bokma.
About the fix: modify the modprobe line to "modprobe -qb ata_piix"

More info:
Ubuntu 9.10
Dell Latitude D510
Wubi install over Winxp

[Jeremy Foshee (jeremyfoshee)]

Would anyone mind testing this for me against the latest daily image and let me know if it still see in the software?

Thanks in advance.

~JFo

[S. Jegen (s-jegen)]

Just wanted to mention that I seem to still have a similar problem. When booting (X)Ubuntu 9.10 the search for my HDDs seems to timeout for a minute or two. The dmesg.log shows a similar Emask DRDY though, even if my Comp starts after the apparent timeout. I hope this issue can be fixed before I will get new hardware... see the dmesg and lspci output in the attachment for information on my machine.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[HARJINDER SINGH (harjinder1988-gmail)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Harjinder

Harjinder Singh
Assistant Systems Engineer at Tata Consultancy Services
Ludhiana Area, India

Confirm that you know Harjinder Singh:
https://www.linkedin.com/e/-p478ow-h6ncdelv-p/isd/8473576947/6yMSbdgp/?hs=false&tok=3u98Qp_bxvulo1

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-p478ow-h6ncdelv-p/7G1TdQm2_0nxFOMdP0cVovv2oWvNsPWoamIhHCv/goo/223014%40bugs%2Elaunchpad%2Enet/20061/I2848869118_1/?hs=false&tok=00dDtH76Fvulo1

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.