Troubleshooting
8
novdocx (en) 6 April 2007
51
8
Troubleshooting
This section presents various troubleshooting procedures for resolving problems with Traditional
volumes:
Section 8.1, “Resolving File I/O Errors,” on page 51
Section 8.2, “Resolving Volume I/O Errors,” on page 51
Section 8.3, “Resolving Problems When the Server Hangs after Mounting the Last Volume,”
on page 52
Section 8.4, “Resolving Problems When No Volumes Mount,” on page 52
Section 8.5, “Resolving Problems When Only Some Volumes Mount,” on page 53
Section 8.6, “Resolving Disk Error Problems When a Volume is Mounting,” on page 53
Section 8.7, “Resolving Memory Errors When a Volume Is Mounting,” on page 53
Section 8.8, “Resolving Volume Mounting Problems Caused by Corrupted Directory Entry
Tables or File Allocation Tables,” on page 54
Section 8.9, “Resolving Volume Mounting Problems Caused by the Name Space Module,” on
page 55
8.1 Resolving File I/O Errors
To resolve a file I/O error, try one or more of the following:
Make sure that the volume (especially volume sys:) is mounted.
If the volume is out of disk space, error messages appear on the Logger Console screen
indicating that the volume is almost out of disk space. Check this screen for messages.
Check how much space remains on the sys: volume. If it is low, increase the size by adding
free space.
To increase the amount of free space, do one or more of the following:
Delete extraneous files (if you can log in from a workstation).
At the server console prompt, enter set immediate purge of files = on, then retry
the action.
If you have an additional disk, increase the size of the volume by creating an additional
segment of the volume on the disk.
8.2 Resolving Volume I/O Errors
To resolve a volume I/O error on Traditional volumes, try one or more of the following:
Make sure that all devices that contain the volume are online. (Volumes can span multiple
devices.)
Repair the volume using the Vrepair utility.
Make sure that the volume is visible.
