Hey, Whenever I boot up my linux machine, it gets stuck on the following :
hda : irq timeout : status 0x50 { DriveReady SeekComplete }
I am running red hat 7.2.. and its a fresh install.. any suggestions on how to fix this??
Regards, Kunal Jhunjhunwala
"Minds think with ideas, not information. No amount of data, bandwidth, or processing power can substitute for inspired thought." - Clifford Stoll
Sometime Today, Kunal Jhunjhunwala assembled some asciibets to say:
Whenever I boot up my linux machine, it gets stuck on the following :
hda : irq timeout : status 0x50 { DriveReady SeekComplete }
may be a DMA problem. You could fool around with hdparm - at your own risk of course.
try some of the following:
DMA off: hdpard -d0
disable 32bit IO (temporarily to see if it makes a difference) hdparm -c0
disable read ahead: hdparm -A
of course, these commands are not complete, because if they were, you'd be tempted to use them without reading the hdparm man page first :)
so, go read it, understand it, and then try it.
Whenever I boot up my linux machine, it gets stuck on the following
:
hda : irq timeout : status 0x50 { DriveReady SeekComplete }
may be a DMA problem. You could fool around with hdparm - at your own risk of course.
Well,
I'd like to add one more possibility - the one I faced. It could be because of a malfunctioning HDD connection or a HDD crash. When we connect standard IDE devices, we use an EIDE 40-pin data cable. There are different types of IDE cables as well - like ATA33, ATA66 and ATA100 compatibles. This cable tends to become loose. So, just check for this possibility as well - even though you feel that the cable is properly connected. Just remove the cable from the back of the drive, clean it with a strong air blow, and replace it back.
There is one more POSSIBILITY of HDD being shut down by the BIOS APM system. In that case, when you boot the system into linux, such problems may occur due to the delay involved in initializing HDD system - escpecially for old HDDs having long init delays. This will happen when you work for about an hr. on your primary HDD without accessing your second HDD at all. The BIOS APM, if set, will shut down the second HDD to save power. If your Linux happens to access the second HDD after some time, you MAY face problems. There was a problem with new Samsung 40GB HDDs as well sometime back. Because of faulty IDE interface/controller, they had surprisingly long init delay. Samsung had to replace them whenever asked for by a customer.
Pls. someone correct me if I'm wrong anyway.
Kunal Gangakhedkar ----------------------
Do you bury me when I'm gone Do you teach me while I'm here As soon as I belong Then it's time I disappear
Metallica - I Disappear
i think the ide problem is due to the DMA and it is through my exprience that i havd problem of dma request timeout but whe ni gave the boot prompt command as LILO: linux ide=nodma it worked
Hi, But linux wont load... so where do i try these commands?? Regards, Kunal Jhunjhunwala
"Minds think with ideas, not information. No amount of data, bandwidth, or processing power can substitute for inspired thought." - Clifford Stoll ----- Original Message ----- From: "Philip S Tellis" philip.tellis@iname.com To: "linux list bombay" linuxers@mm.ilug-bom.org.in Sent: Sunday, March 31, 2002 3:49 PM Subject: Re: [ILUG-BOM] ide drive errors on bootup
Sometime Today, Kunal Jhunjhunwala assembled some asciibets to say:
Whenever I boot up my linux machine, it gets stuck on the following :
hda : irq timeout : status 0x50 { DriveReady SeekComplete }
may be a DMA problem. You could fool around with hdparm - at your own risk of course.
try some of the following:
DMA off: hdpard -d0
disable 32bit IO (temporarily to see if it makes a difference) hdparm -c0
disable read ahead: hdparm -A
of course, these commands are not complete, because if they were, you'd be tempted to use them without reading the hdparm man page first :)
so, go read it, understand it, and then try it.
-- You are false data.
-
Kunal Gangakhedkar -
Kunal Jhunjhunwala -
Philip S Tellis -
sachin