From:
[email protected]
On Sat, 28 Jun 2025 12:59:19 +0000 Wolfgang Zarre <
[email protected]> wrote:
I'll inform you as soon as I have an idea.
I had a look at it and actually I cannot reproduce root=/dev/mapper/loop.. in grub.cfg,
but maybe I did something wrong or I utilise a different scenario.
Anyway, the following I did which was working flawless and I could start it with qemu
without issues:
Test with grml-debootstrap on Debian 12:
grml-debootstrap version 0.103 with unmodified default configuration
-------------------------------
diff -Nup /usr/sbin/grml-debootstrap.orig /usr/sbin/grml-debootstrap
--- /usr/sbin/grml-debootstrap.orig 2023-02-20 11:40:07.000000000 +0100
+++ /usr/sbin/grml-debootstrap 2025-07-03 09:10:49.906989258 +0200
@@ -2014,6 +2014,7 @@ chrootscript() {
else
einfo "Executing chroot-script now"
mount -t devtmpfs udev "${MNTPOINT}"/dev
+ mount -o remount,bind,ro "${MNTPOINT}"/dev
mount -t devpts devpts "${MNTPOINT}"/dev/pts
if [ "$DEBUG" = "true" ] ; then
chroot "$MNTPOINT" /bin/bash -x /bin/chroot-script ; RC=$? -------------------------------
# truncate -s 8G test-image-mbr.img
# fdisk -l test-image-mbr.img
Disk test-image-mbr.img: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x11d9d0cb
Device Boot Start End Sectors Size Id Type test-image-mbr.img1 2048 16777215 16775168 8G 83 Linux
# losetup -P -f test-image-mbr.im