PDA

View Full Version : [ubuntu] 9.04 new install problem with (ata1: softreset failed device not ready)



thenewmexican
April 29th, 2009, 09:46 PM
I'm attempting a new install of 9.04 AMD_X64
When I boot from the CD drive. I receive ata1: softreset failed (Device not ready).

After which. The boot process drops into a shell. In which I have no idea what to do with.

So. I still have not been able to get a full installation done.
Just to check the hardware, I did a fresh install of openSUSE11.1.
I had zero problems getting it installed.

So. This issue is clearly an Ubuntu problem.

Hardware:
-- ASUS M2A-VM MB
-- Opteron 1218 Santa Ana 2.6 GHZ
-- 8GB GSkill PC800 DDR2
-- PNY 8600 GT 512MB Pcie
-- ASUS DRW-2014L1T DVD+R/RW Drive



Any pointers greatly appreciated.

VastOne
April 29th, 2009, 10:03 PM
I'm attempting a new install of 9.04 AMD_X64
When I boot from the CD drive. I receive ata1: softreset failed (Device not ready).

After which. The boot process drops into a shell. In which I have no idea what to do with.

So. I still have not been able to get a full installation done.
Just to check the hardware, I did a fresh install of openSUSE11.1.
I had zero problems getting it installed.

So. This issue is clearly an Ubuntu problem.

Hardware:
-- ASUS M2A-VM MB
-- Opteron 1218 Santa Ana 2.6 GHZ
-- 8GB GSkill PC800 DDR2
-- PNY 8600 GT 512MB Pcie
-- ASUS DRW-2014L1T DVD+R/RW Drive



Any pointers greatly appreciated.

I have this same error message right after the grub selection of 9.04. This was a new machine install and it was a successful installation w/o error.

I get two of these messages and then boot up is normal. I put it down to having no IDE drives, and 2 (of 4) SATA drives connected. Don't know if this info helps you, but just a pass along.

VastOne

koepked
May 7th, 2009, 10:03 PM
I'm experiencing the same thing as VastOne. Clean install, but same 2 errors right outta GRUB on every boot.

seseberg
May 27th, 2009, 10:21 PM
same here. 32 bit, or 64 bit version of either 8.10 or 9.04 on my toshiba satellite a305d-s6848 with a 200gb sata hard drive. WHEN will someone take care of this?

VastOne
May 28th, 2009, 02:39 AM
same here. 32 bit, or 64 bit version of either 8.10 or 9.04 on my toshiba satellite a305d-s6848 with a 200gb sata hard drive. WHEN will someone take care of this?

I compiled and installed kernel 2.6.29-4 and the problem is gone for me now.

VastOne

seseberg
May 28th, 2009, 06:45 AM
could you please point me towards a tutorial on how to do that? can I compile from source under windows? and also, how come I need to compile from source, I mean, isn't the .iso that I download from ubuntu.com good enough? what are the differences?

seseberg
May 28th, 2009, 07:31 AM
I found this website claiming to have the fix
http://kerneltrap.org/mailarchive/git-commits-head/2008/6/14/2122314
could you please teach me how to implement it? thanks you!

GuiGuy
June 12th, 2009, 11:12 PM
I have fallen foul with this this morning. My mythbuntu backend (ASUS M3A) and my wife's eeepc both did an update that involved HAL. both machines now report the ATA sofreset failure and then lock up. I can't even get a CLI cursor.

Now, what's that about Windows?

larseko
June 20th, 2009, 10:23 AM
I've had this problem since 8.04, and been using XP since(!). 7.10 worked flawlessly on this computer, which has the motherboard Asus M2A-VM HDMI with the latest bios. This computer won't even boot from the ubuntu DVD (ubuntu studio 9.04 amd64 that is) or from a USB stick made from a normal ubuntu i386 image. Somehow I managed to install the OS (studio) from the same DVD, though. I get errors about both ata1,ata2,ata3,ata4, and then shortly afterwards I have to reboot.

npark
July 7th, 2009, 11:18 PM
I am having this same problem. I purchased an eMachines D620 laptop with Vista pre-installed, and installed 9.04 on a separate partition. I am getting this error code on both ata1 and ata2. I have looked on a number of different forum threads, and the general consensus seems to be that there is nothing that a non-technical user can do about this, besides waiting for a new Ubuntu release with an updated kernel. Is this correct? And if so, would trying a derivative such as XUbuntu be likely to help solve the problem, or not?

Thanks so much for any help.

kodger
August 3rd, 2009, 04:00 AM
I have the same issue