Unsolved
This post is more than 5 years old
3 Posts
0
2356
June 24th, 2018 21:00
idrac initialization error. PowerEdge T320
Hi,
I just won this server in an auction lot and having a **bleep** of a time getting it up and running. For one the admin left a password to log in to windows so that blows, but that's not the main issue.
When I fire it up it goes through the motions and gets stuck at Initializing iDRAC, then reboots, and gives me the Warning! iDRAC initialization error message.
On my options it'll let me go to F2 System Setup, F11 BIOS boot manager, or F12 PXE boot. The lifecycle controller is disabled.
This is the first time I've messed around with one of these and I'm at a loss, I've gone through the user manual and many burned DVDs trying to get utilities to run / Win server to reinstall and still at a loss. Any help is much appreciated.
Thanks!
0 events found
Daniel My
12 Elder
•
6.2K Posts
0
June 25th, 2018 10:00
Hello
The iDRAC is part of the system board. You will need to replace the system board if the iDRAC is not functional. The Lifecycle Controller runs from the iDRAC. If the iDRAC is not functional the LCC will not work.
Before replacing the system board I would suggest disconnecting all unnecessary hardware to see if the iDRAC initializes properly. Incompatible or faulty hardware connected to the system can cause issues, including initialization problems, with other hardware in the system.
http://www.dell.com/support/
Thanks
UNO Javie
3 Posts
0
June 25th, 2018 21:00
Hi Daniel,
I can pull hardware pretty easily, but how much do I want to pull? Will it boot if I pull the RAM? It's pretty bare-bones right now, just 2 RAM sticks and 2 hard drives. Please advise then I'll begin to pull and test.
Thanks!
Daniel My
12 Elder
•
6.2K Posts
0
June 26th, 2018 08:00
System board
CPU
DIMM in slot 1
Control panel, this is where the power button is located
Power supply
Everything else should be disconnected. You should also swap any parts you have more than one of if the issue persists, like memory, to rule out the possibility that the module you are using is faulty.
Aside from that, draining flea power and clearing NVRAM via jumper are the only steps I can think of prior to part replacement. The most likely part would be the system board unless the above steps point to a different part.
Thanks