archive mirror
 help / color / mirror / Atom feed
From: kurcze <>
Subject: [linux-lvm] LVM thin provisioning on encrypted root unreliable
Date: Thu, 28 Feb 2019 22:31:33 +0100	[thread overview]
Message-ID: <> (raw)

Hello everyone,

I can't manage to get thinly provisioned LVM setup to work.

The problem is: I can't get to the decryption prompt to enter a password 
to decrypt root filesystem. It just hangs there.

My Setup:

VG with 3 PVs: 1 SSD, 1 HDD, 1 NVMe SSD

Thin pool in this VG with 2 LVs (for / and /var mountpoints)

both partitions are encrypted using LUKS

I've spent quite a lot of time trying many possible solutions. The worst 
thing is: sometimes it seems to work flawlessly for several boots. These 
moments convince me every time, that the previous solution I tried was 
the correct one and I can happily go on with my life. That is not the 
case. Sometimes it doesn't work the first 3 times (after reboot) and 
then suddenly it does (possibly after some tweaking with kernel 
parameters). I can't recognize any pattern. I can also reboot 3 times 
without doing anything and the 4th time it works.

Unfortunately I'm not a pro in this area and I don't know any way to 
debug it.

I would really appreciate the help. I would also gladly provide any 
additional information or command output. Following files might be helpful:

1. dmesg output from initramfs prompt (with Call Trace)

2. journal output during shutdown (not cleanly unmounted stuff)

3. lsblk output

4. grepped lsinitramfs with some relevant files

5. lvs with devices

Best regards,


             reply	other threads:[~2019-02-28 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 21:31 kurcze [this message]
2019-03-01  5:42 ` [linux-lvm] LVM thin provisioning on encrypted root unreliable Chris Murphy
2019-03-05 16:59   ` kurcze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).