MSA 2050 - the controller is not operational

[Waldemar1]

Hi,

i have a problem with one of the controller on MSA 2050 

Controller A is working fine but Controller B is not operational.

I've tried to restart and shutdown the controller B but i've got a message:

Error: The reboot operation cannot be completed because a recovery is in progress.

[ArunKKR]

Hi,

Please check whether the Pools and disk group are healthy.

Remove and reseat the storage controller B to check whether it comes back online.

It's recommended to have a data back up before performing these actions.

[Waldemar1]

Thank you for your reply.

I would like to clarify, can I do this on powered on MSA?

[ArunKKR]

Hi,

Controller B seems to be down already. There shouldn't be any issue in reseating controller B as controller A will be managing the load now. It's recommended to have a data backup before performing such actions. You could verify controller and pool status by executing the below commands:show system show controllers show pools

[Waldemar1]

After re-seating Controller B:

Controllers
-----------
Controller ID: B
Serial Number:
Hardware Version:
CPLD Version:
MAC Address: 00:00:00:00:00:00
WWNN: 
IP Address: 192.168.1.26
IP Subnet Mask: 255.255.255.0
IP Gateway: 192.168.1.1
Disks: 18
Virtual Pools: 2
Disk Groups: 3
System Cache Memory (MB): 8192
Host Ports: 4
Disk Channels: 2
Disk Bus Type: SAS
Status: Not installed
Failed Over to This Controller: No
Fail Over Reason: Not applicable
Multi-core: Disabled Health: Fault
Health Reason: The controller is not present.
Health Recommendation: - Install the missing controller module.
Position: Bottom
Phy Isolation: Enabled
Controller Redundancy Mode: Failed Over
Controller Redundancy Status: Operational but not redundant

[ArunKKR · Accepted solution]

Hi,

Storage controller B seems to require replacement as its reporting status as down despite reseating it. You may log an HPE support case to check for the options.

[Waldemar1]

It has been replaced.

Problem resolved

[Sunitha_Mod]

Hello @Waldemar1, 

That's awesome! 

We are extremely glad to know the problem has been resolved and we appreciate you for keeping us updated.