So, the disk will come back in as 'unassigned'. Then it's just a matter of adding it to the group. It shouldn't cause any problems at all. You *may* have to 'initialize' the disk (SMcli or GUI depending on the firmware), and then you can add it to the group.
The SMcli command is: start physicalDisk [enclosureID,slotID] initialize
I hope that helps. Let me know if you have any questions.
Hi thanks for the reply, I want to purchase two new disks and assign the old raid 5 member with the two new disks to a new group, are you saying the SAN will not care that the old disk was part of the in place active raid 5 disk group?
That's exactly what I'm saying. It *should* come back in as unassigned. If you run into some trouble with it (which is not likely) you *may* have to initialize the disk, but other than that, it should be a smooth add.
DELL-Daniel Ca
243 Posts
0
November 24th, 2015 08:00
Hello, xander77.
So, the disk will come back in as 'unassigned'. Then it's just a matter of adding it to the group. It shouldn't cause any problems at all. You *may* have to 'initialize' the disk (SMcli or GUI depending on the firmware), and then you can add it to the group.
The SMcli command is: start physicalDisk [enclosureID,slotID] initialize
I hope that helps. Let me know if you have any questions.
xander77
2 Posts
0
November 25th, 2015 01:00
Hi thanks for the reply, I want to purchase two new disks and assign the old raid 5 member with the two new disks to a new group, are you saying the SAN will not care that the old disk was part of the in place active raid 5 disk group?
Thanks
DELL-Daniel Ca
243 Posts
0
November 25th, 2015 07:00
That's exactly what I'm saying. It *should* come back in as unassigned. If you run into some trouble with it (which is not likely) you *may* have to initialize the disk, but other than that, it should be a smooth add.
Let me know if you have any issues.