User Guide

152 System Messages
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
FILESYS-X-737: Unable to create VOL$LOG.ERR on volume.
Source: FILESYS.NLM
Explanation: The system cannot log the error messages it produces to the VOL$LOG.ERR
file. Historical error information for this volume will not be recorded at the
server.
Possible Cause: The volume was out of room.
Possible Cause: A disk error occurred.
Action: See Resolving Server Disk Space Problems in the Server Operating System
Administration Guide.
FILESYS-X-738: Unable to write to VOL$LOG.ERR on volume.
Source: FILESYS.NLM
Explanation: The system was unable to write to the volume's error file.
Possible Cause: A disk failure occurred.
Action: Another message should appear that indicates what went wrong. Correct the
problem according to the information in the message.
FILESYS-X-739: Volume name still operational despite drive deactivation.
Source: FILESYS.NLM
Explanation: One of the disk drives in the volume has gone down. However, the volume's
integrity has not been compromised sufficiently to bring the entire volume
down.
Action: See Disk Errors in the Server Operating System Administration Guide.
FILESYS-X-740: Volume name dismounted due to drive deactivation.
Source: FILESYS.NLM
Possible Cause: A disk driver was unloaded.
Possible Cause: The operating system initiated the driver unload.
Action: Make sure the disk driver is loaded.
Possible Cause: A disk failure occurred.
Action: See Disk Errors in the Server Operating System Administration Guide.
Possible Cause: The volume is offline and unavailable to users.
Action: Remount the volume.