Quantcast
Channel: PowerEdge General HW Forum - Recent Threads
Viewing all articles
Browse latest Browse all 5887

M1000e PMBus issue / FRU access failed

$
0
0

Hi All,

Have an M1000e, with 4 PSU's installed, 9 fans, 6 switches, 4 M610s - all UK based.

Today went to Home Page >> Power >> budget Status and noticed :

Name  Power State  Input Volts  Input Current  Output Rated Power 
PS-1  Online   239.5 V  0.8 A   2360 W 
PS-2  Online   240.5 V  0.8 A   2360 W 
PS-3   
PS-4   
PS-5  Online   0.0 V   0.0 A   2360 W
PS-6  Online   0.0 V   0.0 A   2360 W

Which meant PS-5/PS-6 look strange, so after grabbing another PSU from spares and doing a swap round, working PSU in slot 4 brings up failed, moved PS-5 (showing online but 0.0v) to slot 3, comes up online and working plus all voltages, moved spares PSU from slot 4 to Slot 3 comes online, move it to slot 5 shows failed.

So its looknig like PS-4, PS-5 and probably PS-6 have an issue.  Both lights were on PS-5 before swap round, PS-6 still has both lights AND shows healthy in GUI, plus Online, but, as above shows 0.0V and 0.0A.

We also changed from Power Supply redundancy (where above table was taken) to AC Redundancy - no change.

 
So in RACADM logs and CMC logs in GUI, we have lots of :

PSU6 PMBus readings suspended for 28800 s due to errors.
PSU5 PMBus readings suspended for 28800 s due to errors.

and

PSU4 FRU access failed.

Last updated Chassis Power Supplies :

Name  Power State  Input Volts  Input Current  Output Rated Power  
PS-1  Online   239.5 V  0.8 A   2360 W  
PS-2  Online   240.0 V  0.8 A   2360 W  
PS-3  Online   239.0 V  0.8 A   2360 W  
PS-4  Failed   0.0 V   0.0 A   
PS-5  Failed   0.0 V   0.0 A   
PS-6  Online   0.0 V   0.0 A   2360 W

(Yes I got another spare PSU to fully populate to see what was going on) :-)

Doing a quick google of the 2 above errors brings nothing up - hence being here - Any thoughts ? :-)

 


Viewing all articles
Browse latest Browse all 5887

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>