@jondo220 said in Error 13: Invalid or unsupported executable format:
Thanks for the reply.
Yep, that’s the issue. Same problem booting with Grub4DOS as it is similar to Grub1/Legacy I guess.
I tried your trick on the VBox install of Antergos, and it worked! Very strange,…
Good! And I’m not alone with this issue.
…I wonder what the Antergos GUI install is doing to the Ext4 filesystem to make it incompatible with Grub4DOS/Grub1?
It doesn’t an Antergos-specific problem. It happens in other Arch clones too - in Bluestar, Apricity, Nurunner, Netrunner, Manjaro.
I’ll try on the other machine on a real partition tomorrow. I had already uninstalled Antergos and restored the partition with partclone. And you’re right, only fsarchiver worked for this fix. I tried with partclone first and it did not work.
That’s because Clonezilla - which uses partclone as a backend - does a very low level, bit-by-bit backup. They read bit chunks first, then compress and backup them. They create an exact copy of a disk | partition, at a physical level. It’s an exact partition copy at a bit level.
During restore, Clonezilla places every single bit in exactly the same place where it was in original partition at backup time.
Differently from partclone, fsarchiver works at the higher file level. All files are included in a backup, but a single bit displacement is not respected by fsarchiver.
During restore, Fsarchiver simply formats the target partition from scratch, and restores all files from a backup. It doesn’t care to respect every single bit position on the target - as Clonezilla does. Fs archiver works much like a regular file archiver.
I don’t ever notice this problem before with the typical Ubuntu, Fedora or other distros. Or, as you detailed in your post, plain vanilla Arch.
You’re right. The problem is not (currently) present in Fedora, Tumbleweed, Debian.
I was just looking at Antergos as another way to get Arch installed. I’m so over the lame “Arch way” of plain vanilla. Right now if I install Arch, I use either of the text based installers, with ArchBoot ISO, or ArchBang is even easier and uses similar text installer.
I did it in another way. Time ago I created a core, bare-bones Arch images. They include an absolutely minimal set of components, like kernel, bash, vga and intel video drivers, network manager, basic IO drivers, and nothing else. They don’t include any boot loader, DE or GUI. They may be restored to disk at any time. Starting from bash, I add to them any additional sw, arriving to a fully fledged graphical DEs.