Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2192

April 8th, 2009 03:00

Cannot delete celerra metahead device

I have a celerra meta device which I unmasked and unmapped thru ECC. I want to delete this device, however, I was able to delete only the members of the meta, NOT the metahead. Everytime I try to delete the metahead, it gives the following message: " The specified device must be unmasked or unmapped before the configuration change can be applied, aborting...". I checked to see if this metahead is still visible on my Celerra (thru nas_disk -l command) or if it is still mapped on any director port (it is already under UNMAPPED folder on ECC), however, did not see the device in either location. Anybody have any idea what went wrong here?

57 Posts

April 9th, 2009 04:00

Finally a solution to the problem has been found. The problem lied with masking which was not completely cleared for the meta heads. It's only the meta heads that are concerned with the masking, that's why even after dissolving the meta, the members can be deleted, NOT the meta heads. You just need to follow one additional step after removing the volumes from NAS. Here are the commands we should have run before trying to delete the metaheads:

symdev -sid 0900 not_ready 407 -celera

symmask -sid 0900 -wwn 5006016930226204 remove devs 40F -dir 8c -p 1 -celera


It will update the masking information which will eventually allow you to delete the metaheads. I hope it helps.

9 Legend

 • 

20.4K Posts

April 8th, 2009 03:00

did you dissolve the meta before you tried to delete its members ? I am surprised it would let you delete meta members without dissolving the meta first.

57 Posts

April 8th, 2009 03:00

Yes, I did dissolve it before removing the members.

9 Legend

 • 

20.4K Posts

April 8th, 2009 04:00

Can you run "symdev show device-name -sid 123"..just to double check device is truly unmapped.

9 Legend

 • 

20.4K Posts

April 8th, 2009 05:00

are you deleting through ECC or symcli ? Have you tried deleting using symcli ?

57 Posts

April 8th, 2009 05:00

# /nas/symcli/bin/symdev show 0407 -sid 900

=====================[output]========================

Device Physical Name : Not Visible

Device Symmetrix Name : 0407
Device Serial ID : N/A
Symmetrix ID : 000290100900

Attached BCV Device : N/A

Attached VDEV TGT Device : N/A

Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5771
Device WWN : 60060480000290100900533030343037
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0005

Device Block Size : 512

Device Capacity
{
Cylinders : 37180
Tracks : 557700
512-byte Blocks : 35692800
MegaBytes : 17428
KiloBytes : 17846400
}

Device Configuration : 2-Way Mir (Non-Exclusive Access)

Device is WORM Enabled : No
Device is WORM Protected : No

SCSI-3 Persistent Reserve: Disabled

Dynamic Spare Invoked : No

Dynamic RDF Capability : None

STAR Mode : No
STAR Recovery Capability : None
STAR Recovery State : NA

Device Service State : Normal

Device Status : Not Ready (NR)
Device SA Status : N/A (N/A)

Mirror Set Type : [Data,Data,N/A,N/A]

Mirror Set DA Status : [RW,RW,N/A,N/A]

Mirror Set Inv. Tracks : [0,0,0,0]

Back End Disk Director Information
{
Hyper Type : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [01A, C, 8]
Disk Director Volume Number : 311 (0x136)
Hyper Number : 17
Disk Capacity : 476837m
Disk Group Number : 3

Hyper Type : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [16D, C, 8]
Disk Director Volume Number : 311 (0x136)
Hyper Number : 17
Disk Capacity : 476837m
Disk Group Number : 3
}

57 Posts

April 8th, 2009 07:00

It gives the same output:

C:\Program Files\EMC\SYMCLI\bin>symconfigure -sid 900 -file c:\delete.txt previe
w

Execute a symconfigure operation for symmetrix '000290100900' (y/ ) ? y

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Error occurred while Defining change number 1:
The specified device must be unmapped or unmasked before the configuration c
hange can be applied
Device 0407 generated the failure

Terminating the configuration change session..............Done.

The configuration change session has failed.

9 Legend

 • 

20.4K Posts

April 9th, 2009 04:00

thanks for the update. This is strange ...i never had to mask devices for my Celerra. I have a pair of FAs that are used strictly for Celerra and they don't even have VCM flag enabled.

11 Posts

April 14th, 2009 09:00

Hello!
I've never deleted any devices without running a Write disable first:

symdev -sid 2886 write_disable 04F7 -sa 8b -p 0 -noprompt

By disabling writing to the metaheads you should be able to delete them with no problems; this needs to be ran prior unmappaing the devices.

1 - Unmask
2 - Write disable
3 - Unmap

Hope it helps for the next time :)

Cheers
No Events found!

Top