Hi. I'm using Linux Opensuse Tumbleweed Gnome Wayland on an AMD laptop. I used Balena Etcher to successfully flash the Rescuezilla ISO to my 32GB USB drive. I then powered off and powered back on and hit the boot menu key. The USB drive was not there. See attached image. How can I fix this? Thanks.
Hi. I'm using Linux Opensuse Tumbleweed Gnome Wayland on an AMD laptop. I used Balena Etcher to successfully flash the Rescuezilla ISO to my 32GB USB drive. I then powered off and powered back on and hit the boot menu key. The USB drive was not there. See attached image. How can I fix this? Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2025-11-20
Did you try disabling Secure Boot in your BIOS/UEFI?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update, I tried both the "alternative" Clonez ISO and ZIP version. Both gave me the "Failed to open \EFI\BOOT\mmx64.efi - Not Found" error when I tried to boot into the USB drive.
Any way to fix this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
6 days ago
Secure boot mode standard sounds like secure boot is enabled to me. it also sounds to me like the boot order setting in your BIOS isn't set to look for usb disk before trying system disk.
\EFI\BOOT\mmx64.efi is the mok manager that linux distros activate after running the mokutil --import command to enroll a mok key to support secure boot functionality. i recently ran into this problem when trying to install Virtual Box on my AlmaLinux 9.7 PC. I fixed the linux mok manager problem by copying the mmx64.efi file from the /boot/efi/EFI/almalinux folder to the /boot/efi/EFI/BOOT folder. i got rid of the "failed to open ..." issue first by setting my boot order to usb disk first, then system disk and then just loaded a live linux distro, removed the usb, and then my regular OS booted normally. Then i did the mmx64 copy to fix the distros mok manager problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi. I'm using Linux Opensuse Tumbleweed Gnome Wayland on an AMD laptop. I used Balena Etcher to successfully flash the Rescuezilla ISO to my 32GB USB drive. I then powered off and powered back on and hit the boot menu key. The USB drive was not there. See attached image. How can I fix this? Thanks.
The USB drive was plugged in when I powered back on.
Hi. I'm using Linux Opensuse Tumbleweed Gnome Wayland on an AMD laptop. I used Balena Etcher to successfully flash the Rescuezilla ISO to my 32GB USB drive. I then powered off and powered back on and hit the boot menu key. The USB drive was not there. See attached image. How can I fix this? Thanks.
Did you try disabling Secure Boot in your BIOS/UEFI?
Secure Boot is disabled on my laptop. It's been disabled for years.
"Secure Boot Mode = "Standard"".
If you have any ideas why the Clonezilla USB drive is not appearing on the boot menu, that would be great.
Should I try the "alternative Clonezilla" ISO?
Last edit: Advait 2025-11-23
Update, I tried both the "alternative" Clonez ISO and ZIP version. Both gave me the "Failed to open \EFI\BOOT\mmx64.efi - Not Found" error when I tried to boot into the USB drive.
Any way to fix this?
Secure boot mode standard sounds like secure boot is enabled to me. it also sounds to me like the boot order setting in your BIOS isn't set to look for usb disk before trying system disk.
\EFI\BOOT\mmx64.efi is the mok manager that linux distros activate after running the mokutil --import command to enroll a mok key to support secure boot functionality. i recently ran into this problem when trying to install Virtual Box on my AlmaLinux 9.7 PC. I fixed the linux mok manager problem by copying the mmx64.efi file from the /boot/efi/EFI/almalinux folder to the /boot/efi/EFI/BOOT folder. i got rid of the "failed to open ..." issue first by setting my boot order to usb disk first, then system disk and then just loaded a live linux distro, removed the usb, and then my regular OS booted normally. Then i did the mmx64 copy to fix the distros mok manager problem.