storeonce5100 disk replacement problem.

[yoo1]

There are a total of 3 expansion JBOD enclosures connected to the StoreOnce 5100 system. Currently,

JBOD1 has 1 failed disk, JBOD2 has 1 failed disk, and JBOD3 has 2 failed disks, making a total of 4 failed disks.

What is the safest way to replace the disks in this situation?

Is it acceptable to replace one disk at a time in each enclosure simultaneously, or

should the disks be replaced one by one in sequence? Please provide an appropriate response.

[yilmazaydin]

Hi @yoo1 .
StoreOnce 5100 has separate RAID groups of each JBOD - RAID6 (9+2+1 HotSpare).
So you can replace disks in each JBOD in parallel.

Replacing 4 disks will reduce the performance of the disk groups - please take this into account.

I also strongly recommend that you set up notifications from the StoreOnce device about  events - this will help you avoid critical situations with a device that is no longer produced and no longer supported.

Best Regards, YA. 

[sbhat09 · Accepted solution]

Hello @yoo1,

As @yilmazaydin rightly said every enclosure is a separate logical disk with separate RAID group. So, no harm in replacing all 4 failed drive at once.

In the enclosures where 1 disk failed, the fresh disk will assume the role of spare. That will not hit on perfomance. But the 2 disk replacement in an enclosure will take some time and performance impact till the RAID rebuild completes. My recommendation is not to run too many backup/replication jobs till the new drives normalise as there may be slight impact on performance.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

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

Thank you for being a HPE valuable community member.