Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site hadron.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!trwatf!rlgvax!prcrs!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.unix-wizards
Subject: Re: RA60 hard error on 4.2BSD
Message-ID: <177@hadron.UUCP>
Date: Mon, 6-May-85 22:24:57 EDT
Article-I.D.: hadron.177
Posted: Mon May  6 22:24:57 1985
Date-Received: Fri, 10-May-85 08:19:38 EDT
References: <10072@brl-tgr.ARPA>
Organization: Hadron, Inc., Fairfax, VA
Lines: 23

>      uda0: hard error, disk transfer error, unit 0, grp 0x0, hdr 0x26aec
>      uda0: hard error, SDI error, unit 0, event 0353, hdr 0x0
> The second error repeats about 6 times.
> 	What do these errors mean?  ...

While working on a System V driver, this happened a lot.  The field
service person had just declared the hardware to be perfect, so I also
assumed it was a problem in a not-yet-quite-bugless driver.  I worked
for weeks (off and on) to make the driver more and more perfect.

The problem was hardware.  One of the boards in the drive itself (the
interface to the outside world, i think) had to be replaced.  For a day
we ran on the opposite side of the dual access.  We found this all out
when it got so bad we went back to DEC.  Our regular field service
person then came out to run diagnostics.  She found the problem
immediately.  (*sigh*)

Try swapping the drive cables in back from "A" to "B", and spinning
up the drive with the "B" button pushed in, rather than the "A".
See if that makes a difference.  Then get your field service to run
lots and lots of diagnasties (on A) to show your advisors.

	Joe Yao		hadron!jsdy@seismo.{ARPA,UUCP}