For the last few Slackware versions I've had to add the LVM option (-L) when creating the initrd for a RAID/LUKS root partition. Previously (a few versions ago) the LVM option was not required.
The disk layer ordering when I install Slackware is the usual; working from the bottom up: partitions, RAID, LUKS, file system.
I used my shiny new official Slackware64 14.2 DVD to install Slackware on a new computer and found that the '-L' option is still required, just as it was required in the last few versions of Slackware.
If I omit the '-L' option from the mkinitrd command I get the following error messages in 14.2 just AFTER entering the LUKS passphrase.
Code:
(retyped from screen, may contain a typo)
Enter Passphrase for /dev/md12:
<type something and hit ENTER>
udevd[558]: failed to execute '/sbin/dmsetup' '/sbin/dmsetup udevflags 5125460': no such file or directory
udevd[559]:failed to execute '/sbin/dmesetup' '/sbin/dmsetup udevcomplete 5125460': no such file or directory
Why is the -L option needed to make it work? I'm not using LVM.
A few years ago I believe I found this workaround (of adding -L) somewhere on the Internet when I couldn't get the newest Slackware version to boot. But I can't find any references to it now.
The mkinitrd command I used (retyped) ...
Code:
mkinitrd -c -k 4.4.14 -f ext4 -r cryptroot -m ext4:\
xhci-pci:ohci-pci:ehci-pci:\
xhci-hcd:uhci-hcd:ehci-hcd:\
usbhid:hid_generic\
-C /dev/md12 -R -u -L -o /boot/initrd.gz
When run on my new computer the command
/usr/share/mkinitrd/mkinitrd_command_generator.sh does NOT include the LVM option (-L) with its list suggested options.
Isn't this a BUG to require LVM functionality when not using LVM to boot?
BONUS QUESTION
The command generator lists the following modules with
underscores:
Code:
hid_generic
hid_multitouch
But the
load_kernel_modules file in the
/boot/initrd-tree directory displays them with
hyphens:
Code:
hid-generic
hid-multitouch
Are
underscores and
hypens interchangeable in module names regarding initrd creation?