Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!usc!orion.oac.uci.edu!mrichey
From: mrichey@orion.oac.uci.edu (Mike Richey)
Newsgroups: comp.dcom.lans
Subject: Re: Recurring Novell Problem
Message-ID: <4598@orion.cf.uci.edu>
Date: 10 Feb 90 19:59:17 GMT
References: <867@gator.usl.edu>
Reply-To: mrichey@orion.oac.uci.edu (Mike Richey)
Organization: University of California, Irvine
Lines: 43

In article <867@gator.usl.edu> pcb@gator.usl.edu (Peter C. Bahrs) writes:
>I used to think it was a loose connection problem that periodically
>caused the Netware server to crash (IBM PS/2 Model 80).  So
>I tightened all the connectors up and no problems, I thought.
>
>Periodically the clients (IBM PS/2 Model 70's) go 'dead' and can't
>locate the server any longer.  The server's screen will show
>  Running MUXPRC
>or something similar and it says to power down the system?!@!@

This is a somewhat important message. If you have a GPI or an NMI
error (Running MUXPRC tipped me off) then you probably have a bad or
very flaky mempry chip/board in your server. 

My experience has been that if the bad memory chip is located in the lower
addresses of RAM, then the errors will occur often. If the failing address
is higher in memory, this error will occur less frequently. Now what
you need to do is either find a good set of diagnostics, like Check-It,
or QAPlus and run the diagnostics on the server and identify the failing
module.

GPI error can be caused by a number of things. Power supplies, a NIC, system
board, etc. All I can offer you is a bit of good luck. So Good luck.

>    FAT location 1041 used
>    but file does not exist. Do you want to mark...y/n
>I said n??)
>
>With the above exception, the server always comes back up with no
>problems ??? I don't understand.
>
>Has anyone seen this?  Where ,..., what have you done to rectify the
>situation?
>

This could be caused by faulty RAM. Netware caches reads and writes.

There are easy ways of taking care of this. I really think you need get
the NMI error fixed first. (The FAT error will be taken care of by Netware)


Michael S. Richey   mrichey@orion.oac.uci.edu
University of California, Irvine     Network Services