Hello,
The issue is not that the firmware gets corrupted but that available threads become exhausted. When this happens it does not leave a thread to use for login. There are several reasons this may occur. One is by not signing out of either SMU or CLI connections so that the threads in use are not released correctly and returned as available. There have also been improvements in newer firmware to time out unused threads to return them to an available state.
Keeping the system upgraded does help to avoid known issues which have been fixed in newer code. If you wish to check your firmware on your system you can now do so easily by checking this link: www.hpe.com/storage/msafirmware
Also, to check the overall health of your system and any available firmware versions you can use our new MSA Health Check Tool at the following link: 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 the results by clicking through the tabs and saving the PDF report
Links to array, enclosure, and drive firmware are provided for easy access
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.