Export of Portable Virtual Disk Fails with Error 467

Asset ID:	1-72-1418785.1
Update Date:	2012-05-10
Keywords:

Solution Type Problem Resolution Sure

Solution 1418785.1 : Export of Portable Virtual Disk Fails with Error 467

Applies to:

Sun Storage 6540 Array - Version Not Applicable and later
Sun Storage 6580 Array - Version Not Applicable and later
Sun Storage 6180 Array - Version Not Applicable and later
Sun Storage 2540-M2 Array - Version Not Applicable and later
Sun Storage 2540 Array - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

In the 6xxx and 2xxx storage arrays with firmware 7.x, the Portable Virtual Disk feature offers the ability to move a Virtual Disk (or Volume Group) between storage arrays by logically exporting the Virtual Disk from the source storage array, physically moving the disk drives to the destination storage array and logically importing the Virtual Disk into the destination array. (See the Sun Storage Common Array Manager Array Administration Guide : "Moving a Virtual Disk Between Arrays").

A Virtual Disk export may fail with an error message as below.

ERROR DATA

Command sent to controller in slot: B
Host name: myhostname
IP address: 10.10.10.10

Return code: Error 467 -

This return code can be returned from exportVolumeGroup. It will be returned if one or more of the VGs drives configuration database is invalid and unusable. A possible recovery is to remove the drive(s) one at a time and re-insert it back into the array to trigger database resynchronization. This is not guaranteed to work, however.

Operation when error occurred: PROC_exportVolumeGroup
Timestamp: Feb 17, 2012 11:48:56 PM

STACK DATA

devmgr.v1060api09.sam.jal.ManagementOperationFailedException:
..

Cause

Each disk drive in the Virtual Disk holds a copy of the array configuration database. In preparation to the logical export of a Virtual Disk, the array firmware verifies the integrity of the configuration database on each drive because an invalid configuration copy could prevent re-importing of the Virtual Disk. If any drive in the Virtual Disk is found to have an invalid or unusable copy of the configuration database, the export fails.

Solution

To successfully export the Virtual Disk, a valid copy of the configuration database must be written to the problem disk(s), as follows.

Preparation

To prevent any reconstruction from being triggered during this procedure, make sure that there is no I/O to any of the volumes in the Virtual Disk.
Identifying the drive with the invalid configuration DB

The drive ID is provided in the details of the last event with code 0x2269 ("Export volume group drive unusable"). To display the event details:

Using the web browser
1. Expand Storage Arrays in the left menu pane.
2. Expand your storage array name in the left menu pane.
3. Expand Troubleshooting in the left menu pane.
4. Click on Events.
5. In the right pane, click on the -|-> icon (Advanced Filter).
6. Set Event to Log Events.
7. Set Event Type to Component.
8. Set Read the last X Kbytes From Log File to 100.
9. Set String Filter to 0x2269 => this is case sensitive
10. Click on the Details of the latest event.
Using the command line

sscs list -d <arrayName> -f 0x2269 event
sscs list -d <arrayName> event <eventID>

sscs (or lsscs) is located in:
Solaris: /opt/SUNWsefms/bin
Windows: C:\Program Files\Sun\Common Array Manager\Component\fms\bin
Linux: /opt/sun/private/fms/bin

Example of event details:
```
Severity    : Minor

Date        : Thu Feb 17 11:22:04 CET 2012

Device      : myarray (Sun Storage 6780)

Component   : Tray.01.Drive.01

Type        : LogEvent

Information : Export volume group drive unusable (0/0/0)

Event Code  : 80.20.491

Aggregated  : No

Description : Feb 17 11:22:04 myarray Tray.01.Drive.01: [ID 0x2269] NOTICE: Export volume group drive unusable (0/0/0)



Probable Cause :

The array firmware has logged an informational event.



Recommended Action :

No action required.
```
Get a valid configuration DB copy onto this drive
Physically remove and re-insert this drive, leaving 1 minute between removal and insertion. Insertion triggers a resynchronization of the configuration database on this drive.
Attempt to export the Virtual Disk again

Repeat steps 2 - 4 until the Virtual Disk export is successful.

The drive ID can also be seen in the majorEventLog. Below is a sample (parsed) log extract where drive t1d01, and in a later attempt drive t85d04, causes the export to fail.

A:2/17/12 11:22:04 PM : 64442 : 0/0/0 : 2269 : Error : Drive : Tray 1, Slot 1 : Export volume group drive unusableA:2/17/12 11:22:04 PM : 64444 : 0/0/0 : 505F : Command : Volume Group : Volume Group 9 : Exporting the volume group has failed


A:2/18/12 12:12:26 AM : 64681 : 0/0/0 : 2269 : Error : Drive : Tray 85, Slot 4 : Export volume group drive unusable

A:2/18/12 12:12:26 AM : 64683 : 0/0/0 : 505F : Command : Volume Group : Volume Group 9 : Exporting the volume group has failed

Attachments

This solution has no attachment

Applies to:

Symptoms

Cause

Solution

Preparation

Identifying the drive with the invalid configuration DB

Get a valid configuration DB copy onto this drive

Attempt to export the Virtual Disk again