EFI Shell on Fujitsu PRIMERGY servers

Fujitsu removed the EFI shell access from their BIOS images some time ago for PRIMERGY servers (I believe Ivy Bridge generation or later models), so you cannot bring up EFI Shell in UEFI mode. In normal cases, this is not a problem. However in some cases, EFI shell makes your life easier.
For example, if the OS boot entry is somehow lost, without EFI Shell, you probably need to boot off of a Linux live CD or something to recreate a boot entry. If EFI shell is available, you don't need to do that. You just simple bring up the shell, and mount the EFI partition to execute the OS boot image.
Another example is that if you want to update PCIe card firmware image such as RAID card firmware before installing an OS, you have to use Fujitsu's Update Manager Express to do the update. It will take long time as it will update the whole system (BIOS, iRMC FW, PCIe FW, etc.). If you have EFI Shell, you can run EFI utilities to update firmware, and it will take less time.
Although Fujitsu disabled EFI Shell, there is still a way to use EFI shell on PRIMERGY servers.

Here are the instructions.
  1. Download the EFI shell binary from tianocore.
  2. Format your USB flash drive in FAT32.
  3. Create the \efi\boot folder.
  4. Copy the downloaded binary to \efi\boot, and rename the file to bootx64.efi.
  5. Boot the PRIMERGY server off of the USB device in UEFI mode.

You can extract the USB EFI shell environment as a HDD image, and mount it via iRMC Remote Storage. It's handy.

I put EFI utilities like LSI's storcli, Intel's bootutil, etc. to this, and created a HDD image as "efitools.img", so I can flash Fujitsu RAID firmware (ROM file), or change the boot mode (PXE or iSCSI) for Intel-based network cards on any PRIMERGY servers.

No comments:

VMware Horizon View Composer Installation Failure (Error Code: 1603)

If you see a VMware Horizon 7.x View Composer installation failure with the error code 1603 when you install it on a Windows Server VM, you ...