Chapter 21 DISK Messages

Cause  The disk completed the last command successfully, after performing some recovery action.

Effect  None.

Recovery  The valid additional sense code (ASC) will indicate if there is a predictive failure or if the drive temperature is exceeding the specified limit. Both these ASCs are a part of the TSM event. This is an informational message only; no corrective action is needed.

Cause  The disk is not in a ready state and cannot be accessed now.

Effect  The drive goes hard-down if it is not the last device in the volume configuration.

Recovery  Load the disk.

Cause  A command terminated with a non-recovered error condition because of a flaw in the medium or sector or an error occurred in the recorded data.

Effect  The device may go down, if it is a mirrored configuration.

Recovery  Spare the sector on the defective drive, which returned medium error.

Cause  The disk drive detected an unrecoverable hardware failure.

Effect  Any command to the device fails.

Recovery  Replace the disk.

Cause  A request has been issued for a disk other than the one being used or resulted in a malformed SCSI command to the disk.

Effect  The request fails.

Recovery  Informational message only; no corrective action is needed.

Cause  The disk has been changed or reset. This is a very common error when performing path probing.

Effect  None.

Recovery  Informational message only; no corrective action is needed. If this error is displayed only during a path probing and input/output (I/O) operation is not occurring, ignore it. Check for a valid additional sense code (ASC), which can indicate that the drive has changed in its size.

Cause  Indicates that a command that reads or writes the medium was tried on a block that is protected.

Effect  The read or write operation is not performed.

Recovery  None.

Cause  A SCSI command has timed out and has been aborted. Possible causes are a SCSI bus reset, a device reset, a controller error, or a ServerNet error.

Effect  The command cannot be completed. The path might be brought down on a parity error, if it is not the last path to the device.

Recovery  Informational message only; no corrective action is needed.

Cause  A source data mismatch has occurred during a write verify command. This can happen because of a bad controller hardware, SCSI command queuing, or an initial path switch to the disk.

Effect  If the controller is bad, the path to the disk might be brought down if an alternative path is available.

Recovery  Informational message only; no corrective action is needed. If this event is followed by a disk path down event, perform a recovery for the disk path down event. Check the controller hardware.

Cause  Any request that has a problem that can be recovered by the IO driver.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  A processor switch occurred.

Effect  None.

Recovery  If the processor switch occurred as a result of a command (for example, the Subsystem Control Facility (SCF) PRIMARY DISK command), no corrective action is needed.

If the processor switch occurred because of a hardware problem, contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A device path state has changed.

Effect  None.

Recovery  Most of the time an informational message only; no corrective action is needed. If the path state has changed to HARDDOWN for various reasons, the operator involvement is required.

Cause  A disk drive reported an internally or externally initiated path switch.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The maximum number of interrupt timeouts for the I/O process (IOP) has been exceeded.

Effect  The current disk path might go down if an alternate path is available.

Recovery  Informational message only; no corrective action is needed. If this event is followed by a disk path down event, the I/O process (IOP) might have already brought up an alternative path, but perform a recovery for the disk path down event.

Cause  An error was injected by an external program.

Effect  The Module Driver has injected an error to comply with the request.

Recovery  Informational message only; no corrective action is needed.

Cause  A power on (PON) interrupt (indicating a power failure) occurred. The state of the hardware can be changed by a power failure and a subsequent power on.

Effect  Microcode is reloaded for all downloadable ServerNet addressable primary controllers in the processor where the power failed.

Recovery  Informational message only; no corrective action is needed.

Cause  An execute I/O (EIO) was issued, but no interrupt was received for the EIO; a timeout on the EIO did not occur. The interrupt from the controller never occurred, or the interrogate I/O (IIO) processing the interrupt failed. A problem exists with the channel or the controller.

Effect  The disk operation aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An unexpected interrupt for a device occurred. The ServerNet addressable controller should not be randomly interrupting.

Effect  A problem might exist with the controller because it should not be randomly interrupting.

Recovery  If this error occurs repeatedly, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  This event was caused by a checksum error on a sector during a read operation.

Effect  The data might be corrupted. However, if the data was recovered by reading the mirror drive, $ZLOG will have the 'block rewritten' event (449).

Recovery  Run FCHECK against the file. If no errors are found, contact your service provider, as directed by your local operating procedures. If errors are found, recover the data by whatever means available and contact your service provider.

For G-series RVUs and above, use the CONTROL DISK command. For more information about the Storage Subsystem and SCF commands, see the SCF Reference Manual.

Cause  The driver timed out selecting the device. There is an issue with the disk drive.

Effect  The device specific path is placed into down state.

Recovery  Check the disk drive. Try the SCF command to start the drive. If the error continues to occur, contact your service provider and provide all relevant information:

Cause  The device could not complete the command within the time frame. There could be some issues with the disk drive.

Effect  The input/output (I/O) command fails. The I/O driver will retry the command before putting the specific path to down state.

Recovery  Reset the disk drive. If the error continues to occur, contact your service provider and provide all relevant information:

Cause  An incomplete command was received by a disk drive.

Effect  The input/output (I/O) command fails.

Recovery  Reset the disk drive. If the error continues to occur, contact your service provider and provide all relevant information:

Cause  A command was not completed by the disk drive.

Effect  The input/output (I/O) command fails.

Recovery  Reset the disk drive and reissue the command. If the error continues to occur, contact your service provider and provide all relevant information:

Cause  Unexpected SCSI status was received. When present, the event detail will help to identify the specific problem.

Effect  The command does not complete.

Recovery  Informational message only; no corrective action is needed. The device I/O process (IOP) retries the command.

Cause  A controller or a SCSI bus error occurred when a command was sent from the controller to the disk drive.

Effect  The input/output (I/O) command fails.

Recovery  If the error continues to occur, contact your service provider and provide all relevant information:

Cause  The disk drive was reset by a controller because a command from the controller to the disk drive aborted.

Effect  The input/output (I/O) command fails.

Recovery  The reset causes the command to be retried. If the error continues to occur, contact your service provider and provide all relevant information:

Cause  The maximum number of errors to the disk path has been exceeded.

Effect  The current disk path goes down if an alternate path is available.

Recovery  Informational message only; no corrective action is needed. If the path probe is enabled, the path will be brought back to up state within the path probe interval.

Cause  Some error has already occurred and most likely this indicates that a write of disk drive's internal cache did not succeed.

Effect  Read and write errors may continue to occur or the disk is unusable.

Recovery  Contact your service provider and provide all relevant information as follows:

Cause  For CLIM devices, incorrect cabling or incorrect LUN manager configuration could cause the issue. For all other devices, incorrect cabling could cause the issue.

Effect  Disk operations will cause data corruption.

Recovery  For CLIM devices, check the LUN manager configuration, the SCF LDEV configuration and verify correct cabling for both paths to the physical disk. For all other devices, verify the cabling and check the SCF LDEV configuration for both paths to the physical disk.

Cause  The error threshold for the specified path has been exceeded.

Effect  The disk path might go down.

Recovery  Informational message only; no corrective action is needed. If this event is followed by a disk path down event, perform a recovery for the disk path down event.

Cause  An error was detected on a disk sector but was successfully reallocated by the auto-reallocate process.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The average I/O response time for the specified path has exceeded a threshold. This problem might be temporary and due to internal recovery on ESS volumes.

Effect  Disk applications might have I/O response times that are longer than usual.

Recovery  Informational message only; no corrective action is needed.

Cause  A media error occurred on this sector of the device.

Effect  The sector on which the error occurred is spared.

Recovery  If auto-reallocation is disabled, this sector must be manually reallocated using the SCF SPARE command.

Cause  A media error occurred on this sector of the device.

Effect  The sector is deleted, which was added to STT when media error occurred on it.

Recovery  This is an informational message only; no corrective action is needed.

Cause  A checksum error was detected on the disk drive of a mirrored volume, but was successfully read from the other disk drive. The DP2 driver has rewritten the good block back out to the disk drive that returned the checksum error.

Effect  None. The problem has been corrected.

Recovery  Informational message only; no corrective action is needed.

Cause  After writing a block to the disk, the DP2 driver found that the data did not compare.

Effect  There is a serious problem with the I/O subsystem.

Recovery  The DP2 driver takes the necessary steps to recover the I/O subsystem. However, you should contact your service provider immediately to investigate the source of this error.

Cause  An I/O attempt failed because of a path or media error. This message describes the action DP2 has taken in response to the failure; it is usually preceded by other messages.

Effect  The disk process makes an entry in the spare tracks table (STT), brings down a path, or tries to switch processors as indicated by the ACTION/DOWN field.

	NOTE: An operation can be successful even if a path is down. For example, a read from a mirrored volume is successful even though it fails on one half of the mirror.

Recovery  Informational message only; no corrective action is needed.

Cause  The internal file format is inconsistent.

Effect  The file is marked as bad.

Recovery  For G-series RVUs, report this message to your service provider and provide all relevant information.

For D-series RVUs, use the Peripheral Utility Program (PUP) LSATOFILE command to convert %aaaaaa,bbbbbb to the file name and offset within the file. The Peripheral Utility Program (PUP) Reference Manual describes the LSATOFILE command and lists supported controllers.

Report this message and the information returned by the PUP command to your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The disk free space (DFS) table of the specified volume contained bad data.

Effect  No more free space can be allocated.

Recovery  Use the PUP REBUILDDFS command (D-series) or the SCF REBUILDDFS (G-series) to rebuild the free-space table. See the Peripheral Utility Program (PUP) Reference Manual for information about PUP commands and the SCF Reference Manual for the Storage Subsystem for information about SCF commands.

If error = 43, the disk is too full or too fragmented to hold the free space table. In this case, purge some files or move them to another volume before running REBUILDDFS. If this error persists, purge or move more files and run REBUILDDFS again.

Cause  The volume labels of a mirrored volume do not match.

Effect  If this situation occurs on a cold load, the processor halts with halt code %2002. If this situation occurs at any other time, the volume goes down.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  DP2 detected an invalid undo area format. (The undo area is normally used for key-sequenced file recovery either during processor failures or when a disk is brought up.)

Effect  The disk goes down or stays down.

Recovery  Issue either the Subsystem Control Facility (SCF) ALTER DISK, LABEL command (for G-series RVUs) or the Peripheral Utility Program (PUP) LABEL command (for D-series RVUs). If the disk remains down, contact your service provider and provide all relevant information:

If your local operating procedures require contacting your service provider, supply your system number and the numbers and versions of all related products as well.

Cause  The volume label contained bad data. This message can occur when the system is initialized, when the Peripheral Utility Program (PUP) UP command is issued (for D‑series RVUs), or when processors are switched.

Effect  The device is not brought up.

Recovery  If the data on the volume is no longer needed, relabel the volume. Otherwise, contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The disk could not come up because it could not use either of the disk names in the volume label.

Effect  The disk stays down.

Recovery  Perform a Subsystem Control Facility (SCF) RENAME DISK command (for G-series RVUs) or a Peripheral Utility Program (PUP) RENAME command (for D-Series RVUs) on the disk.

Cause  The value of error indicates the cause of the message as follows:

Effect  The disk process reporting the problem goes down for all audited activity. Nonaudited activity is not affected. Related messages might be displayed.

Recovery  Correct the reported problem and enable the volume. Use the TMFCOM ENABLE VOLUMES command to enable the volume. If the problem continues, contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The backup disk process detected a discontinuity in the checkpoints it received from the primary disk process about a block in the file.

Effect  Data might be lost.

Recovery  Inspect the file for possible data loss and inspect the operator log for possible problems with the disk.

Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The specified path has been placed in a down state. The disk process issues this message for each path as the path goes down. When the last path goes down, the disk process displays this message without the path, SAC, ID, and LUN specifications.

Effect  The device goes down.

Recovery  Use the Subsystem Control Facility (SCF) START DISK command to bring up the device. If a SCF STOP DISK command did not cause this message, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  This error is usually caused by a drive hardware problem. The read interrupt cause (RIC) word for an outstanding command indicated either that the drive is not ready, a drive selection error occurred, or the drive is not responding. This message is returned only for extended command controllers.

Effect  Retries on this path have failed. Other paths are tried if they are available. If no other paths are available, the drive goes down.

Recovery  Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The read interrupt cause (RIC) word for an outstanding command indicates either that the device is not ready, a drive selection error occurred, or the drive is not responding. This message is returned only for extended command controllers.

Effect  Retries on this path have failed. Other paths are tried if they are available. The drive goes down if no other paths are available.

Recovery  This error is usually caused by a drive hardware problem.

Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The specified path has been placed in an up state. The disk process issues this message for each path as the path comes up. When the volume comes up, the disk process displays this message without the path, SAC, ID, and LUN specifications.

Effect  The operation is completed.

Recovery  Informational message only; no corrective action is needed.

Cause  The read interrupt cause (RIC) word for an outstanding command indicates an exception error. This message is returned only for extended command controllers.

Effect  Retries on this path have failed. Other paths are tried if they are available. The drive goes down if no other paths are available and the error is not a media failure.

If a media failure is detected and the volume is mirrored, the affected drive goes down. If a media failure is detected and the volume is not mirrored, the drive does not go down.

Recovery  This error is usually caused by a hardware problem (drive, controller, or channel).

Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The read interrupt cause (RIC) word for an outstanding command indicates an exception error. This error occurs only on extended command controllers.

Effect  Retries on this path have failed. Other paths are tried if they are available. The drive goes down if no other paths are available and the error is not a media failure.

If a media failure is detected and the volume is mirrored, the affected drive goes down. If a media failure is detected and the volume is not mirrored, the drive does not go down.

Recovery  This error is usually caused by a hardware problem (drive, controller, or channel).

Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The volume label maintained in DP2 memory does not match the volume label read from disk.

Effect  The device goes down.

Recovery  Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal error in the DP2 code was detected at location aaaaaaaa.

Effect  The processor freezes with a %11500 halt.

Recovery  Take a dump of the frozen processor, retain this message, contact your service provider, and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  There is not enough physical memory to support all the activity (primarily disk-process activity) in the processor.

Effect  If memory problems prevent the disk process from performing the requested operation, the DP2 process reporting the problem rejects requests and reports file‑system error 36. All other DP2 disk processes in the processor probably report the same error.

Recovery  Free some memory in the problem processor by doing one or more of the following:

Cause  Not enough memory was available for DP2 to both allocate space for tables and come up.

This message can appear during a cold load or reload if the disk process cannot configure the cache defined by the volume label and has to fall back to the default cache configuration.

Effect  The disk stays down.

Recovery  Make more memory available, or change your SYSGEN configuration to have fewer disk processes for each processor or less cache for each disk process group.

Cause  An attempt to issue a command was rejected too many times with “report of pending status.” This error occurs only on extended command controllers.

Effect  Retries on this path have failed. Other paths are tried if they are available. The drive goes down if no other paths are available.

Recovery  This error is usually a hardware problem (drive, controller, or channel).

Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An I/O error occurred during an attempt to revive a disk, probably due to a hardware error.

Effect  The disk being revived goes down.

Recovery  Contact your service provider to get the hardware error fixed. When contacting your service provider, provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Then reissue the revive request.

Cause  This event was caused by a checksum error.

Effect  Data is corrupted.

Recovery  For D-Series RVUs, use the PUP SPARE command. See the Peripheral Utility Program (PUP) Reference Manual for information about this and other PUP commands. For G-series RVUs, use the CONTROL DISK command. See the SCF Reference Manual for the Storage Subsystem for more information about this and other SCF commands.

Cause  Likely causes are sector checksum errors or uncorrectable ECC errors (on reads issued to the source UP disk drive).

Effect  The revive will loop while waiting for the operator to resolve the problem.

Recovery  Determine what caused the revive error. Once the error is resolved, the revive resumes.

Cause  The system cannot read the specified disk’s directory label.

Effect  The disk stays down. File-system error errnum occurs.

Recovery  For a description of the error, refer to Appendix B. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual. You might have to reformat the disk.

Cause  The volume label could not be written.

Effect  The disk stays down. File-system error errnum occurs.

Recovery  For a description of the error, refer to Appendix B. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual. You might have to reformat the disk.

Cause  An unexpected interrupt occurred. This error occurs only on extended command controllers.

Interrupts on an inactive path are saved until the next time an I/O operation occurs on the path. Therefore, this message might appear hours or days after the error that caused it.

Effect  The driver recovers.

Recovery  If this message occurs frequently, contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An audit-trail volume encountered a write error on file filename.

Effect  The audit trail rejects all audit requests. All audit-trail volumes that audit to the audit trail go down, and the HP NonStop Transaction Management Facility (TMF) halts.

Recovery  Cold load TMF. For a description of the error refer to Appendix B. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  This message provides information about a previously reported problem.

Effect  None.

Recovery  Analyze the preceding operator messages to find out what went wrong. Recovery depends on the problem. The system might automatically retry.

Cause  While trying to clean up its free-space table and volume label, the disk process encountered an inconsistency or file-system error (error).

Effect  The volume goes down.

Recovery  Refer to for a description of the error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual. Analyze preceding operator messages, if any, and correct the error, or contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting your service provider, supply your system number and the numbers and versions of all related products as well.

Cause  A structured file was opened for unstructured access.

Effect  None. The file is opened for unstructured access.

Recovery  In most cases this is an informational message only; no corrective action is needed. If the program that opened the file is not an HP utility and you have been encountering broken files, ensure that the program is a trusted program that does not alter the structure of the files it opens.

Cause  The DP2 driver detected an inconsistency in its communication with an extended command controller (the 3120, 3681, or 3125).

Effect  The effect of this event depends on the error, but the error usually indicates a problem severe enough to bring down the volume on which the error occurred.

Recovery  Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An EIO ownership error has been reported, and the retry has failed.

Effect  The operation is not performed.

Recovery  See the Guardian Procedure Errors and Messages Manual for corrective action for the file-system error returned in the event-message text.

cpu	indicates the processor.
chan	is the channel.
%ctlr	indicates the controller.
%unit	indicates the unit of the drive. NOTE: For an F‑SAC on a ServerNet/DA, the information I/O ADDR (cpu, chan, %ctlr, %unit) information is not reported. Use the OSM or TSM event viewer or EMDIST to view the details of the DISK event and identify the controller location (group, module, and slot).
param1 param2	are parameters passed by the drive cabinet. They are hexadecimal numbers with a bit set to 1 for any error detected in the cabinet. The decoding of the bits depends on the controller reporting the error, as explained in: Figure 21-1 Figure 21-2 Figure 21-1 param1 Values for 3128 Controllers for DISK Message 5047 A ID of LE‑MUX reporting environment status B Slot 5 power sensed bad C Slot 4 power sensed bad D Slot 3 power sensed bad E Slot 2 power sensed bad F Slot 1 power sensed bad G Slot 0 power sensed bad X Reserved and set to zero Figure 21-2 param2 Values for 3128 Controllers for DISK Message 5047 A Module power 1 sensed bad   B Module power 2 sensed bad   C Fan 1 sensed bad   D Fan 2 sensed bad   T Temperature code:     Value Temperature Range   %H00 10.0 C or lower   %H01 10.1 - 15.9 C   %H03 16.0 - 26.9 C   %H07 27.0 - 30.9 C   %H0F 31.0 - 32.9 C   %H1F 33.0 - 38.9 C   %H3F 39 C or above   %H7F Undefined   %HFF Undefined X Reserved and set to zero   Figure 21-3 and explain the param1 and param2 values for 3129 controllers and F‑SACs on ServerNet/DAs. Figure 21-3 param1 Values for 3129 Controllers and ServerNet/DA F‑SACs for DISK Message 5047 Bit Meaning Bit=0 Bit=1 A BEB number reporting this status BEB 0 BEB 1 B Subsystem temperature In range Overtemperature C Module fan assembly sense Fans OK Fan failure detected D Module power supply 1 status Supply OK Not present or has failed E Module power supply 0 status Supply OK Not present or has failed F Drive CRU 7 power status Power OK Power sensed bad G Drive CRU 6 power status Power OK Power sensed bad H Drive CRU 5 power status Power OK Power sensed bad I Drive CRU 4 power status Power OK Power sensed bad J Drive CRU 3 power status Power OK Power sensed bad K Drive CRU 2 power status Power OK Power sensed bad L Drive CRU 1 power status Power OK Power sensed bad M Drive CRU 0 power status Power OK Power sensed bad X Reserved and set to zero     Figure 21-4 param2 Values for 3129 Controllers and ServerNet/DA F‑SACs for DISK Message 5047 Bit Meaning Bit=0 Bit=1 A SCSI bus 3 termination power status OK Term power failure B SCSI bus 2 termination power status OK Term power failure C SCSI bus 1 termination power status OK Term power failure D SCSI bus 0 termination power status OK Term power failure E Module connector 1 presence Connector present No connector F Module connector 1 ID     G Module connector 0 presence Connector present No connector H Module connector 0 ID     X Reserved and set to zero     Figure 21-5 explains the param1 and param2 values for 3120 and 3125 controllers: Figure 21-5 param1 and param2 Values for 3120 and 3125 Controllers for DISK Message 5047 A Parity error on Environmental Monitor Bus (EMB) B Disk power supply failed C Radial interface board (RIB) failed D Cooling fan failure E Temperature out of range X Reserved and set to zero

Cause  This message is an environmental monitoring report. When an error condition such as a power supply failure occurs in a disk subsystem cabinet, the system is notified of the condition the next time an I/O operation is attempted to that cabinet.

Effect  A problem has been detected. The effect varies according to the cause of the message.

Recovery  For G‑series RVUs: Decode the param1 and param2 values from the DISK event, or consult the details of the SCSI Module Driver (SMD) event in the service log to identify the faulty component.

For D‑series RVUs: More detailed information about the failure is displayed in the HP Tandem Maintenance and Diagnostic System (TMDS) log. Note the time of this message and check the TMDS log for the REPORT‑OF‑PENDING‑STATUS message for the logical device that reported this problem. For detailed information on TMDS commands, see the TMDS Reference Manual.

Follow these steps to check the TMDS log:

Based on the detailed event text, take corrective action or contact your service provider. If you contact your service provider, provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The disk process detected an inconsistency in an SQL label whose external name is name and whose rcode is rcode. Several labels are associated with a single SQL table, and all of them have the same external name but are distinguishable by their code. location uniquely determines where in the disk process the inconsistency was detected.

Effect  The operation is not performed.

Recovery  Contact your service provider and provide the following relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products.

Cause  The disk driver turned on the persistent write verify mode after detecting an error during the execution of a write verify command. This implies that every subsequent write command will be verified. This might affect performance. On D‑series systems, this message can also be displayed as a result of the user forcing this mode through a HP Tandem Maintenance and Diagnostic System (TMDS) command.

Effect  Write commands are now verified for all paths belonging to the controller for which the event was reported. Performance is affected.

Recovery  If the change initiator is the disk process, data integrity is suspect. Contact your Global Mission Critical Solution Center (GMCSC) and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The user has forced off the persistent write verify mode through a HP Tandem Maintenance and Diagnostic System (TMDS) command.

Effect  Normal operation is resumed. Only the write operations that require it are verified.

Recovery  Informational message only; no corrective action is needed.

Cause  The disk process brought down the volume, probably because of a path loss. The problem that resulted in the downed volume is described in preceding operator messages generated by the disk driver.

Effect  The volume stays down until the problem is corrected and the volume is brought up.

Recovery  Correct the problem described in the preceding DISK operator messages, then revive the volume, using a Subsystem Control Facility (SCF) START DISK command (on G-series RVUs) or a PUP REVIVE command (on D-Series RVUs).

Cause  The disk process detected an inconsistency in the internal file format. Possible causes include:

Effect  Attempts to access the file might result in error 59.

Recovery  If the file is protected by TMF rollforward recovery, and the first cause was not the problem, use TMF RECOVER FILES to recover the file. If the first cause was the problem, issue TMF RECOVER FILES with a timestamp less than or equal to the initial recovery. If TMF recovery is not available, run FILCHECK for the file or table to determine whether the file or table is broken.

If FILCHECK does not report the file or table as broken, contact your service provider and provide all relevant information.

If FILCHECK does report the file or table as broken, and if recovery of the data is essential, contact your service provider for assistance.

Cause  The backup disk process detected a discontinuity in the checkpoint it received from the primary disk process regarding a block in a particular file.

Effect  The file or table might contain stale or missing data.

Recovery  Inspect the file for data loss and inspect the Event Management Systems (EMS) event log for disk problems. Note this information, contact your service provider, and provide the following relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), provide your system number and the numbers and versions of all related products.

Cause  The disk driver encountered errors when attempting to write to a file. The disk driver errors were reported in previous operator messages.

Effect  If the system did not automatically retry the operation that resulted in the error, the file could be left structurally inconsistent.

Recovery  The recovery depends on the problem. Analyze the preceding DISK operator messages to determine what went wrong. The system might automatically retry the operation. If the problem is not resolved, contact your service provider.

Check for additional DISK event messages. These messages might indicate that the volume went down or that it went down for Transaction Management Facility (TMF).

Cause  A FUP ALTER [NO] AUDIT command was executed for the file, or an SQL ALTER TABLE PARTONLY [NO] AUDIT command was executed for the table, altering it from an audited file or table to a nonaudited one, or vice-versa.

Effect  The file or table is altered.

Recovery  This is an informational message only; no corrective action is needed.

Cause  The disk process detected a timestamp mismatch between a drive and its mirror.

Effect  The mirror drive with the other timestamp is left down.

Recovery  Revive the drive reported by this message, using the Subsystem Control Facility (SCF) START DISK command (on G-series RVUs) or a PUP REVIVE command (on D-Series RVUs).

Cause  The disk process made two attempts to initialize a volume’s cache during volume startup. The first attempt used the cache sizes requested in the most recent PUP SETCACHE command (on D-Series RVUs) or SCF ALTER DISK command (on G‑series systems). The second attempt used the default cache sizes. Both attempts failed for the reason given in the event message.

Effect  The volume remains in a down state.

Recovery  Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An attempt by the disk process to initialize the volume’s cache using the cache sizes requested in the most recent SCF ALTER DISK, CACHE command (for G-series RVUs) or the PUP SETCACHE command (for D‑series systems) failed. The disk process therefore configured the volume’s cache using the default cache sizes.

Effect  The volume remains in an up state, with default cache sizes.

Recovery  The disk process continues to run with the default cache sizes, which are very small and might therefore yield poor performance. To prevent this event from being generated, use the PUP SETCACHE command (on D-Series RVUs) or the SCF ALTER DISK command (on G-series RVUs) to request cache sizes that are smaller than those requested previously but not as small as the default cache sizes. However, reducing the cache sizes might impact the performance of the application. See the Peripheral Utility Program (PUP) Reference Manual for information on PUP commands. See the SCF Reference Manual for the Storage Subsystem for information on SCF commands. For further assistance, contact your service provider.

Cause  Two files or a file and free space have been allocated to the same extent on a disk volume.

Effect  The files that have double allocated extents will be corrupted if written.

Recovery  Try the following recovery action and contact your service provider.

Cause  The disk drive subtype is not supported.

Effect  The disk drive is not brought online.

Recovery  Replace the disk drive and report the problem to your service provider.

Cause  An unexpected message error was encountered by the disk process on the reply to a nonwaited message.

Effect  The disk process goes down for TMF. Eventually, other volumes participating in the TMF configuration might also go down for TMF.

Recovery  If only TMF data volumes have gone down for TMF, use the TMFCOM ENABLE DATAVOL[S] command to reenable those data volumes. If an audit-disk process has also gone down for TMF, restart TMF using the TMFCOM START TMF command.

Cause  A TMF data volume needed to query the TMF Library for the name of the audit disk process to which that data volume should send its audit because either:

Effect  The data volume begins sending its audit to the audit-disk process named by the TMF library if the audit-disk process named by the TMF library is a different volume from the one to which the data volume is presently sending its audit.

Recovery  Informational message only; no corrective action is needed.

Cause  A label of unknown type was discovered in the volume’s directory.

Effect  A label of unknown type might be a legitimate label that was somehow corrupted.

Recovery  Contact your service provider and provide the following relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products.

Cause  A request was received for a DP2 volume. The request can be from a PUP REFRESH command, from a call to the REFRESH subsystem procedure, or from an SCF CONTROL DISK command.

Effect  Service for other requests will be delayed.

Recovery  On D-Series RVUs, identify the PUP command or application REFRESH procedure call, and remove it. Reducing the size of cache will prevent any performance loss. On G-series RVUs, use the SCF CONTROL DISK command and specify the CACHE parameter.

Cause  DP2 failed to obtain space for control blocks.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  The generation of this event typically coincides with space allocation errors being returned to the application. There are two possible methods to prevent these errors:

If you are not certain about the problem, contact your service provider, and supply your system number and the numbers and versions of all related products as well.

Cause  This is an informational message detected under one of these following conditions:

Effect  If the message is detected due to control block failure, requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  If the message occurred due to control block failure, see event message 5067 for recovery actions.

Cause  This is an informational message detected under one of these following conditions:

Effect  If the message is detected due to control block failure, requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  If the message occurred due to control block failure, see event message 5067 for recovery actions.

Cause  This is an informational message detected under one of these following conditions:

Effect  If the message is detected due to control block failure, requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  If the message occurred due to control block failure, see event message 5067 for recovery actions.

Cause  DP2 failed to obtain space for control blocks.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  The generation of this event typically coincides with space allocation errors being returned to the application. There are two possible methods to prevent these errors:

Cause  This message is preceded by message 5071, which indicates that DP2 failed to obtain additional space for its lock tables. This message provides information on the amount of space currently in use by the combined lock tables.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  The generation of this event typically coincides with space allocation errors being returned to the application. There are two possible methods to prevent these errors:

Cause  This message is preceded by message 5071, which indicates that DP2 failed to obtain additional space for its lock tables, and by message 5072, which provides information on the amount of space currently in use by the combined lock tables. This message provides information on the amount of space currently in use by the LAB lock table.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  The generation of this event typically coincides with space allocation errors being returned to the application. There are two possible methods to prevent these errors:

Cause  This message is preceded by message 5071, which indicates that DP2 failed to obtain space for control blocks. This message provides information on the use of active lock name space.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  The generation of this event typically coincides with space allocation errors being returned to the application. There are two possible methods to prevent these errors:

Cause  DP2 failed to obtain space for control blocks.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  The generation of this event typically coincides with space allocation errors being returned to the application. Recovery might require a reduction in cache sizes.

Cause  DP2 failed to obtain space for control blocks.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  The generation of this event typically coincides with space allocation errors being returned to the application. Recovery might require a reduction in cache sizes.

Cause  A user requested the amount of memory space used by DP2.

Effect  None.

Recovery  This is an informational message only; no corrective action is needed.

Cause  DP2 failed to obtain virtual memory during UP processing.

Effect  The volume remains in a down state.

Recovery  Reduce the virtual memory used by other DP2 volumes or other processes within the same DP2 processor.

Cause  DP2 failed to obtain space from the workpool.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  Contact your service provider and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  DP2 failed to obtain space from the workpool.

Effect  Requests to open or access files on the DP2 volume might incur allocation errors (33 or 35).

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  DP2 volume initialization failed.

Effect  The DP2 volume is not accessible.

Recovery  Cold load or reload the primary and backup DP2 volume processors. If COUP support of DP2 is available, the volume can be stopped and restarted.

Cause  DP2 volume backup processor initialization failed.

Effect  The DP2 volume is not accessible if the primary processor fails.

Recovery  Reload the backup DP2 volume processor. For D-Series RVUs, if COUP support of DP2 is available, the volume can be stopped and restarted.

If this message occurs after a cold load or reload, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  DP2 failed in an attempt to process-create a tailpin within the same processor.

Effect  The number of processes specified in the NUMDISCPROCESSES SYSGEN modifier will not be available for servicing requests.

Recovery  If this event is reported during cold load or reload, the primary and backup DP2 processors should be halted, dumped, and reloaded. For D-Series RVUs, if COUP support of DP2 is available, the volume can be stopped and restarted.

If this message occurs after a cold load or reload, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  DP2 failed in an attempt to process create the brother processor headpin.

Effect  The brother processor headpin may not start, and it will not be able to provide service should the reporting DP2 processor fail.

Recovery  If this event is reported during cold load or reload, the brother DP2 processor should be halted, dumped, and reloaded. For D-Series RVUs, if COUP support of DP2 is available, the volume can be stopped and restarted.

If this message occurs after a cold load or reload, contact the HP Global Customer Service Center to file a Genesis case against the operating system and provide all relevant information as follows:

If your local operating procedures require contacting your service provider, supply your system number and the numbers and versions of all related products as well.

Cause  DP2 failed to obtain virtual memory during initialization.

Effect  The DP2 volume is not accessible.

Recovery  Cold load or reload the primary and backup DP2 volume processors. For D‑series systems, if COUP support of DP2 is available, the volume can be stopped and restarted.

If this message occurs after a cold load or reload, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  DP2 failed to obtain virtual memory during initialization.

Effect  The DP2 volume is not accessible.

Recovery  Cold load or reload the primary and backup DP2 volume processors. For D‑series systems, if COUP support of DP2 is available, the volume can be stopped and restarted.

If this message occurs after a cold load or reload, contact your service provider to file a Genesis case against the operating system and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  DP2 detected an internal inconsistency and initiated a processor softdown state. This message is generated when DP2 halts (halt code %11500) are disabled. Rather than halt, DP2 enters into a softdown state for the given DP2 processor, and the other DP2 processor continues to provide service for the volume.

Effect  The volume is no longer fault-tolerant. If both DP2 processors enter the softdown state or if one DP2 processor is in softdown state and the other processor is down, the volume is considered down.

Recovery  Perform a RECEIVEDUMP command using the ONLINE dump option for the affected DP2 processor. Once the data is collected, use a Peripheral Utility Program (PUP) UP command (for D-series systems) or the System Control Facility (SCF) (for G-series systems) of the affected processor. Even if one of the DP2 processors is up and the other is softdown, a PUP UP command (for D-series systems) or SCF (for G-series systems) will restore the DP2 processor in a softdown state. On D-series systems, a PUP PRIMARY command might also be required to restore the correct primary processor.

Cause  A softdown DP2 processor was reset by a PUP UP (on D-Series RVUs) command or an SCF START command (on G-series RVUs).

Effect  The DP2 processor is fully restored to service.

Recovery  This is an informative message only; no corrective action is needed.

Cause  A softdown DP2 processor was reset by a PUP UP command (D-series) or an SCF START command (G‑series).

Effect  Fault-tolerant protection is restored.

Recovery  This is an informational message only; no corrective action is needed.

Cause  A softdown DP2 processor was reset due to a DP2-driver requested processor switch.

Effect  Fault-tolerant protection is restored.

Recovery  This is an informational message only; no corrective action is needed.

Cause  A DP2 processor has entered a softdown state. This event is generated every five minutes as a reminder to the operator to initiate a DP2 processor softdown recovery.

Effect  The affected DP2 processor remains in a softdown state.

Recovery  Initiate a RECEIVEDUMP command with the ONLINE option for the affected DP2 processor, if possible. After the online dump is complete, use the Peripheral Utility Program (PUP) UP command (for D-Series RVUs) or a System Control Facility (SCF) command (for G-series RVUs) to bring up the affected DP2 processor, which resets the state of the processor.

Cause  DP2 volume initialization failed to obtain virtual memory space due to software incompatibility.

Effect  The DP2 volume is not accessible.

Recovery  Contact your service provider to file a Genesis case against the operating system and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The space available on a disk has crossed a user-specified threshold or interval for the amount of remaining space.

Effect  None.

Recovery  This is an informational message only; no corrective action is needed.

Cause  The space available on a disk has crossed a user-specified threshold or interval for the amount of remaining space.

Effect  None.

Recovery  This is an informative message only; no corrective action is needed.

Cause  DP2 incurred a timeout while attempting to checkpoint to the backup DP2 processor.

Effect  DP2 continues to retry the checkpoint. If this event continues, the backup DP2 processor may be hung.

Recovery  If this event continues, halt, dump, and reload the backup DP2 processor.

Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal error occurred.

Effect  DP2 continues to retry the operation. If this event continues, the DP2 processor may be hung.

Recovery  If this event continues, halt, dump, and reload the DP2 processor.

Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The syndrome indicates a SCSI exception error.

Effect  DP2 continues to retry the operation on this path and then on other paths if they are available. The drive goes down if no other paths are available.

Recovery  If the drive goes down, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An online disk upgrade was initiated by a user.

Effect  An online disk upgrade allows data to be revived from a low-capacity disk to a high-capacity disk, which enables customers to migrate to a higher-capacity disks without an interruption in data availability. At the end of the online disk upgrade, the source device is brought down because the source and the target devices no longer have the same capacity.

Recovery  An online disk upgrade is not reversible (not possible to revive from a higher-capacity disk to a lower-capacity disk).

Cause  The disk drive returned an unknown or an unexpected subtype value.

Effect  The attempted operation was not performed, and the target disk drive was brought down.

Recovery  If this event occurs during an online disk upgrade, check that the target disk drive has at least the same capacity as the source disk drive, and retry the operation.

Cause  An attempt to revive a disk failed, because the processor where the primary volume resides does not own the destination path to the disk that was being revived.

Effect  The revive is aborted.

Recovery  Check that the current LDEV is made primary to the suggested processor, and try the revive again.

Cause  Some devices support the self-monitoring, analysis and reporting technology (SMART) feature for monitoring and storing critical performance and calibration information. A device that has the SMART feature enabled attempted to report a performance degradation or a device failure before the problem occurred, and it sent a recovery action against data loss.

Effect  Performance degradation or a device failure might occur if the suggested recovery action is not performed.

Recovery  You might want to replace the device, which reduces the likelihood of a driver failure and loss of data.

Cause  A device that has a self-monitoring analysis ad reporting technology (SMART) feature enabled, monitors and stores critical performance and calibration information. A device that has the SMART feature enabled attempted to report a performance degradation or a device failure before the problem occurred, and it sent a recovery action against data loss. This event occurs when testing and debugging programs.

Effect  Performance degradation or a device failure might occur if the suggested recovery action is not performed.

Recovery  You might want to replace the device, which reduces the likelihood of a driver failure and loss of data. This event is intended for HP internal use only for testing and debugging purposes.

Cause  A user has attempted to increase memory (in 128-kilobyte units) to be allocated for lock-key space. This operation is not allowed online.

Effect  The operation is unsucessful. Lock key space is not changed.