I'm migrating a custom Linux image setup from KIWI NG 10 + Dracut 9 to KIWI NG 10 + Dracut 10 on RHEL 9, and I’m encountering issues related to kernel/initrd verification during boot. 🧩 Previous Setup (KIWI NG 10 + Dracut 9): Checksums (*.sha256) for vmlinuz and initrd were automatically verified during boot. I did not explicitly configure any checksum generation or verification in config.sh, images.sh. Boot worked reliably with implicit SHA256-based verification behavior. 🚧 Problem in New Setup (KIWI NG 10 + Dracut 10): After upgrading to Dracut 10, I observe that: SHA256 checks are not automatically performed. If I manually generate /run/image/*.sha256, they are ignored during boot. I also attempted to rely on pre-generated .vmlinuz.hmac (available on RHEL 9 systems), but Dracut does not seem to use it. I cannot find any logic in dracut-kiwi-lib or core dracut that verifies kernel/initrd hashes out of the box. The image boots and throw information about missing /run/image/*.sha256. After that vm just shutdown. Any help would be appreciate :)

I have a 2TB external SSD connected to a server. Using the server, I booted into the RHEL8 installer and successfully installed onto the external drive, however during the post-install reboot (and all reboot attempts after) the boot hangs at the switch-root step. Obviously the drive is recognized by the system and is able to provide the bootloader / initramfs, but dracut/systemd seems to just hit a hard stop when switching to /sysroot using the slash partition on the drive (non-llvm ext4 formatted). The interesting thing is several machines (laptops, desktops) will successfully boot from the drive into the OS, indicating the server chipset/usb bus is the cause. Unfortunately, I am stuck with the server (a Gigabyte... didn't realize they made more than boards) and the external drive (a Kanguru UltraLock SSD). Kanguru claims there are no drivers required for their drive, which makes sense. Also, I have not attempted to update/flash the UEFI on the server. I've avoided it for fear of making things worse. I did try adding a short delay in a pre-mount-hooked dracut script within the initramfs, thinking it might be a race condition of some sort, but it had no effect. That script also does an ls /dev/disk/by-uuid which shows the drives and partitions as they should be (i.e. the root=UUID:.. in the kernelopts matches the partition in the list). Anything obvious I'm missing? Update: I realized that I actually used a PXE kickstart to install the OS because I was unable to boot into the RHEL8 installer using my thumbdrive USB stick. Initially I thought the issue was my stick (old USB2 SanDisk), so I switched to my PXE server on my laptop. I just tested a theory now and was able to boot into System Rescue (CD) on that same USB stick that did not work with the RHEL8 installer. System Rescue CD uses the typical embedded busybox boot approach, which seems to point to a dracut issue in RHEL with regard to the server's hardware or USB connections? Thanks in advance!

I'm trying to disable kernel module for my motherboard's bluetooth chip: btintel. I've added a blacklist entry to /etc/modprobe.d/blacklist-btintel.conf (I also tried blacklist.conf, this didn't make a difference):

blacklist btintel

I have also symlinked this file to /usr/lib/modprobe.d/ because of [this](https://bugzilla.redhat.com/show_bug.cgi?id=873220) possible issue. Furthermore, I've edited /etc/sysconfig/grub, to include the module in both rd.driver.blacklist as well as modprobe.blacklist:

$ grep 'GRUB_CMDLINE_LINUX' /etc/sysconfig/grub
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau,btintel modprobe.blacklist=nouveau,btintel nvidia-drm.modeset=1 resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"

Afterwards, I've tried running both:

sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

as well as

sudo dracut -fv

But after rebooting, I'm still presented with a loaded module:

$ lsmod | grep btintel
btintel                28672  1 btusb
bluetooth             626688  48 btrtl,btintel,btbcm,bnep,btusb,rfcomm

Anyone have a suggestion?

I am currently using Rocky 9 + Linux kernel 5.14.0 + security / stability patches. I have two GPT partitions that contain multiple LVM filesystems. One partition is encrypted (LUKS), and one is not. The non-encrypted partition boots to multi-user fine. For the encrypted partition, I do not get a prompt to enter the passphrase. Within a few minutes, it breaks out to a shell where I can poke around - I added rd.shell and rd.break to my kernel command line arguments. I can use cryptsetup (which I explicitly added to my initramfs to assist with diagnosis) to manually open the LUKS encrypted container, activate my LVMs and mount filesystems (I don't know how to convince the system to exit the ramdisk shell and continue booting up to multi-user after having provided assistance to mount the root filesystem - how to do that would be a side question). Here's the question: What are the pieces to pursue to investigate why I get no passphrase prompt to decrypt my LUKS volume at boot time? I'm looking for hints to methodically determine the culprit. I have configured systems similarly in the past where it worked (including using dracut-sshd to allow for entering the passphrase over the network in addition to the console). I'm just not sure what's different this time. My initramfs image includes the 'crypt' module (and now some other tools like cryptsetup to try to help diagnose the issue **Update**... In my case I *do* get the prompt for passphrase when the unit is power cycled, but NOT when rebooted. In the good case, I get the following messages from systemd-cryptsetup:

-none
May 21 17:51:06 localhost systemd[1] : Created slice Slice /system/systemd-cryptsetup.
 .
 .
May 21 17:54:04 localhost systemd-cryptsetup: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/sdc7.

In the bad case, I never see that last message from systemd-cryptsetup. Eventually dracut-initqueue just gets tired of waiting for the root filesystem to show up. I get the following where dracut_initqueue seems to say to systemd-cryptsetup that "Ahem... I am waiting here" while impatiently tapping its foot:

-none
May 21 17:39:53 localhost systemd[1] : Created slice Slice /system/systemd-cryptsetup.
 .
 .
May 21 17:42:04 localhost dracut-initqueue: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
May 21 17:42:04 localhost dracut-initqueue: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-label\x2fap_root1.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
May 21 17:42:04 localhost dracut-initqueue:     [ -e "/dev/disk/by-label/ap_root1" ]
May 21 17:42:04 localhost dracut-initqueue: fi"
May 21 17:42:04 localhost dracut-initqueue: Warning: dracut-initqueue: starting timeout scripts
May 21 17:42:05 localhost dracut-initqueue: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
May 21 17:42:05 localhost dracut-initqueue: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-label\x2fap_root1.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
May 21 17:42:05 localhost dracut-initqueue:     [ -e "/dev/disk/by-label/ap_root1" ]
May 21 17:42:05 localhost dracut-initqueue: fi"
May 21 17:42:05 localhost dracut-initqueue: Warning: dracut-initqueue: starting timeout scripts
May 21 17:42:06 localhost dracut-initqueue: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
May 21 17:42:06 localhost dracut-initqueue: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-label\x2fap_root1.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
May 21 17:42:06 localhost dracut-initqueue:     [ -e "/dev/disk/by-label/ap_root1" ]
May 21 17:42:06 localhost dracut-initqueue: fi"

So now, I am searching for information on how to get debug information about systemd-cryptsetup to see what it's doing.

I am using dracut to create an initramfs to test a script for creating a key in the TPM chip. For now, this script is just a dummy script, so I can see if I've created the initramfs correctly:

#!/usr/bin/env bash
#
read -p 'This file will run to initialize the TPM'
exit 0

I want to include this script in the pre-mount boot phase. I followed the answer to the question "How to write a pre-mount startup script?" in this forum, modifying it as necessary, but when I list the contents of the image file, my scripts are not there. I also tried using the --include and --install dracut options, but I either receive an error, or if I don't, the scripts are not in the initramfs. I named my file tpm.img, and placed it in the /boot directory. When booting the computer, I press 'e' to modify the grub line, and change the initrdefi command to point to my tpm.img. Of course, my script doesn't run, because it's not present in the initramfs. I'm not sure that I understand the "Injecting custom Files" section of the dracut manual: I haven't been able to find any examples of dracut configuration files or dracut command line files that show the complete path to the module to be included. Please help me understand why my script is not being included in the initramfs. Thanks! Jeff

I want to install a centos7.9 minimal version, and burn the iso image into a use device, the startup guide to install centos7, and i press enter, then failed. After searching many answers from internet, inst.stage2=hd:/dev/sda1 would be the answer. after try, there is also a error happen like this:

I want to use Dracut for initramfs image creation. This image should be able to shrink a root filesystem on a Fedora machine. I would like to test partition shrinking flow manually first. If everything is okay, I will replace these commands with a script to do shrinking automatically in non-interactive mode on a remote machine. I was able to add the 'parted' and 'resize2fs' tools that I needed for this task. However, the image still uses 'systemd' as the init process and just boots the main Fedora installation. So I need to boot into some kind of shell and run the 'parted' and 'resize2fs' commands by hand. My attempt to add a simple 'init' script to the initramfs image failed (I put it as '/sbin/init' and turned the execution bit on. But the kernel complains that it can't find a runnable init process). So my question my question is: how to add your own init process to an initramfs image with Dracut?

Im trying to minimize boottime as much as possible. Currently im running Void Linux with an EFISTUB and dracut as the init manager. I now want to utilize bootchart to check where i can improve, but I cant get it to work. It seems that in older versions of dracut one could use dracut -f -a bootchart to include the bootchart package and use rdinit=/sbin/bootchartd to start it on boot, but dracut doesnt seem to have the bootchart module anymore.

I started using Dracut around a year ago to use Yubikey Pin unlock and everything was fine a few days ago. After a routine apt update on my LUKS encrypted Debian Trixie machine the linux kernel was updated to 6.7.12-amd64. Now every boot gets stuck with the following errors:

Dracut-initqueue rm: cannot remove '/lib/dracut/hooks/initqueue/finished/devexists-.sh': Read-only file system
Dracut-initqueue rm: cannot remove '/lib/dracut/hooks/initqueue/finished/devexists-.sh': Read-only file system

Here is a picture of the boot process: There's still a prompt for the LUKS password (or Yubikey pin) and the disk seems to be decrypted fine after entering. However, afterwards there's an endless systemd start job for the LVM volume containing the root partition. Here are the partitions incl. UUIDs. The root partition resides in a LUKS container:

sdb                     8:16   0 476,9G  0 disk                                     
├─sdb1                  8:17   0   243M  0 part  /boot/efi         DB08-0D0C
├─sdb2                  8:18   0   954M  0 part  /boot             74559e4f-03f0-46db-98f3-fa2633484d4c
└─sdb3                  8:19   0 475,8G  0 part                    3bce844f-0111-4b31-b551-4b82dbfc88bf
  └─debianlvm         253:1    0 475,8G  0 crypt                   bSc1Y8-yMKj-dfUJ-RSmh-9FrQ-BzcE-yvmmcj
    ├─emzwolvm-debian 253:2    0 111,8G  0 lvm   /                 7c6c5be7-4ddf-4ba5-beef-b29bf92322a1
    └─emzwolvm-vms    253:3    0   364G  0 lvm                     d43f0f69-dbb5-4a04-9099-963dd37dab8a

This is the corresponding grub menu entry:

menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-7c6c5be7-4ddf-4ba5-beef-b29bf92322a1' {
	load_video
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  74559e4f-03f0-46db-98f3-fa2633484d4c
	else
	  search --no-floppy --fs-uuid --set=root 74559e4f-03f0-46db-98f3-fa2633484d4c
	fi
	echo	'Loading Linux 6.7.12-amd64 ...'
	linux	/vmlinuz-6.7.12-amd64 root=/dev/mapper/emzwolvm-debian ro rootflags=subvol=@rootfs  quiet
	echo	'Loading initial ramdisk ...'
	initrd	/initrd.img-6.7.12-amd64

Here's /etc/crypttab:

emzwo_crypt UUID=3bce844f-0111-4b31-b551-4b82dbfc88bf none fido2-device=auto,token-timeout=1,luks,discard
home_crypt UUID=75b97063-8c09-4089-9ea2-a82ffea5ee34 /root/luks_keys/luks_home_keyfile.key luks,discard

And /etc/fstab:

#                
/dev/mapper/emzwolvm-debian /               btrfs   defaults,subvol=@rootfs 0       0
/dev/mapper/emzwolvm-vms /vms               btrfs   defaults 0       2
UUID=74559e4f-03f0-46db-98f3-fa2633484d4c /boot           ext4    defaults        0       2
UUID=DB08-0D0C  /boot/efi       vfat    umask=0077      0       1
/dev/mapper/home_crypt /shared_home           ext4    defaults        0       2

What I tried so far, everything without a difference: - booting from the older kernel - booting from a live stick, chroot into system, regenerate grub and initramfs via dracut - Checking if there are btrfs snapshots - nope (but created one now...) - replacing the "ro" with "rw" in linux command line of the grub entry Not tested: - switching back to initramfs-tools I have no clue what was happening. Any ideas how to fix this? Thanks in advance.

In an attempt to use my TPM module to automatically unlock the LUKS-encrypted LVM volume, I followed a guide and set up /etc/crypttab and installed dracut which then proceeded to create what I think are new initrd images (but it complained about a bunch of modules not existing). When I rebooted the system, it hangs for a long time on "initializing ramdisk" and then repeatedly prints

Warning: dracut-initqueue: starting timeout scripts
Warning: dracut-initqueue: still waiting for following initqueue hooks:
Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fubuntu--vg-ubuntu--lv.sh: (cut for brevity)

And then finally prints Warning: could not boot before dropping me into an emergency mode shell. I'm not actually sure how to fix this. I don't know how to use the emergency shell, so I've tried using an Ubuntu live cd and unlocking the encrypted partition, chrooting into it and undoing the changes from the guide and regenerating initrd images, but to no avail. My lack of understanding of what goes on at a boot process and which files are loaded by which process is probably what's between me and the solution. Grub is responsible for loading initrd? And it finds initrd at the /boot partition? And I can use update-initramfs to create new initrd images? And initrd tries to load whatever script it is that's stuck? Is that correct? Is there a way to remove those hooks from the initrd script? How can I fix this? For completeness: * It's an EFI system * Secure boot is on * Dualboot with Windows * LVM was installed with LUKS encryption on the other partition

I see that dracut has been run on my system (RHEL 9) during the weekend, and it seems like it has changed my authselect configuration messing up SSH connections. After some searching I've found that: > What is the use of dracut? Dracut is a set of tools that provide > enhanced functionality for automating the Linux boot process. The tool > named dracut is used to create a Linux boot image (initramfs) by > copying tools and files from an installed system and combining it with > the Dracut framework, which is usually found in > /usr/lib/dracut/modules. It was run using: dracut -f

dracut: drwxr-xr-x   2 root     root            0 Mar 21 10:23 etc/authselect

**Question:** Why has this happened, and which process decides "now I'll run dracut"? The machine has not been rebooted.

Dead community, Does anyone know the solution to this error message that I get when starting **Centos Linux (3.10.0-1160.66.1.el7.x86_64) 7 (Core)**

[ 198.942749] dracut-initqueuel3371: Warning: /dev/centos/root does not exist




Starting Dracut Emergency Shell...

Warning: /dev/centos/root does not exist
Varning: /dev/centos/swp does not exist
Warning: /dev/disk/by-id/md-uuid-md-uuid-00a7896a:5363ef2f:ccd81c8f:8e11e69e does not exist
Warning: /dev/mapper/centos-root does not exist

Generating “/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.
Type ”journalctl” to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt” to a USB stick or /boot
after mounting them and attach it to a bug report.

dracut:/#

I am booting a CentOS image via NFS, which requires a custom initramfs from dracut, with some extra modules. I want the kernel to get updated normally, using yum update. This will automatically generate a new initramfs each time the kernel is updated, which doesn't include any of my extra modules. - How/when does yum update generate the new initramfs? - Can the system be configured so that yum update includes my custom modules every time? The goal is to avoid needing yum update + dracut -m "etc" name.img kernel.ver every time we update, since there will be many different system images that we need to maintain.

Ok so dracut is not performing as I believe it should and I cannot find a workaround. I have created several images before but now I am trying to create a live boot initramfs to go along with a custom live iso. every time I try the cmdlind argument below it fails and I have also tried putting the extra modules into dracut.conf but each time it gives me warnings,(which I saw on another post that they are just warnings you can ignore) but after the messages it returns to the terminal prompt and I have no option to ignore or continue with the dracut build etc.

#dracut.conf short and sweet
add_dracutmodules+="nfs dmsquash-live livenet "
omit_dracutmodules+="biosdevname"

#dracut terminal argument
dracut -v testinitramfs.img 

#output
dracut: Executing: /usr/bin/dracut -v testinitramfs.img
dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
dracut: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found!
dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
dracut: dracut module 'dmsquash-live-ntfs' will not be installed, because command 'ntfs-3g' could not be found!
dracut: dracut module 'livenet' depends on 'dmsquash-live', which can't be installed
dracut: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found!
dracut: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
dracut: dracut module 'dmsquash-live' cannot be found or installed.

and I have the packages installed I have the dracut.x86 -tools -network -caps -live -squash all installed and my available modules list shows busybox and dmsquash-live yet it still fails and says it cannot find them. Is there another dependency I am missing or more to the dracut build command that I need in this case to make those modules viewable by dracut?

dracut --list-modules
/etc/dracut.conf: line 8: biosdevname : command not found
bash                            crypt                         terminfo   
systemd                         dm                            udev-rules
warpclock                       dmraid                        virtfs
fips                            **dmsquash-live**                 **biosdevname**
systemd-initrd                  **dmsquash-live-ntfs**            dracut-systemd
caps                            kernel-modules                ecryptfs
systemd-networkd                kernel-modules-extra          ...
modsign                         **livenet**                       ...
rescue                          mdraid                        squash
watchdog                        multipath
**busybox**                         qemu
nss-softokn                     qemu-net
rdma                            stratis
rngd                            crypt-gpg
i18n                            crypt-loop
convertfs                       cifs
network-legacy                  debug
network-manager                 fcoe
network                         fcoe-uefi
ifcfg                           fstab-sys
url-lib                         iscsi
drm                             lunmask
plymouth                        nbd
prefixdevname                   **nfs**
prefixdevname-tools             resume
lvmmerge                        rootfs-block
btrfs                           ssh-client

I want to create a bootup script that runs before the root filesystem / has been mounted as I want to use dm-cache to cache it. The script is supposed to contain cache setup commands. Where would I need to put such a script and what format does it need to have? I cannot find any useful documentation by googling. Running Fedora 17, Kernel 3.9.10.

I want to share the following issue after upgrading the security rpm's on RHEL 7.9 machines include update of microcode_ctl rpm rpm -qa | grep microcod microcode_ctl-2.1-73.15.el7_9.x86_64 we noticed about the following kernel messages. [Sun Jun 4 13:12:19 2023] Microcode update for Intel Broadwell-EP/EX (BDX-ML B/M/R0; family 6, model 79, stepping 1; CPUID 0x406f1) CPUs is disabled as it may cause system instability. Please refer to /usr/share/doc/microcode_ctl/caveats/06-4f-01_readme and /usr/share/doc/microcode_ctl/README.caveats for details. [Sun Jun 4 13:13:35 2023] After installation of a new version of microcode_ctl package, [Sun Jun 4 13:13:35 2023] initramfs hasn't been re-generated for all the installed kernel packages. [Sun Jun 4 13:13:35 2023] The following kernel packages have been skipped: kernel-3.10.0-514.26.2.el7.x86_64. [Sun Jun 4 13:13:35 2023] Please re-generate initramfs manually for these kernel packages with the [Sun Jun 4 13:13:35 2023] "dracut -f --kver KERNEL_VERSION" command in order to get the latest [Sun Jun 4 13:13:35 2023] Intel CPU microcode included into early initramfs image for it, if needed. the current RHEL kernel version is uname -r 3.10.0-1160.80.1.el7.x86_64 so according to dmesg we can see that. dracut -f --kver KERNEL_VERSION so is it means that we need to set the current kernel version in command as dracut -f --kver 3.10.0-1160.80.1.el7.x86_64 or to set the kernel as defined in kernel message as dracut -f --kver kernel-3.10.0-514.26.2.el7.x86_64

Ok so I have a system running a RHEL 6 server and due to hardware restraints RHEL 6 is the newest I can use. Second I am trying to create a live network bootable initramfs for a pxe operation. In newer systems RHEL 7/8 I can just include the dmsquash-live-root and livenet dracut modules to give my initramfs files remote root and live boot capabilities. My RHEL 6 server does not have livenet, just dmsquash-live-root. So I copied the 90livenet directory from a new system and placed it in the /usr/share/dracut/modules.d/ directory as seen in image below. it then looks and contains same content as my RHEL 7 system. but when I run the following dracut command using the below conf file the dracut just skips over the modules like it does not exist. which is what is strange to me because if you specify a module that doesn't exist the dracut command will complain and usually fail but it this case it does not complain about including livenet but instead seems to simple just cruise over it.

dracut -v -f -c dracut.conf initramfs-3.10.0-693.72.1.rt56.672.el6rt.x86_64.img 3.10.0-693.72.1.rt56.672.el6rt.x86_64 > output.txt

#Dracut.conf 
# Dracut modules to add to the default
add_dracutmodules+="nfs network dmsquash-live livenet"

# additional kernel modules to the default
add_drivers+="nfs nfs4"

omit_dracutmodules+="biosdevname"

Soo My question is, can anyone point out an error in my command or conf usage or can someone explain the extra steps I need to do other than include the modules directory and contents into the modules.d directory.(ps I did also try ./module-setup.sh just to see if that setup script has to be run prior to using dracut command - some modules have scripts called install so not sure if I need on but the setup scripts looks very similar to install scripts of other working modules) I can grep everything else in that config file and it is there except the livenet module I injected.

In the dracut.cmdline manpage, under the deprecated section, it has these old options and their replacements.

rd_LVM_SNAPSHOT
    rd.lvm.snapshot

rd_LVM_SNAPSIZE
    rd.lvm.snapsize

But no actual mention of what exactly these do. I haven't been able to find archived manpages or anything online about the specifics behind these options. So I presume it allows you to boot to a specific snapshot instead of the current root. But which snapshots? Normal or Thin or either? What does the option actually take? The name or some sort of other id? Does it require specific dracut modules? Would booting into a snapshot with an older kernel cause problems? Anything else noteworthy or to be concerned about that I'm not thinking of right now?

During boot system logs into journal [ 4.604302] x-com (udev-worker): sda: /usr/lib/udev/rules.d/73-seat-late.rules:13 Failed to import properties 'ID_SEAT' from parent: Operation not permitted [ 4.604326] x-com (udev-worker): sda: Failed to process device, ignoring: Operation not permitted Then I get Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f23fe245f-68fa-4619-8411-ba1aa5bbddfa.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then [ -e "/dev/disk/by-uuid/23fe245f-68fa-4619-8411-ba1aa5bbddfa" ] fi" Warning: starting timeout scripts And finally it lands in emergency console. I can see there that /dev/disk doesn't exist. Running udevadm test /dev/sda3 in emergency creates /dev/disk/by-uuid/23fe245f-68fa-4619-8411-ba1aa5bbddfa but it doesn't help to boot system into usable state. From my understanding this path should be created by udev in 60-persistent-storage.rules or 13-dm-disk.rules. I don't see any related errors before line mentioning 73-seat-late.rules. Here is content of rdsosreport.txt: https://paste.opensuse.org/pastes/b0c8cca5eee2 Why udev don't create /dev/disk path? How can I find what is wrong?

Recently tried booting up my server but i get the following error. It seems that initramfs is not able to generate and i tried to boot into rescue mode and found that fstab file was empty. Updated the file, but no luck. I have attached the image since im unable to copy the lines.