Disk error and recovery

mitch geier mg at gritty.UUCP
Tue Jun 14 01:09:01 AEST 1988


> > <>I saw this disk error on my console this morning. Now I'm worried.
> > <>Disk I/O Error: Fun: 30  Cy: 220  Hd 4 Sec 12  Status: 51 Estat: 80 Drstat: A4
> > <>Which drive had the I/O error? What do I do to fix the file that is now
> > <>corrupt? How do I find the file that is corrupt? I assume that I should
> > <>add this location into the bad sector map, but can I do this now without
> > <>re-building the system?
> > 
> > I had the same problem and called Microport.  Their answer (this is no joke!)
> > was "Just use dd to read the entire disk -- chances are you can reproduce
> > the error this way, and that'll tell you which disk had the error."
> 
> > They also had nothing to say about how to find out which file might have
> > been affected, and whether the bad sector would be remapped or not.
> > 
         part of aritcal omited to save space

> Eric Dorman				Kirk- "Wheels, Mr. Spock"
> University of California, San Diego	Spock- "A flivver, Captain"
> Scripps Institution of Oceanography	  From- A Piece of the Action"
>  siolmd!eric at sdsioa.ucsd.edu
>  mp1 at sdcc12.ucsd.edu  Attn: eric
>  dorman at mplvax.nosc.mil  Attn: eric

I have had the same problem using 386 unix but not the same response 
from microport they were verry helpfull and I have had little if any
problem getting support.

	1 drstat in the error line will tell you which drive has the 
	  problem: 
	       	  if the hex byte is AX then it is drive 0 
		  if the hex byte is BX then it is drive 1
		  yes X is not a hex char but use your head
		  and substitute any value for X

  	2 I do understand that in the release comming out soon
	  they will fix some of the disk error problems
	  can't say which ones but I'm sure you will be pleased

Mitch Geier
CECG Inc.
{...}!rutgers!gritty!mg



More information about the Comp.unix.microport mailing list