Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

6085

December 28th, 2014 06:00

Unable to remove lun - Being used by a feature of the storage system

Hi

We're having a problem removing old LUN's that were once part of a MirrorView.

When removing we are getting the error:Unable to remove lun - Being used by a feature of the storage system.


Problem details:

We used to have two Clarrion systems that were connected via Mirrorview.

The secondary/slave Clariion has moved to a new location, without removing the old MirrorView connections first.

We have removed the Remote mirrors using "Force removal" in the GUI , and disabled the K10FarCopy using :

naviseccli -h <SP_IP_address> mirror -async -setfeature -off -lun


When running :
NaviSECCli.exe -h getlun -messner 0 -stack

We are getting :

Listed Driver:         K10RollBackAdmin
K10SnapCopyAdmin

There are no sessions/snapshots on the clariion system. ( at least known or visible ones ).

The LUNs are not part of the reserved LUN Pool, are not MetaLuns, nor appear in the private LUN folder. They Do appear in Unowned LUNs folder.

We have tried removing the LUNs using engineering mode from the Physical Storage Groups but without success.

Trespassing the LUN returns error: EsxCluster1Lun9 - Transfer of ownership of a LUN failed (0x40008059)

Clicking properties on the LUN shows current owner N/A:

emc1.PNG.png

Running:

NaviSECCli.exe -h clone -messner -setclonefeature -off   -lun 0

Does not produce any errors but does not remove the drivers

We have tried rebooting SP's , removing the LUN from both SP's, restarting the management processors -  all with the same results

Please help , We are already 3 days looking for a solution  without success.

Thanks...

A.

Edit: Forgot to mention an important thing: The disks were shuffled in the enclosure from the original location when the LUNs worked. It's impossible for us to recover the correct order ( we did not collect this info) . And the data in the LUNs is not important to us, We just want to delete them.

Message was edited by: aviel

37 Posts

January 2nd, 2015 09:00

Hi,

>> The reason what seems to me for unable to destroy the luns being reshuffled drives from the original enclosures, causing CRU Siganture errors on it and also the lun in question not having any current owner.
>> You can try below command using naviseccli to unbind the luns.

naviseccli unbind -messner < >

>> The command should allow you to unbind the luns.

>> If still that doesn't work, we suggest to open SR with the EMC Support team to investigate further and give faster resolution.

December 28th, 2014 23:00

Hi,

I think the below mentioned link might help you:

https://community.emc.com/message/511789

Thanks

Jyothi

3 Posts

December 28th, 2014 23:00

Thanks Jyothi,

I forgot to mention - I've already tried creating snapshot & Sessions and destroying them, It does not release the LUNs and  the same issue happens.

2 Intern

 • 

715 Posts

December 29th, 2014 00:00

I'd try removing the MV enablers. 

If you'll need to use it again, make sure you have the enablers available to reinstall.

1K Posts

December 29th, 2014 06:00

Try this:

naviseccli -h getlun -messner LUN# -stack

If something is returned run this command:

naviseccli -h mirror -async|-sync -setfeature -off -lun LUN#

1K Posts

December 29th, 2014 06:00

Never mind, looks like you tried that already

3 Posts

January 6th, 2015 02:00

Thank you all for your support

naviseccli -messner solved the issue !

i tried with mesner on the gui and then unbind but it did not take. did not know there was a difference between the two..

(BTW - removing the MV enablers and reinstalling did not help)

Thank you very much.

A

4 Posts

May 19th, 2015 04:00

Hello Aviel,

Did you solved the issue?

I've the same problem and i'm looking for a solution.

Thanks

1.4K Posts

May 19th, 2015 08:00

Run:

naviseccli unbind -messner LUNID

4 Posts

May 19th, 2015 08:00

Thank you very much, It worked fine!!

No Events found!

Top