On Wed, 28 Apr 1999, George Bonser wrote:

> On Wed, 28 Apr 1999, Bruce A. Locke wrote:
> 
> > 
> > 
> > Bad Bad Bad... I got that from an HD and it died one month later (can you
> > say "*click* *click*" ;)
> > 
> > I would seriously back up stuff ASAP :)
> 
> Nope, this is quite normal from many UDMA disks and Linux . Try forcing
> the disk into PIO mode 3. See if the errors go away.
> 
> I have two systems, different drives, different controllers, different
> motherboards report this error until I forced the drives into PIO Mode 3
> (one is a Seagate, one is a Maxtor). It is a funky Linux driver problem or
> a funky drive problem that other operating systems ignore and Linux is
> hypersensative to.

Hmmmmmm.......

I have found that these messages with a drive making a clanking noise is
an indicator of S.M.A.R.T failure.  This was observed imperically.
I was a Quantum drive, and I contacted on of the design engineers that I
know.  If I recall correctly, this conclusion was verified.

"funky Linux driver", Please clarify and suggest a solution.

Where did you get the info about forcing "PIO Mode 3"??

> > > 
> > > 	I get the following during high disk activity (fscking etc) from a 
> > > "ST31720A, 1626MB w/0kB Cache, CHS=826/64/63" disk:
> > > 
> > > hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> > > hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=1643225, sector=1437593
> > > end_request: I/O error, dev 03:42, sector 1437593
> > > hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> > > hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=1647634, sector=1442002
> > > end_request: I/O error, dev 03:42, sector 1442002
> > > 
> > > 	And so on. I'm using a 2.0.35 kernel. Is my disk dying or what?
> > > I haven't noticed any corruption, and the dos on a small partition near the
> > > end of the disk hasn't complained anything.
> > > 
> > > 	'hdparm -v' says the following for that disk:
> > > 
> > > /dev/hdb:
> > >  multcount    =  0 (off)
> > >  I/O support  =  0 (default 16-bit)
> > >  unmaskirq    =  0 (off)
> > >  using_dma    =  0 (off)

Since the drive is not in any (active) DMA modes from his report,
one can conclude that PIO4 may be active.

> > >  keepsettings =  0 (off)
> > >  nowerr       =  0 (off)
> > >  readonly     =  0 (off)
> > >  readahead    =  8 (on)
> > >  geometry     = 826/64/63, sectors = 3331852, start = 0
> > > 
> > > 	Thanks a lot for your time.
> > > 		-- Jakke

Andre Hedrick
The Linux IDE guy
http://www.dyer.vanderbilt.edu/server/udma/2.2.6.uniform-ide-6.19.patch.4.gz
http://www.dyer.vanderbilt.edu/server/udma/hdparm-3.5i.patch.gz

APC UPS Daemon Support Center.
                        http://www.brisse.dk/site/apcupsd/
GPLed source on April 7, 1999




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/