Discussion Locked

Netware 5.0 Server error

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I run a LAN with a Novell 5.0 server at a CPA office. Since we are in tax season... I have been coming in on Sat nights to reboot the server. The last few weekends I have encountered and error when I cold boot the server:

"Warning {server name}expirenced a critical error, the offending process was suspended or recovered. Services hosted by this server may have been affected"

This happens when mounting one of my volumes. The (data)volume mounts and the server loads everthing correctly and runs fine.

Novell speaks about a TID 10054649 but it speaks about a server abending or not coming up.

My server is behind in patches... but I don't want to mess with it during tax season. Any quick fixes?

I am running:
Support pack 2
NICI 1.0

Have not run VREPAIR this year.... might need to do that.
If VREPAIR is needed.... do I need to dismount SYS using 5.0 or does it dismount automatically?

Thanks,
Rob

5 replies

by jimbb

I would read the Abend-TID if I were you, because you did have one. Whatever caused this abend is no longer active, but still somewhere in memory, protected by the OS from doing any more damage.
Check your SYS:\SYSTEM\ABEND.LOG to see what module did which strange thing. It will be at the end of the file, and there will be heaps of unreadable stuff and a big list of modules loaded at that time, so prepare to scroll a bit. Once you have that message, which will be like "page fault" or "processor exception" or so, scroll down a few lines and you'll see "Additional information". Together they may already give you a hint about the offending module, and with those exact descriptions Novell's knowledgebase - or Techrepublic ;-) - may give you more details on what to do next.

If the volume is somehow mixed into this, a Vrepair might indeed do the trick. Yes, you need to dismount a volume before you can repair it. And you also need the v_*.* name space files loaded. If you have theNFS name space for example, you need V_NFS.NLM loaded to run the vrepair on that volume.

Jim

by pawel_wiszniewski

You have an abend. It could be one time event (sometimes it just happens) or it can be repeating. But my recommendations would be:
1) Do the full backup of your server. Verify it. Or do it twice for security. If it is really CRITICAL, and you have some spare equipment (and a whole weekend ;), I would try to install a backup server (not connected to your network) with all data restored on it. In case of any problems, just swap them.
2) Use VREPAIR. You will have to dismount volume which is causing problems. I would recommend to do it for all volumes exept SYS. Also check MONITOR statistics for bad blocks: Go to STORAGE DEVICES, then to HOTFIXED PARTITION and check statistic for "Used hot fix blocks" (you will have to press TAB to see it).IF it is greater then 0, your hard drive can have some physical problems. I would start to prepare for swapping it. If you want to VREPAIR SYS: volume, you will have to dismount it an then run VREPAIR from disk C: (LOAD C:\NWSERVER\VREPAIR.NLM)
3) If after this you will still experience any errors, install support pack 6a. It is quite stable (exept maybe for NDPS - another small patch ;) and no TID or support team will help you if you will not have newest support pack installed. Maybe your problem was already solved in this pack.
4) If it will still not help, start analyzing ABEND.LOG. If you don't know what to look for -> go for support.novell.com or just ask here at the forum.

I hope it'll help.
Good Luck :)

This discussion is closed to new replies.