[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 412
  • Last Modified:

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
0
dcarrion
Asked:
dcarrion
  • 6
  • 3
1 Solution
 
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.
0
 
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.
0
 
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~
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
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.
0
 
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
0
 
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.
0
 
dcarrionAuthor Commented:
Okay I will migrate to 2.6.16.9 and will let you now how it goes.
0
 
dcarrionAuthor Commented:
Okay reinstall debian with manual package selection.
Installed Kernel 2.6.16.
Works Fine

Thanks slow1000
0
 
dcarrionAuthor Commented:
actually one problem...I can no longer eject or unmount my CDROM drive. it is saying it's always busy.
0
 
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
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now