Common problems and their solutions
Learn to solve some common problems.
Unknown type in component table entry
Symptom
An attempt to boot a Linux volume that is prepared for
secure boot fails, and a message similar to the following is
displayed on the console:
MLOEVL012I: Machine loader up and running (version v3.1.4).
MLOLOA027E: Unknown type in component table entry.
MLOEVL010E: IPL failed.
Problem
The hardware or hypervisor environment does not support secure boot. See Supported environments for a list of hardware and software requirements for secure boot.
Solution
Reinstall the Linux boot volume without secure boot support. For details, see Preparing a boot device.
No signed components found
Symptom
An attempt to boot a Linux volume with secure boot enabled fails, and a message similar to the following
is displayed on the
console:
MLOLOA62693212 Audit: No signed components found for program 0
loaded from device Problem
The Linux boot volume is not correctly prepared for secure boot - it is missing signature data. Signature data can be
missing due to one of the following reasons:
- The Linux version does not support secure boot.
- The Linux boot-file signatures have been removed.
- No secure boot signatures were written during boot loader installation.
Solution
- Check the list in Supported environments to ensure that the Linux version that is used supports secure boot.
- Reinstall Linux packages that contain boot files. For more information, see Reinstalling Linux boot-file packages.
- Reinstall the boot volume while forcing the installation of secure boot data. For more information, see Preparing a boot device.