On 2017-04-21 21:03, Anton Aylward wrote:
On 21/04/17 12:25 PM, Per Jessen wrote:
L A Walsh wrote:
I see...maybe I'll try that next. Sorry, but that wasn't clear. Thanks for clearing that up.
No problem - when you didn't know about modules-load.d, it's an honest mistake to make.
Let's clarify this: It loads a kernel module. It *ONLY* loads a kernel modules.
In the case of LVM it does not
* load any of the LVM config files * any of the user level LVM libraries or binaries * any of the UDEV rules pertaining to LVM or LVM initialization * any of the scripts that are needed to support any of the above * does not start lvmetad * does not run 'pvscan -a'
It is NOT, repeat NOT a solution to the issue that Linda was raising. Using a properly configured Dracut to build the custom kernel/initrd after a successful vanilla installation is the way to go. Get a baseline system running first. The after you've proven a baseline system is runnable, bootable, start modifying it ....
No no. On a freshly installed system, using YaST to do the installation, where YaST knows that it is installed on LVM and how exactly, the user can not configure dracut at all before it boots once. And configuring dracut is incorrect. YaST must provide a system that boots the first time after installation, it must do the correct dracut configuration itself. If the dracut configuration is incorrect, that is a bug of the installation system. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)