🚀 go-pugleaf

Shaw Carruthers <shaw@shawc.demon.co.uk> writes:

> 
> Recently I have been getting warnings of the following type referring to
> my 2nd IDE drive:
> 
> Jan 31 12:14:44 shawc linux: hdb: read_intr: status=0x59 { DriveReady 
>  SeekComplete DataRequest Error } 
> 
> Jan 31 12:14:44 shawc linux: hdb: read_intr: error=0x04 {
> DriveStatusError }
> 
> Does this mean the drive is on its way out?
> 
> Is there an IDE surface check program for Linux?
> 

badblocks. And there was an article in Linux Journal Jan. '97
explaining how to use it with dumpe2fs and debugfs to mark bad
blocks as used/bad/allocated.

Somebody should turn that article into an howto (mini) because it
seems like most people don't have a clue when it comes to dealing with
such problems. Hor is there an howto dealing with this?

-- 
Jon Martin Solaas				
jonso@ifi.uio.no				
http://www.ifi.uio.no/~jonso			

In article <32F1E56C.6616A7E1@shawc.demon.co.uk>,
Shaw Carruthers  <shaw@shawc.demon.co.uk> wrote:
>Recently I have been getting warnings of the following type referring to
>my 2nd IDE drive:
>
>Jan 31 12:14:44 shawc linux: hdb: read_intr: status=0x59 { DriveReady 
> SeekComplete DataRequest Error } 
>
It doesn't happen to a Western Digital HDD does it? Mine did exactly the 
same recently. 

For some of the WD drives there is a firmware upgrade available on their 
website (http://www.wdc.com/). This corrects a problem with the error 
correction code built into the drive.

Alan.
apc95@aber.ac.uk
alan@welsh-cob.cix.co.uk
 

On Sat, 01 Feb 1997 13:38:37 GMT, Shaw  Carruthers <shaw@shawc.demon.co.uk> wrote:
>
>So I guess I either have a soft error or a timing problem.
>
>I get 0x51 or 0x59 errors followed by 0x04 .
>
>The drive is Seagate ST36660A	

Hmm. I don't know the specifics of that particular model, so how
old is it and how much use you've gotten out of it?

The last Seagate I got in 1991 and didn't last very long. One of the
two Maxtor's I got just recently but the other one's been in use since
fall 1993. No problems yet.

>--
>Shaw Carruthers - shaw@shawc.demon.co.uk
>London SW14 7JW UK
>This is not a sig( with homage to Magritte).  


-- 
------------------------------------------------------------------------
David E. Fox                 Tax              Thanks for lettimg me
dfox@belvdere.vip.best.com   the              change magnetic patterns
root@belvedere.sbay.org      churches         on your hard disk.
-----------------------------------------------------------------------

In article <32F1E56C.6616A7E1@shawc.demon.co.uk>,
Shaw Carruthers  <shaw@shawc.demon.co.uk> wrote:
>Recently I have been getting warnings of the following type referring to
>my 2nd IDE drive:
>
>Jan 31 12:14:44 shawc linux: hdb: read_intr: status=0x59 { DriveReady 
> SeekComplete DataRequest Error } 
>
>Jan 31 12:14:44 shawc linux: hdb: read_intr: error=0x04 {
>DriveStatusError }
>
>Does this mean the drive is on its way out?

Maybe, maybe not.  I get this error from my laptop, when it
powers down the disk underneath Linux's feet and then get spun up
again.  It all appears to be fine.  Having said that, this is the
laptop which crashes after 15 minutes of running windows and has
a 3 week uptime with Linux. YMMV.

-Dom

David E. Fox wrote:
> 
> On Sat, 01 Feb 1997 13:38:37 GMT, Shaw  Carruthers <shaw@shawc.demon.co.uk> wrote:
> >
> >So I guess I either have a soft error or a timing problem.
> >
> >I get 0x51 or 0x59 errors followed by 0x04 .
> >
> >The drive is Seagate ST36660A

Should read ST3660A

> 
> Hmm. I don't know the specifics of that particular model, so how
> old is it and how much use you've gotten out of it?
> 

It is exactly one year old. The machine is never switched off, so the
disk runs all the time but does not have a great data load in and out. I
guess I'll take the lid off and rattle a few cables to see if anything
is loose. Grepping the logs I see I had about 7 errors in December and
60 in January.
-- 
Shaw Carruthers - shaw@shawc.demon.co.uk
London SW14 7JW UK
This is not a sig( with homage to Magritte).

Shaw Carruthers (shaw@shawc.demon.co.uk) wrote:

: Jan 31 12:14:44 shawc linux: hdb: read_intr: status=0x59 { DriveReady 
:  SeekComplete DataRequest Error } 

We used to get this on one of our machines - up until yesterday, in fact.
The drive incidentally was not a Western Digital. After reading your post
I ran badblocks, and as that showed up no problems I began wondering what
could be affecting it. After remembering that we'd had problems with a drive
that was mounted in a removable pack under NT, I removed the drive from the
removable pack it was in, and since then have had no errors. Strange, but
true.

	Cheers,
		Steve

dirk@loth.demon.co.uk (Steve Dodd) wrote:

>Shaw Carruthers (shaw@shawc.demon.co.uk) wrote:
>
>: Jan 31 12:14:44 shawc linux: hdb: read_intr: status=0x59 { DriveReady 
>:  SeekComplete DataRequest Error } 
>
>We used to get this on one of our machines - up until yesterday, in fact.
>The drive incidentally was not a Western Digital. After reading your post
>I ran badblocks, and as that showed up no problems I began wondering what
>could be affecting it. After remembering that we'd had problems with a drive
>that was mounted in a removable pack under NT, I removed the drive from the
>removable pack it was in, and since then have had no errors. Strange, but
>true.

Strange, on my machine the master is in a removable tray and the slave
is fixed; but it is the slave that is showing the problem.

I think I have now cracked it. The error developed into an 0x40 error
which gives a sector number. Turned out to be a bad sector in the swap
partition. Fixed it with mkswap -c.

No errors since( now 36 hours and counting).
--
Shaw Carruthers - shaw@shawc.demon.co.uk
London SW14 7JW UK
This is not a sig( with homage to Magritte).