Cannot boot from USB: “Could not create MokListRT: Volume full”

Troubleshooting USB Boot Failures: Resolving “Could not create MokListRT: Volume full” Error

Introduction

Booting from a USB device is a common method for system maintenance, OS installation, or running live environments such as Clonezilla. However, users may sometimes encounter errors that prevent successful booting. One such issue involves error messages related to MokListRT and volume capacity, which can halt the boot process entirely.

Understanding the Issue

A typical error message seen during an attempt to boot Clonezilla from a USB might read:

“Could not create MokListRT: Volume full
Could not create MokListXRT: Volume full
Could not create SbatLeve1T: Volume full
Could not create MokListTrustedRT: Volume full
Something has gone seriously wrong: import_mok_state() failed: Volume full”

In this scenario, the system attempts to generate or access certain trusted key lists (MokListRT, MokListXRT, etc.) necessary for secure boot processes. The repeated message “Volume full” indicates that the storage space allocated for these operations is exhausted, leading to failure in creating or updating required data structures and ultimately preventing the system from booting.

Potential Causes

1. USB Drive Space Limitations: The USB device might not have enough free space to accommodate the necessary files and updates.
2. Corrupted or Improperly Created Boot Media: The USB image may be incomplete or corrupted, causing the system to attempt to write to a read-only or full section.
3. Firmware or Secure Boot Settings: Certain BIOS/UEFI configurations, especially those enforcing secure boot, can interfere with the process.
4. Compatibility Issues: An incompatible or unsupported USB drive or partition setup may cause unexpected errors during boot.

Recommended Solutions

1. Verify USB Drive Capacity and Integrity

2. Ensure that your USB drive has sufficient free space, ideally at least 8-16 GB depending on the image size.

3. Re-create the bootable USB using a reliable tool like Rufus or balenaEtcher, ensuring the ISO image is not corrupted.

4. Check and Modify Secure Boot Settings

5. Enter your system’s BIOS/UEFI settings during startup.

6. Disable secure boot to allow unsigned or custom images to boot.

7. Save changes and attempt the boot process again.

8. Recreate the Bootable USB with Correct Settings

9. Use recommended procedures for creating a Clonezilla bootable USB.

10. Format the USB drive to FAT32 or ex