Boot ISO from grub fails

verndog · 2021-01-18 16:42:51

Here's my grub entry:

menuentry "bunsenlabs" {
	set isofile="/ISO/lithium-1-amd64.hybrid.iso"
	loopback loop (hd1,1)$isofile
	linux (loop)/live/vmlinuz boot=live config fromiso=$isofile
	initrd (loop)/live/initrd.img
        }

It boots the ISO, but stops right after showing the file systems, usb, keyboard, etc.
At some point I can get to busy box. but that's it.
I added "toram=filesystem.squashfs", maid no difference.
I examined all the loopback methods. Here's one that's like mine:
https://forums.bunsenlabs.org/viewtopic … 530#p26530

Last edited by verndog (2021-01-19 14:57:02)

rbh · 2021-01-18 17:00:35

verndog wrote:

It boots the ISO, but stops

I boot BL live session (and live iso of GRML, Finix and SystemRescueCD) with package grml-rescueboot.

Last edited by rbh (2021-01-18 17:00:52)

ohnonot · 2021-01-19 06:19:10

verndog wrote:

It boots the ISO, but stops right after ?????????

Didn't get that last bit.
Anyways, how did you create the bootable medium?

unklar · 2021-01-19 14:57:59

^@ohnonot,
the ISO is on his hard drive and he is trying to boot it using grub.

@verndog
have you already looked in the ISO for the appropriate startup parameters ?
You dig up here a 4 year old, unresolved, thread and think here solutions served?

Apart from that, you do NOT do that in the grub.cfg and the procedure is tedious. You are ten times faster with a VM!

verndog · 2021-01-19 14:59:36

I downloaded the latest lithium ISO, and used it as shown. Not sure what you might be referring to.

verndog · 2021-01-19 15:05:47

unklar wrote:

^@ohnonot,
the ISO is on his hard drive and he is trying to boot it using grub.
@verndog
have you already looked in the ISO for the appropriate startup parameters ?
You dig up here a 4 year old, unresolved, thread and think here solutions served?
Apart from that, you do NOT do that in the grub.cfg and the procedure is tedious. You are ten times faster with a VM!

That 4 yr old thread is just an example. I googled for hours and found nothing that worked.
If I wanted to use a VM I would have. Tedious doesn't make any sense. People do this all the time. Its on my grub submenu. Ubuntu, Mint, Fedora, CloneZilla, etc all work this way. And I though in the distant past bunsen worked. Not anymore

The loopback method works on 90+ % of distros. It works on Ventoy. But that's booting up another hard drive. I want to use grub and loop.

Last edited by verndog (2021-01-19 15:10:41)

unklar · 2021-01-19 15:28:08

^^Yes.
But Ubuntu, Mint, Fedora, CloneZilla, etc. are not bunsenlabs
or siduction, mageia, antiX etc. pp.
It also always bugged me that the distributions don't ALL use the same startup parameters and you always have to re-edit the grub config files.

Mount the ISO and see for yourself e.g.:

mkdir /mnt/disk
mount -o loop /path/to.iso /mnt/disk

rbh · 2021-01-19 15:58:26

verndog wrote:

The loopback method works on 90+ % of distros. It works on Ventoy. But that's booting up another hard drive. I want to use grub and loop.

I quit manualy editing grub-entry for is-boot, when grml-rescueboot was released. It is so handy. You do not need to update configfile, when new iso is downloaded. "update-grub2", takes care of that too.
Works for al isos with configfile = /boot/grub/loopback.cfg. That is for many Debian based dists. Works for SystemRescueCD too, but you need to look into the iso for the name of the configfile and edit grub.cfg acordinly.

I recomended it erlier. Still does.

Last edited by rbh (2021-01-19 15:59:16)

verndog · 2021-01-19 17:13:17

unklar wrote:

^^Yes.
But Ubuntu, Mint, Fedora, CloneZilla, etc. are not bunsenlabs
or siduction, mageia, antiX etc. pp.
It also always bugged me that the distributions don't ALL use the same startup parameters and you always have to re-edit the grub config files.
Mount the ISO and see for yourself e.g.:
mkdir /mnt/disk
mount -o loop /path/to.iso /mnt/disk

I don't edit grub.cfg. I have my own and prevent os-prober and the like from interfering.
This topic is how to loopback Bunsenlabs. Not let me give my opinion of what you should do instead.

rbh · 2021-01-19 18:35:37

verndog wrote:

I don't edit grub.cfg. I have my own

The computer reads /boot/grub/grub.cfg. Normal boot or iso loopback boot from harddrive is configured in grub.cfg.
Yes, normaly you do not edit grub.cfg directly, files in /etc/grub.d/, is used and update-grub2 command, updates grub.cfg.

This topic is how to loopback Bunsenlabs.

It is easy to make error when writing defaults for iso loopback boot. Grml-rescueboot, eliminates syntax errors and ensures that iso loopback boot of isos with an loopback.cfg realy boots of the harddrive.

Check it out. In Debian repo. Documentation here: https://wiki.grml.org/doku.php?id=rescueboot

ohnonot · 2021-01-20 06:21:05

verndog wrote:

I don't edit grub.cfg. I have my own and prevent os-prober and the like from interfering.
This topic is how to loopback Bunsenlabs. Not let me give my opinion of what you should do instead.

Sorry about the confusion.
unklar made an important point though:
Mount the iso you want to boot, and see what kernel command & options it uses , and put those in your config.
Both for the kernel and the initrd.
Otherwise, I trust you read up on current grub documentation to make sure you're doing this right.

Once you get this working you should indeed move it out of grub.cfg, possibly to one of those include files.

#1 2021-01-18 16:42:51

Boot ISO from grub fails

#2 2021-01-18 17:00:35

Re: Boot ISO from grub fails

#3 2021-01-19 06:19:10

Re: Boot ISO from grub fails

#4 2021-01-19 14:57:59

Re: Boot ISO from grub fails

#5 2021-01-19 14:59:36

Re: Boot ISO from grub fails

#6 2021-01-19 15:05:47

Re: Boot ISO from grub fails

#7 2021-01-19 15:28:08

Re: Boot ISO from grub fails

#8 2021-01-19 15:58:26

Re: Boot ISO from grub fails

#9 2021-01-19 17:13:17

Re: Boot ISO from grub fails

#10 2021-01-19 18:35:37

Re: Boot ISO from grub fails

#11 2021-01-20 06:21:05

Re: Boot ISO from grub fails

Board footer