InveStore Event Log HEX Error Codes

General Format of the InveStore Event Log Files:

 

The InveStore Event Log files contain a complete description of all system errors that occur. They also contain informational logging of events that provide the users with an audit trail of various actions that have occurred. Informational log messages are not errors and should not be reported to Pegasus.

 

InveStore Event Log files are created and stored in the following sub-directory:

 

\PDT\LOG

 

The file name consists of your storage serverís assigned name by your administrator, followed by the date on which the log file was created. The file extension is ".LOG".

 

Example: [Serverís name]013005.LOG = STORAGESRVR1013005.LOG

 

"StorageSrvr1" being the assigned name of the above example server. The above file name is for the log file that was generated on January 30th, 2005. For each new day that the InveStore Console is initialized, a new log file is created.

 

Note: Successful READ or WRITE operations are not recorded in the log file. Only those errors that indicate a problem are recorded.

 

Some of the standard operations found in the log file include:

      The startup and shutdown of storage library

      Identification of SCSI adapter card

      Identification of storage library

      SCSI ID and firmware revision of storage devices

      Format operations

      Mount operations

      Unmount operations

Each of the entries in the log file has a TIME stamp followed by messages or error codes indicating the nature of the operation or error condition. This allows tracking of problems in a more efficient fashion.

 

The error log files are not normally deleted and may therefore grow quite large. The only time the InveStore kernel will delete log files is if there is not enough free magnetic disk space when InveStore is initialized. Be sure that at least 50M bytes is available on the local magnetic drive at all times.

 

To locate and open an InveStore event log(s), select the Event Log option from the Server view:

 

image\ebx_-1850776017.gif

 

An example of a Hex error in the InveStore log file is as follows:

 

17:04:39 (Error) OSIO Error Code = 197 (0x00c5) LINE: 762, FILE: OSMGR.c

 

The code in parentheses (0x00c5), being the pertinent Hex error in this message.

 

Note: for further information on how to read these event logs, please see the Help File section on Managing the Storage Subsystem.