| Asset ID: |
1-72-1345746.1 |
| Update Date: | 2012-05-09 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1345746.1
:
Unable To Delete Volume After Disk Replacement on a StorageTek 2500 Arrays, Sun Storage 2500-M2 and Sun Storage 6000
| Related Items |
- Sun Storage 6180 Array
- Sun Storage 6580 Array
- Sun Storage 6780 Array
- Sun Storage 2540 Array
- Sun Storage 2510 Array
- Sun Storage 2540-M2 Array
- Sun Storage 6140 Array
- Sun Storage 2530 Array
- Sun Storage 2530-M2 Array
- Sun Storage 6540 Array
- Sun Storage 6130 Array
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>Arrays>SN-DK: ST25xx
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 2xxx Arrays
|
Created from <SR 3-4090760225>
Applies to:
Sun Storage 6540 Array - Version Not Applicable and later
Sun Storage 6180 Array - Version Not Applicable and later
Sun Storage 6580 Array - Version Not Applicable and later
Sun Storage 6780 Array - Version Not Applicable and later
Sun Storage 2540 Array - Version Not Applicable and later
Information in this document applies to any platform.
Symptoms
A volume is reported missing after a disk replacement. A section like the following appears in the file storageArrayProfile.txt which is in the supportdata bundle:
MISSING VOLUMES
------------------------------
Number of missing volumes: 1
Volume WWN: 600A0B80005A433B0000022E499A7662
Note: The above WWN is only an example.
Furthermore the volume cannot be deleted because the array firmware has registered that it contains unreadable sectors that need to be cleared. The following error message is returned when trying to delete the volume via the Sun Storage Common Array Manager (CAM) BUI:
Volume {0} could not be deleted. Missing volumes could not be deleted because they currently have unreadable sectors. Contact your Technical Support Representative for assistance.
The sectors cannot be cleared because the device on which they were reported is no longer present.
Changes
A disk in a RAID-0 volume group was replaced using an incorrect procedure.
Cause
A failed disk in a RAID-0 volume group was replaced without deleting the volumes or re-initializing the VDisk, leading to an inconsistent or corrupted state of the internal configuration database.
In case of a disk failure in a RAID-0 volume group, all volumes in the volume group must be deleted or the volume group wiped clean via the Initialize VDisk option of the Service Advisor.
Solution
It seems the only way to get rid of the missing (ghost) volume in this situation is to wipe the configuration and recreate it. Please contact the Oracle support to get assistance from an engineer.
Instructions for the Oracle engineer. Since this procedure involves controller shell access and a significant risk to customer data, it should only be undertaken by an L2 engineer.
- Prepare a recovery script using make-sscs.pl with supportData showing the desired configuration.
- If necessary, edit the script to make sure it does exactly what is needed.
- Make the recovery script available on the customer's CAM server.
- On each controller, run sysWipe in the controller shell and reboot the controller.
This can also be done via CAM (without controller shell access) using:
service -d <device-id> -c initialize -t dacstore
- Remove and re-register the array in CAM.
- Set the array name to its original value (as it appears in the recovery script).
- Run the recovery script on the customer's CAM server.
- Verify that the resulting configuration is as expected.
- Verify in read-only mode that the data can be accessed.
Attachments
This solution has no attachment
