Sun Storage 2500, 2500-M2 and 6000 Arrays : Missing Volumes Reported After Disk Replacement in Single-disk RAID-0 Vdisk

Asset ID:	1-72-1345746.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 1345746.1 : Sun Storage 2500, 2500-M2 and 6000 Arrays : Missing Volumes Reported After Disk Replacement in Single-disk RAID-0 Vdisk

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

Volumes are reported missing after replacing the failed disk in a single-disk RAID-0 volume group. 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(s) 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 single-disk RAID-0 volume group failed and was replaced.

Cause

A failed disk in a single-disk RAID-0 volume group was replaced without first deleting the volumes it contained 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 single-disk RAID-0 volume group, all volumes in the volume group must be deleted or the volume group wiped clean via the Initialize VDisk option on the Service Advisor before carrying out the disk replacement.

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.

Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

Attachments

This solution has no attachment