Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!cwlim!david
From: david@cwlim.CWRU.EDU (David Nerenberg)
Newsgroups: comp.dcom.lans
Subject: Re: Recurring Novell Problem
Message-ID: <1990Feb11.060053.4392@usenet.ins.cwru.edu>
Date: 11 Feb 90 06:00:53 GMT
References: <867@gator.usl.edu>
Sender: david@cwlim.ins.cwru.edu
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 50

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?!@!@
>Then we have to reboot the clients.  What a pain...>
>(Today after I reboot the server it said:
>    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?

Your problem could be caused by many possible things as, if you can find
in the Novell error manual, says.  In my experience, it is one of two
things:  1.  Your servers memory.  Although IBM 80's are usually good with
             what type and quality of memory chips/SIMMS they have, one
    	     unreliable byte and your server goes into this process.  You
     	     could try changing memory.  Unfortunately, memory tests don't
	     usually find these subtle errors because they are not always
  	     there (heat, flaw, who knows).  I have found that talking the
	     server down and making it into a DOS machine with a RAM disk
	     taking up all of the memory and then running disk checking
	     programs has been able to find some of these subtle errors.
	     Both Norton DT and OPTUNE in non-cache mode have been able 
	     able to find some of my problems.
	 2.  The other possible cause could be a dirty AC line.  Without
	     the use of an osciloscope, I know of no easy way to tell if
	     this is the problem.  If you have a UPS or a good line
	     conditioner, this isn't the problem.
	My first guess would have to be the memory, that is as long as
you are not running MAC VAPs! 

The error you received was because the server locked up when it was  accessing
the hard drive and the operating system FAT has an entry without a file being
on the disk.  The error would continue to be there on bootup of the server
until the OS either uses the HOT FIX or another file uses the space on the
drive intend for the file that the FAT thinks shoud be there.  Basiclly,
no matter what you answered to the quetion, no harm willl come to your
server.
 
					Good luck....
						Dave
david@cwlim.ins.cwru.edu
dwn@pyrite.som.cwru.edu