Hello Dimitris,
From the log information you have provided you had two issues.
Controller A went down due to the SC suffering a crash. There are no crash logs provided so I cannot determine why the SC crashed.
ERR) 2020-04-29 09:25:39.014 (10) LocalPipe: SC is down
INF) 2020-04-29 09:25:39.126 (11) HEALTH: add unhealthy component controller/controller_a
INF) 2020-04-29 09:25:39.136 (11) iomHealth: unexpected controllerStatus=5215=ControllerStatusUndefined
ERR) 2020-04-29 09:25:39.203 (11) LocalPipe: SC is down
Controller B lost the heartbeat communication with Controller A (but Controller A was up at the time) and due to the lost PCIE link Controller B went down to allow Controlelr A to remain active. Unfortunately, Controller A was going down for an SC crash.
Couple of things you can do.
Check and make sure you have no unwritten cache on both controllers. The cache may have already flushed but while Controller B was going down there was some cache sitting on that controller.
There have been many fixes in newer firmware - some relating to SC stability and PCIE link improvement. I suggest you upgrade your system to the latest firmware versions. Also, confirm your the HBAs on your servers are running the latest firmware and drivers.
As Subhajit mentioned - check the other components on your array by performing an MSA Health Check here:
www.hpe.com/storage/MSAHealthCheck
Download your MSA Log File from your MSA array
Upload the MSA Log File into the MSA Health Check website
Review Results by clicking through the tabs and saving the PDF report
Links to array, enclosure, and drive firmware will be provided
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.