Since it's working grml-rescueboot I'm closing this bug report, sorry for no
further feedback since back then :)

regards,
Michael

On 11/04/2014 06:27 PM, Michael Prokop wrote:
>
> Michael Prokop <mika@grml.org> added the comment:

> You could use grml-rescueboot as an alternative, if that would be an
> option for you.

No such issue using grml-rescueboot!

* Jos van Wolput wrote in grml's BTS on 20141104 / 10:58:
> On 11/04/2014 04:52 PM, Michael Prokop wrote:

> > Does it work for you with boot option ignore_bootid?
> > How much memory/RAM do you have available?

> Adding ignore_bootid to /etc/defaults/grub-imageboot:
> ---
> IMAGES="/boot/grml"
> ISOOPTS="iso"
> IMAGEOPTS="ignore_bootid"
> ---
> skips the warning 'BOOTID does not match' and starts busybox!

Ok, that's bad.

> I have 4GB of RAM which is enough to run grml64-full_2014.03.iso in RAM

Ok, then I'm afraid the memdisk feature (that's what grub-imageboot
is using) in the initramfs got broken, so this needs further
investigation.

You could use grml-rescueboot as an alternative, if that would be an
option for you.

regards,
-mika-

On 11/04/2014 04:52 PM, Michael Prokop wrote:
>
> Michael Prokop <mika@grml.org> added the comment:
>
> * Jos van Wolput wrote in grml's BTS on 20141104 / 09:32:
>
>> I tried to run the bootable iso image grml64-full_2014.10-rc1.iso (using grub-imageboot)
>> but it doesn't install properly, showing the following warning and starting busybox:
>> ---
>> Begin: Mounting root file system... *Warning: BOOTID does not match.
> [...]
>
>> No such issue using grml64-full_2014.03.iso, it runs properly.
>
> Does it work for you with boot option ignore_bootid?
> How much memory/RAM do you have available?

Adding ignore_bootid to /etc/defaults/grub-imageboot:
---
IMAGES="/boot/grml"
ISOOPTS="iso"
IMAGEOPTS="ignore_bootid"
---
skips the warning 'BOOTID does not match' and starts busybox!

I have 4GB of RAM which is enough to run grml64-full_2014.03.iso in RAM

Regards,
Jos v.W.

* Jos van Wolput wrote in grml's BTS on 20141104 / 09:32:

> I tried to run the bootable iso image grml64-full_2014.10-rc1.iso (using grub-imageboot)
> but it doesn't install properly, showing the following warning and starting busybox:
> ---
> Begin: Mounting root file system... *Warning: BOOTID does not match.
[...]

> No such issue using grml64-full_2014.03.iso, it runs properly.

Does it work for you with boot option ignore_bootid?
How much memory/RAM do you have available?

regards,
-mika-

I tried to run the bootable iso image grml64-full_2014.10-rc1.iso (using grub-imageboot)
but it doesn't install properly, showing the following warning and starting busybox:
---
Begin: Mounting root file system... *Warning: BOOTID does not match.
Busybox buildin shell
/bin/sh: can't access tty; job control turned off
---
No such issue using grml64-full_2014.03.iso, it runs properly.

My system:
System:    Host: debian Kernel: 3.17-2.dmz.1-liquorix-amd64 x86_64 (64 bit)
            Desktop: Xfce 4.11.8git-de73451 Distro: Debian GNU/Linux jessie/sid
Machine:   System: Acer (portable) product: TravelMate 4530 v: V1.11 serial: LXTPN0C01491707B691601
            Mobo: Acer model: Elgon serial: LXTPN0C01491707B691601
            Bios: Acer v: V1.11 date: 08/06/2008
CPU:       Dual core AMD Athlon X2 QL-64 (-MCP-) clocked at 2100 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RS780M [Mobility Radeon HD 3200]
            Display Server: X.org 1.16.99.1 driver: radeon
            tty size: 80x24 Advanced Data: N/A for root
Network:   Card-1: Ralink RT2790 Wireless 802.11n 1T/2R PCIe driver: rt2800pci
            Card-2: Broadcom NetXtreme BCM5764M Gigabit Ethernet PCIe
            driver: tg3
Drives:    HDD Total Size: 250.1GB (23.3% used)