Novell Open Enterprise Server 2 Benutzerhandbuch
52
OES 2: NetWare Traditional File System Administration Guide
no
vd
ocx
(e
n)
6 Ap
ril 20
ril 20
07
If you have tried all of the above without success, contact a Novell
®
Support Provider or the disk
drive manufacturer.
8.3 Resolving Problems When the Server Hangs
after Mounting the Last Volume
To diagnose problems when the server stops processing after mounting the last volume, identify
whether the following conditions exist:
whether the following conditions exist:
Make sure the server network board is installed or seated correctly and is initializing when the
server is started.
server is started.
Make sure that the server network board is configured correctly.
Check the network board configurations of the boards in the server and the settings shown on
the server and make sure that the settings match.
the server and make sure that the settings match.
Make sure that all server and workstation network boards are seated properly and that cabling
and connections are attached securely.
and connections are attached securely.
Make sure that the terminators on cables have the right ohm rating and are installed correctly.
The IBM PC Cluster sends a broadcast message during initialization, then stops processing if
the network is not cabled or terminated properly.
The IBM PC Cluster sends a broadcast message during initialization, then stops processing if
the network is not cabled or terminated properly.
Check the network boards in all workstations for correct node address settings.
8.4 Resolving Problems When No Volumes
Mount
The sys: volume contains the NetWare system files and the NLM
TM
programs.
If the sys: volume does not mount when the server is booted, then the autoexec.ncf file does
not execute, LAN drivers do not load, and the volume does not become part of the Novell
eDirectory
eDirectory
TM
tree.
To diagnose problems when no volumes mount, identify whether the following conditions exist:
The sys: volume is corrupted.
The server disk containing volume sys: volume has failed.
The cable or power to the external server disks has malfunctioned.
To resolve problems when no volumes mount, do the following:
Repair the volume using the utilities that are appropriate for the volume type.
Check the cabling and power to the external server disks. Replace any faulty components.
Replace the server disk containing the sys: volume.
Create the partitions and the sys: volume.
Restore the data from a backup copy.