Time-out on waiting for label ROOT uuid on ISO boot

77 views
Skip to first unread message

Jan Robinson

unread,
Aug 22, 2025, 7:49:32 AMAug 22
to kiwi
Hello Marcus

Please assist.

Goal: To build a SLES16 version of our MiniOS ISO image we use to install physical servers.

Building the image works 100%
Booting the image with qemu-kv works 100%

Booting the image on hardware fails.
Loading kernel...  all fine
Loading initrd...  problem starts here

During the kiwi-ng build this line is reported with an UUID.

[ INFO    ]: 12:25:11 | --> DEFAULT_APPEND:"splash=verbose rd.kiwi.ramdisk ramdisk_size=4096000 rd.shell rd.kiwi.debug root=UUID=b611ce5b-b0ba-410f-9c54-ec8a80b5fcb0"


In the qemu-kv booted image the UUID is used.
blkid -o json
{
   "label": "ROOT",
   "uuid": "b611ce5b-b0ba-410f-9c54-ec8a80b5fcb0",
   "block_size": "4096",
   "type": "ext4",
   "partlabel": "p.lxroot",
   "partuuid": "167fb5f1-58bc-43a4-b02b-90740cf36e61"
}





Problem:
As I interpret it.

Short:
Timed out waiting for device /dev/disk/by-uuid/b611ce5b-b0ba-410f-9c54-ec8a80b5fcb0
UUID not available

Long:
------------------------------------------------------------------------
       ┌───────────────────────────────────────────────────────────────┐
       │ Loading SLES16-MiniOS-ABC-UEFI.INPROGRESS.raw...              │
       │                                                               │
       │  ┌─────────────────────────────────────────────────────────┐  │
       │  │                           80%               [ TIME [  OK  ] Started Emergency Shell.
[  OK  ] Reached target Emergency Mode.─────────────────────────────┘  │
[  OK  ] Stopped dracut pre-mount hook.────────────────────────────────┘
[  OK  ] Stopped Dracut Run Interactive.
[  OK  ] Stopped dracut initqueue hook.
[  OK  ] Stopped dracut pre-trigger hook.
[  OK  ] Stopped dracut pre-udev hook.
[  OK  ] Stopped dracut cmdline hook.

Press Enter for system maintenance
(or press Control-D to continue):
------------------------------------------------------------------------

Because the ISO image is booted on a server that already have a SLES installation on it.
This ROOT label's uuid does exist.
{
   "label": "ROOT",
   "uuid": "df25bc3e-3994-4090-883f-d4b79ee0d654",
   "block_size": "512",
   "type": "xfs",
   "partuuid": "12e6cb22-8bb2-4241-aec5-ef1803d88537"
}


dracut:/run/initramfs# grep -B3 -A5 ec8a80b5fcb0 rdsosreport.txt
[    2.762739] localhost systemd[1]: bpf-restrict-fs: LSM BPF program attached
[    2.762746] localhost systemd[1]: Queued start job for default target Initrd Default Target.
[    2.762753] localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    2.762760] localhost systemd[1]: Expecting device /dev/disk/by-uuid/b611ce5b-b0ba-410f-9c54-ec8a80b5fcb0...
[    2.762767] localhost systemd[1]: Reached target Local Encrypted Volumes.
[    2.762774] localhost systemd[1]: Reached target Initrd Root Device.
[    2.762780] localhost systemd[1]: Reached target Initrd /usr File System.
[    2.762787] localhost kernel: tsc: Refined TSC clocksource calibration: 2095.077 MHz
[    2.762793] localhost kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1e33060eadb, max_idle_ns: 440795261188 ns
--
[   17.131007] localhost kernel: loop0: detected capacity change from 0 to 507904
[   17.134006] localhost kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   17.166979] localhost systemd[1]: Starting Dracut Run Interactive...
[   91.615795] localhost systemd[1]: dev-disk-by\x2duuid-b611ce5b\x2db0ba\x2d410f\x2d9c54\x2dec8a80b5fcb0.device: Job dev-disk-by\x2duuid-b611ce5b\x2db0ba\x2d410f\x2d9c54\x2dec8a80b5fcb0.device/start timed out.
[   91.615810] localhost systemd[1]: Timed out waiting for device /dev/disk/by-uuid/b611ce5b-b0ba-410f-9c54-ec8a80b5fcb0.
[   91.615915] localhost systemd[1]: Dependency failed for /sysroot.
[   91.615946] localhost systemd[1]: Dependency failed for Initrd Root File System.
[   91.615974] localhost systemd[1]: Dependency failed for Mountpoints Configured in the Real Root.
[   91.616014] localhost systemd[1]: initrd-parse-etc.service: Job initrd-parse-etc.service/start failed with result 'dependency'.
[   91.616019] localhost systemd[1]: initrd-parse-etc.service: Triggering OnFailure= dependencies.
[   91.616162] localhost systemd[1]: initrd-root-fs.target: Job initrd-root-fs.target/start failed with result 'dependency'.
[   91.616165] localhost systemd[1]: initrd-root-fs.target: Triggering OnFailure= dependencies.
[   91.616221] localhost systemd[1]: sysroot.mount: Job sysroot.mount/start failed with result 'dependency'.
[   91.616226] localhost systemd[1]: dev-disk-by\x2duuid-b611ce5b\x2db0ba\x2d410f\x2d9c54\x2dec8a80b5fcb0.device: Job dev-disk-by\x2duuid-b611ce5b\x2db0ba\x2d410f\x2d9c54\x2dec8a80b5fcb0.device/start failed with result 'timeout'.
[   91.616770] localhost systemd[1]: systemd-ask-password-console.path: Deactivated successfully.
[   91.620025] localhost systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
[   91.620092] localhost systemd[1]: Stopped target Basic System.
[   91.620124] localhost systemd[1]: Reached target Initrd File Systems.
[   91.620142] localhost systemd[1]: Stopped target System Initialization.


Setup:
config.xml
    <type image="oem" filesystem="ext4" installiso="true" initrd_system="dracut" installboot="install" kernelcmdline="splash=verbose rd.kiwi.ramdisk ramdisk_size=4096000 rd.shell rd.kiwi.debug" firmware="efi">
       
    <source path="https://rmt.abcgroup.net/repo/SUSE/Products/SLE-Product-SLES/16.0/x86_64/product/"/>    
    <source path="https://smt.abcgroup.net/repo/SUSE/Products/PackageHub/16.0/x86_64/product/"/>
    <source path="https://smt.abcgroup.net/repo/SUSE/Backports/SLE-16.0_x86_64/standard/"/>
    <source path="https://download.opensuse.org/repositories/Virtualization:/Appliances:/Staging/SLFO/"/> (Builder also tried)


grep dracut /global/http/uefiminios-result16/SLES16-MiniOS-ABC-UEFI.INPROGRESS.x86_64-16.0.packages

dracut-kiwi-lib|(none)|10.2.32|160000.3.1|x86_64|obs://build.opensuse.org/Virtualization:Appliances:Staging/SLFO/182414bb6fa3c8cc33bc4dbb5cc2442e-python-kiwi|GPL-3.0-or-later
dracut-kiwi-live|(none)|10.2.32|160000.3.1|x86_64|obs://build.opensuse.org/Virtualization:Appliances:Staging/SLFO/182414bb6fa3c8cc33bc4dbb5cc2442e-python-kiwi|GPL-3.0-or-later
dracut-kiwi-oem-dump|(none)|10.2.32|160000.3.1|x86_64|obs://build.opensuse.org/Virtualization:Appliances:Staging/SLFO/182414bb6fa3c8cc33bc4dbb5cc2442e-python-kiwi|GPL-3.0-or-later
dracut-kiwi-oem-repart|(none)|10.2.32|160000.3.1|x86_64|obs://build.opensuse.org/Virtualization:Appliances:Staging/SLFO/182414bb6fa3c8cc33bc4dbb5cc2442e-python-kiwi|GPL-3.0-or-later
dracut|(none)|059+suse.692.g6ec224d5|160000.1.3|x86_64|obs://build.suse.de/SUSE:SLFO:Main:Build/standard/56fc723e26103361ccdb6e1042b52c8f-dracut|GPLv2+ and LGPLv2+ and GPLv2


The kiwi server:

SUSE Linux Enterprise Server 15 SP5

kiwi-boot-descriptions-1.2.0-2.51.x86_64
kiwi-man-pages-10.2.32-lp156.3.1.x86_64
kiwi-systemdeps-bootloaders-10.2.32-lp156.3.1.x86_64
kiwi-systemdeps-containers-10.2.32-lp156.3.1.x86_64
kiwi-systemdeps-core-10.2.32-lp156.3.1.x86_64
kiwi-systemdeps-disk-images-10.2.32-lp156.3.1.x86_64
kiwi-systemdeps-filesystems-10.2.32-lp156.3.1.x86_64
kiwi-systemdeps-image-validation-10.2.32-lp156.3.1.x86_64
kiwi-systemdeps-iso-media-10.2.32-lp156.3.1.x86_64
python311-kiwi-10.2.32-lp156.3.1.x86_64
python311-solv-0.7.30-150400.3.27.2.x86_64

Thank you.
       

       
        

Jan Robinson

unread,
Sep 10, 2025, 6:26:55 AMSep 10
to kiwi
Hi

With updating dracut to dracut-kiwi-lib|(none)|10.2.32|160000.8.1|x86_64
The problem persists.
QEMU works
Booting the ISO on hardware fails.

Attached is two logs.
rdosreport.txt
kiwi.boot.

Could you please assist.

Thanks so much.
kiwi-rdsosreport-10sept25.txt
kiwi-boot.kiwi-10sept25.txt

Marcus Schäfer

unread,
Sep 10, 2025, 9:14:53 AMSep 10
to kiwi-...@googlegroups.com
Hi Jan,

> Booting the ISO on hardware fails.

I looked at the log files and I was wondering about the following.
It seems this ISO installs the image into a ramdisk. As I can see
from the log:

dump_local_image /run/image/SLES16-MiniOS-abc-UEFI.INPROGRESS.raw /dev/ram0 /dev/install_progress

When using a ramdisk as target to install, kiwi does not reboot
because that would wipe all data in RAM. Instead it directly boots
into the system. I saw the needed cmdline parameters for this
setup are also set "rd.kiwi.ramdisk ramdisk_size=4096000"

When I replicate this setup here locally the system in RAM is
mounted using the unix device node names for the ramdisk deployment,
which is the expected behavior:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
ram0
...
|-ram0p3 254:2 0 2.4G 0 part /

Further looking into your logs I see

/dev/ram0: PTUUID="b7a5c098-a98e-4269-ae28-7c4a0a8ad267" PTTYPE="gpt"

which indicates there is some system in ram. The actual cmdline looks
ok to me too:

[ 3.970082] localhost dracut-cmdline[490]: Using kernel command line parameters: BOOT_IMAGE=(cd0)/boot/x86_64/loader/linux cdinst=1 splash=verbose rd.kiwi.ramdisk ramdisk_size=4096000 rd.shell rd.kiwi.debug console=ttyS1,230400n8 console=ttyS0,230400n8 loglevel=0 root=install:CDLABEL=INSTALL ip=10.2.24.220 netmask=255.255.255.0 gw=10.2.24.1 hst=itadell200 dom=abcgroup.net dns=160.50.250.2 v6ip=2a03:1e80:f807:51e:0:0:1:6 v6gw=2a03:1e80:f807:51e:0:0:0:1 v6prefix=64

later on it tries to use another device for sysroot

[ 16.638370] localhost systemd[1]: Starting Dracut Run Interactive...
[ 91.537696] localhost systemd[1]: dev-disk-by\x2duuid-64bed273\x2d7267\x2d4860\x2d9769\x2d5035a0acd62c.device: Job dev-disk-by\x2duuid-64bed273\x2d7267\x2d4860\x2d9769\x2d5035a0acd62c.device/start timed out.
[ 91.537710] localhost systemd[1]: Timed out waiting for device /dev/disk/by-uuid/64bed273-7267-4860-9769-5035a0acd62c.

And this part is completely weird.

Are you using other dracut module code e.g iscsi target or something
which triggers a different sysroot.mount unit ?

From the log information you sent I don't see where this change
in sysroot had happened. In kiwi and when you are using rd.kiwi.ramdisk,
kiwi creates a sysroot.mount unit suitable for booting into a
ramdisk. Im my test this information also appears in journalctl
if you boot with rd.debug (and no rd.kiwi.debug)

Sep 10 14:56:11 localhost(sd-e[149]): /usr/lib/systemd/system-generators/dracut-kiwi-ramdisk-generator succeeded.

That generator is produced via this code

https://github.com/OSInside/kiwi/blob/main/dracut/modules.d/55kiwi-dump/kiwi-ramdisk-deployment-generator.sh


I guess when you are testing in qemu the generated sysroot.mount
unit is the one from this generator. If you are testing on real hardware
it seems that some other code also creates a sysroot.mount unit
for a device that doesn't exist.

I'm sorry there is not more debugging that I can offer with the
provided logs. Maybe this helps in your research a bit

Regards,
Marcus
--
Public Key available via: https://keybase.io/marcus_schaefer/key.asc
keybase search marcus_schaefer
signature.asc

Jan Robinson

unread,
Sep 11, 2025, 7:33:13 AMSep 11
to kiwi
Hello Markus,
thank you for the reply.

This booted ISO is meant to be installed/running as a RAM-disk.
We use this as a rescue and install(get image and dd it to the hard drive) disk.
This works in SLES15 SP4/5/6/7.

It is booted on a server where an existing installation is running.
SLES15 ISO accommodates the exiting installation with a /dev/sda4: LABEL="ROOT" UUID=xx
is present, SLES16 does not.

It does boot in QEMU as these is no existing volume with LABEL="ROOT".

Could please try to boot this iso on a physical server with an installed SLES?

Thanks again.
Jan

Marcus Schäfer

unread,
Sep 11, 2025, 9:49:58 AMSep 11
to kiwi-...@googlegroups.com
Hi,

> This booted ISO is meant to be installed/running as a RAM-disk.
> We use this as a rescue and install(get image and dd it to the hard
> drive) disk.

ok

> This works in SLES15 SP4/5/6/7.
> It is booted on a server where an existing installation is running.
> SLES15 ISO accommodates the exiting installation with a /dev/sda4:
> LABEL="ROOT" UUID=xx
> is present, SLES16 does not.
> It does boot in QEMU as these is no existing volume with LABEL="ROOT".
> Could please try to boot this iso on a physical server with an
> installed SLES?

Hmm, so you are saying we have a label clash. Does it fix the issue
if you build your ramdisk image with:

<type .... rootfs_label="some"/>

?
signature.asc

Jan Robinson

unread,
Sep 11, 2025, 10:25:29 AMSep 11
to kiwi
Hi Marcus

Sorry, it does not.

The label is called: RAMROOT

kiwi-ng build.

[ DEBUG   ]: 15:56:02 | EXEC: [mkfs.ext4 -L RAMROOT -U 843f3433-52fe-4dac-89bc-7eab24ffa588 /dev/loop0p3]
[ INFO    ]: 15:56:07 | --> DEFAULT_APPEND:"splash=verbose rd.kiwi.ramdisk ramdisk_size=4096000 rd.shell rd.kiwi.debug console=ttyS1,230400n8 console=ttyS0,230400n8 root=UUID=843f3433-52fe-4dac-89bc-7eab24ffa588 "

Debug shell.

dracut:/run/initramfs# grep timeout rdsosreport.txt
[    5.718492] localhost kernel: megaraid_sas 0000:c5:00.0: FW provided TM TaskAbort/Reset timeout      : 6 secs/60 secs
[   91.608062] localhost systemd[1]: dev-disk-by\x2duuid-843f3433\x2d52fe\x2d4dac\x2d89bc\x2d7eab24ffa588.device: Job dev-disk-by\x2duuid-843f3433\x2d52fe\x2d4dac\x2d89bc\x2d7eab24ffa588.device/start failed with result 'timeout'.

dracut:/run/initramfs# blkid
/dev/mapper/vglocal-lvvartmp: LABEL="LVVARTMP" UUID="2daa5917-2e32-4aac-a2da-cfde0b77aa9c" BLOCK_SIZE="512" TYPE="xfs"
/dev/mapper/vglocal-lvnfs: LABEL="LVNFS" UUID="7bee8e0b-459a-4e02-93f7-54e3576027ed" BLOCK_SIZE="512" TYPE="xfs"
/dev/sr0: BLOCK_SIZE="2048" UUID="2025-09-11-16-01-31-00" LABEL="INSTALL" TYPE="iso9660"
/dev/mapper/vglocal-lvhome: LABEL="LVHOME" UUID="825b985d-e77a-49fd-9acc-b08f4d6667ae" BLOCK_SIZE="512" TYPE="xfs"
/dev/loop0: BLOCK_SIZE="1048576" TYPE="squashfs"
/dev/mapper/vglocal-lvvarcrash: LABEL="LVVARCRASH" UUID="62435454-8cdf-4def-9fe0-1fafcd774341" BLOCK_SIZE="512" TYPE="xfs"
/dev/sda4: LABEL="ROOT" UUID="a324f8a6-3627-4d6c-90a0-004c178d6bdc" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="63f91285-e9d9-114b-bab1-5531ce9816a3"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI" LABEL="EFI" UUID="CAA8-1D48" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="p.UEFI" PARTUUID="f64678fc-664c-4727-9174-c0d045df30d9"
/dev/sda5: LABEL="SWAP" UUID="38721685-268d-45c9-9226-ba3ab48e9d4d" TYPE="swap" PARTLABEL="primary" PARTUUID="ef76032b-b7cb-45be-9683-e4f2e3e83f39"
/dev/sda3: LABEL="BOOT" UUID="ea161336-07de-439b-b93d-78e5b5935fda" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="p.lxboot" PARTUUID="1ef07181-7eee-4cb1-9ec2-bd8cbfd14961"
/dev/sda6: UUID="gVlUuu-HzLf-Pos8-n6bp-YIvC-KRSA-3A5LYl" TYPE="LVM2_member" PARTLABEL="primary" PARTUUID="799ac4ac-7575-4ab4-90cb-01180fb4b0f6"
/dev/mapper/vglocal-lvtmp: LABEL="LVTMP" UUID="af90bcdf-cf16-4ca1-bbd3-32bec5567088" BLOCK_SIZE="512" TYPE="xfs"
/dev/ram0: PTUUID="4f67f145-cecc-4bc0-807b-efd090fc058a" PTTYPE="gpt"
/dev/sda1: PARTLABEL="p.legacy" PARTUUID="5c479a2d-663b-4543-aa42-f3f3487994a2"

Regards.

Marcus Schäfer

unread,
Sep 11, 2025, 10:46:12 AMSep 11
to kiwi-...@googlegroups.com
Hi,

> Sorry, it does not.

Ok, I still don't think that the sysroot.mount unit for ramdisk
deployments from the kiwi provided systemd generator is used here,
for whatever reason. I also tested with a system that has SLES
installed and I cannot reproduce the problem you have. Strange.

So when you are in that initrd debug shell, can you look and
find the sysroot.mount file and see what is inside ?

Also what does lsblk from the debug shell tell you ?

Also what does ls -l /dev/disk/by-id from the debug shell tell you ?

Also you can try to rebuild your ram image with a hack like this:

<type ... kernelcmdline="... root=/dev/mapper/ram0p3"/>

This forces root to be looked up at "/dev/mapper/ram0p3" which
should exist for ramdisk deployments. But that's not really a
good solution.

I could imagine that udev does not create by-id representations
for ramdisk mapped partitions. Thus it's not surprising that
/dev/disk/by-id/843f3433-52fe-4dac-89bc-7eab24ffa588 was not
found, but it should also actually not searched

Pretty confusing one
signature.asc

Jan Robinson

unread,
Sep 11, 2025, 10:52:17 AMSep 11
to kiwi
Thank you Marcus, will let you know tomorrow.

Jan Robinson

unread,
Sep 12, 2025, 5:41:51 AMSep 12
to kiwi
Hello Marcus.

No change.

Now using:
dracut-kiwi-lib|(none)|10.2.33|160000.1.1|x86_64

Attached:
kiwi-rdsosreport-12sept25-0900
kiwi-boot.kiwi-12sept25-0900


Hardware boot:

<type image="oem" filesystem="ext4" installiso="true" initrd_system="dracut" installboot="install" kernelcmdline="splash=verbose rd.kiwi.ramdisk ramdisk_size=4096000 rd.shell rd.kiwi.debug console=ttyS1,230400n8 console=ttyS0,230400n8  root=/dev/mapper/ram0p3" firmware="efi" rootfs_label="RAMROOT" >


NAME                   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0                    7:0    0 244.5M  1 loop /run/image
sda                      8:0    0 446.6G  0 disk
|-sda1                   8:1    0     2M  0 part
|-sda2                   8:2    0   100M  0 part
|-sda3                   8:3    0     1G  0 part
|-sda4                   8:4    0    85G  0 part
|-sda5                   8:5    0    32G  0 part
`-sda6                   8:6    0 328.5G  0 part
  |-vglocal-lvvarcrash 254:0    0    50G  0 lvm
  |-vglocal-lvvartmp   254:1    0     8G  0 lvm
  |-vglocal-lvhome     254:2    0     5G  0 lvm
  |-vglocal-lvtmp      254:3    0     2G  0 lvm
  `-vglocal-lvnfs      254:4    0   500M  0 lvm
sr0                     11:0    1 378.5M  0 rom  /run/install


dracut:/root# blkid

/dev/mapper/vglocal-lvvartmp: LABEL="LVVARTMP" UUID="2daa5917-2e32-4aac-a2da-cfde0b77aa9c" BLOCK_SIZE="512" TYPE="xfs"
/dev/mapper/vglocal-lvnfs: LABEL="LVNFS" UUID="7bee8e0b-459a-4e02-93f7-54e3576027ed" BLOCK_SIZE="512" TYPE="xfs"
/dev/sr0: BLOCK_SIZE="2048" UUID="2025-09-12-08-08-48-00" LABEL="INSTALL" TYPE="iso9660"

/dev/mapper/vglocal-lvhome: LABEL="LVHOME" UUID="825b985d-e77a-49fd-9acc-b08f4d6667ae" BLOCK_SIZE="512" TYPE="xfs"
/dev/loop0: BLOCK_SIZE="1048576" TYPE="squashfs"
/dev/mapper/vglocal-lvvarcrash: LABEL="LVVARCRASH" UUID="62435454-8cdf-4def-9fe0-1fafcd774341" BLOCK_SIZE="512" TYPE="xfs"
/dev/sda4: LABEL="ROOT" UUID="a324f8a6-3627-4d6c-90a0-004c178d6bdc" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="63f91285-e9d9-114b-bab1-5531ce9816a3"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI" LABEL="EFI" UUID="CAA8-1D48" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="p.UEFI" PARTUUID="f64678fc-664c-4727-9174-c0d045df30d9"
/dev/sda5: LABEL="SWAP" UUID="38721685-268d-45c9-9226-ba3ab48e9d4d" TYPE="swap" PARTLABEL="primary" PARTUUID="ef76032b-b7cb-45be-9683-e4f2e3e83f39"
/dev/sda3: LABEL="BOOT" UUID="ea161336-07de-439b-b93d-78e5b5935fda" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="p.lxboot" PARTUUID="1ef07181-7eee-4cb1-9ec2-bd8cbfd14961"
/dev/sda6: UUID="gVlUuu-HzLf-Pos8-n6bp-YIvC-KRSA-3A5LYl" TYPE="LVM2_member" PARTLABEL="primary" PARTUUID="799ac4ac-7575-4ab4-90cb-01180fb4b0f6"
/dev/mapper/vglocal-lvtmp: LABEL="LVTMP" UUID="af90bcdf-cf16-4ca1-bbd3-32bec5567088" BLOCK_SIZE="512" TYPE="xfs"
/dev/ram0: PTUUID="5211a675-9631-46cb-a995-3d1f78f79d43" PTTYPE="gpt"

/dev/sda1: PARTLABEL="p.legacy" PARTUUID="5c479a2d-663b-4543-aa42-f3f3487994a2"


dracut:/root# l /dev/disk/by-uuid/
total 0
drwxr-xr-x  2 root root 240 Sep 12 06:13 .
drwxr-xr-x 11 root root 220 Sep 12 06:13 ..
lrwxrwxrwx  1 root root   9 Sep 12 06:13 2025-09-12-08-08-48-00 -> ../../sr0
lrwxrwxrwx  1 root root  10 Sep 12 06:13 2daa5917-2e32-4aac-a2da-cfde0b77aa9c -> ../../dm-1
lrwxrwxrwx  1 root root  10 Sep 12 06:13 38721685-268d-45c9-9226-ba3ab48e9d4d -> ../../sda5
lrwxrwxrwx  1 root root  10 Sep 12 06:13 62435454-8cdf-4def-9fe0-1fafcd774341 -> ../../dm-0
lrwxrwxrwx  1 root root  10 Sep 12 06:13 7bee8e0b-459a-4e02-93f7-54e3576027ed -> ../../dm-4
lrwxrwxrwx  1 root root  10 Sep 12 06:13 825b985d-e77a-49fd-9acc-b08f4d6667ae -> ../../dm-2
lrwxrwxrwx  1 root root  10 Sep 12 06:13 CAA8-1D48 -> ../../sda2
lrwxrwxrwx  1 root root  10 Sep 12 06:13 a324f8a6-3627-4d6c-90a0-004c178d6bdc -> ../../sda4
lrwxrwxrwx  1 root root  10 Sep 12 06:13 af90bcdf-cf16-4ca1-bbd3-32bec5567088 -> ../../dm-3
lrwxrwxrwx  1 root root  10 Sep 12 06:13 ea161336-07de-439b-b93d-78e5b5935fda -> ../../sda3
dracut:/root# l /dev/disk/by-id/
total 0
drwxr-xr-x  2 root root 540 Sep 12 06:13 .
drwxr-xr-x 11 root root 220 Sep 12 06:13 ..
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-name-vglocal-lvhome -> ../../dm-2
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-name-vglocal-lvnfs -> ../../dm-4
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-name-vglocal-lvtmp -> ../../dm-3
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-name-vglocal-lvvarcrash -> ../../dm-0
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-name-vglocal-lvvartmp -> ../../dm-1
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-uuid-LVM-B7xsNd1VKrgdYe84GcBFLIRWliAO1DX318ERWXWJkFV3RzCZZjnAZbk1mxXwLE3X -> ../../dm-2
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-uuid-LVM-B7xsNd1VKrgdYe84GcBFLIRWliAO1DX33T6p1Q4QdDdes0ozDY8m3v7HfqUCicJS -> ../../dm-4
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-uuid-LVM-B7xsNd1VKrgdYe84GcBFLIRWliAO1DX3fyvymtkjvUSCLuUt1A3G6C0P8FwefduU -> ../../dm-0
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-uuid-LVM-B7xsNd1VKrgdYe84GcBFLIRWliAO1DX3mcEVPbzxONtDEzBN9HUdQjMHLCVJTdSt -> ../../dm-3
lrwxrwxrwx  1 root root  10 Sep 12 06:13 dm-uuid-LVM-B7xsNd1VKrgdYe84GcBFLIRWliAO1DX3ryvaD2z60TRnTolQ26Qf6dOpUl50I0RB -> ../../dm-1
lrwxrwxrwx  1 root root   9 Sep 12 06:13 scsi-36f4ee0802304a600304dc6a3577a35de -> ../../sda
lrwxrwxrwx  1 root root  10 Sep 12 06:13 scsi-36f4ee0802304a600304dc6a3577a35de-part1 -> ../../sda1
lrwxrwxrwx  1 root root  10 Sep 12 06:13 scsi-36f4ee0802304a600304dc6a3577a35de-part2 -> ../../sda2
lrwxrwxrwx  1 root root  10 Sep 12 06:13 scsi-36f4ee0802304a600304dc6a3577a35de-part3 -> ../../sda3
lrwxrwxrwx  1 root root  10 Sep 12 06:13 scsi-36f4ee0802304a600304dc6a3577a35de-part4 -> ../../sda4
lrwxrwxrwx  1 root root  10 Sep 12 06:13 scsi-36f4ee0802304a600304dc6a3577a35de-part5 -> ../../sda5
lrwxrwxrwx  1 root root  10 Sep 12 06:13 scsi-36f4ee0802304a600304dc6a3577a35de-part6 -> ../../sda6
lrwxrwxrwx  1 root root   9 Sep 12 06:13 usb-Linux_Virtual_CD_DVD_1028_123456-0:0 -> ../../sr0
lrwxrwxrwx  1 root root   9 Sep 12 06:13 wwn-0x6f4ee0802304a600304dc6a3577a35de -> ../../sda
lrwxrwxrwx  1 root root  10 Sep 12 06:13 wwn-0x6f4ee0802304a600304dc6a3577a35de-part1 -> ../../sda1
lrwxrwxrwx  1 root root  10 Sep 12 06:13 wwn-0x6f4ee0802304a600304dc6a3577a35de-part2 -> ../../sda2
lrwxrwxrwx  1 root root  10 Sep 12 06:13 wwn-0x6f4ee0802304a600304dc6a3577a35de-part3 -> ../../sda3
lrwxrwxrwx  1 root root  10 Sep 12 06:13 wwn-0x6f4ee0802304a600304dc6a3577a35de-part4 -> ../../sda4
lrwxrwxrwx  1 root root  10 Sep 12 06:13 wwn-0x6f4ee0802304a600304dc6a3577a35de-part5 -> ../../sda5
lrwxrwxrwx  1 root root  10 Sep 12 06:13 wwn-0x6f4ee0802304a600304dc6a3577a35de-part6 -> ../../sda6

dracut:/root# ls -l /sys/fs/cgroup/system.slice/
total 0
-r--r--r-- 1 root root 0 Sep 12 07:01 cgroup.controllers
-r--r--r-- 1 root root 0 Sep 12 06:13 cgroup.events
-rw-r--r-- 1 root root 0 Sep 12 07:01 cgroup.freeze
--w------- 1 root root 0 Sep 12 07:01 cgroup.kill
-rw-r--r-- 1 root root 0 Sep 12 07:01 cgroup.max.depth
-rw-r--r-- 1 root root 0 Sep 12 07:01 cgroup.max.descendants
-rw-r--r-- 1 root root 0 Sep 12 07:01 cgroup.procs
-r--r--r-- 1 root root 0 Sep 12 07:01 cgroup.stat
-rw-r--r-- 1 root root 0 Sep 12 06:13 cgroup.subtree_control
-rw-r--r-- 1 root root 0 Sep 12 07:01 cgroup.threads
-rw-r--r-- 1 root root 0 Sep 12 07:01 cgroup.type
-r--r--r-- 1 root root 0 Sep 12 07:01 cpu.stat
-r--r--r-- 1 root root 0 Sep 12 07:01 cpu.stat.local
drwxr-xr-x 2 root root 0 Sep 12 06:14 emergency.service
-r--r--r-- 1 root root 0 Sep 12 07:01 pids.current
-r--r--r-- 1 root root 0 Sep 12 07:01 pids.events
-r--r--r-- 1 root root 0 Sep 12 07:01 pids.events.local
-rw-r--r-- 1 root root 0 Sep 12 06:13 pids.max
-r--r--r-- 1 root root 0 Sep 12 07:01 pids.peak
drwxr-xr-x 2 root root 0 Sep 12 06:13 systemd-journald.service
drwxr-xr-x 3 root root 0 Sep 12 06:13 systemd-udevd.service

dracut:/root# ls -l /sys/fs/cgroup/system.slice/emergency.service/
total 0
-r--r--r-- 1 root root 0 Sep 12 07:02 cgroup.controllers
-r--r--r-- 1 root root 0 Sep 12 06:14 cgroup.events
-rw-r--r-- 1 root root 0 Sep 12 07:02 cgroup.freeze
--w------- 1 root root 0 Sep 12 07:02 cgroup.kill
-rw-r--r-- 1 root root 0 Sep 12 07:02 cgroup.max.depth
-rw-r--r-- 1 root root 0 Sep 12 07:02 cgroup.max.descendants
-rw-r--r-- 1 root root 0 Sep 12 06:14 cgroup.procs
-r--r--r-- 1 root root 0 Sep 12 07:02 cgroup.stat
-rw-r--r-- 1 root root 0 Sep 12 06:14 cgroup.subtree_control
-rw-r--r-- 1 root root 0 Sep 12 07:02 cgroup.threads
-rw-r--r-- 1 root root 0 Sep 12 07:02 cgroup.type
-r--r--r-- 1 root root 0 Sep 12 07:02 cpu.stat
-r--r--r-- 1 root root 0 Sep 12 07:02 cpu.stat.local
-r--r--r-- 1 root root 0 Sep 12 07:02 pids.current
-r--r--r-- 1 root root 0 Sep 12 07:02 pids.events
-r--r--r-- 1 root root 0 Sep 12 07:02 pids.events.local
-rw-r--r-- 1 root root 0 Sep 12 06:14 pids.max
-r--r--r-- 1 root root 0 Sep 12 07:02 pids.peak

Here a cat but cannot match output to a filename.
If important I can redo witha for loop to get the name/content.

dracut:/root# cat /sys/fs/cgroup/system.slice/emergency.service/*
pids
populated 1
frozen 0
0
cat: /sys/fs/cgroup/system.slice/emergency.service/cgroup.kill: Invalid argument
max
max
2475
2529
nr_descendants 0
nr_subsys_cpuset 0
nr_subsys_cpu 0
nr_subsys_io 0
nr_subsys_memory 0
nr_subsys_perf_event 1
nr_subsys_hugetlb 0
nr_subsys_pids 1
nr_subsys_rdma 0
nr_subsys_misc 0
nr_dying_descendants 0
nr_dying_subsys_cpuset 0
nr_dying_subsys_cpu 0
nr_dying_subsys_io 0
nr_dying_subsys_memory 0
nr_dying_subsys_perf_event 0
nr_dying_subsys_hugetlb 0
nr_dying_subsys_pids 0
nr_dying_subsys_rdma 0
nr_dying_subsys_misc 0
2475
2529
domain
usage_usec 150591
user_usec 33464
system_usec 117126
nice_usec 0
core_sched.force_idle_usec 0
2
max 0
max 0
max
4

===============================================

QEMU boot (works):

<type image="oem" filesystem="ext4" installiso="true" initrd_system="dracut" installboot="install" kernelcmdline="splash=verbose rd.kiwi.ramdisk ramdisk_size=4096000 rd.shell rd.kiwi.debug console=ttyS1,230400n8 console=ttyS0,230400n8  root=/dev/mapper/ram0p3" firmware="efi" rootfs_label="RAMROOT" >

localhost-MiniOS:/root # lsblk

NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
fd0     2:0    1     4K  0 disk
loop0   7:0    0 244.5M  1 loop /run/image
sr0    11:0    1 398.4M  0 rom  /run/install


localhost-MiniOS:/root # blkid|grep ec3395ff-8202-42c7-a748-9142c664cc75
/dev/mapper/ram0p3: LABEL="RAMROOT" UUID="ec3395ff-8202-42c7-a748-9142c664cc75" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="p.lxroot" PARTUUID="dd2da203-90f8-40b7-898f-17be204787da"

localhost-MiniOS:/root # blkid
/dev/mapper/ram0p2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI" LABEL="EFI" UUID="5D9A-F8AF" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="p.UEFI" PARTUUID="d6519cfe-628b-483c-8e03-1f3467c2ee74"
/dev/sr0: BLOCK_SIZE="2048" UUID="2025-09-12-05-56-17-00" LABEL="INSTALL" TYPE="iso9660" PTTYPE="PMBR"
/dev/mapper/ram0p3: LABEL="RAMROOT" UUID="ec3395ff-8202-42c7-a748-9142c664cc75" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="p.lxroot" PARTUUID="dd2da203-90f8-40b7-898f-17be204787da"

/dev/loop0: BLOCK_SIZE="1048576" TYPE="squashfs"
/dev/ram0: PTUUID="5211a675-9631-46cb-a995-3d1f78f79d43" PTTYPE="gpt"
/dev/mapper/ram0p1: PARTLABEL="p.legacy" PARTUUID="a0196df2-f74c-4022-ba01-6eb5c39fd4aa"

localhost-MiniOS:/root # find /dev|grep ec3395ff-8202-42c7-a748-9142c664cc75
/dev/disk/by-uuid/ec3395ff-8202-42c7-a748-9142c664cc75

localhost-MiniOS:/root # l /dev/disk/by-uuid/
lrwxrwxrwx  1 root root   9 Sep 12 07:57 2025-09-12-05-56-17-00 -> ../../sr0
lrwxrwxrwx  1 root root  10 Sep 12 07:57 5D9A-F8AF -> ../../dm-1
lrwxrwxrwx  1 root root  10 Sep 12 07:57 ec3395ff-8202-42c7-a748-9142c664cc75 -> ../../dm-2

localhost-MiniOS:/root # l /dev/disk/by-id/
lrwxrwxrwx  1 root root   9 Sep 12 07:57 ata-QEMU_DVD-ROM_QM00003 -> ../../sr0
lrwxrwxrwx  1 root root  10 Sep 12 07:57 dm-name-ram0p1 -> ../../dm-0
lrwxrwxrwx  1 root root  10 Sep 12 07:57 dm-name-ram0p2 -> ../../dm-1
lrwxrwxrwx  1 root root  10 Sep 12 07:57 dm-name-ram0p3 -> ../../dm-2
lrwxrwxrwx  1 root root  10 Sep 12 07:57 dm-uuid-part1-devnode_1:0_Wh5pYvM -> ../../dm-0
lrwxrwxrwx  1 root root  10 Sep 12 07:57 dm-uuid-part2-devnode_1:0_Wh5pYvM -> ../../dm-1
lrwxrwxrwx  1 root root  10 Sep 12 07:57 dm-uuid-part3-devnode_1:0_Wh5pYvM -> ../../dm-2

localhost-MiniOS:/root # ls -l /sys/fs/cgroup/system.slice/sysroot.mount
total 0
-r--r--r-- 1 root root 0 Sep 12 09:00 cgroup.controllers
-r--r--r-- 1 root root 0 Sep 12 07:57 cgroup.events
-rw-r--r-- 1 root root 0 Sep 12 09:00 cgroup.freeze
--w------- 1 root root 0 Sep 12 09:00 cgroup.kill
-rw-r--r-- 1 root root 0 Sep 12 09:00 cgroup.max.depth
-rw-r--r-- 1 root root 0 Sep 12 09:00 cgroup.max.descendants
-rw-r--r-- 1 root root 0 Sep 12 07:57 cgroup.procs
-r--r--r-- 1 root root 0 Sep 12 09:00 cgroup.stat
-rw-r--r-- 1 root root 0 Sep 12 07:57 cgroup.subtree_control
-rw-r--r-- 1 root root 0 Sep 12 09:00 cgroup.threads
-rw-r--r-- 1 root root 0 Sep 12 09:00 cgroup.type
-r--r--r-- 1 root root 0 Sep 12 09:00 cpu.stat
-r--r--r-- 1 root root 0 Sep 12 09:00 cpu.stat.local
-r--r--r-- 1 root root 0 Sep 12 09:00 pids.current
-r--r--r-- 1 root root 0 Sep 12 09:00 pids.events
-r--r--r-- 1 root root 0 Sep 12 09:00 pids.events.local
-rw-r--r-- 1 root root 0 Sep 12 07:57 pids.max
-r--r--r-- 1 root root 0 Sep 12 09:00 pids.peak

Thank you.
kiwi-boot.kiwi-12sept25-0900.txt
kiwi-rdsosreport-12sept25-0900.txt

Jan Robinson

unread,
Sep 12, 2025, 5:44:42 AMSep 12
to kiwi
New uuuid:

ec3395ff-8202-42c7-a748-9142c664cc75

Jan Robinson

unread,
Sep 18, 2025, 3:13:26 AM (11 days ago) Sep 18
to kiwi
Pressing Ctrl-D gave this


┌──────────────────────────────────────────────────────────────────────────────┐
│ Failed to mount install image squashfs filesystem                            │
├──────────────────────────────────────────────────────────────────────────────┤
│                                   <  OK  >                                   │
└──────────────────────────────────────────────────────────────────────────────┘

Marcus Schäfer

unread,
Sep 22, 2025, 9:39:49 AM (6 days ago) Sep 22
to kiwi-...@googlegroups.com
Hi,

> Pressing Ctrl-D gave this
> ┌──────────────────────────────────────────────────────────────────────
> ────────┐
> │ Failed to mount install image squashfs filesystem

Sorry I'm a bit lost on this issue as I don't see the error
on my tests and I cannot reproduce the same hardware situation
that you have in your lab.

This one is weird, especially because even if you give it
a ramdisk device as root parameter the dracut sysroot unit
is not searching for this information but for something else.
That usually means there is another dracut code in the game
which interferes here.

But all this is based on a guessing game and therefore not
helpful to you.
signature.asc
Reply all
Reply to author
Forward
0 new messages