Asset ID: |
1-72-1309987.1 |
Update Date: | 2012-08-27 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1309987.1
:
VSM / SVA - Failed Disk Drive - HDA - FSC Fault Symptom Code
Related Items |
- Sun StorageTek VSM System
- Sun StorageTek V2X SVA Disk System
|
Related Categories |
- PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VTL
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Datacenter Disk - Other
- PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM
|
VTSS Virtual Tape Storage Subsystem. In VSM, a back-end disk drive
SVA Shared Virtual Array V2X V24F back-end disk drive
In this Document
Created from <SR 3-3313062461>
Applies to:
Sun StorageTek VSM System - Version 4 to 5C [Release 4.0 to 5.0]
Sun StorageTek V2X SVA Disk System - Version Not Applicable to Not Applicable [Release N/A]
IBM z/OS on System z
Symptoms
Multiple Fault Symptom Codes, FSCs, may occur for the same failed disk drive (HDA) on the same VSM serial number. The following FSCs may be associated with a failed disk drive:
3E00 FSC3E00 DRIVE_FAILURE
3E73 FSC3E73 ED_DESTAGE_FAILURE_DRIVE_READY
79EE FSC79EE PSA_ASYNC_FENCE
BA04 FSCBA04 REQUEST_FCBE_DRIVE_FENCE
B90D FSCB90D ESCS_SECTOR_REASSIGNMENT_SENT
D00C FSCD00C FSC_TI_FCAL_IOCB_TIMEOUT
D01D FSCD01D CC_SCSI_HW_ERROR
D039 FSCD039 CC_SCSI_PFA_THRESHOLD_REACHED
D057 FSCD057 TI_FCAL_IOCB_PORT_LOGGED_OUT
D078 FSCD078 FSC_CC_SCSI_UNRECOVERED_MEDIUM_ERROR
D082 FSCD082 FSC_CC_SCSI_WRITE_FAULT_MEDIA_ERROR_RETRY
3E01 FSC3E01 DRIVE_RECONSTRUCTION_BEGUN
3E02 FSC3E02 DRIVE_RECONSTRUCTION_COMPLETE
3E60 FSC3E60 NO_SPARES_REMAINING
3E61 FSC3E61 1_SPARE_REMAINING
3E62 FSC3E62 2_SPARES_REMAINING
3E63 FSC3E63 3_SPARES_REMAINING
7341 FSC7341 SNS_1_BROKEN_BACKEND_DRIVES
7342 FSC7342 SNS_2_BROKEN_BACKEND_DRIVES
7343 FSC7343 SNS_3_BROKEN_BACKEND_DRIVES
Cause
The impact of a failed disk drive is minimal as spare drives are typically available. Spares, devices not logically associated with an array, are used to automatically reconstruct and logically replace failed drives. A background function recreates and rewrites the data from a failed (fenced) device to a spare device. The timeframe of the reconstruction depends on the amount of data on the drive and the workload on the VSM or SVA. The data reconstruction must complete prior to the replacement of the failed device. Following the reconstruction of a fenced disk drive, a replacement is recommended to be scheduled in a timely manner. To minimize potential impact, avoid waiting until multiple drives fail to replace the disk drives.
Solution
Automatic service alerts (ASRs) will be generated if SDP and MOS are activated with the associated serial number for the VSM. A service request will be opened with the associated disk drive failure.
If duplicate service requests (SRs) are opened for the same serial number and same disk drive, one SR will be worked and the others will be closed.
If a service request is to be opened, then note:
1. Serial number of the VSM.
2. Severity as 3 unless critical hardware circumstances exist (multiple disk drive failures at one time).
3. Timeframe for the field engineer to be scheduled onsite (if known).
4. Name of the field service engineer (FSE) if a DEDICATED or specific FSE is to be dispatched.
5. Location and type or part number of the disk drive (if known).
6. Information regarding how the disk drive is known to be failed (i.e., field engineer, host messages, alert).
While the service request being worked, a field engineer will be dispatched following a field service task (FST) being created. The required part will be ordered, and then the field engineer will be scheduled to be onsite.
Attachments
This solution has no attachment