Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1377
  • Last Modified:

How to fix "Doesn't Match Any Storage Profile" error on EMC CX600

I added a disk to RAID Group 0, not I am getting the above error when the system does a backedn health check.  How can I fix this?   Thank you.

0
altonyoung
Asked:
altonyoung
  • 5
  • 4
1 Solution
 
Duncan MeyersCommented:
Is there a Celerra gateway attached to the CX600? This appears to be an issue specific to Celerra systems.
0
 
Duncan MeyersCommented:
If it is a Celerra gateway, then you need to use 4+1 or 8+1 RAID groups (or perhaps 6+1  - depending on the code revision).

Can you also post the full text of the error message?
0
 
altonyoungAuthor Commented:
yes.  I do have a Nas gateway in my system.   Celerras version is 5.5.32-4.  Below is the message i see in the log file.  The error appeared after I added the disk to the RAID group.   Thank you very much  for you time and support.  


Symptom: Backend Health Check failed: Unknown check found
         * Command: /nas/bin/nas_storage -check -all
         * Command output: Discovering storage (may take several minutes)
         *        Error 5017: storage health check failed
         *        APM00033702042 root_disk, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 root_ldisk, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d3, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d4, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d5, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d6, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d7, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d8, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d9, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d10, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d11, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d12, RAID5(5+1), doesn't match any
                  storage profile
         *        APM00033702042 d13, RAID5(5+1), doesn't match any
                  storage profile
         * Command exit code: 6
*Action : If you are setup for Call-Home: Your EMC Service Provider
         will be in contact with you in order to resolve this issue. If you are
         not setup for Call-Home: Contact EMC Customer Service and refer to EMC
         Knowledgebase emc146016. Include this log with your support request.
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Duncan MeyersCommented:
The Celerra doesn't know what to do with a 5+1 RAID 5 group (it's not a supported Celerra configuration), so you're out of luck I'm afraid. The only way out of this is to create a new file system with some spare disks, migrate the data, blow away the bad RAID group and recreate it as a 4+1 RAID 5. You *may* be able to upgrade to a later version of DART (the Celerra OS) and use a 6+1 RAID 5 as an alternative, but that will take some serious investigation to work out if that's possible.

References: https://community.emc.com/message/381947, emc183839 and others.
0
 
altonyoungAuthor Commented:
Thanks for the information.   Access to CIFS shares are OK now.  If I leave this along, will Celerra eventually stop working for me?   What will happen if I reboot the box?   Thank you.  

0
 
altonyoungAuthor Commented:
Meyersd,  I have another question for you.   Is it safe to just blow away the RAID group after I migrate my data over to other disks?  Will there be system data stored on this RAID group that I might risk damaging?   Thank you again for your time and support.  
0
 
Duncan MeyersCommented:
>If I leave this along, will Celerra eventually stop working for me?
It may unmount the file system on a reboot - which means you wouldn't be able to access the files.

If these are FC drives (and I'd expect that RAID Group 0 would be), then you need to be using either a 4+1 group or 8+1 RAID 5 group. If the RAID group was originally allocated using the Celerra's tools, then the RAID group is almost certainly exclusive to the Celerra so it is safe to move the Celerra LUN and recreate the RAID group. It is easy to check from Navisphere by looking at the RAID group in the Navisphere tree - you'll see the LUNs that are sitting on the RAID group.

Having said all that, Celerra boot LUNs are on RAID Group 0, so you will need to be VERY careful.

Have a read of these EMC KB articles: emc138143  (Adding new storage to a Celerra using Automatic Volume Management (AVM)) and emc144545 (How do I perform a CLARiiON LUN migration on a Celerra server?)

From emc144545:

"CLARiiON LUN Migrations are supported, but only under the following criteria. These are restrictions which MUST be followed carefully, otherwise data outages or data loss can be incurred.  

A LUN migration is supported when migrating the control volumes as part of a CX to CX3 upgrade. This is normally a Professional Services engagement; an RPQ is no longer required, but a CCA is required.  Celerra boot LUNs 0-5 should reside on the CLARiiON Vault drives.

When LUNs in a Celerra storage group are greater than an Host ID of 15, the following rules apply to LUN migrations with regards to data LUNs:

The RAID type is the same (for example, RAID 5 RAID5, or RAID 3  RAID 3)  (NOT RAID 5 -> RAID 3 or RAID 3 -> RAID5)
 
The drive type is similar. (FC allowed to FC), (ATA allowed to ATA)
 
The number of the physical drives in the RAID group is the same.  (Source and target RAID groups)
 
The source and target LUNs must be identical size (According to block count size, not MB size)"

If you're not 100% confident of what you're doing here, I'd strongly recommend getting in touch with EMC Support.

0
 
altonyoungAuthor Commented:
Thank you.  
0
 
Duncan MeyersCommented:
Thanks! Glad I could help. I hope you get it sorted out without too much pain...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now