That seems quite strange.
Can you share the output of ls /etc/kernel/install.d
ls /etc/kernel/install.d
.rwxr-xr-x 2.2k root 31 Aug 07:56 50-dracut.install
.rwxr-xr-x 5.9k root 31 Aug 07:56 90-loaderentry.install
ls /usr/lib/kernel/install.d
ls /usr/lib/kernel/install.d
.rwxr-xr-x 2.0k root 27 Sep 09:11 50-depmod.install
.rwxr-xr-x 2.3k root 31 Aug 07:56 50-dracut-fallback.install
.rwxr-xr-x 2.0k root 2 Aug 02:52 50-dracut.install
.rwxr-xr-x 3.5k root 2 Aug 02:52 51-dracut-rescue.install
.rwxr-xr-x 7.6k root 27 Sep 09:11 60-ukify.install
.rwxr-xr-x 6.3k root 31 Aug 07:56 90-loaderentry-fallback.install
.rwxr-xr-x 5.8k root 27 Sep 09:11 90-loaderentry.install
.rwxr-xr-x 3.1k root 27 Sep 09:11 90-uki-copy.install
What version of kernel-install-for-dracut do you have installed?
It looks like your initrds are being written to completely the wrong location. The fallback is going to /boot and the normal one if going to /usr/lib. Both of which are wrong.
It looks like I have 1.9.1-1.
pacman -Si kernel-install-for-dracut
Repository : endeavouros
Name : kernel-install-for-dracut
Version : 1.9.1-1
[...]
The normal ones appear in /boot also, I’m not sure if that is a significant detail or not, but there they are:
ls /boot
.rw------- 44M root 29 Sep 15:43 initramfs-linux-fallback.img
.rw------- 42M root 29 Sep 16:50 initramfs-linux-lts-fallback.img
.rw-r--r-- 15M root 29 Sep 16:50 initramfs-linux-lts.img
.rw-r--r-- 16M root 29 Sep 15:43 initramfs-linux.img
.rw-r--r-- 13M root 29 Sep 15:42 vmlinuz-linux
.rw-r--r-- 11M root 29 Sep 16:50 vmlinuz-linux-lts
The images in /efi have not been updated since August 14 it looks like. 
ls /efi
drwxr-xr-x - root 29 Sep 15:43 788ec469dc1d4b8399e5bcfe958e9f3e
drwxr-xr-x - root 7 Aug 09:47 EFI
drwxr-xr-x - root 29 Sep 15:47 loader
.rwxr-xr-x 44M root 14 Aug 10:09 initramfs-linux-fallback.img
.rwxr-xr-x 16M root 14 Aug 10:09 initramfs-linux.img
.rwxr-xr-x 13M root 14 Aug 10:09 vmlinuz-linux
Not with kernel-install-for-dracut. It should be writing it to /efi/<machineid>/<kernel version>/initrd
Okay, now that you mention it I do see them in there as well.
lt /efi
/efi
├── 788ec469dc1d4b8399e5bcfe958e9f3e
│ ├── 6.1.55-1-lts
│ │ ├── initrd
│ │ ├── initrd-fallback
│ │ └── linux
│ └── 6.5.5-arch1-1
│ ├── initrd
│ ├── initrd-fallback
│ └── linux
├── EFI
│ ├── BOOT
│ │ └── BOOTX64.EFI
│ ├── Linux
│ └── systemd
│ └── systemd-bootx64.efi
├── loader
│ ├── entries
│ │ ├── 788ec469dc1d4b8399e5bcfe958e9f3e-6.1.55-1-lts-fallback.conf
│ │ ├── 788ec469dc1d4b8399e5bcfe958e9f3e-6.1.55-1-lts.conf
│ │ ├── 788ec469dc1d4b8399e5bcfe958e9f3e-6.5.5-arch1-1-fallback.conf
│ │ └── 788ec469dc1d4b8399e5bcfe958e9f3e-6.5.5-arch1-1.conf
│ ├── entries.srel
│ ├── loader.conf
│ └── random-seed
├── initramfs-linux-fallback.img
├── initramfs-linux.img
└── vmlinuz-linux
It looks like I have some bonus content for some reason.
You might want to be cautious about rebooting. I am going to update and test with the latest version of systemd but it was just a minor point release so things should not have change there.
Do you have any other dracut automation installed?
What does pacman -Q | grep dracut show?
Oops! Well this machine is a VM I keep at work and I had to leave, so I did shut it down. The good news is it came back up just fine, so perhaps I dodged a bullet.
No, nothing that I have done intentionally.
pacman -Q | grep dracut
dracut 059-3
dracut-hook 0.5.3-1.1
kernel-install-for-dracut 1.9.1-1
Ahh…
Why do you have this installed?
You probably have two competing sets of hooks running.
I have no clue. 
I just uninstalled it and the dracut output is back to quiet when I reinstall a kernel. Thanks Dalto, sorry to chew up your time with that one.
2 Likes
question about dracut , install kernel and rebuild and grub
i have added a kernel , dracut-rebuild had generated all , bur grub do not see 2nd kernel
is there something to do in this case ?
Regenerate the GRUB config.
sudo grub-mkconfig -o /boot/grub/grub.cfg
2 Likes
Dracut 108-eos is out
2 Likes
I’m seeing this:
Failed to add dependency on unit: Unit initrd.target does not exist
during the update. Not rebooting yet until I hear more info.
That is harmless.
It is an issue in eos-dracut that needs updating for dracut 108. I didn’t want to change both eos-dracut and dracut at the same time though.
I am going to close this topic though as it is from Jan 2023 and related to something else entirely.
2 Likes