Troubleshooting NetWare boot up

  • 10094155
  • NOVL98384
  • 13-Aug-2004
  • 21-Oct-2005

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Fact

NetWare 5.x

NetWare 6.x

Symptom

Server fails to boot properly

Troubleshoot NetWare bootup

Troubleshooting NetWare boot-up

Fix

Server startup switches

SERVER -NA -NS  Means no autoexec.ncf and no startup.ncf

SERVER -NDB   Means no DS database, if server abends when loading ds or other ds trouble. Bring server up with SERVER -NDB | Run dsrepair | adv | local repair, locking the DB | until no errors and then unlock the DB (After repair escape out and you will see it unlock, verify on the console). Usually this fixes the problem; if not consider restoring dib...xk2/xk3...or worse.


Server -kf8 - Step through step by step (Need at least NW 5.1 sp2) upon boot up.  Kind of like break points so you can see which module/process you are having trouble with.


To troubleshoot hardware/drivers:

server -na -ns

loadstage 1

loadstage 2

startup.ncf

Any hardware/driver errors?

mount sys

NSS VOLUMES or VOLUMES to confirm

If this looks good, go to boot troubleshooting or boot normally.



To troubleshoot bootup.

Server.exe -na -ns
OR
server.exe -kf8

startup.ncf

loadstage 1

loadstage 2

loadstage 3

loadstage 4

autoexec.ncf

loadstage 5


At any point you can do a LIST STAGES, which will show you the modules and stages you have completed. Look for errors, public symbols etc. Public symbol means you have a missing, corrupt or mis-matched module.


Files I have had trouble with for bootup.

  • Servcfg.* copy these to the root of C and then del servcfg.* - not so rare on NW 5.x. WARNING. If you have NW 6.x or ifolder or the newer products that store setting in here you may need to reinstall them. Check your timesync/SLP scope list if you delete these.

  • filesys.nlm (if you have one, try renaming it to filesys.old, server.exe has an internal filesys and often backup vendors put a version NW doesn't like and the server will not boot or abends).

  • Nssstart.ncf on NW 6, try renaming it.

  • Dsloader.nlm, rarely will it be the wrong version

  • polimgr.nlm, very rare.

  • Mismatch clib files. Get a clib patch from https://support.novell.com/servlet/filefinder?name=libc.nlm |  match this to your server and copy these files to the c:\nwserver. If that fails do AN INPLACE UPGRADE (NOT new server) and you 'should' maintain your DS, trustees, and volumes. The in place upgrade will replace missing, corrupt or mis-matched modules. I would recommend overwriting the modules. But it depends, consider your DS. Ideally use a NW overlay cd that has the same sp as your current server. Otherwise you will have to reapply the SP and may risk DS issues (TALK TO NTS before doing this!).


Search knowledge base for LOADSTAGE or kf8 or SERVER COLON PROMPT for other TIDs or call Novell support.

.

NetWare 6.5 sp3 loadstage files

 

Novell-Rocks-FS1:list stage 0


The following applications are loaded for Stage 0:

SHOWLOGO.NLM

CPUCHECK.NLM

DIAG500.NLM

NEB.NLM

NBI.NLM

SGUID.NLM

MM.NLM

NWPA.NLM

NWPALOAD.NLM

CIOS.NLM

FLOPPY.HAM

ORION.NLM


Novell-Rocks-FS1:list stage 1


The following applications are loaded for Stage 1:

LSL.NLM

CONNMGR.NLM

LFS.NLM

FILESYS.NLM

UNICODE.NLM

LOCNLM32.NLM

NSS.NLM


Novell-Rocks-FS1:list stage 2


The following applications are loaded for Stage 2:

QUEUE.NLM

NCP.NLM

WS2_32.NLM

XIM.XLM

XSUP.XLM

XMGR.XLM

NOVXENG.XLM

INSTAUTO.NCF


Novell-Rocks-FS1:list stage 3


The following applications are loaded for Stage 3:

DSLOADER.NLM

CCS.XLM

SLP.NLM

PMLODR.NLM

POLIMGR.NLM

MASV.NLM

NASAUTO.NCF

TIMESERV.NCF


The following applications are loaded for Stage 4:

NDSAUDIT.NLM

DS.NLM


The following applications are loaded for Stage 5:

HWDETECT.NLM

LOADIMG.NLM

NLSINIT.NCF

INETSTRT.NCF

DBNET6.NLM