Novell Open Enterprise Server 2 Benutzerhandbuch
Troubleshooting
55
no
vd
ocx
(e
n)
6 Ap
ril 20
ril 20
07
8.9 Resolving Volume Mounting Problems
Caused by the Name Space Module
After a volume has been configured to support more than the DOS naming convention, the name
space NLM program must be loaded before the volume can be mounted.
space NLM program must be loaded before the volume can be mounted.
To diagnose problems when a Traditional volume cannot mount because the name space NLM
program is not loaded, identify whether the following conditions exist:
program is not loaded, identify whether the following conditions exist:
The command to load the name space NLM is not in the startup.ncf file.
The NLM to load the name space has not been copied to the boot directory of the server.
To resolve problems when a Traditional volume cannot mount because the name space NLM
program is not loaded, do the following:
program is not loaded, do the following:
Load the name space NLM program, then mount the volume. Copy the name space NLM to the
server boot directory and add the load command to the startup.ncf file. The NLM then
loads automatically whenever the server is booted.
server boot directory and add the load command to the startup.ncf file. The NLM then
loads automatically whenever the server is booted.
Delete the name space configuration from the volume.
WARNING: This is a destructive step that destroys all of the extended file information.
Back up all non-DOS files.
Load the Vrepair utility, select Set VRepair Options, then select the Remove Name Space
Support from the Volume and Write All Directory and FAT Entries to Disk options. Exit to the
main menu, then run Vrepair > Repair a Volume on the volume that would not mount.
Support from the Volume and Write All Directory and FAT Entries to Disk options. Exit to the
main menu, then run Vrepair > Repair a Volume on the volume that would not mount.