Hmmm...I may have stumbled on the answer. It appears that the "new" disk was being viewed as though it had a foreign (RAID) configuration on it. I was able to "clear" that foreign configuration, and the disk appeared as "ready". I then added it as a hot spare, and a few moments later, it's status changed to "rebuilding". Fingers crossed...
foreign means this new drive was part of another virtual disk before. As the drive have metadata of its previous virtual disk it is shown as foreign. By clearing the foreign you deleted this metadata which made the drive to be available to use in another virtual disk.
Hi, On-The-Move, thanks for choosing Dell. I saw the picture of the LEDs you posted and it looks just fine by me. May I ask why you are doing what you're trying to do?
Please take another look at the picture I posted. Yes, the 8-Bay (RAID 6) array is doing fine. But that's not what I was posting about. LOOK UP!
See the two icy box caddies above the 8-bay array? Those two bays hold the OS HDDs, configured in a RAID1 array. It was one of those that had failed, and, having added a replacement drive, I was having issues having it recognised as "ready", so the H310 controller would rebuild it.
As Dell-Shine K notes, the replacement drive had likely been part of an array at some time in the past...I needed to clear its residual config. so the controller would recognise it as in a "ready" state.
From there, it was as simple as adding it as a hot spare to the RAID1 array, and the rebuild kicked off a few minutes later.
I'd off-lined the Server during the process (booting OMSA from USB). As a result, the rebuild took ~ 3 hours and is now complete.
On-The-Move
1 Rookie
•
16 Posts
0
December 29th, 2021 18:00
Hmmm...I may have stumbled on the answer. It appears that the "new" disk was being viewed as though it had a foreign (RAID) configuration on it. I was able to "clear" that foreign configuration, and the disk appeared as "ready". I then added it as a hot spare, and a few moments later, it's status changed to "rebuilding". Fingers crossed...
DELL-Shine K
4 Operator
•
3K Posts
0
December 29th, 2021 22:00
foreign means this new drive was part of another virtual disk before. As the drive have metadata of its previous virtual disk it is shown as foreign. By clearing the foreign you deleted this metadata which made the drive to be available to use in another virtual disk.
DELL-Young E
Moderator
•
5.4K Posts
0
December 29th, 2021 23:00
Hi, On-The-Move, thanks for choosing Dell. I saw the picture of the LEDs you posted and it looks just fine by me. May I ask why you are doing what you're trying to do?
On-The-Move
1 Rookie
•
16 Posts
0
December 30th, 2021 00:00
Hi DELL-Young E,
Please take another look at the picture I posted. Yes, the 8-Bay (RAID 6) array is doing fine. But that's not what I was posting about. LOOK UP!
See the two icy box caddies above the 8-bay array? Those two bays hold the OS HDDs, configured in a RAID1 array. It was one of those that had failed, and, having added a replacement drive, I was having issues having it recognised as "ready", so the H310 controller would rebuild it.
As Dell-Shine K notes, the replacement drive had likely been part of an array at some time in the past...I needed to clear its residual config. so the controller would recognise it as in a "ready" state.
From there, it was as simple as adding it as a hot spare to the RAID1 array, and the rebuild kicked off a few minutes later.
I'd off-lined the Server during the process (booting OMSA from USB). As a result, the rebuild took ~ 3 hours and is now complete.