| View previous topic :: View next topic |
| Author |
Message |
silentcola
n00b
Joined: 17 Nov 2019
Posts: 23
|
 Posted: Sat Dec 21, 2019 12:00 pm Post subject: [solved] cannot grub-mkconfig: Failed to connect to lvmetad. |
 |
|
Hi all,
Going through install process for Gentoo with LUKS/LVM, first by following Sakaki's EFI Install Guide then MoJo's 'Encrypted Gentoo Linux Install Tutorial | LVM - LUKS - Plymouth' on youtube.
Unfortunately when I try to make crub config | Code: | | grub-mkconfig -o /boot/grub/grub.cfg |
I get below error. I exited chroot and remounted hostrun/run etc, re chrooted back in, but no success.
| Code: |
livecd / # mount --bind /run /mnt/gentoo/hostrun/
livecd / # chroot /mnt/gentoo /bin/bash
livecd / # mount --bind hostrun/lvm /run/lvm
livecd / # grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
done
livecd / #
|
I checked a few more videos/resources they remount and it just works, what am I doing wrong?
My steps leading up to make grub:
| Code: |
echo 'GRUB_PLATFORMS="efi-64"' >> /etc/portage/make.conf
echo "sys-boot/grub:2 mount device-mapper" >> /etc/portage/package.use/sys-boot
emerge -av sys-boot/grub:2
mount /boot
vim /etc/default/grub
GRUB_PRELOAD_MODULES=lvm
GRUB_ENABLE_CRYPTODISK=y
GRUB_DEVICE=/dev/ram0
GRUB_CMDLINE_LINUX="crypt_root=/dev/sda3 real_root=/dev/mapper/gentoo-root rootfstype=ext4 dolvm quiet splash"
grub-install --target=x86_64-efi --efi-directory=/boot --modules="linux crypto search_fs_uuid luks lvm" --recheck /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg |
I'm still new, so not sure what log files to add, so if you need anymore info, let me know.
Last edited by silentcola on Sat Jan 04, 2020 3:26 pm; edited 1 time in total |
|
| Back to top |
|
 |
nick_gentoo
Tux's lil' helper
Joined: 07 Jan 2019
Posts: 140
|
| Posted: Sat Dec 21, 2019 3:05 pm Post subject: |
|
|
Those are just some warnings, the "done" at the end should mean that the file was generated.
Do you have now a /boot/grub/grub.cfg file? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W
|
| Posted: Sat Dec 21, 2019 3:17 pm Post subject: |
|
|
silentcola,
lvmetad is optional at the moment. In large systems, its much faster than device scanning, which reads every block device to find LVM volumes.
lvmetad is preferred over device scanning, so lvm shouts at you.
Its safe to ignore the warnings for now.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
silentcola
n00b
Joined: 17 Nov 2019
Posts: 23
|
| Posted: Sat Dec 21, 2019 3:31 pm Post subject: |
|
|
Thanks for the rapid response team.
I looked over the Done, didn't realize it was completed successfully.
Seems like it worked. =) |
|
| Back to top |
|
|
|
Installing Gentoo
