User:Jepio/EFI Shell for recovery
UEFI firmware is great. It's easy to use and transparent - the booting happens from a FAT formatted partition called the EFI System Partition (ESP). The files that can be loaded are in the EFI executable format and have a .efi suffix. UEFI implementations are supposed to provide users with a built-in boot manager whose entries are stored in the NVRAM. This boot manager should allow the registration and selection of entries. The entries can be adjusted using Efibootmgr. The kernel can be configured with an EFI stub which allows it to be directly booted by the firmware. Therefore UEFI has effectively rendered separate boot loaders obsolete, at least for most use cases.
Bootloaders only have a couple of advantages left over the firmware bootloader:
- consistency - UEFI implementations can vary strongly in functionality and standards compliance
- recovery solutions
While GRUB provides the grub command line for recovering from a misconfigured system, with minimal effort it is possible to provide the same level of functionality using UEFI components. The goal of this guide is to provide a standardized UEFI based recovery solution.
A part of the UEFI specification is a sub-specification for a shell. This shell is based on DOS and Unix shells and its purpose is to allow manual running of EFI applications and interacting with the firmware. Basic usage instructions for the UEFI shell can be found in . For more details it is best to dive directly into the specification .
There are two problems with this shell:
- it is not provided with all distributed firmware
- it has limited file system support
Only FAT filesystem support is mandatory for UEFI firmware. Some vendors (like Apple, for obvious reasons) implement drivers for other filesystems. If the shell is to be useful for recovery purposes both points need to be addressed.
Obtaining/installing the UEFI shell
In the case of firmware with the shell built-in, it should be accessible by choosing it from the boot menu which can usually be accessed by pressing F12 during boot.
The Tianocore EDKII project provides a toolkit for building EFI applications. It provides the source code for an UEFI Shell executable along with a prebuilt binary versions of it. The binary version can be downloaded from here.
To install the shell simply place it in your ESP partition. The existence of an fstab entry for this partition at the standard /boot/efi location will be assumed.
mkdir -p efi/boot/
wget https://svn.code.sf.net/p/edk2/code/trunk/edk2/ShellBinPkg/UefiShell/X64/Shell.efi -O bootx64.efi
The shell executable has been saved in the default boot location for UEFI firmware. In the absence of a better boot entry, the default behaviour is to boot a hard drive by finding the first ESP and executing \EFI\BOOT\BOOTX64.EFI (\ path separators and lack of case sensitivity are both properties of the FAT filesystem).
Obtaining filesystem drivers
Filesystem drivers in the EFI format can be obtained from http://efi.akeo.ie/. All that needs to be done with them is to place them somehwere on the ESP partition.
mkdir -p efi/shell
wget -nd -np -r -A efi http://efi.akeo.ie/downloads/efifs-0.7/x64/
This package contains drivers for all commonly used filesystems, among others:
- ext4/xfs/btrfs for Linux
- ufs/zfs for *BSD
- HFS+ for OSX
Loading the modules
A startup script can load the filesystem drivers on every start of the UEFI shell. This startup script is shown below.
echo -off cd efi\shell\drivers echo "Loading drivers:" for %d in *.efi load %d endfor echo "Reloading filesystems" map -r
This script should be located in the root of the ESP partition, which has been mounted at /boot/efi
Testing under Qemu
The above configuration should be tested before relying on it. Thankfully this can be done without leaving your system by using Qemu. First we need to obtain an UEFI implementation for use with Qemu. This is also provided by Tianocore under the name OVMF.
unzip OVMF-X64-r15241.zip OVMF.fd
We will allow qemu direct access to the ESP so make let's make a packup of it before.
tar cf efi.tar efi/
Assuming the block device on which the ESP is located is /dev/sda1 the following qemu invocation will allow us to test our recovery solution:
qemu-system-x86_64 -bios OVMF.fd -hda /dev/sda1 -boot c
Newer builds of OVMF are available in this Fedora repository. They need to be unpacked using app-arch/rpm2targz.
This guide has prepared a recovery solution for times when the boot configuration of a UEFI based system is wrong. An UEFI Shell application will be launched when the firmware is told to boot from the harddrive and will load drivers for all conceivable filesystems. This allows access to many different filesystems which allows booting other EFI applcations or even to recover data by moving it between filesystems.
- ↑ 1.0 1.1 Intel's articles on the UEFI shell and scripting it
- ↑ 2.0 2.1 The UEFI shell specification v2.0
- ↑ https://edk2.groups.io/g/devel/topic/patch_shellbinpkg_remove/31209298