This post is more than 5 years old

1 Rookie

 • 

10 Posts

8534

July 13th, 2018 06:00

Cannot update PERC H310 Firmware

Hello, I have a T420 server with a PERC H310 adapter on 20.10.2-0002 firmware. The Dell support page for my server shows the latest firmware as 20.13.3-0001. I cannot update the firmware no matter what I try. My server BIOS is at the latest which is 2.6.0. Here's what I have tried so far. 

1) Lifecycle controller - The H310 adapter shows in inventory but does not show in the firmware update section. I have tried to use the Windows firmware files on a USB but the files are not recognized. 

2) I downloaded all the Windows update packages but when I try to execute the program it says it's not compatible with my 64bit OS which is Windows 2012 R2.

I have two H310 adapters with the exact same firmware. I have installed them separately and they behave the same. Neither will update to the latest firmware. 

When I login to iDRAC Enterprise and click on Storage>Controllers I get a RAC0503 error. 

I need to get this server deployed. Any suggestions?

 

Thank you!

 

 

1 Rookie

 • 

10 Posts

July 15th, 2018 18:00

Hi Daniel, 

I was not aware there were different versions of the same H310 adapter. It seems the H310 pn HV52W I purchased cannot be upgraded to the firmware from my T420 support site. 

Thank you for educating me.

10 Elder

 • 

6.2K Posts

July 13th, 2018 10:00

Hello

Check the controller for a part number. There should either be something listed as DPN or DP/N or Dell Part Number. You are looking for a 5 digit alphanumeric. The PPID contains the part number. If you locate a 25 digit PPID then the fourth through eighth  digits are the part number(CN0456780000000...)

Also, make sure you are able to enter the controller BIOS. It should be CTL R during boot. If you are unable to enter the controller BIOS then it may not be enabled or initializing properly. You can't update the firmware on the controller if it is not functional. You will need to resolve that issue first.

The ability of the update package to run in the operating system is not reliant on the controller. The error you received about the package not being compatible with the operating system is a separate issue. You likely downloaded the wrong package for your OS. Make sure your OS is in the supported OS list of the download page.

http://www.dell.com/support/

Thanks

1 Rookie

 • 

10 Posts

July 13th, 2018 14:00

Hi Daniel,

Thank you for the quick response. I greatly appreciate it.

My adapters have the following part numbers. 012T is currently installed. 

DP/N 0HV52W    CN-0HV52W-75435-360-012T-A00

DP/N 0HV52W    CN-0HV52W-75435-360-0313-A00

I can access the H310 BIOS with a CTL R, no problem. 

Regarding the Windows Update Packages, I agree that it's a separate issue but I'm not sure why I am having a problem. I have made sure I am using the correct package for Windows 2012 64bit.

I have decided to load VMware since that is my longterm anyway. I also installed Perccli for VMware 6.5. The controller shows up fine using the show command. (see below output) When I try to flash the adapter it says the file is corrupted. I have downloaded it many times with the same result. I got the ROM file from the Windows Update package. Am I suppose to use a different file?

 

[root@host2:/opt/lsi/perccli] ./perccli show

Status Code = 0
Status = Success
Description = None

Number of Controllers = 1
Host Name = esxi2
Operating System = VMkernel6.5.0

System Overview :
===============

----------------------------------------------------------------------------
Ctl Model Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth
----------------------------------------------------------------------------
0 PERCH310Adapter 8 1 0 0 0 0 Msng On 3 N 0 Opt
----------------------------------------------------------------------------

Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=DG NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled _Patrol Read|DS=DimmerSwitch|EHS=Emergency Hot Spare
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit
Hlth=Health|Safe=Safe-mode boot

 

[root@host2:/opt/lsi/perccli] ./perccli /c0 download file=/vmfs/volumes/temp/H310/Firmware/FW6325A.rom
Download Completed.
Flashing image to adapter...
Controller = 0
Status = Failure
Description = image corrupted

 

 

10 Elder

 • 

6.2K Posts

July 13th, 2018 14:00

Part HV52W is not showing in the part list of a T420. It is showing as validated for several workstations. The workstation version of our PERCs often use a different firmware and respond with a different device ID than the version for our servers. The cards you have show as validated for the Precision T3600, T5600, and T7600. I suggest using the firmware update on the support page of one of those systems.

Updating PERC firmware from Vmware is not supported. I suggest using our Support Live Image. Boot to SLI and use the Redhat firmware package. You can also update our PERCs through the iDRAC web interface using Windows Dell Update Packages. I suggest using the 32-bit version. I think support for the 64-bit version was added, but I tend to have issues with it. I would use SLI first. Since the controller you are using is not supported on this server I would only use the iDRAC to update it as a last resort.

https://www.dell.com/support/contents/article/product-support/self-support-knowledgebase/enterprise-resource-center/enterprise-tools/support-live-image

Thanks

1 Rookie

 • 

10 Posts

July 17th, 2018 11:00

Daniel,

I am going to purchase an H310 that is compatible with my T420. Do you show p/n 3P0R3 as compatible? 

Thank you.

10 Elder

 • 

6.2K Posts

July 18th, 2018 09:00

Yes, I show 3P0R3 in the part list of the T420.

Another option would be to force flash the server version firmware onto the cards you have. It is my understanding that the only difference between the cards is firmware. If you force flash the server version firmware onto the card it will change the device ID and report as that version of the card to all of our utilities. Force flashing is very risky and could cause the cards to not function.

We do not support cross-flashing our controller firmware, so this is something you will need to figure out on your own or get community assistance with. Also, don't let this be confused with cross-flashing non-Dell firmware onto our products. Anything that could be seen as copyright infringement is a terms of use violation on our forums. You can discuss cross-flashing firmware between our PERCs, but please do not discuss putting non-Dell firmware onto our controllers.

Thanks

No Events found!

Top