HPE EVA Storage
1753626 Members
5287 Online
108797 Solutions
New Discussion

EVA 8400: two I/O modules replaced and stuck in "loading firmware"

 
SOLVED
Go to solution
Dennis_Lee
Occasional Contributor

EVA 8400: two I/O modules replaced and stuck in "loading firmware"

Hi HPE storage experts,

  I have two I/O modules with yellow alert in P2. I saw HPE employee replaced I/O moduled and fixed it before. I buy two I/O modules and replaced but after more than 1 hour, both I/O modules still stuck in "loading firmware".

I google and find these two threads:

https://community.hpe.com/t5/EVA-Storage/EVA-6400-quot-I-O-Module-B-Stuck-in-quot-Loading-Firmware-quot/td-p/7028074#.XmCfayEkuNU

>This tell me to replace a failed FC HDD.

https://community.hpe.com/t5/EVA-Storage/EVA-8400-After-adding-new-disk-enclosure-not-updated-firmware/m-p/6999598#M68333

"If you add or replace an I/O module, the EVA will always check and correct the firmware. After loading the firmware it will reboot the module, if it is redundant.

In your case it is still working, but not redundant (no cables connected yet), hence it cannot reboot. You don't have another choice other to continue and add the other loop."

> This tell me I should make sure it is redundant. But I have two I/O modules failures right now so it can't be redundant anyway.

 

How do I fix it? I have called HPE support center.

EVA8400CV.png

1 REPLY 1
Dennis_Lee
Occasional Contributor
Solution

Re: EVA 8400: two I/O modules replaced and stuck in "loading firmware"

Hi All,

  Fixed. After HPE RC analysis, she identify disk enclosure 14 failed. Although it may show

Disk Enclosure 10 P1(failed) -> Disk Enclosure 14 P2  & Disk Enclosure 14 P1 -> Disk Enclosure 12 P2(failed).

But the fact is Disk Enclosure 14 cause D.E. P1 and D.E. P2 lost connection.

 

Anyway, only HPE RC can find this by running a analysis report.