Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site ron1.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!timeinc!phri!pesnta!amd!amdcad!amdimage!prls!philabs!ron1!ron From: ron@ron1.UUCP (Ron Saad) Newsgroups: net.unix-wizards Subject: Re: Re: RA60 hard error on 4.2BSD Message-ID: <115@ron1.UUCP> Date: Wed, 26-Jun-85 14:06:53 EDT Article-I.D.: ron1.115 Posted: Wed Jun 26 14:06:53 1985 Date-Received: Wed, 3-Jul-85 08:38:42 EDT References: <10072@brl-tgr.ARPA> <177@hadron.UUCP> Organization: CATT, Polytechnic Inst. of N.Y. Lines: 57 >> 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} *** REPLACE THIS LINE WITH YOUR LUNCH *** We are rather new on the net, so I missed the original article. I tried to contact the author of the 'solution' several times via mail, but never got a response, so I assume my message never got there. We have been having the same problem with our UDA50-RA81-RA60 system. We are running a VAX 11/780 with 4.2 BSD. Since the problem occurred on a Sys-V machine also, I assume it's not the drivers. Our service people have replaced every board on the system (all the RA60 boards, the uda50, the personality module on the RA81), all with no success - the problem keeps occurring. It wouldn't be so bad if it just crashed the system, but sometimes UNIX does not recover, and just hangs there till I come in and force a reboot. If anyone out there in wizard-land can give us more information, it would be greatly appreciated (the service people are now going to replace the power supply boards ... :-) If the person who posted the problem originally has succeeded in solving the problem - PLEASE tell us how ? -- ------------the opinions expressed above etc. etc. -------------- Ron Saad (4Z4UY) Sys Adm - Center for Advanced Technology in Telecommunications Polytechnic Institute of New York UUCP: ...{ihnp4,seismo}!{philabs,cmcl2}!ron1!ron MAIL: 333 Jay St. Brooklyn, N.Y. 11201 PHONE: (718) 643-7303