HP Guardian Errors Manual page 50

Procedure errors and messages manual
Table of Contents

Advertisement

The interprocessor bus monitor process ($IPB or for TorusNet configurations, $IPBn, where n
is a number in the range of 1 through 4) reported that the FOX link or TorusNet vertical link
to an Expand process is down
A subunit or logical unit is not in the started condition
Refer to the appropriate subsystem manual for additional information.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is device dependent. If the problem is not apparent, submit the trace,
log file, CONFLIST, subunit, and line configuration to your service provider.
148
Cause There was an attempt to write to an optical disk where data was already written, or there
was an attempt to read data from a location on an optical disk where there was no data.
Effect The procedure sets the error code and returns.
Recovery Recovery is application dependent.
150
Cause The tape unit encountered the end-of-tape marker in the forward direction during this
operation, or it passed the marker on a previous operation and has not yet passed it in reverse.
Effect The last operation is completed normally, but very little tape is left.
Recovery Informative message only; no corrective action is needed. If this error occurs at the
beginning of several tapes, contact your service provider regarding a possible hardware problem.
151
Cause The tape drive detected a runaway tape. This error usually occurs when the system tries to
read a blank tape or a tape written at a density lower than the tape drive can read.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Check the tape and replace it if it is faulty. If a read fails, change the density switch
setting or mount the tape on a tape drive that can read the tape at the density at which it was
written. If this error occurs at the beginning of several tapes, contact your s regarding a possible
hardware problem.
152
Cause The device controller returned an "unusual end" status. If the device is a tape unit, the tape
drive was taken offline manually during this operation.
Effect Part of the requested operation might be complete.
50
File-System Errors
(%224)
Attempt to read unwritten data or
to over-write existing data on an
optical disk. (device type: 3.56)
(%226)
End-of-tape marker detected.
(device type: 4)
(%227)
Runaway tape detected, or attempt to
access a tape whose density is lower than
the switch setting on the tape drive.
(device type: 4)
(%230)
Unusual end (device type: 4 or 11)--tape
unit went offline or CP6100 file closed
while requests still in progress
(device type: 11).

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Guardian

Table of Contents