#222 EFI boot "error: invalid magic number" caused by search command

[Julien]

Symptoms

Booting clonezilla live causes "error: invalid magic number"

Reproduce

I downloaded the clonezilla-live-20141208-utopic-amd64.zip, and followed instructions for setting up my USB drive. It boots fine on legacy systems (non-EFI). On an EFI system, it errors out. The cause appears to be the "search --set -f /live/vmlinuz" line which sets $root to "hd0".

Work-around:

I played around in the command-line to find a workaround:
"search -f /live/vmlinuz" returns "hd0 hd0 hd0,msdos1"
If I "set root=hd0,msdos1", I can boot!

To make this more permanent, I have removed the search line entirely! The boot process seems to work fine as before that command runs, my $root is set properly to hd0,msdos1.

This is probably a debian live or grub or upstream issue (possibly limited to my Asus S200e laptop), please let me know where to post if it belongs upstream.

[Steven Shiau]

Thanks for reporting this issue.
Is this issue reproducible on 20150210-vivid:
http://clonezilla.org/downloads.php
?

Steven.

[LeMerP]

Get the same message within current unstable version "clonezilla-live-20150812-wily-amd64".
Mentioned work-around works as described.

[Steven Shiau]

Thanks. I have never have such issue here.
Is this issue also reproducible on different machines there?

Steven.

[Kokos]

Thank you for sharing this with us, the problem exists with current version of alternative stable. Workaround works. Machine - Asus N550JK

[Michal Zatloukal]

I'm seeing this issue on an Acer (Aspire One) Cloudbook with 20180725-bionic. Seeing as this affects GRUB2-enabled builds, is the debian-based clonezilla also affected? (I recall seeing isolinux loader there some time last year, not sure if it's still present)

[Michal Zatloukal]

Ah, nevermind - stable release (20180329-artful) works fine, so the issue is probably with specific version of GRUB2. In the working version, the search command returns "hd0,msdos1" as expected.

[Peter Schüller]

I have the same issue with the latest alternative bionic image (clonezilla-live-20180812-bionic-amd64.iso) and the same fix works (adding "set root=hd0,msdos1")