You are not logged in.
I was using the the /usr/lib/initcpio/udev/11-dm-initramfs.rules file in a initcpio hook for bringing dm-integrity volumes up at boot, before lvm2, before dm-encrypt. The said hook is here :
https://gist.github.com/vishalbelsare/a … a3c8246299
Now after updating, I am facing the same problem with the initramfs not being 'complete.
==> ERROR: file not found: '/usr/lib/initcpio/udev/11-dm-initramfs.rules'
/usr/lib/initcpio/functions: line 1068: /usr/lib/initcpio/udev/11-dm-initramfs.rules: No such file or directory
What is or could be a solution to this?
Offline
I ran into the same error, but in a different setup, with a custom encryption hook.
Looks like other hooks in the mkinitcpio-package were updated because the config is now part of other regularly included files (10-dm.rules) and thus the inclusion of 11-dm-initramfs.rules is not necessary there any longer:
https://gitlab.archlinux.org/archlinux/ … 39d382f08e, which links to https://gitlab.com/lvmteam/lvm2/-/commi … e91a5b3535
I did not validate what was in 11-dm-initramfs.rules and if everything made it over to the other files, but in my case I could just remove the line including 11-dm-initramfs.rules in my hook/install-script and build a new initramfs. Rebooting with the new initramfs went fine for me afterwards.
You could try removing the line (and the backslash on the line above) as well. (Maybe have a rescue-usb-stick or something at hand if something goes wrong?)
Edit:
Just looked it up: 11-dm-initramfs.rules just had the db-persist-option (https://gitlab.archlinux.org/archlinux/ … amfs.rules), which is now included in 10-dm.rules (https://gitlab.com/lvmteam/lvm2/-/commi … e91a5b3535) (also checked in local file system). I'd wager that removing the line in your hook should therefore be fine and cause no trouble.
Last edited by csmnn (2025-11-10 13:29:43)
Offline
Offline
Sounds reasonable. Will try this and inform if that works on the next reboot, which is some days away. Thanks much for checking the actual file content!
I ran into the same error, but in a different setup, with a custom encryption hook.
Looks like other hooks in the mkinitcpio-package were updated because the config is now part of other regularly included files (10-dm.rules) and thus the inclusion of 11-dm-initramfs.rules is not necessary there any longer:
https://gitlab.archlinux.org/archlinux/ … 39d382f08e, which links to https://gitlab.com/lvmteam/lvm2/-/commi … e91a5b3535I did not validate what was in 11-dm-initramfs.rules and if everything made it over to the other files, but in my case I could just remove the line including 11-dm-initramfs.rules in my hook/install-script and build a new initramfs. Rebooting with the new initramfs went fine for me afterwards.
You could try removing the line (and the backslash on the line above) as well. (Maybe have a rescue-usb-stick or something at hand if something goes wrong?)
Edit:
Just looked it up: 11-dm-initramfs.rules just had the db-persist-option (https://gitlab.archlinux.org/archlinux/ … amfs.rules), which is now included in 10-dm.rules (https://gitlab.com/lvmteam/lvm2/-/commi … e91a5b3535) (also checked in local file system). I'd wager that removing the line in your hook should therefore be fine and cause no trouble.
Offline