OpenSUSE Leap 15.5 Live USB KDE

I download Leap ISO (openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.40-Media.iso) at 08/06/2023 (as asoon as relased) then I “dd” to USB stick and pluged worked fine. At first boot created the persistent storage cow . dracut : mkfs2.ext4 … and so on.

Few days later I download again this time build number was different (openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.57-Media.iso) this time at first boot it stops the creating persistent storage. dracut says “fall back to ramdrive” or someting like that. and it does not creates Persistent storage. I even try to run at AMD INTEL (core Duo, I, I5) differnt computers with no luck. I can not create persistent storage on USB.

Does anybody can help me with my problem.

Thank you very much.

By the way, this is the copy of the /var/logs/boot.log

[ 13.134017] dracut-initqueue[990]: mount: /run/overlay/overlayfs: can’t find LABEL=“cow”.
[ 13.202712] dracut-initqueue[995]: This disk is currently in use - repartitioning is probably a bad idea.
[ 13.202963] dracut-initqueue[995]: It’s recommended to umount all file systems, and swapoff all swap
[ 13.203167] dracut-initqueue[995]: partitions on this disk.
[ 13.203412] dracut-initqueue[995]: The device contains ‘iso9660’ signature and it may remain on the device. It is recommended to wipe the device with wipefs(8) or fdisk --wipe, in order to avoid possible collisions.
[ 13.360127] dracut-initqueue[916]: Warning: Failed to setup persistent write space !
[ 13.360398] dracut-initqueue[916]: Warning: Falling back to temporary overlay

This comes from attempt to mount persistent partition.

These messages are from fdisk. There is no errors logged so probably fdisk completed successfully. Is there are additional partition (it should use all remaining space) now? If not, can you provide full dmesg output after booting this stick (upload to

I tested it in VM and persistent partition was created. So it does not look like some general problem. Could be something with your USB device. Try wiping it (see man wipefs) to remove all signatures that may confuse startup scripts.

1 Like

I used dd if-/dev/zero… to wipe USB. I even buy new USB to try … I tryed with different brand and size USB (8Gb 16Gb even 32Gb on different computers…USB2 USB3 … then I notticed that same problem with 15.4 current build of 15.4 is the same… openSUSE-Leap-15.4-KDE-Live-x86_64-Build6.1-Media.iso works but openSUSE-Leap-15.4-KDE-Live-x86_64-Build32.1-Media.iso don’t. It does not creates persistent “cow” partittion. On the other hand Tumbleweed live works fine very fine.

I downloaded that, maybe 2 weeks ago, and put it on a USB.

I still have that USB, and it does have a persistent partition from when I first used it.

1 Like

I paste the dmesg output. Hope I did right I am quite new to forum… I am not familier with GUI

Where? It is not on this forum and you have not provided the link to it.

1 Like

I pate to the link you have provided. something like paste.opensu…

Each uploaded document has unique URL. If you uploaded it to pastebin, dropbox or anything other file sharing would you also expect me to find it without knowing direct link?

1 Like

There are no kernel errors. I assume the live USB is 16GB one (sdb in this boot). Could you upload the full output of

journalctl --no-pager --full -b

Run it as root.

Ok here it is

Please note that I did not shutdown the pc since yesterday

This is race condition between udev and startup scripts

Jul 12 18:18:25 localhost dracut-initqueue[980]: Created a new partition 3 of type 'Linux' and of size 13.8 GiB.
Jul 12 18:18:25 localhost dracut-initqueue[980]: Command (m for help): The partition table has been altered.
Jul 12 18:18:25 localhost dracut-initqueue[980]: Syncing disks.
Jul 12 18:18:25 localhost dracut-initqueue[995]: mke2fs 1.46.4 (18-Aug-2021)
Jul 12 18:18:25 localhost dracut-initqueue[995]: /dev/sdb3 is apparently in use by the system; will not make a filesystem here!

My best guess is that udev locks device during processing and script runs too soon. Did not I ask you whether there was additional partition?

Open bug report. It is not something you can fix without recreating initrd. The script that is used here comes from kiwi dracut module, so I would submit an issue at GitHub - OSInside/kiwi: KIWI - Appliance Builder Next Generation. You may also open bug report on (same user/password as here).

By the way, I notice two things may interest :

1: With build10.40.iso 6 new updates avaible OpenSUSE-15.5-2023-2550 (2571, 2742 ,2772 , 2245, 2495) with Build10.57 4 updates OpenSUSE-15.5-2023-2550 (2571, 2742, 2772) therefore Updates OpenSUSE-15.5-2023-2245 and OpenSUSE-15.5-2023-2495 is already patched to Build10.57

2: sudo fdisk -l output as follows
Disk /dev/sdb: 14.65 GiB, 15728640000 bytes, 30720000 sectors
Disk model: ProductCode
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: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 1817827 1817764 887.6M cd unknown
/dev/sdb2 1817828 1858787 40960 20M ef EFI (FAT-12/16/32)
/dev/sdb3 1859584 30719999 28860416 13.8G 83 Linux

hence partition is created but the mkfs.ext4 did not created the filesystem