Had the same problem with a new T320 out of the box. It shipped with 2.10.10.10 which should have been fine. I ended up downgrading to 1.66.65 and then upgrading back to 2.10.10.10 and that seemed to fix the issue.
Another new T320 has the same issue but it looks like an issue with the PERC H710P and a PCIE training issue. Working on getting that replaced.
Thanks for listening ..
Then I do a downgrade ? Downgrading that ? iDRAC ? And then come the latest version ?
Where can I see the current version ... and which version is available for update / download ? It is according to the server model ? in my case the T320 ...
I have had this issue on my T620 now for several years. When I posted back in 2013 some folks reported fixing it by shutting down and unplugging the power for 5 min. I tired that along with all the firmware updates to the idrac, as a matter of fact I just upgraded to latest idrac on Friday and still have the issues.
I concluded myself that since the SUU doesn't work for my H310, somehow I received a H310 for precision workstation (not the poweredge) - apparently there is 2 versions of the controller, or so it appears to me since the SUU through LM didn't work but the dos firmware update for precision h310 did work. (what a pain to get the server to boot to dos)
Not sure if this is your same situation, id be interested to see what you find.
richochet
8 Posts
3869
0
Posted June 29th, 2015 10:00
Had the same problem with a new T320 out of the box. It shipped with 2.10.10.10 which should have been fine. I ended up downgrading to 1.66.65 and then upgrading back to 2.10.10.10 and that seemed to fix the issue.
Another new T320 has the same issue but it looks like an issue with the PERC H710P and a PCIE training issue. Working on getting that replaced.