If the ZimaOS installer completes successfully but the target PC's BIOS shows no bootable drive, the installation media or disk may not be the real problem. In this October 2025 thread, a Fujitsu Esprimo Q556/S failed to list ZimaOS as bootable even though the same installed SSD booted successfully when connected to a ThinkPad T495.
That cross-test is the key diagnostic result. It strongly shifted attention from the SSD and ZimaOS filesystem toward the Fujitsu firmware and its UEFI boot-entry handling.
The Installation Completed but BIOS Had an Empty Boot List
The user tried multiple known-good SATA drives, including Kingston, Micron, and Toshiba models. Windows and Debian could boot from those drives on the same mini PC, while ZimaOS could not. Secure Boot was disabled, Legacy mode was off, and the BIOS had been updated.
After moving the ZimaOS SSD to a ThinkPad, the drive booted. That test showed that ZimaOS files were present and bootable on another UEFI system.
The Community Suspected UEFI Boot Registration
A community reply proposed that the firmware had not registered the installed bootloader as a UEFI boot entry. The original poster also linked the behavior to an IceWhaleTech GitHub issue about boot entries not being added after installation.
This is a plausible explanation for the case, but the thread did not include an IceWhale staff confirmation or a final solved post from the original user. The page should therefore describe this as a diagnosis pattern rather than a confirmed fix.
Do Not Turn Community Bootloader Repair Ideas into Official Commands
The thread suggested manually recreating a boot entry or reinstalling the bootloader from a recovery environment. Those steps can be valid Linux techniques, but no ZimaOS team member in this thread confirmed a specific command sequence for this hardware.
Because bootloader repair can make a system unbootable if the wrong disk or EFI partition is modified, this page intentionally does not reproduce an unverified repair command set.
A Safer Diagnostic Order
- Confirm that installation finishes without an error.
- Remove the USB installer and check whether the system disk appears in BIOS/UEFI boot options.
- Verify Secure Boot and Legacy/UEFI settings against the current hardware requirements.
- If practical, test the installed ZimaOS disk in another compatible x64 system.
- If the disk boots elsewhere, focus on firmware boot-entry behavior rather than repeatedly replacing disks.
- Check the motherboard or vendor documentation for manually adding an EFI boot entry.
- Use the current download the current ZimaOS installer before attempting a reinstall.
Why This Should Not Be Called a General ZimaOS Disk Failure
The same ZimaOS installation booted on the ThinkPad. That makes a blanket statement such as “ZimaOS cannot boot from this SSD” unsupported by the source evidence.
The source thread is best understood as a firmware compatibility or boot-entry discovery case on one Fujitsu Esprimo model.
ZimaOS UEFI Boot FAQ
Does an empty BIOS boot list mean the ZimaOS installation failed?
Not necessarily. In the source case, the installed SSD booted on another laptop, showing that the disk contained a bootable ZimaOS installation.
Should I keep changing SSDs?
The original poster tried several working drives with the same result. Once the installed disk booted on another machine, changing disks was no longer the strongest troubleshooting direction.
Is manually recreating the EFI entry an official ZimaOS fix?
Not from this thread. It was a community suggestion tied to a known class of UEFI problems, not an IceWhale-confirmed procedure for this Fujitsu model.
Was the thread marked solved?
No. It established a strong firmware/UEFI suspicion but did not publish a confirmed final repair from the original poster.
