Clonezilla UEFI Boot Failure on Lenovo B51-30
Complete Fix Guide
Resolving a multi-layered boot failure on a UEFI-locked InsydeH2O laptop: BIOS password removal, correct Clonezilla image format, kernel load error recovery, and Ubuntu filesystem backup to external disk with fsarchiver.
Problem Statement
Booting Clonezilla from USB on the Lenovo B51-30 fails completely. The USB is not recognized as bootable and the system falls back to the internal disk GRUB menu (Windows/Ubuntu dual-boot). Five distinct failure modes occur simultaneously, each pointing to a locked BIOS security state and an incorrect USB image format.
Environment
| Component | Details |
|---|---|
| Laptop | Lenovo B51-30 |
| BIOS | InsydeH2O (UEFI firmware) |
| Internal Disk | Seagate ST500LT012 (500GB) |
| OS | Windows 10 + Ubuntu dual-boot |
| USB Drive | 16GB (previously used for OS installs) |
| Clonezilla | v3.3.2-31-amd64 |
Primary Issues
1. USB Drive Not Detected in Boot Menu
Boot Option Menu shows only internal disk entries. No USB option appears despite drive being plugged in. System boots straight to Windows/Ubuntu GRUB.
2. BIOS Settings Cannot Be Saved
Changes made in BIOS (disable Secure Boot, enable USB boot) revert immediately. "Save and Exit" loops back to BIOS setup. Secure Boot re-enables, USB boot disables — every time.
3. GRUB EFI Variable Error
error: could not set EFI variable 'OsIndications' when attempting to enter BIOS firmware from GRUB. Indicates NVRAM/EFI write protection is active.
4. BIOS Flash Failure at 50%
InsydeH2O flash utility reaches 50% then fails: Invalid firmware image. The BIOS file is correct (model matches, version is newer) but the security subsystem blocks the EC firmware write.
5. Clonezilla Kernel Load Failure
When USB is eventually detected: invalid magic number then you have to load the kernel first. GRUB drops to command line. Root cause: ISO format is incompatible with UEFI directory structure.
Methods Tried That Failed
- Rufus with ISO image in ISO mode
- Rufus with ISO image in DD mode
- Changing BIOS boot mode to Legacy/CSM
- Multiple USB ports (USB 2.0 and 3.0)
- BIOS update via Windows utility (failed at 50%)
- Removing CMOS battery (no effect on passwords)
Symptoms & Diagnostic Signs
Symptom 1: USB Invisible in Boot Menu
Boot Option Menu
├── Ubuntu (ST500LT012-1DG142)
├── Windows Boot Manager (ST500LT012-1DG142)
└── ubuntu (ST500LT012-1DG142)
[USB drive is NOT listed]
Meaning: Firmware does not recognize the USB as a valid bootable device. Not a hardware failure — the USB LED lights, the drive works in Windows.
Diagnostic check: Was the USB created with Rufus ISO mode? → Yes = wrong format for UEFI.
Symptom 2: BIOS Settings Revert Loop
Enter BIOS → change setting → F10 Save & Exit → system reboots → immediately returns to BIOS setup → changed setting is back to original.
Key indicator: You can enter the password to unlock settings (they become editable) but cannot SAVE — the security layer rejects any write to NVRAM.
Symptom 3: GRUB OsIndications Error
error: could not set EFI variable 'OsIndications'.
Press any key to continue...
Meaning: GRUB failed to write the EFI variable that requests BIOS setup on next boot. NVRAM is locked by active security settings.
Symptom 4: BIOS Flash — Invalid Firmware Image
Insyde H2OFFT (Flash Firmware Tool)
Current BIOS Version: C5CN32WW(v2.03)
New BIOS Version: C5CN35WW(v2.06)
[Progress bar reaches 50%]
Error: Invalid firmware image!!!
Please press any key to reset system...
Meaning: The BIOS file is correct. The 50% failure marks the EC (Embedded Controller) firmware update — which the locked state blocks. No damage occurs; the system just reboots.
Symptom 5: Kernel Load Failure
error: invalid magic number
error: you have to load the kernel first
grub> _
Meaning: GRUB found the menu config but cannot read vmlinuz from the USB. The ISO format writes files in a structure UEFI cannot navigate — the kernel path resolves to nothing.
Symptom 6: Windows/Ubuntu GRUB Instead of Clonezilla
Booting with USB plugged in shows the internal disk GRUB (Ubuntu / Windows Boot Manager) instead of the Clonezilla menu. The laptop is ignoring the USB entirely due to wrong format, Fast Boot priority, or Secure Boot blocking the unsigned bootloader.
Step-by-Step: Creating a UEFI-Compatible Clonezilla USB
Download the Correct File — ZIP, Not ISO
Go to clonezilla.org/downloads.php. Select your architecture (amd64). Choose ZIP format. Download e.g. clonezilla-live-3.3.2-31-amd64.zip.
| Format | Boot Type | UEFI Compatible |
|---|---|---|
| ISO | Legacy/BIOS only | ❌ No |
| ZIP | UEFI native | ✅ Yes |
Format USB as FAT32
UEFI firmware can only read FAT32 (or FAT16) during boot. NTFS and exFAT are not supported at the firmware level.
Windows: Right-click USB in File Explorer → Format → File system: FAT32 → Quick Format ✓ → Start.
Linux:
sudo mkfs.vfat -F 32 /dev/sdX
# Replace sdX with your actual USB device (check with lsblk)
Extract ZIP to USB Root — Critical Rule
Extract the ZIP contents directly to the root of the USB. Do NOT leave them inside a parent folder.
Correct structure:
E:├── 📁 EFI
│ └── 📁 BOOT
│ └── BOOTX64.EFI ← UEFI bootloader
├── 📁 live
│ ├── vmlinuz ← Linux kernel
│ └── initrd.img
├── 📁 syslinux
└── 📄 Clonezilla-Live-Version
Wrong structure (extraction created a parent folder — move contents up one level):
E:└── 📁 clonezilla-live-3.3.2-31-amd64 ← Extra folder. Open, select all, cut, paste to E:\
Configure BIOS — Remove Passwords First
CRITICAL: If any BIOS password is set, no settings will save. Remove all passwords before changing anything.
Remove passwords: Power on → F2 → Security tab → remove each (Admin, User, Master, HDD) by entering current password, leaving new password blank → Save & Exit (F10).
Configure boot: Re-enter BIOS → Security → Secure Boot: Disabled → Boot → USB Boot: Enabled → Boot Mode: UEFI → (optional) Fast Boot: Disabled → Save & Exit.
Verify: Re-enter BIOS and confirm settings still show your saved values. If they do, the lock is gone. ✅
Boot from USB via F12 One-Time Boot Menu
Insert prepared USB → power on → press F12 immediately (Lenovo) → select USB UEFI or your USB brand name → Enter.
Expected Clonezilla GRUB:
Clonezilla live (VGA 800x600)
Clonezilla live (VGA 800x600 & To RAM)
Clonezilla live (VGA with large font & To RAM)
Clonezilla live (Verify integrity of the boot medium)
Other modes of Clonezilla live
Local operating system (if available)
UEFI firmware setup
If you still see the Windows/Ubuntu GRUB: confirm ZIP format was used, FAT32 filesystem, files are at root level, all BIOS passwords removed, Secure Boot is off.
Solutions & Fixes — Complete Resolution Path
Solution 1: Remove BIOS Password Locks (Do This First)
Multiple BIOS security layers (Admin, User, Master, HDD passwords) prevent all firmware modification. This is the root cause of the settings revert loop, flash failure, and EFI variable errors.
Enter BIOS (F2) → Security Tab
Administrator Password → [current] → [leave blank] → Enter
User Password → [current] → [leave blank] → Enter
Master Password → [current] → [leave blank] → Enter
HDD Password → [current] → [leave blank] → Enter
→ Exit Tab → Save Changes and Exit (F10)
After this fix: Settings save permanently. USB boot appears in menu. GRUB writes EFI variables. BIOS flash utility can write firmware.
Solution 2: ZIP Image + FAT32 for UEFI
ISO images target Legacy/BIOS boot. UEFI firmware cannot locate the bootloader (BOOTX64.EFI) in an ISO-created directory structure.
- Download Clonezilla ZIP image (not ISO)
- Format USB as FAT32 (not NTFS, not exFAT)
- Extract ZIP to root of USB — no parent folder
After extraction, verify EFI/BOOT/BOOTX64.EFI exists at root level.
Solution 3: Manual Kernel Load via GRUB Command Line (Emergency)
If you see invalid magic number or you have to load the kernel first, press C at the Clonezilla GRUB menu for a command prompt:
grub> ls
grub> ls (hd0,msdos1)/
grub> set root=(hd0,msdos1)
grub> linux /live/vmlinuz boot=live union=overlay username=user config components quiet
grub> initrd /live/initrd.img
grub> boot
Alternative: Highlight first menu entry → press E → locate the linux line → fix or remove wrong device prefix before /live/vmlinuz → press Ctrl+X to boot.
Solution 4: BIOS Flash via Windows (After Unlocking)
Only attempt after removing all BIOS passwords. The flash will succeed because the security subsystem no longer blocks NVRAM writes.
- Boot into Windows
- Download correct BIOS
.exefrom Lenovo Support (model AIWB0, target v2.06) - Run as Administrator → Install → Flash BIOS → Enter to start
- Do NOT power off during flash — system reboots automatically
Solution 5: Ubuntu Backup with fsarchiver
dd creates a raw 289GB image that will not fit in 267GB and cannot restore to a smaller disk. Use fsarchiver for file-based compressed backup that restores to any disk size.
sudo mkdir -p /mnt/target
sudo mount /dev/sdc6 /mnt/target
sudo mkdir -p /mnt/target/backup
# Save partition table for reference
sudo sfdisk -d /dev/sda > /mnt/target/backup/partition-table.txt
# Backup small EFI partitions with dd (fast, fixed-size)
sudo dd if=/dev/sda1 of=/mnt/target/backup/sda1-efi.img bs=4M status=progress
sudo dd if=/dev/sda4 of=/mnt/target/backup/sda4-efi.img bs=4M status=progress
# Backup Ubuntu — only used data, zstd compressed
sudo fsarchiver savefs /mnt/target/backup/ubuntu.fsa /dev/sda5
sudo umount /mnt/target
Solution 6: Restore to New Disk
# Restore Ubuntu to new partition (any disk size)
sudo fsarchiver restfs /path/to/ubuntu.fsa id=0,dest=/dev/sdX5
# Restore EFI boot partitions
sudo dd if=/mnt/target/backup/sda1-efi.img of=/dev/sdX1 bs=4M status=progress
sudo dd if=/mnt/target/backup/sda4-efi.img of=/dev/sdX4 bs=4M status=progress
Only requirement for the target disk: must accommodate ~150GB of actual data.
Results & Outcomes
BIOS Fully Unlocked
All 4 passwords removed. Settings save permanently on every reboot. USB boot option is visible and enabled. Secure Boot stays disabled when set. GRUB writes EFI variables without error.
Clonezilla USB Boots Successfully
USB UEFI option now appears in the F12 boot menu. Full Clonezilla GRUB menu loads:
Clonezilla GNU GRUB
Clonezilla live (VGA 800x600)
Clonezilla live (VGA 800x600 & To RAM)
Clonezilla live (VGA with large font & To RAM)
Clonezilla live (Verify integrity of the boot medium)
Clonezilla live (Speech synthesis)
Other modes of Clonezilla live
Local operating system (if available)
Memtester (VGA 800x600 & To RAM)
UEFI firmware setup
Clonezilla live 20260525-resolute-amd64 info
Ubuntu Backup Completed
| Metric | Value |
|---|---|
| Ubuntu partition size | 289 GB |
| Used data | ~150 GB |
| Compressed backup (ubuntu.fsa) | ~85 GB |
| Destination available | 267 GB |
| Files processed | 257,656 (0 errors) |
| Compression | zstd level 3 |
| Archive format | FSA0002 |
BIOS Firmware Updated
| Attribute | Before | After |
|---|---|---|
| BIOS Version | C5CN32WW (v2.03) | C5CN35WW (v2.06) |
| NVRAM | Corrupted | Repaired |
| SPD write | Disabled | Enabled |
| Intel TXE | — | 2.0.5.3107 |
| Settings storage | Broken | Functional |
Issue Resolution Summary
| Issue | Status | Fix Applied |
|---|---|---|
| USB not in boot menu | ✅ Resolved | ZIP image + FAT32 + root extraction |
| BIOS settings reverting | ✅ Resolved | Removed all BIOS passwords |
| GRUB OsIndications error | ✅ Resolved | BIOS unlock re-enabled NVRAM writes |
| Invalid firmware image | ✅ Resolved | BIOS unlock allowed flash to complete |
| Kernel load failure | ✅ Resolved | Correct format + manual GRUB fix documented |
| Ubuntu backup | ✅ Completed | fsarchiver to external disk (85GB compressed) |
Key Takeaways
- BIOS passwords are the silent killer — they cause symptoms that look like hardware failure, NVRAM corruption, or firmware bugs. Check security locks first.
- UEFI needs ZIP, not ISO — ISO format is legacy-only. UEFI requires the ZIP structure on FAT32 with
EFI/BOOT/BOOTX64.EFIat root level. - Path depth matters — extra folder layers break UEFI boot. Files must be at the root of the FAT32 filesystem.
- fsarchiver > dd for flexible backups — file-based compressed backup restores to any disk size; raw sector images do not.
- Always verify settings save after BIOS change — if they revert, check security locks before assuming corruption or hardware failure.