[[fester:prelim_bios]]

This is an old revision of the document!


Configuring the BIOS

We now need to configure the BIOS of the server motherboard.

You can do this via a keyboard and monitor attached to the server or through IPMI as outlined in a previous section.

The settings and screen shots are all taken from a Supermicro X10SRH-CLN4F, but most are applicable to most server motherboards (I would imagine).

In order to gain access to the motherboard’s BIOS the user is required to press a certain key at a certain point in time (usually as the POST messages are displayed).

Consult your motherboard documentation to find out how to gain access to your motherboard’s BIOS.

On Fester’s motherboard it is done by pressing the “DEL” key at a specific point.

Incidentally, motherboards usually display a screen at some point during the POST process that tells you what key to press, something like this.

When you have access to the BIOS it’s time to configure it.

Most BIOS settings are navigated using the “←→↑↓” keys.

This setting is entirely optional.

It determines if POST messages are displayed on screen or a graphic logo (so the POST messages are hidden from view) when you first turn on the server. Fester likes to see the POST messages so I disabled this function.

Navigate to the “Advanced” page.

Select the submenu “Boot Feature”.

Now go to “Quiet Boot” and select “Disabled”.

Remain in the “Advanced → Boot Feature” page and select “Watch Dog Function”.

The watch dog function serves to reboot the server if it experiences an error it cannot recover from (and so hangs) for more than 5 minutes. It works by starting a 5 minute count-down timer when the server hangs. When this timer reaches zero the system is forced to reboot.

When I first tried this in FreeNAS it caused my system to spontaneously reboot every 5 minutes even though the system was not hanging, so I disabled it.

If you intend to encrypt the information on your storage drives then you need to enable this in the BIOS.

This can be useful as it allows a failing HDD in a vdev to be discarded without worrying about wiping the information before disposal.

Go to the “Advanced” page.

Now navigate to “CPU Configurtion”.

Then scroll down (it is towards the bottom) to “AES-NI” and select “Enable”.

There are certain advantages to putting the SATA controller in AHCI mode. By enabling this option any SATA devices connected to the SATA ports on the motherboard will operate in AHCI mode.

Go to the “Advanced” page.

Now select “SATA Configuration” from the submenu.

Now navigate to “Configure SATA as” and select “AHCI” from the options.

You do not have to configure the IPMI of the server through the BIOS. You can use the IPMI web GUI which I will cover in a later section. However, if you decide to do this through the BIOS the following should help.

Go to the IPMI page.

Now select “BMC Network Configuration” (BMC=Board Management Controller and is the hardware through which IPMI is managed and implemented on the motherboard).

Navigate to the “Update IPMI Lan Configuration” and select “Yes” (1). At this point the greyed out text below should become active (it may go from grey to blue) allowing you to input your own values.

In “Configuration Address Source” select “Static” (2).

In the “Station IP Address” text box (3) type in an IP address of your choosing. Make sure you give it an IP address that is outside the range of the DHCP server in the router (Fester used 192.168.0.2).

Now put in the subnet mask of the private network which you obtained earlier in the “Subnet Mask” text box (4) (Fester’s was 255.255.255.0).

Now place the Default Gateway IP address in the “Gateway IP Address” text box (5) if it is not already there.

You have now assigned a static IP address to the IPMI web GUI. We will now always know where to find the IPMI GUI and it will not change even when the router gets rebooted.

  • fester/prelim_bios.1465579935.txt.gz
  • Last modified: 2016/06/10 17:32
  • by dan