My service tag is [tag removed per TOS] . A little backstory on how my server got in the state its in.
I'm using this box as a ESXi host, I had 6 hard disk installed. I turned the server off and added two more disk and booted into the lifecycle controller to configure the disk. After configuring them with my raid controller (perch310) I rebooted.
Message came up saying “Warning: Power required exceeds PSU wattage. Check PSU” I decided to proceed with booting up because it was only showing that I was at like 150 watts at the time.
It failed to boot and a message appeared saying “scanning for devices please wait”. I let that sit there for awhile before I killed power with the front panel button.
Took the two added drives out so I could try and get it to boot again. Now I’m getting a idrac initialization error at boot along with the message “warning power management firmware not responsive. disconnect and reconnect system input power” f1 to continue boot or f2 to enter system setup.
If I hit f2 I can log into the idrac. Everything looks normal while logged in except I’m not getting any information on the power supply unit or thermal temps. Pressing F1 would get me back to the "scanning for devices. Please wait" where it would sit indefinitely.
I've tried draining the flea power. Using the "I" button to reset the iDrac. Using the RACADM hard reset command. nothing has worked.
My bios and firmware were on BIOS- 2.54 Firmware- 2.41.40.40
I've stepped up my firmware to 2.60.60.60 but am unable to update the bios as it looks like it needs to POST to apply the update which it wont do. It's stuck in the job queue.
I can ping the idrac through out the process but can only access it in the browser after I press F2 to run the system setup process. Once inside the idrac everything looks normal except for the power supply tabs or thermal temps. I started out with two 495watt units. I’ve since installed two 1100 watt PSUs.
I tried to upload the file. But I get an error saying that it's not a valid file format. Exact wording may be slightly different, but that is the jist of it.
It may be preventing backflashing that far because of some newer CPUs won’t work on the older version. There isn’t a newer version of the repair package.
Sere81
6 Posts
18728
0
Posted October 8th, 2018 10:00