Hitachi HUS154530VLF400 Manuel D’Utilisation
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification
343
21.21.4.3 Recovered Drive Error
The Initiator should log the error as soft with the recovery level.
21.21.4.4 Drive Not Ready
The initiator should do the following:
1. Issue a Start Stop Unit (1B) command.
2. Verify that the drive comes ready within the time specified in Section 4.5.2, “Drive ready time” on page 13.
3. If the drive fails to come ready within the specified time, service the drive using the service guidelines specified in Sec-
2. Verify that the drive comes ready within the time specified in Section 4.5.2, “Drive ready time” on page 13.
3. If the drive fails to come ready within the specified time, service the drive using the service guidelines specified in Sec-
4. Retry the failing command.
a. If the failing command completes with Good Status, log the error as recovered.
b. If the failing command completes with Not Ready sense, verify there is no outside cause (for example, the power
b. If the failing command completes with Not Ready sense, verify there is no outside cause (for example, the power
supply). Then service the drive using the service guidelines specified in Section 21.21.1, “Drive Service Strategy”
on page 339.
on page 339.
21.21.4.5 No Defect Spare
Three conditions can cause this error:
1. When the Reassign Blocks (07) command is issued and there are no spares available for the Drive to use for the reloca-
tion requested.
2. When the Glist is full and the sector to be reassigned cannot be added.
3. During a format operation, there was not enough space available to fulfill the spare requirement (Dlist is too large).
3. During a format operation, there was not enough space available to fulfill the spare requirement (Dlist is too large).
Service the Drive following Section 21.21.1, “Drive Service Strategy” on page 339.
21.21.4.6 Degraded Mode
Refer to Section 21.6.9, “Degraded Mode” on page 320, for the definition of this state. There are three causes for entering
degraded mode. In all cases the Sense Key is Not Ready. The causes are the following:
degraded mode. In all cases the Sense Key is Not Ready. The causes are the following:
1. Sense Code/Qualifier of Logical Unit Not Ready, initializing command required. The spindle motor not spinning or not
at the proper speed. This may not be an error condition. The initiator should issue a Unit start (1B) command to start
the spindle motor. If the Drive fails to come ready in the time specified in Section 21.20, “Command Time out Limits”
on page 337, service the drive using the service guideline recommended in Section 21.21.1, “Drive Service Strategy”
on page 339.
the spindle motor. If the Drive fails to come ready in the time specified in Section 21.20, “Command Time out Limits”
on page 337, service the drive using the service guideline recommended in Section 21.21.1, “Drive Service Strategy”
on page 339.
2. Sense Code/Qualifier of Diagnostic Failure. Failure of a Send Diagnostic self test, a start up sequence, or other internal
target failures.
- Failure of a send diagnostic self test or a start up sequence.
This failure is the result of the diagnostics that are executed during power on or when the Send Diagnostic (1D) com-
mand is executed detecting a failure. As with the RAM code not loaded and the configuration data not loaded, the
recovery is either a power cycle or issuing the Send Diagnostic (1D) command with the self test bit set active.
Recovery for a failed Send Diagnostic (1D) is achieved in one of the following ways:
mand is executed detecting a failure. As with the RAM code not loaded and the configuration data not loaded, the
recovery is either a power cycle or issuing the Send Diagnostic (1D) command with the self test bit set active.
Recovery for a failed Send Diagnostic (1D) is achieved in one of the following ways:
Executing the Send Diagnostic (1D) command
Power cycling the drive
If the failure repeats, service the drive using the service guideline recommended in Section 21.21.1, “Drive Service
Strategy” on page 339.
Strategy” on page 339.
Recovery for a failed power up sequence is achieved in one of the following ways:
Issuing a Unit start (1B) command
Power cycling the drive.
If the failure repeats, service the drive using the service guideline recommended in Section 21.21.1, “Drive Service
Strategy” on page 339.
Strategy” on page 339.