Filter
Top Products
HP StorageWorks 2000 G2 Modular Smart Array Reference Guide 69
NOTE: If you are having a problem with the system or a vdisk, check the event log before calling
technical support. Event messages might enable you to resolve the problem.
When reviewing events, do the following:
1. For any critical or warning events, look for recommended actions in the Event code reference appendix.
Identify the primary events and any that might be the cause of the primary event. For example, an
over-temperature event could cause a disk failure.
2. Review the event log for the controller that reported the critical/warning event by viewing the event log
by controller. Locate the critical/warning events in the sequence.
Repeat this step for the other controller if necessary.
3. Review the events that occurred before and after the primary event.
During this review you are looking for any events that might indicate the cause of the critical/warning
event. You are also looking for events that resulted from the critical/warning event, known as secondary
events.
4. Review the events following the primary and secondary events.
You are looking for any actions that might have already been taken to resolve the problems reported by
the events.
Viewing information about all vdisks
In the Configuration View panel, right-click Vdisks and select View > Overview. The Vdisks Overview table
shows the overall health, quantity, capacity, and space usage of existing vdisks. For descriptions of
storage-space color codes, see About storage-space color codes on page 26.
For each vdisk, the Vdisks table shows the following details:
• Health.
OK. The vdisk is online with all disks working.
Degraded. The vdisk is being reconstructed, as shown by its Current Job property; or, a RAID-6
vdisk has degraded performance due to one missing disk but remains fault tolerant. You can use a
degraded RAID-6 vdisk but resolve the problem as soon as possible.
Fault. The vdisk can perform I/O functions for hosts but is not fault tolerant. Review the status
information and take the appropriate action, such as replacing a disk. You can use the vdisk but resolve
the problem as soon as possible.
Unknown.
• Name. Vdisk name.
• Size. Total storage space in the vdisk.
• Free. Available space in the vdisk.
• RAID. RAID level of the vdisk and all of its volumes.
• Status.
• CRIT: The vdisk is online, however some disks are down and the vdisk is not fault tolerant.
• FTDN: The vdisk is online and fault tolerant, however some of the disks are down.
• FTOL: The vdisk is online and fault tolerant.
• OFFL: The vdisk is offline because it is using offline initialization, or because disks are down and
data may be lost.
• QTCR: The vdisk is in a critical state and has been quarantined because some disks are missing.
• QTOF: The vdisk is offline and has been quarantined because some disks are missing.
• UP: The vdisk is online and does not have fault-tolerant attributes.
• Disk Type. SAS (dual port), SAS-S (single port), SATA (dual port), or SATA-S (single port).
• Preferred Owner. Controller that owns the vdisk and its volumes during normal operation.