Unsolved
This post is more than 5 years old
3 Posts
0
1594
September 5th, 2013 05:00
CX300 - LUN feature inconsistencies
Hi guys,
I have problem with my CX300 Storage, because I can't destroy or create LUN. Always when I'm doing that actions, I have error "The array configuration cannot be modified due to LUN feature inconsistencies. Contact your Service Provider (0x40008061)".
First problem is, that I can't contact EMC, because that storage is about one year without support.
And now all story, how I get to that state:
1. That storage has been replaced by VNX 5700, and for moving all data SnapView and SanCopy features was enabled on that CX300
2. When CX300 finished it's production live in my company, it was moved to another site, and during that process disks from one shelf were removed
3. When I powered on storage on second site (because I want to use it as logs storage), I noticed, that I can remove all LUNs and RAIDs, except two, because they landed in "unowned" LUNs.
4. When I tried to unbind that LUNs, I have error, that some feature is using that LUN, so unbind is impossible
5. I tried from naviseccli to find that feature blocks that LUN, and I noticed, that it was SnapView
6. I tried to disable that feature from naviseccli, but it doesn't work
7. So I uninstalled SnapView and SanCopy features from that storages, everything goes well and now I have that "0x40008061"
Worst thing is, that before my actions I was able to create new LUNs, now it's impossible.
Please help me in that case.
AnkitMehta
1.4K Posts
0
September 5th, 2013 07:00
You can not perform any actions on an unowned LUN. Unowned means that neither SPA nor SPB owns the LUN. The only LUNs you normally would see in the Unowned LUNs folder would be the Hot Spares. Anyhow, there is a lengthy procedure and then there is a short procedure. Lets see if short one works!
Disable Access Logix: [Install latest version of CLI]
#naviseccli -h sc_off
Refer: https://community.emc.com/docs/DOC-10060 for more information.
Delete the LUNs via CLI, if GUI is still giving you an error.
Refer http://corpusweb130.emc.com/upd_prod_VNX/UPDFinalPDF/jp/Command_Reference_for_Block.pdf for commands on LUN deletion.
(I am assuming here, that you don't need any data from that LUN and by any method you just want this Storage Unit blank, if not then do not perform above steps)
mszpad
3 Posts
0
September 5th, 2013 14:00
Firstly - thank you Ankit for your response.
I tried your solution, disabled Access Logix, and then from naviseccli tried to unbind that LUNs, but I got response:
"
Error: unbind command failed
Error returned from Agent
SP A: The array configuration cannot be modified due to LUN feature inconsistencies. Contact your Service Provider. (0x40008061)"
I think that now my biggest problem are not unowned LUNs, but feature inconsistencies
Any other suggestion ?? Data on that storage is not important, I can do anytihing with my cx300
Vipin VK
2 Intern
•
812 Posts
0
September 6th, 2013 05:00
Previous power down of the system may have caused this issue. Improper shut down of the system may have caused dirty cache in these LUN which in turn caused them to go unowned. The dirty cache need to be cleared and this is done by Support.
Do you have valid contract for this system ?
kelleg
4.5K Posts
0
September 6th, 2013 14:00
It also appears that you have a fault disk in one of the DAE's - you should repair that first, then check the status of the disks. On the older CX line, unowned usually meant dirty cache on the LUN (as mentioned above) that requires a service engagement to clear.
glen
mszpad
3 Posts
0
September 10th, 2013 01:00
Guys,
I have no chance for support - I have to fix it myself, or left broken. If you have any suggestion which might help, I'm ready to try it
o17Uu33DCF12520
4 Operator
•
1.1K Posts
0
September 10th, 2013 19:00
The 0X40008061 (MMAN_ERROR_MAPFILE_CORRUPT) error indicates that device map corruption is present. Configuration changes that modify the device map are disallowed starting with FLARE Release 24. The array configuration cannot be modified due to LUN feature inconsistencies. The only way is to engage the EMC support.