On 2017-02-23 20:08, Thanos Baloukas wrote:
On 23/02/2017 07:25 μμ, Thanos Baloukas wrote:
On 23/02/2017 02:59 μμ, Linuxero wrote:
Hi everybody;
I have finished the latest development systemd LFS book. I have NVME
disks in my machine and the LFS partition is a GUID one. I configured
my
kernel and it boot well if I compile the NVME drivers built-in.
However,
I wanted to compile NVME as loadable modules. I installed dracut and
tried to create an initrd. Actually, the initrd is well, but for some
strange reason I am always dropped to dracut emergency shell as the
partition can not be found.
Dracut version is 044. The emergency shell is unusable, as if the
system
were halted.
Any suggestion about dracut with LFS/BLFS?
Thanks in advance,
Are there any messages? Are the 'linux' and 'root=UUID='
entries in grub.cfg correct? Could it be that there is not
/etc/os-release? I recall that it would not switch root
if it did not exist.
You said you are using GUID (I'm getting that as GPT partition table).
I have no experience with GPT, sorry, the required root= entry
may differ. UUIDs may not be required, I mentioned that because
I'm using them in /etc/fstab and grub.cfg when booting with
an initramfs built with dracut.
--
Thanos
Thanks for your answers. It is GPT scheme that I am using. UUIDs, Labels
and everything is correct.
BTW; UUIDs work the same on GPT.
I guess that my problem is the following:
NVME modules are not loaded in initrd. Because; when I compile the
kernel with NVME built-in, I can boot without any problem. So it should
be something with initrd. I am new to dracut. I could write a hook or a
module, but I don't think that is necessary for my scenario. Am I right?
If someone has more experience with dracut and how to build initrd for
LFS using it; I'd appreciate any hint.
Thanks again
--
Be good, be happy and never let the lovely smile on your nice lips fade
away
--
http://lists.linuxfromscratch.org/listinfo/lfs-chat
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
