Unassociated Disk Group on HPE MSA 2062

[ShakeelAhamed]

Hi Team,

On our HPE MSA 2060 first we created one disk group as with two 1.9 TB  SSD drivces RAID 1 in pool A.

Later added Perfomance tier license and immediately created Disk group in Pool B RAID 10 with 4 HDD 10K the diskgroup created but its outside of Pool B and saying ..

Unassociated Disk Groups

The disk groups in this table are not associated with pools that are local to this system. These disk groups were possibly imported into the system on disks that were moved from another system, and thus may contain data that you do not want to delete. If you know it is ok to delete the data on these disks, the disk groups can be deleted by manually clearing metadata. In cases where you are unsure, it is best to return these disks to the pool from which they came and manage the disk groups appropriately from that system before returning the disks to this system for re-use.

The should I try delete the new disk group and create again, please help.

Thanks,

Shakeel

[support_s]

System recommended content:

1. HPE MSA 2062 Storage Array - Specifications

2. HPE MSA 2062 Storage Array - Option Parts

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[ShakeelAhamed]

Not help question is different.

[JonPaul · Accepted solution]

@ShakeelAhamed 
Was the RAID 1 Pool A installed in the system when you created the RAID 10 Pool B?
The Pools maintain information about the other pool and the message you are showing is typically seen when 'rogue' disk-groups are attempted to be added whole to the system.  Often using the same pool identifier (Pool A and Pool A).

Was the RAID 1 SSD disk-group the only other storage in the system?

Since the RAID 10 drives are just added and should not have any data on them can you 'remove' the disk-group (not physically).  If the disk-group has the same name as another then use the disk-group serial number and the CLI.  Note: removing a disk-group will remove any data on that disk-group so be careful.
It might be good to use your HPE warranty and get a support case going to get someone to guide you through the recovery.

[ShakeelAhamed]

Hi John,

Yes RAID 1 already exists in Pool A, when I tried to add another Diskgroup with RAID 10 on Pool B the disk group created but DG was not showing in any of the pool.

Later I removed this newly created DG from CLI, and readded DG in Pool B now its fine.

Thanks for your reply appreciate.

[Sunitha_Mod]

Hello @ShakeelAhamed,

That's great! 

We are glad to know the problem has been resolved. 

[klindsay]

Hello All.,

I have the same issue. this is the MSA 2060. I have a Raid 10 that has been running fine for a few years. I needed to expand this raid and found that I needed to make another DG. also needed 4 disk to complete this task. I had another MSA that was delevered with the same drives. I removed 2 of the drives from this new MSA and put them in the running RAID 10. the MSA took the info from the disk and make another DG with the same name but in the MSA-DP+ RAID level and its missing 10 drives. I did not want to make this DG and cannot remove it. I have contacted Support and level 1 said you have to backup data then redo the entire MSA. Level 2 looked at the logs and looked at the CLI but could not help. As said above, how do I remove this unallocated DG gtom the SAN. There is no data on the 2 drives I put in but the RAID 10 has the customers most used application that runs the entire company. 

[JonPaul]

@klindsay 
All new MSA 2060 Flash Bundle systems come with the disk-group created in the recommended configuration.  12 drive RAID MSA-DP+.  Your process basically took 2 drives with Metadata on them and put them into the running system.  
L1 and L2 are partially correct, they can not resolve the issue.
You can resolve the issue by taking the drives back to the other system and installing them.  They could be LEFTOVR, meaning that the original system recognizes them but know the data on them is out of date, this would be if the original system has been powered on.  Or the disks could be re-integrated into the original MSA-DP+ disk-group and you can remove the entire disk-group/Pool.
If that is not an option then push on the support ticket to get an L3 support person who will be able to help remove the disk-meta data from the newly installed drives. 

[klindsay]

@JonPaul Thank you for the quick reply!

If I remove the 2 drives back out of the MSA will the Bad DG go away since there will be 0 disk. Also will this affect the good DG with pool?

[JonPaul]

@klindsay 
Removing the 'rogue' disks will remove the Bad DG.  It will not effect the running DG.  Make sure to select the correct drives.
One way to select the correct drives is to set the 'locate' LED pattern for the drive.

CLI>  set led disk x.x on
This will turn the AMBER led on the disk on for 3 seconds and off for 1 second.  See led descriptions in the MSA 2060 Installation Guide
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00128579en_us