Hello all,
Actually, my error was to use live-media-path=/live/grml64/
instead of live-media-path=/live/grml/ - everything seems to work
nicely now (though there were some "Module unknown not found in
modules.dep" messages as before).

Ciao,
Thomas

Ulrich Dangel wrote:
> 
> Ulrich Dangel <mru@grml.org> added the comment:
> 
> JFTR:
> kvm -kernel /tmp/vmlinuz -initrd /tmp/initrd.img -append "apm=power-off boot=live live-media-path=/live/autobuild/ 
> bootid=autobuild20120108_121023 findiso=/grml.iso" -hda /tmp/grml-hd.img
> 
> vmlinuz and initrd are files from the grml iso.
> 
> I am pretty sure your specified parameter in findiso is wrong as i can reproduce your error if i specify a parameter to a 
> non existant file in findiso.
> 
> To debug the issue please start with break=top which will give you a shell in the initramfs. You can afterwards start 
> udev via
> /scripts/init-top/udev
> 
> and mount your partition with:
> 
> mount -t vfat $partition /root 
> 
> and check if the file exists.
> 
> _____________________________________
> GRML issue tracker <bts@bts.grml.org>
> <http://bts.grml.org/grml/issue1129>
> _____________________________________
> 

-- 
 Thomas Köhler       Email:       jean-luc@picard.franken.de
     <><             WWW:              http://gott-gehabt.de
                     IRC: tkoehler       Freenode: thkoehler
                     PGP public key available from Homepage!

JFTR:
kvm -kernel /tmp/vmlinuz -initrd /tmp/initrd.img -append "apm=power-off boot=live live-media-path=/live/autobuild/ 
bootid=autobuild20120108_121023 findiso=/grml.iso" -hda /tmp/grml-hd.img

vmlinuz and initrd are files from the grml iso.

I am pretty sure your specified parameter in findiso is wrong as i can reproduce your error if i specify a parameter to a 
non existant file in findiso.

To debug the issue please start with break=top which will give you a shell in the initramfs. You can afterwards start 
udev via
/scripts/init-top/udev

and mount your partition with:

mount -t vfat $partition /root 

and check if the file exists.

Hello,

I think I'll have to upgrade to the latest grub first in order to
try the loopback.cfg stuff. Last time I tried that it didn't work
with the version on my USB disk.
Apart from that, changing live-media-path to /live/grml64/ didn't
work.
I think I will try to get it to work by using the latest grml2usb
on the latest ISO on another USB disk. If that works, I'll then
use that. Expect that test to happen end of this week.

Ciao,
Thomas

Ulrich Dangel wrote:
> 
> Ulrich Dangel <mru@grml.org> added the comment:
> 
> JFTR the code supporting the findiso paramter (live-boot-grml) was released on December the 6th.
> 
> That being said i tried to recreate your problem with the current release but was unsuccessful. I even extracted all the 
> files and just booted with 
> 
>  kvm -kernel /tmp/vmlinuz -initrd /tmp/initrd.img -append ???
> 
> and created luksDevices. Everything worked OOTB.
> 
> 
> After examining your bug report i think your bootoptions are wrong. The live-media-path contains nowadays the release name. 
> So it should be something like live-media-path=/live/grml64/
> 
> Please be aware that manually using your setup like you did in grub.cfg is highly discouraged. If you want to integrate a 
> grml iso into your Grub environment use loopback.cfg
> 
> 
> menuentry "grml bootmenu" {
>         iso_path="path_to_iso_image" 
>         export iso_path
>         kernelopts="  KERNEL_OPTIONS "
>         export kernelopts
>         loopback loop "path_to_iso_image"
>         set root=(loop)
>         configfile /boot/grub/loopback.cfg
> }
> 
> If you don't want to do that please directly include the grml config menus:
> 
> 
> menuentry "my grml" {
>         iso_path="path_to_iso_image" 
>         export iso_path
>         kernelopts="  KERNEL_OPTIONS "
>         export kernelopts
>         loopback loop "path_to_iso_image"
>         set root=(loop)
>         set loopback="findiso=${iso_path}"
>         export loopback
>         configfile /boot/grub/grml64_default.cfg
> }
> 
> Please reply if changing live-media-path solves your problem.
> 
> _____________________________________
> GRML issue tracker <bts@bts.grml.org>
> <http://bts.grml.org/grml/issue1129>
> _____________________________________
> 

-- 
 Thomas Köhler       Email:       jean-luc@picard.franken.de
     <><             WWW:              http://gott-gehabt.de
                     IRC: tkoehler       Freenode: thkoehler
                     PGP public key available from Homepage!

JFTR the code supporting the findiso paramter (live-boot-grml) was released on December the 6th.

That being said i tried to recreate your problem with the current release but was unsuccessful. I even extracted all the 
files and just booted with 

 kvm -kernel /tmp/vmlinuz -initrd /tmp/initrd.img -append …

and created luksDevices. Everything worked OOTB.


After examining your bug report i think your bootoptions are wrong. The live-media-path contains nowadays the release name. 
So it should be something like live-media-path=/live/grml64/

Please be aware that manually using your setup like you did in grub.cfg is highly discouraged. If you want to integrate a 
grml iso into your Grub environment use loopback.cfg


menuentry "grml bootmenu" {
        iso_path="path_to_iso_image" 
        export iso_path
        kernelopts="  KERNEL_OPTIONS "
        export kernelopts
        loopback loop "path_to_iso_image"
        set root=(loop)
        configfile /boot/grub/loopback.cfg
}

If you don't want to do that please directly include the grml config menus:


menuentry "my grml" {
        iso_path="path_to_iso_image" 
        export iso_path
        kernelopts="  KERNEL_OPTIONS "
        export kernelopts
        loopback loop "path_to_iso_image"
        set root=(loop)
        set loopback="findiso=${iso_path}"
        export loopback
        configfile /boot/grub/grml64_default.cfg
}

Please reply if changing live-media-path solves your problem.

Hi mika,

Michael Prokop wrote:
> Michael Prokop <mika@grml.org> added the comment:
> 
> Are you sure the squashfs files from /live are present accordingly on your USB disk?

I want to boot the ISO, not directly from the disk. Maybe that
was unclear.

Grub entry that works:

menuentry "grml-amd64-self-20111217.iso" {
    set gfxpayload=1024x768x16,1024x768
    linux  /boot/20111217/linux26 boot=live live-media-path=/live/ bootid=grml20111217 findiso=/grml-amd64-self-20111217.iso lang=de hostname=desktop-tk
    initrd /boot/20111217/initrd.gz
}

The files in /boot/20111217 are from /boot/grml on grml-amd64-self-20111217.iso


Grub entry that doesn't work:

menuentry "grml-amd64-self-20120104.iso" {
    set gfxpayload=1024x768x16,1024x768
    linux  /boot/20120104/vmlinuz boot=live live-media-path=/live/ bootid=grml20120104 findiso=/grml-amd64-self-20120104.iso lang=de hostname=desktop-tk
    initrd /boot/20120104/initrd.img
}

The files in /boot/20120104 are from /boot/grml on grml-amd64-self-20120104.iso

Ciao,
Thomas

-- 
 Thomas Köhler       Email:       jean-luc@picard.franken.de
     <><             WWW:              http://gott-gehabt.de
                     IRC: tkoehler       Freenode: thkoehler
                     PGP public key available from Homepage!

Are you sure the squashfs files from /live are present accordingly on your USB disk?

Hello all,

I currently use my own remastered grml iso in order to boot my
desktop PC. For that, I once installed an old version of grml via
grml2usb on the first partition of a USB disk, and keep my
personal data on another partition.
In order to use a new version of grml, I just copy the iso to the
first partition, put the kernel/initrd into /boot/<version> and
create another menu entry in the bootloader.
Well, that worked nice until 2011/12/17. My next iteration,
2011/12/23, and all later versions, refuse to boot. Kernel and
initrd will be loaded, but when searching for the GRML file,
modprobe complains about modules "unknown" and "luks" not being
present in modules.dep, and "unable to open '/dev/sdb'" messages
appear. Nothing else will happen from that point on.

The funny thing is, the very same version of grml will boot from
USB after creating a bootable USB stick via:
   grml2usb --grub --grub-mbr latest-grml.iso /dev/sdd1
The difference then is (as far as I can tell):
- findiso kernel commandline switch is not being used, no iso
  involved
- bootable USB stick, everything is on the stick
- stick has only one (vfat) partition
- version of grub used on the USB disk is outdated

I have taken pictures of the error messages:
http://gott-gehabt.de/tmp/IMAG0341.jpg
http://gott-gehabt.de/tmp/IMAG0342.jpg

Attached is also grml-hwinfo's output.

Ciao,
Thomas

-- 
 Thomas Köhler       Email:       jean-luc@picard.franken.de
     <><             WWW:              http://gott-gehabt.de
                     IRC: tkoehler       Freenode: thkoehler
                     PGP public key available from Homepage!