Drive Monitoring Features Are Unobtainable - HP ProLiant series Troubleshooting Manual

Drive Monitoring Features Are Unobtainable

Description: ADU
data due to a fatal command problem (such as drive time-out), or is unable to get data due to these
features not being supported on the controller.
Action: Check for other errors such as time-outs. If no other errors occur, upgrade the firmware to a
version that supports monitor and performance, if desired.
Drive Monitoring is NOT Enabled for SCSI Port X Drive ID Y
Description: The monitor and performance features have not been enabled on this drive.
Action: Run the server setup utility to initialize the monitor and performance features.
Drive Time-Out Occurred on Physical Drive Bay X
Description: ADU issued a command to a physical drive and the command was never acknowledged.
Action: The drive or cable may be bad. Check the other error messages on the Diagnostics screen to
determine resolution.
Drive X Indicates Position Y
Description: Message indicates a designated physical drive, which seems to be scrambled or in a drive
bay other than the one for which it was originally configured.
Action:
Examine the graphical drive representation on ADU
1.
determine proper drive locations.
Power down the server.
2.
Remove drive X and place it in drive position Y.
3.
Rearrange the drives according to the ADU instructions.
4.
Duplicate Write Memory Error
Description: Data cannot be written to the array accelerator board in duplicate due to the detection of
parity errors. This is not a data-loss situation.
Action: Replace the array accelerator board.
Error Occurred Reading RIS Copy from SCSI Port X Drive ID
Description: An error occurred while ADU
the RIS from this drive.
Action: HP stores the hard drive configuration information in the RIS. If multiple errors occur, the drive
may need to be replaced.
FYI: Drive (Bay) X is Third-Party Supplied
Description: Third-party supplied the installed drive.
Action: If problems exist with this drive, replace it with a supported drive.
("Array Diagnostic Utility" on page 56) is unable to get monitor and performance
("Array Diagnostic
("Array Diagnostic Utility" on page 56) was trying to read
Utility" on page 56) to
Error messages 73