Debian: ata1 command 0x35 timeout

Hello

Getting this error when trying to restart, switch to terminal, shutdown or do anything in terminal:

ata1:command 0x35 timeout, stat 0x50 host_stat 0x4

Before that I get a whole bunch of other errors like IRQ 217 nobody cares and other errors.

I am using a SATA hard disk in native mode

Kind Regards

Daniel
dcarrionAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bryanfordCommented:
sounds like the hard disk is crap... probably a western digital right?

try using a different sata disk if you got another one and see how that goes.
dcarrionAuthor Commented:
I don't think it is the hard disk as i did a scan on it and it seems okay. The smart monitor in the bios isn't picking up any errors on it either.
dcarrionAuthor Commented:
Oh yes something else important i forgot to mention.

I am running Debian Sarge 3.1 r1 with Kernel 2.6.8-3

It does not have that problem when runing Kernel 2.4.7~
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

slow1000Commented:
You should update to a newer kernel if you are using 2.6, since the SATA support has been enhanced since 2.6.8 came out.
dcarrionAuthor Commented:
I would rather use a kernel that is noted as stable in the distribution. Any other ideas? It seems to work fine in Kernel 2.4
slow1000Commented:
Unfortunately, the 2.6.8 kernel is from summer 04.  Accordingly, support for hardware that was becoming common at that time (many SATA chipsets) is NOT stable.  I suggest that you switch back to parallel ata if the 2.6.8 kernel is a necessity, so that your hardware and software are from similar time periods, unless you are willing to patch your existing kernel from upstream (which is how your 2.4 kernel works with your sata chipset).  However, that would be much more difficult than just moving to a more recent Linux (kernel) listed as stable by the upstream developers.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dcarrionAuthor Commented:
Okay I will migrate to 2.6.16.9 and will let you now how it goes.
dcarrionAuthor Commented:
Okay reinstall debian with manual package selection.
Installed Kernel 2.6.16.
Works Fine

Thanks slow1000
dcarrionAuthor Commented:
actually one problem...I can no longer eject or unmount my CDROM drive. it is saying it's always busy.
slow1000Commented:
Hmm, I don't know about the cdrom drive.  Try using fuser to see if a file is open.

e.g. /usr/sbin/fuser /mnt/cdrom
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.