> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/support/tutorials/linux/how-to-check-bios-or-uefi-on-linux.md).

# How to tell if your server is BIOS or UEFI in GNU/Linux - Plenit

## How to know if your server is BIOS or UEFI in GNU/Linux

Join us in this article and discover **how to know if your server is BIOS or UEFI in GNU/Linux**.

When preparing the migration of machines from any source to the Plenit infrastructure, it must be clear whether the server to be migrated is based on UEFI or BIOS.

Knowing this is really important since machines based on **UEFI are not supported** in the Plenit infrastructure.

In this case, we are going to see how to perform the checks on GNU/Linux systems.

#### Method 1: Checking for the existence of firmware files

The first way we can find out whether the computer is based on BIOS or UEFI is **to check whether the path "/sys/firmware/efi" is present on the system**. If the system is UEFI, the path will exist, but that will not be the case if we are dealing with a BIOS-based system.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FKrmtvVERxmu1yQDOv5bM%2F01_Comprobamos-si-existen-los-ficheros-de-firmware-EFI.png?alt=media&amp;token=93da18cf-81f5-4eb7-9801-aa9fdc86cc5c" alt=""><figcaption><p>Checking whether EFI firmware files exist</p></figcaption></figure>

This, as you can see, is a simple and straightforward way.

#### Method 2: Using efibootmgr

The second way to test it is by using **the "efibootmgr" command**. This is a command that allows you to check whether the system is compatible with UEFI and that, if it is compatible, when run, will generate different variables related to UEFI. If it is a BIOS-based system, a message will appear indicating that EFI variables are not supported.

To use it, the first thing will be to check whether it is available. To do so, you must **run the "efibootmgr" command**, which, if present, will directly show the execution output. If it is not available, it will show a command not found message after which it can be installed.

**The installation varies depending on the GNU/Linux** system distribution:

On GNU/Linux systems **RedHat, CentOS and derivatives** you should use the "yum" command:

**# yum install efibootmgr**

On GNU/Linux systems **Debian, Ubuntu and derivatives** you should use the "apt" command:

**# apt install efibootmgr**

Below, you can see an example of installation on CentOS.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FskvxbIBkHLYN9CJrlNmq%2F02_Instalamos-efibootmgr-para-hacer-consultas-y-pruebas.png?alt=media&amp;token=39627318-41ed-45ec-bf0b-73357bc489e2" alt=""><figcaption><p>We install efibootmgr to make queries and tests</p></figcaption></figure>

Once installed, it can be **run by typing** the command name directly without modifiers **"efibootmgr",** which will directly show the execution output.

**# efibootmgr**

If the system uses UEFI, the associated variable settings will be shown; otherwise, **a message will be displayed indicating that UEFI is not used**, something similar to this message **"EFI variables are not supported on this system"**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F5GZHzdi9WOnnnh21xgBX%2F03_Lanzamos-el-comando-efibootmgr-para-ver-si-tenemos-un-sistema-UEFI.png?alt=media&amp;token=911740aa-0c03-490b-843b-7b66e2d87061" alt=""><figcaption><p>We run the efibootmgr command to see if we have a UEFI system</p></figcaption></figure>

And what do we do if the server is a machine that uses UEFI? Well, all is not lost; we only need to take an additional step, following the method described in the tutorial [How to convert UEFI disks to BIOS on your Windows server](https://docs.plenit.com/support/tutorials/windows/how-to-convert-uefi-disks-to-bios).

#### Conclusions

The query processes described in this article, **how to know if your server is BIOS or UEFI in GNU/Linux,** allow you to quickly and easily check whether a machine uses UEFI or BIOS.

As you can see, these are somewhat more complicated processes than usual, but they have been described in a guided way through well-defined steps so that the reader has no problems.

**Thank you for your trust!**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/support/tutorials/linux/how-to-check-bios-or-uefi-on-linux.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
