the RAID Group being shown may be the internal/private one for the Pool it is a member of. Where are you seeing this ?

I would check from naviseccli also to get more verbose info;

naviseccli -h ipspa -getdisk 0_0_22

Check your Pool properties to verify the disk is a member.

Also, with Permanent sparing, there's no real reason to 'failback' the hot spare drive, it's not necessary.

tnx Dear Brett@s

My pool disk members is as below:Disk 22 isn't its member!!!! should I expand my pool after I seat disk 22 then copy to hit spare or not?

I didn't expand pool after reseating new disk.is it wrong?

Hardware--->Disks--->disk22----->Properties

What are the properties on disk 24 now ?

..and I would get some sp collects done and log an SR.

Disk 24 screen shot

Hello,

If I understand correctly:

- Disk 0.0.22 failed, and 0.0.24 took its place in the pool.
- You replaced 0.0.22, and it showed as unbound, ready to act as a spare.

- You Copied 0.0.24 to a spare.

- Now you see 0.0.22 in RG 58 and 0.0.24 as an unbound spare.

Correct?

- Are you sure you have no RAID Group 58 created under Storage > RAID Groups?

- Can you put more screenshots of the RAID Groups tab, refresh Unisphere, and show the pool's used drives again?

As mentioned before, it'd be easier to check SP Collects, which you should open an SR for. Also for your reference, you could have either used the copytodisk CLI command, or used the drive mobility feature, both options are explained in KB https://support.emc.com/kb/305286 ("How does next-generation VNX (MCx/05.33) choose hot spares?").

Adham

absoultly right,as you see I never have RAID group

DEar glen

I know the difference between VNX1 and VNX2.you are right in vnx2 every unbound disk may consider for spare.

so how can I replace 22 in my pool?Where I was wrong?

The way the VNX2 (VNX 54xx) works for hot spares is different from VNX1. When the hot spare (0-0-24) replaced 0-0-22, disks 0-0-24 became part of the Pool. When you inserted the new 0-0-22, that disk then became a new, possible hot spare. All unused disks are potential hot spares.

From KB 306286

What if the customer wants to keep the disk configuration the same and doesn't want the drives to move due to the permanent sparing?

If the customer wants to keep RAID Groups within the same Bus, Enclosure, Disk ( B.E.D.) location there are two options:

1. Use the MCx Drive Mobility feature after the rebuild has completed to the spare.
2. Use the copytodisk CLI command to copy the data back to the original disk slot.

This means that you should use the Naviseccli command to move the data from 0-0-24 to the new 0-0-22. 

As for the rsaid group that the new 0-0-22 now shows, select the Properties for disk 0-0-21 and see what you get? In Pools, the disks are configured into Private raid groups.

glen

I'm not completely sure, but maybe using the GUI to do the second copy to hot spare (disks 24 -> 22), although that seems to have worked.

When a disk fails and copies to the hot spare, once it's completed, you can remove the failed disk, then take the hot spare and move it to the empty slot where you removed the failed disk (Drive mobility). Once it's powered up, take the new disk and put that in slot 24 for the new hot spare.

The KB implies that you must use the CLI command to copy the data from the hot spare back to the new disk. I'm not certain what happened with 0-0-22 after you ran the copy to disk command - in the Disk Properties the "Storage Pool Name" should be the name of the Pool. Why it's showing as raid group 58 is not clear to me.

Is disk 0-0-22 still showing RG 58 when you look at the properties of the disk 0-0-22? What is the Pool Properties/Disks showing?

I tried coping to a Hot Spare from one of the disks in a Pool (1-0-1 is the original, 1-0-0 is the hot spare) - I can see it copying on the Pool Properties

In the Disk Properties I can also see the disk (1-0-1) copying to the hot spare (1-0-0).

For each of the disks it looks the same 1-0-0 is the Hot Spare) - they both show up in Pool 0

glen

Tnx Glen

If I want to use Drive mobility it requires down time and it seems it is not a good way for replacing hard disk.

for Tshoot I tested another thing.I right clicked to disk 22 and select copy to hot spare option.Both of my disk went to rebuild status(22 and 24) and after it finished I saw disk 24 is my in pool and disk 22 is unbound status.

I repeated this process again.R click on disk 24 and select copy to host spare (disk 24 and 22 went to rebuild status) but after it finished disk 22 didn't go to pool and it shows it is a member of RAID group58.realy crazing issue !!!

any idea ?

It is worthwhile to mention that all my disks in pool is hitachi and my new disk on bay 22 is seagate.does it cause this problem or not?