ISO error message during boot: mount: /sysroot: special device LiveOS_rootfs does not exist

Patrick · March 18, 2024, 1:50pm

Does not have any known bad effects but is an optical issue that many users will report, therefore needs to be fixed.

Mar 12 12:51:24 localhost systemd[1]: run-initramfs-squashfs.mount: Deactivated successfully.
Mar 12 12:51:24 localhost systemd[1]: Mounting sysroot.mount - /sysroot...
Mar 12 12:51:24 localhost mount[545]: mount: /sysroot: special device LiveOS_rootfs does not exist.
Mar 12 12:51:24 localhost mount[545]:        dmesg(1) may have more information after failed mount system call.
Mar 12 12:51:24 localhost systemd[1]: sysroot.mount: Mount process exited, code=exited, status=32/n/a
Mar 12 12:51:24 localhost systemd[1]: sysroot.mount: Failed with result 'exit-code'.
Mar 12 12:51:24 localhost systemd[1]: Failed to mount sysroot.mount - /sysroot.
Mar 12 12:51:24 localhost systemd[1]: Reached target initrd-root-fs.target - Initrd Root File System.
Mar 12 12:51:24 localhost systemd[1]: Starting initrd-parse-etc.service - Mountpoints Configured in the Real Root...
Mar 12 12:51:24 localhost kernel: overlayfs: failed to resolve '/run/overlayfs': -2
Mar 12 12:51:24 localhost systemd[1]: initrd-parse-etc.service: Deactivated successfully.
Mar 12 12:51:24 localhost systemd[1]: Finished initrd-parse-etc.service - Mountpoints Configured in the Real Root.
Mar 12 12:51:24 localhost systemd[1]: Reached target initrd-fs.target - Initrd File Systems.
Mar 12 12:51:24 localhost systemd[1]: Reached target initrd.target - Initrd Default Target.

Patrick · April 23, 2024, 12:45pm

github.com/dracutdevs/dracut

rd.live.overlay.overlayfs doesn't seem to work when $DRACUT_SYSTEMD=1

opened 02:24PM - 12 May 22 UTC

jdharms

bug dmsquash-live

**Describe the bug** I'm attempting to boot into a squashfs image with an overl…ayfs overlay. The switch root fails, here are some relevant lines from my rdsosreport.txt: ```[ 36.385861] localhost systemd[1]: Sent message type=error sender=org.freedesktop.systemd1 destination=n/a path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=org.freedesktop.DBus.Error.InvalidArgs error-message=Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 36.385975] localhost systemctl[782]: Got message type=error sender=org.freedesktop.systemd1 destination=n/a path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=org.freedesktop.DBus.Error.InvalidArgs error-message=Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 36.385975] localhost systemctl[782]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 36.385975] localhost systemctl[782]: Bus n/a: changing state RUNNING → CLOSED [ 36.386080] localhost systemd[1]: Failed to process message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=SwitchRoot cookie=1 reply_cookie=0 signature=ss error-name=n/a error-message=n/a: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. ``` If I remove or alter the line here: https://github.com/dracutdevs/dracut/blob/master/modules.d/90dmsquash-live/dmsquash-live-root.sh#L394 to add the overlayfs even with DRACUT_SYSTEMD is not zero then my system boots exactly how I would expect it to. Is this conditional necessary? Is systemd not doing something that dracut assumes it should do? **Distribution used** Ubuntu 22.04 **Dracut version** `dracut --version` reports only `dracut`. `apt info dracut` reports version 051-1. Was installed via apt. **Init system** systemd **To Reproduce** My dracut.conf: ``` hostonly=no hostonly_cmdline="root=live:UUID=xxxxxxx-xxxx debug mitigations=auto rd.live.debug=1 rd.live.overlay.overlayfs=1 rd.shell" compress=xz uefi=yes uefi_stub=/usr/lib/........... add_dracutmodules+=" dmsquash-live " ``` /LiveOS/squashfs.img is a squashfs image containing a flat ubuntu root fs. **Expected behavior** Should set up an overlayfs fs over the squashfs image

github.com/dracut-ng/dracut-ng

rd.live.overlay.overlayfs doesn't seem to work when $DRACUT_SYSTEMD=1

opened 12:25PM - 23 Apr 24 UTC

LaszloGombos

bug

https://github.com/dracutdevs/dracut/issues/1820 Issue can be reproduced by r…unning test-16 with the following change in the source tree ``` --- a/test/TEST-16-DMSQUASH/test.sh +++ b/test/TEST-16-DMSQUASH/test.sh @@ -136,8 +136,8 @@ SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ntfs", ENV{ID_FS_TYPE}="ntfs3" EOF "$basedir"/dracut.sh -l -i "$TESTDIR"/overlay / \ - --modules "test dash dmsquash-live qemu" \ + --modules "test dash dmsquash-live qemu dracut-systemd" \ ```

Patrick · April 25, 2024, 6:43pm

Maybe related:

github.com/grml/grml-debootstrap

image should not contain folders /run /sys /proc /dev

opened 06:42PM - 25 Apr 24 UTC

adrelanos

Image should not contain folders /run /sys /proc /dev. These should be deleted a…t the end of the build process. Rationale: * These don't belong there. Serve no purpose. Are instantiated during the boot process. * Are confusing dracut. Relevant code excerpt: https://github.com/dracutdevs/dracut/blob/master/modules.d/90dmsquash-live/dmsquash-live-root.sh ``` elif [ -d /run/initramfs/squashfs/proc ]; then FSIMG=$SQUASHED if [ -z "$overlayfs" ] && [ -n "$DRACUT_SYSTEMD" ]; then reloadsysrootmountunit=":>/xor_overlayfs;" fi overlayfs="required" ``` (Some dracut internals: Folder `/run/initramfs/squashfs/proc` is inside the `LiveOS/squashfs.img`, which can be based on grml-debootstrap (and created by mksquashfs). An image containing an already existing `/proc` folder can be useful for I don't know what. But either the `/proc` folder should be complete. This is probably for a complex use case we don't know about. Absent of this, best if the `/proc` folder doesn't exist. There should not be an empty folder `/proc` inside the image.) Would a PR deleting these folders be welcome?

Patrick · April 25, 2024, 8:08pm

github.com/dracut-ng/dracut-ng

`LiveOS/squashfs.img` missing an empty `/proc` results in broken boot

opened 08:07PM - 25 Apr 24 UTC

adrelanos

bug

dracut currently requires in some cases folder `/proc` to be existing inside the… `LiveOS/squashfs.img`. No image should require to come with an empty `/proc` folder. [`dmsquash-live-root.sh`](https://github.com/dracut-ng/dracut-ng/blob/main/modules.d/90dmsquash-live/dmsquash-live-root.sh#L347) ``` elif [ -d /run/initramfs/squashfs/proc ]; then ``` This seems wrong. `/proc` is created at boot time. There should be no need for an image to come with an empty `/proc` folder. Was also pointed out by @FGrose here: https://github.com/dracutdevs/dracut/issues/1820#issuecomment-1206498286 (and also been the committer https://github.com/dracut-ng/dracut-ng/commit/789668deb3e6f8584ffab964d2204ddcb75f0a06). I guess the intention is to check if the mounting of the `LiveOS/squashfs.img` has resulted in a usable image? How about checking `/usr` instead? Images without `/etc` might be available at some point but probably not without `/usr` which seems more appropriate.

Patrick · September 14, 2024, 1:50pm

This might likely be fixed once Debian live-build gets dracut support.

And once Kicksecure starts using live-build to create ISO images.

Patrick · September 29, 2024, 9:12am

Debian bug report:
dracut-core: Live Bookworm ISO + dracut boot faliure with "mount: /sysroot: special device LiveOS_rootfs does not exist.

Thanks to @arraybolt3!