Troubleshooting
Recovery USB shows no UEFI boot option on an edge PC
Short answer
A recovery USB with no UEFI entry in the boot menu was written in a layout the firmware cannot launch. Rebuild the Clonezilla stick on a Windows PC with Rufus, confirm the UEFI line appears in the boot menu, restore from that entry, then cold-start with the USB removed to prove the internal drive boots.
On this page
If the boot menu shows no UEFI entry for your recovery USB, do not run the restore again from that stick. The media was written in a layout the firmware cannot launch, and the same stick will reproduce the same result: the restore completes, then the edge PC reports that it can find no bootable drive at the next power-on. UEFI firmware lists removable media only when the stick carries a FAT partition holding the boot loader at the path the UEFI Specification defines for removable media, and sticks that some cross-platform imaging tools write never get that layout. The fix is to rebuild the Clonezilla stick on a Windows PC with Rufus, confirm the firmware now lists a UEFI entry for it, run the restore from that entry, then shut down, pull the USB and cold-start so the internal drive has to boot on its own.
What the missing UEFI entry means #
For media with no entry stored in the firmware's own boot list, the UEFI Specification defines a fallback: the firmware scans the stick's first FAT-formatted partition and launches the loader at \EFI\BOOT\BOOTX64.EFI on an x64 system. No FAT partition, or that file missing, means the firmware has nothing to list, so no UEFI line for the stick appears. This is a media-layout test, not a file test: a stick that a file manager reads without errors, or that starts the recovery environment through a legacy path, can still fail it.
Attach the stick, open the boot menu and classify what you see before touching the internal drive.
| What the boot menu shows | What it means | Decision |
|---|---|---|
| A UEFI line for the stick | The firmware can launch this media in UEFI mode | Select that line and run the restore |
| Only a plain legacy line for the stick | The layout lacks the FAT fallback loader | Stop. Rebuild the stick before restoring |
| No line at all for the stick | Format, port or Secure Boot issue | Try another port, check Secure Boot, then rebuild |
| No bootable drive after a restore | The restored disk has no boot path the firmware accepts | Restore again only from a stick the firmware lists as UEFI |
Why a finished restore can still leave the drive unbootable #
The recovery program's success message covers the copy it performed inside the live environment. It says nothing about the chain the firmware walks at the next power-on: firmware boot mode, the boot structures the restore wrote to the internal disk, and the loader the installed system provides. A live environment that starts through a legacy path can complete a copy the firmware then cannot start, which is the pattern behind a restore that reports success and a drive that reports no bootable path.
Imaging tools that write a hybrid MBR or a non-FAT partition set produce exactly that gap: no FAT partition carrying the fallback loader, so the UEFI line never appears. Sticks written on macOS have been reported to show this pattern. The three common ways to put Clonezilla on a stick — a raw dd write, a manual file copy onto FAT32 and a Rufus build — do not produce the same layout, and only some of them satisfy the removable-media rule; how dd, Clonezilla and Rufus each write a bootable USB stick compares the three.
Rebuild the Clonezilla stick on Windows with Rufus #
A restore overwrites the internal drive, so back up application data and configuration first, and take the edge PC out of service for the window.
- Get the factory recovery package from the device vendor's support or firmware download channel: the package built for that hardware, not a fresh ISO of the same Linux distribution. The factory image carries the vendor's drivers and preinstalled edge software, which a generic distribution image does not.
- Take a stick with room for the live system plus the recovery image; the worked example below budgets a 16 GB stick.
- On a Windows PC, write the package with Rufus in ISO mode, choosing the GPT layout for UEFI (non-CSM) and FAT32, so the stick gets the FAT partition and fallback loader the firmware scans for.
- Eject the stick cleanly and connect it to the powered-off edge PC.
- Open the one-time boot menu during power-on; the key or firmware setting that opens it is vendor-specific, so use the device manual rather than guessing.
- Confirm the firmware now lists a UEFI entry for the stick. If it does not, stop and work through the last section before restoring anything.
- Select the UEFI entry and run the restore to completion.
Before step 7 overwrites the drive, settle what build should live on it afterwards: choosing an operating system image for an industrial PC walks through that decision for plant-floor machines. If you keep one stick for several machines, tools that boot multiple ISO files from a UEFI menu — Ventoy, Easy2Boot and YUMI are the common ones — save per-image rebuilds, but every image still has to pass the same boot-menu test; creating a UEFI multi-ISO bootable USB with Ventoy, Easy2Boot and YUMI covers the trade-offs.
Worked example: does the package fit a FAT32 stick? #
The FAT32 route has one hard limit worth checking before you build. FAT32 stores at most 4,294,967,295 bytes in a single file — 2^32 - 1, about 4 GiB minus 1 byte.
Illustrative package: a vendor recovery image of 10 GiB, shipped as volume files capped at 4,000 MiB each, plus a 0.5 GiB Clonezilla Live system.
- One volume file: 4,000 MiB x 1,048,576 bytes per MiB = 4,194,304,000 bytes, safely under that ceiling, so FAT32 accepts every volume.
- Volume count: the 10 GiB image is 10 x 1,073,741,824 = 10,737,418,240 bytes; 10,737,418,240 / 4,194,304,000 = 2.56, so 3 volume files.
- Package on the stick: worst case 3 x 4,000 MiB = 12,000 MiB = 11.7 GiB, plus the 0.5 GiB live system, about 12.2 GiB total.
- Stick margin: a 16 GB stick holds 16,000,000,000 bytes / 1,073,741,824 bytes per GiB = 14.9 GiB nominal, leaving 14.9 - 12.2 = 2.7 GiB of margin, enough to absorb formatting overhead. The package fits.
What moves the answer: a package shipped as a single file over the ceiling cannot sit on FAT32 at all. For such a package, use a route that splits the image into volumes under the cap or writes NTFS with its own UEFI loader, and re-run the boot-menu test either way, because the loader layout changes with the file system. The 10 GiB package is an illustrative input; the ceiling above is the documented FAT32 limit.
Prove the internal drive boots #
Shut the edge PC down from inside the recovery environment, remove the USB stick and apply power. With the stick gone, the firmware must fall through to the internal drive, so this cold start is the acceptance test for the whole chain: media layout, restore and internal boot path in one pass.
| Cold-start result | Interpretation | Next step |
|---|---|---|
| Linux starts with no stick attached | USB layout, restore and internal boot path all passed | Check the installed build against the package's release notes, then restore application configuration |
| No bootable drive again | The internal boot path is still not accepted | Confirm the restore ran from the UEFI entry, rebuild the stick, repeat the test |
| The recovery environment starts again | Boot order still points at the stick | Remove the stick and repeat; if it persists, move the internal drive above USB in the firmware boot order |
If the rebuilt stick still shows no UEFI entry #
Check Secure Boot first. Clonezilla's own issue tracker recorded reports, around the 2020 builds, of Clonezilla media that UEFI firmware would not recognize with Secure Boot enabled, and firmware that cannot verify the loader can simply hide the device. The documented route: boot the vendor's signed recovery image where one exists, or make the temporary Secure Boot change in firmware setup that the vendor documents for recovery, and turn Secure Boot back on afterwards.
Then verify the layout from a working Windows PC: the stick should expose a FAT partition carrying the EFI fallback loader, not a single NTFS volume or a hybrid MBR. Try a different USB port as well — firmware support for booting from every port is not guaranteed. If a confirmed-good layout on two ports still lists nothing, the firmware itself lacks usable UEFI USB boot support or needs an update, and that goes to the vendor's support channel rather than another restore attempt.
And when the unit is out of support and the internal drive keeps failing the cold-start test after a restore from a stick the firmware lists as UEFI, stop spending hours on the board: replacing it with a fanless mini PC returns an edge host to service faster than chasing a hardware fault.
Questions asked
Where do I get the factory recovery image for an edge PC?
From the device manufacturer's support or firmware download channel, or from the distributor that supplied the unit. The factory package is built for that hardware and carries the vendor's drivers and preinstalled edge software; a fresh ISO of the same Linux distribution from elsewhere will not reproduce that stack, and unofficial copies can be modified or stale. Ask the vendor which release matches your unit before you build the stick.
Does Secure Boot block a Clonezilla recovery USB?
It can. A live recovery build that is not signed for Secure Boot may be hidden or rejected by the firmware, which looks exactly like a missing UEFI entry. Check the Secure Boot state in firmware setup before blaming the media again, prefer a vendor-signed recovery image where the vendor ships one, and treat any Secure Boot change as temporary: re-enable it after recovery so the unit keeps its boot integrity.
Why remove the USB stick before the final power-on?
Because boot order can mask the result. With the stick attached and still first in the boot sequence, a successful start proves only that the stick boots again. Removing it forces the firmware to fall through to the internal drive, so the cold start either finds a working boot path on the restored disk or reports no bootable drive, with nothing in between.
The restore finished but the drive still will not boot: what mode mismatch should I check?
Check that the firmware boot mode matches the way the image was installed. A Linux build set up for UEFI on a GPT disk carries no legacy MBR boot code, so firmware running a legacy or CSM boot finds nothing to start; the reverse mismatch fails the same way. Restoring from media launched through the UEFI entry keeps the whole chain in one mode.