Re: [gentoo-user] pvcreate on LUKS container -> 'Device not found'

[Willie Matthews]

On 03/08/2016 01:41 PM, Frank Steinmetzger wrote:
> Hi folks
>
> I’m trying to follow an article¹ on setting up a fully encrypted system for
> my soon-to-arrive laptop. It and others (e.g. ² in a very condensed form)
> simply luksFormat a block device, then luksOpen it and run pvcreate on that.
>
> I’ve never used LVM before, it’s only installed as a dependency for various
> FS tools. Hence, my LVM install is basically pure vanilla. But when I try to
> follow those articles, I get:
>
> kern $ cryptsetup status /dev/mapper/tp
> /dev/mapper/tp is active.
> [...]
>
> kern $ pvcreate /dev/mapper/tp
>   /run/lvm/lvmetad.socket: connect failed: No such file or directory
>   WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
>   Device /dev/mapper/tp not found (or ignored by filtering).
>
> The filter rule in /etc/lvm/lvm.conf simply says the default:
> filter = [ "r|/dev/nbd.*|", "a/.*/" ]
> Meaning ‘include everything except /dev/nbd*’.
>
> Can you give me a hint what I might be missing? Perhaps I need to set some
> other of the many options in lvm.conf?
>
> Gratefully awaiting any helpful nudge.
>
>
> ¹ https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide/Preparing_the_LUKS-LVM_Filesystem_and_Boot_USB_Key
> ² http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
>

If I am not mistaken you have to create a partition on the drive before
you can use "pvcreate /dev/sda1".

If you would like to get rid of the /run/lvm/lvmetad.socket error just
start lvm with "service lvm start". I still get the error when starting
up but it still works.

I used your first link to do a full encrypted secure boot install of
Gentoo.
(https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide/Preparing_the_LUKS-LVM_Filesystem_and_Boot_USB_Key).
It works like a charm.

If you don't want to use a USB key to boot every time make sure you make
a small partition on the drive to hold all the information for your
encryption and secure boot files. I made that mistake and it took a
while to fix.

Hope this helps you.


-- 

Willie Matthews
matthews.willie80@×××××.com
[phone]