diff options
| author | Qrius <[email protected]> | 2024-09-26 00:11:05 +0200 |
|---|---|---|
| committer | Qrius <[email protected]> | 2024-09-26 00:11:05 +0200 |
| commit | d727fbf3ebb1a31af7fbbb74a3b8e0d601a269a3 (patch) | |
| tree | 780116dafee47066a81361b080735b0952110bf4 /build/articles/unbricking_idrac.html | |
| parent | 132286c7798c79a900e88e250a68d5da62fd8fb8 (diff) | |
| download | skaldpress-d727fbf3ebb1a31af7fbbb74a3b8e0d601a269a3.tar.gz skaldpress-d727fbf3ebb1a31af7fbbb74a3b8e0d601a269a3.zip | |
Remove build directory
Diffstat (limited to 'build/articles/unbricking_idrac.html')
| -rw-r--r-- | build/articles/unbricking_idrac.html | 104 |
1 files changed, 0 insertions, 104 deletions
diff --git a/build/articles/unbricking_idrac.html b/build/articles/unbricking_idrac.html deleted file mode 100644 index dd404bb..0000000 --- a/build/articles/unbricking_idrac.html +++ /dev/null @@ -1,104 +0,0 @@ -<!DOCTYPE html> -<html> - <head> - <title>Quirio</title> - </head> - <body> - <article aria-label="Article"> - <div class="article-meta"> - <span>Published at - <time datetime="04.04.2024"> - 04.04.2024 - </time> - </span> - </div> - - <p>So, the iDRAC6 on my Dell R710 got bricked when attempting to update the lifecycle controller to 1.6.0.73. -The front lcd was dead, and also the rear service led was unlit. -I attempted to drain the power, that made no difference. -I attempted to load <code>firmimg.d6</code> onto a FAT formatted SD card and put it int the vFlash. -But no reaction whatsoever. -It looks to me like everyone ("on the internet") is saying this means a new motherboard, -but I was able to reflash the chip using the BIOS's serial console.</p> -<p>First I needed to get into the BIOS settings, to change some settings there: -When the iDRAC is in this state, the BIOS will complain that it cannot contact the RAC, -and this will make it attempt a reboot. If you wait and let it reboot, -the second time it figures out it cannot contact the RAC it will let you press <code>f1</code> -to continue boot <code>f2</code> to open BIOS settings. -If you disconnect the boot drive and press <code>f1</code> -it will attempt to boot using PXE, when that fails. -You will get the same prompt, -with the additional option of pressing <code>f11</code> to choose the boot device.</p> -<section id="bios-settings"> -<h2><a href="#bios-settings">#</a> BIOS Settings</h2> -<p>In the “Serial Communication” menu, make sure everything is set like this:</p> -<pre><code>Serial Communication …………………… On with Console Redirection via COM2 -Serial Port Address ……………………… Serial Device1=COM1,Serial Device2=COM2 -External Serial Connector ……… Serial Device 1 -Failsafe Baud Rate ………………………… 115200 -Remote Terminal Type …………………… VT100/VTZZ0 -Redirection After Boot ……………… Enabled</code></pre> -</code></pre> -</section> -<section id="boot-an-os"> -<h2><a href="#boot-an-os">#</a> Boot an OS</h2> -<p>Now you should boot an operating system, I booted Linux MX from a USB stick. -But you will probably be fine with the OS you have installed as well.</p> -<p>When you have an OS running, you will need some kind of serial console -(could use just screen and ttys or something) I used Putty.</p> -</section> -<section id="setup-your-serial-console"> -<h2><a href="#setup-your-serial-console">#</a> Setup your serial console</h2> -<p>Serial port has to be configured like this:</p> -<pre><code>Port/address/device: /dev/ttyS1 (For windows it should be COM2) -Baud rate (speed in Putty): 115200 -Data bits: 8 -Pairity: None -Stop Bits: 1 -Flow Control: Hardware -</code></pre> -<p>Your terminal should be configured like this:</p> -<pre><code>Function, arrow and ctrl keys should be set to Terminal Keys or VT100+ -Backspace key sends should be set as Ctrl+H -Emulation should be VT100/220 or auto, NOT ANSI. -</code></pre> -</section> -<section id="setup-a-tftp-server"> -<h2><a href="#setup-a-tftp-server">#</a> Setup a TFTP server</h2> -<p>Now you need to put the <code>firming.d6</code> on a tftp server. -I just downloaded the newest firmware from downloads.dell.com -(in my case, the iDRAC was running the latest version last time it worked) and extracted the firmimg.d6 -from the EXE file. -I started a TFTP server on my laptop on the same network as the dedicated iDRAC Enterprise NIC port. -and put the firmware image on the root there. -You could in theory also start a TFTP server on the OS you are running on the server.</p> -</section> -<section id="flash-the-firmware"> -<h2><a href="#flash-the-firmware">#</a> Flash the firmware</h2> -<p>At this point you should connect to the serial console using the terminal/console you set up earlier. -Now, if you press Enter in the console, you should get a Firmware recovery menu.</p> -<ul> -<li>Setup the iDRAC Enterprise IP (so it can connect to the TFTP server). -If there is a DHCP server on that network, press the number of the action mentioning DHCP (9), -and this should happen automatically.</li> -<li>Select the TFTP server by pressing 7. -If you have the firmimg.d6 on the root of the TFTP server, -you don't have to configure anything else.</li> -<li>Hit the option that mentions Firmware Upgrade. -This will download the firmware image and flash it. -This will take a few minutes, and then the RAC (NOT THE OS YOU ARE RUNNING) will reboot, -and you should hear the fans change speed and the LCD should turn on.</li> -<li>When the RAC is updated with this new firmware, the serial console should become unresponsive.</li> -<li>When everything seems to be done “doing things”, -and you have waited a few minutes extra just to be sure. -You can now reboot the server, at this point you should see the “System services” again.</li> -<li>Time to reconfigure the iDRAC and the BIOS again, as everything probably has been wiped :)</li> -</ul> -<p>Good luck</p> -</section> - - </article> - </body> -</html> - - |