Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!FORD-WDL1.ARPA!rion From: rion@FORD-WDL1.ARPA (Rion Cassidy) Newsgroups: comp.sys.sgi Subject: (none) Message-ID: <8712081617.AA02286@FORD-WDL1.ARPA> Date: Tue, 8-Dec-87 11:17:24 EST Article-I.D.: FORD-WDL.8712081617.AA02286 Posted: Tue Dec 8 11:17:24 1987 Date-Received: Sun, 13-Dec-87 12:16:41 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 30 Here at Ford Aerospace we have several IRIS 3120's, and one of them has had hardware problems in the form of parity errors. The problem has reared its head several times, each time pretty much at random, and the witless maintenance people at SGI have been unable to fix it. I am posting this because, as I've mentioned the problem does continue, and in the interest of productivity, we would like to get it fixed. If you are unfamiliar with hardware errors, they generally seem to stop the computer dead in its tracks, causing untold confusion upon rebooting. One time the entire file system had to be restored (and many files were simply lost). The hardware maintenance people at SGI have replaced the memory or CPU (or both) cards each of the six times our machine has failed, each time telling us that they are now *SURE* the problem is fixed. We are tired of screwing around, obviously they are not. My questions to you as fellow IRIS users are: 1) Have you experienced similar hardware problems, and if so did you ever get a satisfactory solution? What was the answer? 2) Have you been similarly frustrated by SGI incompetence? Rion Cassidy rion@ford-wdl1.arpa ...{sgi,sun,ucbvax}!wdl1!rion