This should have been on the news page imo.
Agreed. The news page seems to have fallen out of use recently, 3 months since the last news about a package upgrade. Anyone know why? This is the second time recently that I feel news is missing from the news page.
(FWIW, pacman -S linux after pacman -Syu fixed the problem just fine here.)
]]>Cools. You should notify pkg maintainer that hook install file needs to be fixed.
Seeing as this could leave systems in a state where they won't boot post upgrade I would hope it gets add to the news page too.
I do not normally come to the forums looking for issues that may stop my system booting after an upgrade but I do read the news page before startingan upgrade.
Cheers
Mick
@aussielunix
# vim: set ft=sh:
build()
{
if [ -z "${CRYPTO_MODULES}" ]; then
MODULES=" dm-crypt $(all_modules "/crypto/") "
else
MODULES=" dm-crypt ${CRYPTO_MODULES} "
fi
FILES=""
SCRIPT="encryptssh"
[ -f "/sbin/cryptsetup" ] && add_binary "/sbin/cryptsetup" "/sbin/cryptsetup"
[ -f "/usr/sbin/cryptsetup" ] && add_binary "/usr/sbin/cryptsetup" "/sbin/cryptsetup"
add_binary "/sbin/dmsetup"
add_file "/usr/lib/udev/rules.d/10-dm.rules"
add_file "/usr/lib/udev/rules.d/13-dm-disk.rules"
add_file "/usr/lib/udev/rules.d/95-dm-notify.rules"
add_file "/usr/lib/initcpio/udev/11-dm-initramfs.rules" "/usr/lib/udev/rules.d/11-dm-initramfs.rules"
}
help ()
{
cat<<HELPEOF
This hook allows for an encrypted root device.
HELPEOF
}
don'd forget to make again
# mkinitcpio -p linux
SCRIPT="encryptssh" [ -f "/sbin/cryptsetup" ] && add_binary "/sbin/cryptsetup" "/sbin/cryptsetup" [ -f "/usr/sbin/cryptsetup" ] && add_binary "/usr/sbin/cryptsetup" "/sbin/cryptsetup" add_binary "/sbin/dmsetup" # add_file "/lib/udev/rules.d/10-dm.rules" # add_file "/lib/udev/rules.d/13-dm-disk.rules" # add_file "/lib/udev/rules.d/95-dm-notify.rules" # add_file "/lib/initcpio/udev/11-dm-initramfs.rules" "/lib/udev/rules.d/11-dm-initramfs.rules"
And doing again # mkinitcpio -p linux. It makes initframes without errors.
But situatuin is the same: cusror on the second line. Boot proccess stops.
Help me please.
Don't comment them out. That's just pointing to old path - make them point at /usr/lib/udev/rules.d/ instead
]]>This has nothing to do with udev. The rules, which all belong to core/device-mapperth , moved to /usr/lib/udev/rules.d.
Really useful response that.
The problem is hook install files pointing at the old location.
This is an "order of installation" problem. For me, lvm2 got installed after linux so when it rebuilt the ramdisk the lvm2 hook install was still pointing at the old udev rule location.
So, if a package with hooks you need is installed AFTER linux you're going to get this problem.
Rerun mkinitcpio manually or just pacman -S linux again.
Glad I checked for forum before reboot.
]]>Reinstalling device-mapper fixed it for me.
It doesn't work for me
When I use this line in /etc/mkinitcpio.conf
HOOKS="base udev keymap autodetect pata scsi sata encrypt filesystems"
Everything works fine, but I loose ability to enter password over network
with this line
HOOKS="base udev keymap autodetect pata scsi sata dropbear encryptssh filesystems"
I have this problem
# mkinitcpio -p linux
-> Parsing hook: [encryptssh]
==> ERROR: file not found: `/lib/udev/rules.d/10-dm.rules'
==> ERROR: file not found: `/lib/udev/rules.d/13-dm-disk.rules'
==> ERROR: file not found: `/lib/udev/rules.d/95-dm-notify.rules'
==> ERROR: file not found: `/lib/initcpio/udev/11-dm-initramfs.rules'
I understand that this comes from /lib/initcpio/install/encryptssh:
SCRIPT="encryptssh"
[ -f "/sbin/cryptsetup" ] && add_binary "/sbin/cryptsetup" "/sbin/cryptsetup"
[ -f "/usr/sbin/cryptsetup" ] && add_binary "/usr/sbin/cryptsetup" "/sbin/cryptsetup"
add_binary "/sbin/dmsetup"
add_file "/lib/udev/rules.d/10-dm.rules"
add_file "/lib/udev/rules.d/13-dm-disk.rules"
add_file "/lib/udev/rules.d/95-dm-notify.rules"
add_file "/lib/initcpio/udev/11-dm-initramfs.rules" "/lib/udev/rules.d/11-dm-initramfs.rules"
I tried to comment these lines
SCRIPT="encryptssh"
[ -f "/sbin/cryptsetup" ] && add_binary "/sbin/cryptsetup" "/sbin/cryptsetup"
[ -f "/usr/sbin/cryptsetup" ] && add_binary "/usr/sbin/cryptsetup" "/sbin/cryptsetup"
add_binary "/sbin/dmsetup"
# add_file "/lib/udev/rules.d/10-dm.rules"
# add_file "/lib/udev/rules.d/13-dm-disk.rules"
# add_file "/lib/udev/rules.d/95-dm-notify.rules"
# add_file "/lib/initcpio/udev/11-dm-initramfs.rules" "/lib/udev/rules.d/11-dm-initramfs.rules"
And doing again # mkinitcpio -p linux. It makes initframes without errors.
But situatuin is the same: cusror on the second line. Boot proccess stops.
Help me please.
The question is what should we do about it. How do I tell mkinitcpio to look there? I'm sure that there will be many LVM/RAID users having this problem.
pacman.log:
[2012-04-27 20:07] >>> Updating module dependencies. Please wait ...
[2012-04-27 20:07] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-04-27 20:07] ==> Building image from preset: 'default'
[2012-04-27 20:07] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-04-27 20:07] ==> Starting build: 3.3.3-1-ARCH
[2012-04-27 20:07] -> Parsing hook: [base]
[2012-04-27 20:07] -> Parsing hook: [udev]
[2012-04-27 20:07] -> Parsing hook: [autodetect]
[2012-04-27 20:07] -> Parsing hook: [pata]
[2012-04-27 20:07] -> Parsing hook: [scsi]
[2012-04-27 20:07] -> Parsing hook: [sata]
[2012-04-27 20:07] -> Parsing hook: [lvm2]
[2012-04-27 20:07] ==> ERROR: file not found: `/lib/udev/rules.d/10-dm.rules'
[2012-04-27 20:07] ==> ERROR: file not found: `/lib/udev/rules.d/13-dm-disk.rules'
[2012-04-27 20:07] ==> ERROR: file not found: `/lib/udev/rules.d/95-dm-notify.rules'
[2012-04-27 20:07] ==> ERROR: file not found: `/lib/initcpio/udev/11-dm-initramfs.rules'
[2012-04-27 20:07] -> Parsing hook: [filesystems]
[2012-04-27 20:07] ==> Generating module dependencies
[2012-04-27 20:07] ==> Creating xz initcpio image: /boot/initramfs-linux.img
[2012-04-27 20:08] ==> Image generation successful
[2012-04-27 20:08] ==> Building image from preset: 'fallback'
[2012-04-27 20:08] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-04-27 20:08] ==> Starting build: 3.3.3-1-ARCH
[2012-04-27 20:08] -> Parsing hook: [base]
[2012-04-27 20:08] -> Parsing hook: [udev]
[2012-04-27 20:08] -> Parsing hook: [pata]
[2012-04-27 20:08] -> Parsing hook: [scsi]
[2012-04-27 20:08] -> Parsing hook: [sata]
[2012-04-27 20:08] -> Parsing hook: [lvm2]
[2012-04-27 20:08] ==> ERROR: file not found: `/lib/udev/rules.d/10-dm.rules'
[2012-04-27 20:08] ==> ERROR: file not found: `/lib/udev/rules.d/13-dm-disk.rules'
[2012-04-27 20:08] ==> ERROR: file not found: `/lib/udev/rules.d/95-dm-notify.rules'
[2012-04-27 20:08] ==> ERROR: file not found: `/lib/initcpio/udev/11-dm-initramfs.rules'
[2012-04-27 20:08] -> Parsing hook: [filesystems]
[2012-04-27 20:08] ==> Generating module dependencies
[2012-04-27 20:08] ==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
[2012-04-27 20:08] ==> Image generation successful
[2012-04-27 20:08] upgraded linux (3.3.2-1 -> 3.3.3-1)
[2012-04-27 20:08] upgraded lvm2 (2.02.95-1 -> 2.02.95-2)
I used LiveCD, mounted FS under chroot, tried
# mkinitcpio -g /boot/initramfs-linux-fallback.img -S autodetect -k /boot/vmlinuz-linux
and had the same error with the same result .
How to solve the problem?