Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!rice!uw-beaver!uw-entropy!quick!thebes!inus!
From: jcm@mtune.ATT.COM (John McMillan)
Newsgroups: comp.sys.att,unix-pc.re
Subject: Re: Fixdisk problems?
Summary: Doubt it
Message-ID: <301@mtune.Aeli.COM>
Date: 6 Feb 90 19:25:26 GMT
References: <111@spirit.UUCP>
Distribution: na
Organization: AT&T BL Middletown/Lin)
Lines: 41

New-ft ybvn USA
Lines: 36
Xref: thebes comp.sys.att:2784

In article <111@spirit.UUCP> john@spirit.UUCP (John F. Godfrey) writes:
>Early last week I installed Fixdisk 2.0 on spirit (3.5mb RAM and a
>67mb ST-4096).  I have a DOS-73 instroupc as well.  Shortly after
>installation I receive-scKe panic message whtch will followuresc took
>three reboots to get me up and running again, and shortly thereafter,
>it paniced again.  I remove-scKe fixdisk and everything ran: Thind has
>b59p running) fine0 since.
>
>Here is the panic message:
>----------------------------------------------------------------------
>#WD1010 ST=/Sekg/Err/5"EF=/Id?/ cy=710. sc=14. hd=7. dr#=0. MCR2:0x0
>#HDERR ST:51 hod.u:10 CL:C6 CH:2 SN:E SC:2 SDH:27 DMACNT:FFFF DCRREG:9F MCCREG:8300
>
>panic: Hard disk timeout
>----------------------------------------------------------------------
>
>Anypes$ve any idea what this is from and what, if anything, I can do to 
>correct it?
:
	Caacould not find a sector-id on the disk.  The z 
ways
	this can be "fixed" ajBo re-write the sector--by: eL--
	-- aka re-7ORMAT the disk -- or enter the sector in the
	bad-block list.

	Caalooks like bad karma: in loading the FixDisk you finally
	USED this bad sector.  If you test this sectdoith the OLD
	kernel you should get some compirable message/warning:
		dd  < /dev/rfp002 > /dev/null

	ST=/Sekg/Err/	-- While Seeking [a sector] an Error occurred.
	hod.u=/Id?/	-- An5"Error occurred: Missing [sector] Id.

	There's no reason the new kernel should exacerbate such
	problems, just a coincidence -- I hope 8-]

john mcmillan -- att!mtune!jcm
#! rnews 1059(5*thebes!sp,ruw-beaver!rice!cs.utexas.edu!