From d727fbf3ebb1a31af7fbbb74a3b8e0d601a269a3 Mon Sep 17 00:00:00 2001 From: Qrius Date: Thu, 26 Sep 2024 00:11:05 +0200 Subject: Remove build directory --- build/about.html | 23 -------- build/articles/testart.html | 23 -------- build/articles/unbricking_idrac.html | 104 ----------------------------------- build/test.html | 22 -------- 4 files changed, 172 deletions(-) delete mode 100644 build/about.html delete mode 100644 build/articles/testart.html delete mode 100644 build/articles/unbricking_idrac.html delete mode 100644 build/test.html diff --git a/build/about.html b/build/about.html deleted file mode 100644 index e28dae0..0000000 --- a/build/about.html +++ /dev/null @@ -1,23 +0,0 @@ - - - - Quirio - - -
- - -

About

-

this is some about text.

- -
- - - - diff --git a/build/articles/testart.html b/build/articles/testart.html deleted file mode 100644 index 3a7854e..0000000 --- a/build/articles/testart.html +++ /dev/null @@ -1,23 +0,0 @@ - - - - Quirio - - -
- - -

Test article

-

this is some about text.

- -
- - - - 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 @@ - - - - Quirio - - -
- - -

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.

-

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.

-<section id="bios-settings"> -<h2><a href="#bios-settings">#</a> BIOS Settings</h2> -

In the “Serial Communication” menu, make sure everything is set like this:

-
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>
-
-</section> -<section id="boot-an-os"> -<h2><a href="#boot-an-os">#</a> Boot an OS</h2> -

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.

-

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.

-</section> -<section id="setup-your-serial-console"> -<h2><a href="#setup-your-serial-console">#</a> Setup your serial console</h2> -

Serial port has to be configured like this:

-
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
-
-

Your terminal should be configured like this:

-
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.
-
-</section> -<section id="setup-a-tftp-server"> -<h2><a href="#setup-a-tftp-server">#</a> Setup a TFTP server</h2> -

Now you need to put the firming.d6 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.

-</section> -<section id="flash-the-firmware"> -<h2><a href="#flash-the-firmware">#</a> Flash the firmware</h2> -

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.

- -

Good luck

-</section> - -
- - - - diff --git a/build/test.html b/build/test.html deleted file mode 100644 index fdc3647..0000000 --- a/build/test.html +++ /dev/null @@ -1,22 +0,0 @@ - - - - Quirio - - -
- - -

TEST

- -
- - - - -- cgit v1.2.3