Disque failed RAID 5 MSA 1050

[testfkjaghgjl]

Bonjour,

Je vous contact car j'ai une problématique, nous avons un client avec une Baie MSA 1050 qui était en version VE270P002-2 où un disque est tombé en panne sur un de mes 2 pools de stockage, il s'agit du Pool A. Ce pool fonctionne en RAID 5 et nous avons donc remplacé le disque défectueux par un nouveau disque aux caractéristique identiques et quand nous l'avons remplacé, aucun job de reconstruction de RAID n'a été fait, le disque apparait en AVAIL, impossible de l'ajouter manuellement au disk group....

J'ai passé la maj firmware VE270P008 en pensant que cela pourrait m'aider mais ce n'est pas le cas je suis toujours au même point.

Mon pool A est composé de disue EG00120JWJNQ en "Revision : HPD2", je n'ai pas pu trouver exactement la même référence donc j'ai mis un disque EG00120JXLWA en "Revision : HPD8" et je ne sais pas si cela peut avoir un lien avec le fait que je suis dans l'incapacité à remonter mon dsique remplacé sur mon RAID.

En vous remerciant par avance de votre retour,

Cordialement.

Google Translated: 

Disk failed RAID 5 MSA 1050
Hello,

I am contacting you because I have a problem, we have a customer with an MSA 1050 Bay that was in version VE270P002-2 where a disk failed on one of my 2 storage pools, it is Pool A. This pool works in RAID 5 and we therefore replaced the defective disk with a new disk with identical characteristics and when we replaced it, no RAID reconstruction job was done, the disk appears in AVAIL, impossible to add it manually to the disk group ....

I updated the firmware VE270P008 thinking that it could help me but it is not the case I am still at the same point.

My pool A is composed of disk EG00120JWJNQ in "Revision: HPD2", I could not find exactly the same reference so I put a disk EG00120JXLWA in "Revision: HPD8" and I do not know if this can have a link with the fact that I am unable to remount my replaced disk on my RAID.

Thanking you in advance for your feedback,

Sincerely.

[ira6655gorby]

The Quest for RAID Reconstruction:
Disk Replacement and RAID 5:
Replacing a failed disk in a RAID 5 configuration should indeed trigger a reconstruction job.
However, it seems your new disk isn’t joining the party. Perhaps it’s shy or lost in the digital forest.
Firmware Update (VE270P008):
You’ve wielded the firmware update spell (VE270P008), hoping it would awaken the RAID reconstruction magic.
Alas, the disk remains in AVAIL, like a wandering spirit.
Disk Compatibility and Revisions:
The disk you replaced (EG00120JXLWA) has a different revision (HPD8) than the original (HPD2).
This mismatch might indeed be causing the hiccup. RAID controllers can be picky about their companions.
The Compatibility Spell:
Here’s what you can try:
Compatibility Check: Ensure the new disk (HPD8) is compatible with your RAID controller and the existing disks.
Manual Addition: If compatibility checks pass, manually add the disk to the disk group. Sometimes, a gentle nudge works wonders.

[testfkjaghgjl]

@ira6655gorby J'ai pu voir qu'il était apparemment possible de mettre à jour les firmware des disques donc de passer de HPD 2 à peut être HPD8 ?

La seule chose que j'ai pu faire avec mon disque était de l'ajouter en tant que disque de spare mais ce n'est pas la config de base.

Pensez-vous que si je fais cette fameuse mise à jour de mes firmwares de disque cela pourrait m'aider à reconstruire mon RAID ?

Google Translated:

I could see that it was apparently possible to update the disk firmware so to go from HPD 2 to maybe HPD8?

The only thing I could do with my disk was to add it as a spare disk but it is not the basic configuration.

Do you think that if I do this famous update of my disk firmware it could help me rebuild my RAID?

[ArunKKR]

Hi, Please check whether the disk group is in FTOL (Fault tolerant and online) state or critical state. If the disk group is in FTOL state it indicates that one of the spares already kicked in and joined the disk group. If the disk group is in critical state , configuring  a replacement drive as spare should ideally allow it to kick in and reconstruction should start. You could launch a putty SSH session and execute the command show disk-groups to verify disk group status.

[testfkjaghgjl]

Thank you for your reply. My disk group is well in “FTOL” status, and not knowing what to do with the new disk I added it as a SPARE disk on my Pool A even if it's not what I wanted to do in the first place, but considering the situation I think I have no choice due to the fact that I'm unable to add it back to my RAID.

[ArunKKR · Accepted solution]

Hi,

If the disk group is in FTOL state it indicates that there was a spare drive in the array, and it kicked in when the original drive failed and joined the disk group.

The replacement drive can be configured as a spare and it will kick in when ever there is a new drive failure.