Install on usb don't boot - Ventoy / Super Grub2 Disk - loopback.cfg

hi friends

I’m very interested in kicksecure and wanted to have it installed on a usb drive to test it longer before installing on hard drive, but i’ve got a serious problem. I can’t have the usb drive running the totally standard install

I run from a ventoy usb with kicksecure 17 iso; and install on another usb drive.
Config is standard : erase complete sdb device, and automatic partitioning

BUT, whether I choose luks crypted or not, the USBN isn’t bootable
a few errors appears before grub shell starts : I reach GNU GRUB version 2.06 etc… minimal bash-like line editing.

errors very briefly appears just before :
error : no such device: /.disk/info.
.................''...../.disk/mini-info.
.................''...../26adaabd-0000-0000...etc...

and then go to gnu grub bash like command line

I don’t know how to get kicksecure installed on the usb, although I keept all the standard ready to go parameters.
I looked on the net, and didn’t find much. The tutorial from kicksecure for installing on a usb is very limited ; i found no indication on partitioning nor on how to manage luks encrypted partitions
I’d be glad to have any indications or help to deal with this, many thanks !

or any other tool like Balena Etcher or USBImager.

This is handled by calamares gui installer.

If issue is not resolved, maybe write in details every step you are doing to see whats the issue you are doing.

For now, this is unsupported.

That’s not something that will be supported anytime soon.

This might be possible once Kicksecure ISO build process gets ported to Debian live-build. That is, if Debian is compatible with ventoy, then Kicksecure might also gain this capability.

But unfortunately, I am pretty sure, nobody is going to look into explicit ventoy support anytime soon. ISO building is way too complicated and there are a lot higher priority improvements we have to work on first.

2 posts were split to a new topic: Boot issue after installking Kicksecure

Kicksecure ISO build process is using live-build for a while now.

A live-build fix had been submitted to and merged by upstream live-build which makes live-build compatible with dracut:

Kicksecure should now be compatible with loopback.cfg.

Kicksecure ticket: live-build - grub.cfg GRUB configuration - loopback.cfg

Quote @arraybolt3:

In result:

  • Kicksecure compatibility with Ventoy: Remains untested.
  • Kicksecure compatibltiy with Super Grub2 Disk: Was tested to be functional by @arraybolt3.
    • Broken by default in the Super Grub2 Disk release at the time of writing. A workaround is available. See above link.
      • The bug seems unspecific to Kicksecure and might be applicable to all Linux distributions. So there is nothing further that can be done on the Kicksecure side.
    • Might be fixed by default if Super Grub2 Disk updates its version of GRUB.
1 Like

I’ll make a post about this but is Super Grub2 Disk anyhow related to GRUB2-BLS that opensuse-tumbleweed and Fedora uses now?

I do not believe so. It’s basically just GRUB on an external USB drive,
with a configuration that can detect and boot operating systems on the
computer it’s booted on. GRUB2-BLS is a GRUB variant meant to be installed
with an OS, and adds support for BootLoader Specification configuration
files. Technically Super GRUB2 Disk could in the future use a version of
GRUB with BLS support, but at the moment it does not.

1 Like