On Mon, 22 May 2000, Shaggy Im-erbtham wrote about, hda: status timeout: .....
strange messages:
> I keep getting this strange message on my console
>
> hda: status timeout: status = 0xd0 {busy}
> hda: no DRQ after issuing WRITE
> ida0: reset: success
>
> While it does not seem to affect the computer (does
> not hang or otherwise) it is an irritation. Not to mention
> the nagging feeling that something is "wrong" with the
> computer and you don't know what it is.
>
> What is it and how can I get rid of it?
As to what it is;
Data-Read-reQuest = DRQ
It can be caused by different things, all of which point to a disk that is
not working optimally.
Possable causes;
1) Timing
2) DRQ_STAT bit set unexpectedly.
3) Drive reset
4) there are others but at the minute i cant think of them.
What can you do to stop the messages.
To answer that with "you cant" would be defeatist, what you can do is use
'hdparm' to check the drive and test its timings.
Please read 'man hdparm' BEFORE using that program, you can destory your
data and/or the drive itself.
On the otherhand you could run fsck on the filesystem(s) first to make sure
there are no problems in the filesystem itself.
I dont want to confirm your worst susspions but when you get messages like
that it could mean the drive is going to dye.
I have had DRQ messages from a drive in the past that was a ST38420A
of which segate kindly replaced.
You can go to
http://seagate.com/support/service/warranty_validation.html
or start at the begining.
http://seagate.com
to check the warrenty of the drive.
Seagate is a very customer concious company, i had no problems getting a
new drive at all, only a 2 week wait.
If it is the drive playing up, you might be able to get a imidiate
replacement from the place where you brought the drive.
> This happens on a RedHat 6.0 installation on a new
> 8.4 GB HDD. CPU is 300mgz AMDk6-2. 64MB RAM.
> HDD is a Seagate U8 model ST38410A. I have been
> having problems (temporary failures, strange clicking
> noises, etc.) with another Seagate HDD (windows OS)
> lately.
>
> So could the above problem be a HDD problem?
Another thing to check first is the jumper settings on your motherbaord, i
have heard of overclocking causing IDE problems.
>
> Shaggy
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
