====== 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).

===== Getting Into Your BIOS =====

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.

{{:fester:94c6e18bdb6bd389e71de5c5b3531a94.png}}

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

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

===== BIOS Settings =====

==== Quiet Boot ====

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.

{{:fester:d8522b3a234972889e6cae3bfea826b5.png}}

Select the submenu “Boot Feature”.

{{:fester:598b861c7cfd26d240bd607d2c616cc5.png}}

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

{{:fester:121ebb481316a793fd256996eb91c0a4.png}}

==== Watch Dog Function ====

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.

{{:fester:e67357e796d4f007ff943fd86ce3f70b.png}}

==== AES-NI Encryption ====

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.

{{:fester:d8522b3a234972889e6cae3bfea826b5.png}}

Now navigate to “CPU Configurtion”.

{{:fester:1a1fa05bff7f91bae574f5788093b363.png}}

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

{{:fester:3a6c951479ea3763d4012e3156539ff9.png}}

==== AHCI SATA Configuration ====

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.

{{:fester:d8522b3a234972889e6cae3bfea826b5.png}}

Now select “SATA Configuration” from the submenu.

{{:fester:96792cf3d16846247823152940e7d3e8.png}}

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

{{:fester:8ea5f6daec072fd9fb0416c3da60c4ec.png}}

==== IPMI Configuration ====

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.

{{:fester:d9335772f5556d00da6748d7e811cc8c.png}}

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

{{:fester:d5cf4e80c2f921f4618792fb19c62814.png}}

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.

{{:fester:130a9c9c6f0303988f9d1de18f5be876.png}}

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.

==== Boot Order Configuration ====

FreeNAS can be installed in a number of ways. It can be installed from a bootable CD/DVD, a bootable USB stick or even across a network using PXE.

When you boot the server and watch the various pages of information come and go as the server goes through its POST, you may have noticed that a certain key press at the correct time will allow you to boot from an attached storage device of your choice temporarily (i.e. just that one time).

This is fine, but if you install FreeNAS from one particular type of storage device regularly then it might be more convenient to change the boot order of the server.

The boot order is the order in which the motherboard’s BIOS will look for an OS or something it can boot from, on the various storage devices connected to it. This change is persistent (i.e. it applies each time the server is booted).

The regular method by which you install FreeNAS will determine the boot order, if that’s how you want to do things.

Fester favours a USB stick so “USB Key” must be the first device selected in the boot order list. Why? If we had the HDD/SDD (with the installed FreeNAS OS on it) listed before the USB key (with the bootable FreeNAS installation program on it) then if we want to reinstall the FreeNAS OS again, a problem would occur. The BIOS will encounter the installed FreeNAS OS on the HDD/SDD before it encounters the bootable FreeNAS installation program on the USB key and reinstallation will not take place (unless you temporarily alter the order through the key press at POST boot up method).

So if you would like to alter the boot order (it’s completely optional) this is how you do it.

Select the “Boot” page.

{{:fester:8722dc20723bc7a90dd8490ce6e3137e.png}}

Navigate to “Dual Boot Order #1” (“Boot Mode Select” should be set to “Dual” or this part will look different) and select “USB Key” (1), in Fester’s case this is where the bootable FreeNAS intallation program will reside.

Notice how the storage device that contains the actual FreeNAS OS appears further down the list, in Fester’s case it’s the Samsung SSD (2).

{{:fester:ff4eb858ec8001892e675662791d0c9b.png}}

There doesn’t seem to be a lot of information on the configuration of a server BIOS for a FreeNAS installation. I suspect there are other essential settings that need to be made (e.g. power management, etc), but this is all I could find. If I have missed any please let me know and I will try to include them in the guide or you could replace this or any section with your own?