Troubleshooting For Leftover Disk Drives; Troubleshooting Steps For Leftover Disk Drives - HP P2000 G3 MSA Reference Manual

495
Warning The algorithm for best-path routing selected the alternate path to the indicated disk because the I/O error
count on the primary path reached its threshold.
The controller that logs this event indicates which channel (path) has the problem. For example, if the B
controller logs the problem, the problem is in the chain of cables and expansion modules connected to the
B controller module.
Recommended actions
• If this event is consistently logged for only one disk in an enclosure, perform the following actions:
• Replace the disk.
• If that does not resolve the problem, the fault is probably in the enclosure midplane. Replace the
chassis-and-midplane FRU for the indicated enclosure.
• If this event is logged for more than one disk in an enclosure or disks in multiple enclosures, perform the
following actions:
• Check for disconnected SAS cables in the bad path. If no cables are disconnected, replace the
cable connecting to the ingress port in the most-upstream enclosure with reported failures. If that
does not resolve the problem, replace other cables in the bad path, one at a time until the problem
is resolved.
• If that does not resolve the problem, replace the expansion modules that are in the bad path. Begin
with the most-upstream module that is in an enclosure with reported failures. If that does not resolve
the problem, replace other expansion modules (and the controller module) upstream of the affected
enclosure(s), one at a time until the problem is resolved.
• If that does not resolve the problem, the fault is probably in the enclosure midplane. Replace the
chassis-and-midplane FRU of the most-upstream enclosure with reported failures. If that does not
resolve the problem and there is more than one enclosure with reported failures, replace the
chassis-and-midplane FRU of the other enclosures with reported failures until the problem is
resolved.

Troubleshooting steps for leftover disk drives

HP MSA2000/P2000 arrays use metadata on hard drives to identify vdisk members and identify other
disk members of the vdisk.
Hard drives enter a Leftover state for several reasons:
• Drive spin up was not completed before a controller polled the drive. When the controller queries the
drive and finds the drive is not in a ready state, the controller may place the drive into a Leftover state.
• Improper power-on sequences.
• Firmware upgrade (due to a timing issue).
• Failover taking longer than expected.
• The drive is swapped from another MSA system, or removed and reinserted in the array.
Metadata on a disk identifies the disk as being a member of a vdisk. Improperly clearing the metadata
from a disk may cause permanent data loss.
CAUTION: Clearing metadata from a leftover drive should be done with extreme care. Only clear
metadata without looking at logs if you are certain the drive has never been associated with a vdisk in this
MSA system or contains no data. This situation most often occurs when inserting a previously used hard
drive into a live system or moving a drive between two systems.
Never clear metadata from a drive if any vdisk in the array is in an Offline, Quarantined, or inaccessible
state. Do not clear metadata from a drive if you are unsure this is the correct step to take. Clearing
metadata from a drive permanently clears all data from the drive. In these types of situations, a backup of
data should be done if possible.
60 Event descriptions