HP MSA 1040 HP MSA Events Description Reference Guide (762785-001, March 2014) - Page 24

Check that the SAS expansion cables are connected between each enclosure in the storage system

Page 24 highlights

170 Info. 171 Info. 172 Error The last rescan detected that the indicated enclosure was added to the system. Recommended actions • No action is required. The last rescan detected that the indicated enclosure was removed from the system. Recommended actions • No action is required. The indicated vdisk has been quarantined because not all of its disks are accessible. While the vdisk is quarantined, any attempt to access the volumes in the vdisk from a host will fail. If all of the disks become accessible, the vdisk will be dequarantined automatically with a resulting status of FTOL (fault tolerant and online). If not all of the disks become accessible but enough become accessible to allow reading from and writing to the vdisk, the vdisk will be dequarantined automatically with a resulting status of FTDN (fault tolerant with a down disk) or CRIT (critical); if a spare disk is available, reconstruction will begin automatically. When the vdisk has been removed from quarantine, event 173 is logged. For a more detailed discussion of quarantine, see the WBI help for the Tools > Dequarantine Vdisk panel or the CLI help for the dequarantine command. CAUTION: • Avoid using the manual dequarantine operation as a recovery method when event 172 is logged because this causes data recovery to be more difficult or impossible. • If you clear unwritten cache data while a vdisk is quarantined or offline, that data will be permanently lost. Recommended actions • If event 173 has subsequently been logged for the indicated vdisk, no action is required; the vdisk has already been removed from quarantine. • Otherwise, perform the following actions: • Check that all enclosures are powered on. • Check that all disks and I/O modules in every enclosure are fully seated in their slots and that their latches are locked. • Reseat any disks in the quarantined vdisk that are reported as missing or failed in the user interface. (Do NOT remove and reinsert disks that are not members of the vdisk that is quarantined.) • Check that the SAS expansion cables are connected between each enclosure in the storage system and that they are fully seated. (Do NOT remove and reinsert the cables because this can cause problems with additional vdisks.) • Check that no disks have been removed from the system unintentionally. • Check for other events that indicate faults in the system and follow the recommended actions for those events. But, if the event indicates a failed disk and the recommended action is to replace the disk, do NOT replace the disk at this time. • If the vdisk is still quarantined after performing the above steps, shut down both controllers and then power down the entire storage system. Power it back up, beginning with any disk enclosures (expansion enclosures), then the controller enclosure. • If the vdisk is still quarantined after performing the above steps, consult the online troubleshooting guide at http://www.hp.com/support/msa2040/Troubleshooting for more information. 24 Event descriptions

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80

24
Event descriptions
170
Info.
The last rescan detected that the indicated enclosure was added to the system.
Recommended actions
No action is required.
171
Info.
The last rescan detected that the indicated enclosure was removed from the system.
Recommended actions
No action is required.
172
Error
The indicated vdisk has been quarantined because not all of its disks are accessible. While the vdisk is
quarantined, any attempt to access the volumes in the vdisk from a host will fail. If all of the disks become
accessible, the vdisk will be dequarantined automatically with a resulting status of FTOL (fault tolerant and
online). If not all of the disks become accessible but enough become accessible to allow reading from and
writing to the vdisk, the vdisk will be dequarantined automatically with a resulting status of FTDN (fault
tolerant with a down disk) or CRIT (critical); if a spare disk is available, reconstruction will begin
automatically. When the vdisk has been removed from quarantine, event 173 is logged. For a more
detailed discussion of quarantine, see the WBI help for the Tools > Dequarantine Vdisk panel or the CLI
help for the
dequarantine
command.
CAUTION:
Avoid using the manual dequarantine operation as a recovery method when event 172 is logged
because this causes data recovery to be more difficult or impossible.
If you clear unwritten cache data while a vdisk is quarantined or offline, that data will be permanently
lost.
Recommended actions
If event 173 has subsequently been logged for the indicated vdisk, no action is required; the vdisk has
already been removed from quarantine.
Otherwise, perform the following actions:
Check that all enclosures are powered on.
Check that all disks and I/O modules in every enclosure are fully seated in their slots and that their
latches are locked.
Reseat any disks in the quarantined vdisk that are reported as missing or failed in the user
interface. (Do NOT remove and reinsert disks that are not members of the vdisk that is
quarantined.)
Check that the SAS expansion cables are connected between each enclosure in the storage system
and that they are fully seated. (Do NOT remove and reinsert the cables because this can cause
problems with additional vdisks.)
Check that no disks have been removed from the system unintentionally.
Check for other events that indicate faults in the system and follow the recommended actions for
those events. But, if the event indicates a failed disk and the recommended action is to replace the
disk, do NOT replace the disk at this time.
If the vdisk is still quarantined after performing the above steps, shut down both controllers and
then power down the entire storage system. Power it back up, beginning with any disk enclosures
(expansion enclosures), then the controller enclosure.
If the vdisk is still quarantined after performing the above steps, consult the online troubleshooting
guide at
for more information.