All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Fwd: LVM/BTRFS on LUKS unreadable
Date: Sun, 13 Sep 2015 20:15:42 +0300	[thread overview]
Message-ID: <55F5AF3E.1070709@gmail.com> (raw)
In-Reply-To: <55DDF9BB.8050503@autoboot.org>

26.08.2015 20:39, Klemens Nanni пишет:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> - -------- Forwarded Message --------
> Subject: LVM/BTRFS on LUKS unreadable
> Date: Mon, 17 Aug 2015 23:24:32 +0000
> From: Autoboot <contact@autoboot.org>
> To: bug-grub@gnu.org
>
> Hello,
>
> GRUB 2.02~beta2 as of commit afd0f21b2027310fda52b00ac1b964041d39a363
> used as autoboot payload on a ThinkPad X201 here.
>
> After setting up LVM on LUKS and writing random test files on the disk,
> GRUB2 opens the disk but cannot read it's content at (crypto0).
>
> Disk setup:
> 	$ cryptsetup luksFormat /dev/sdb
> 	$ cryptsetup open /dev/sdb test
> 	$ pvcreate /dev/mapper/test
> 	$ vgcreate test /dev/mapper/test
> 	$ lvcreate test -L 50G -n root
> 	$ mkfs.ext4 -L test_root /dev/mapper/test-root
> 	$ mount /dev/mapper/test-root /mnt
> 	$ dd if=/dev/urandom bs=1M count=20M of=/mnt/20M
>
> GRUB Shell:
> 	(all modules incl. lvm properly loaded)
> 	$ cryptomount (ahci0)

I pushed fix that properly strips parenthesis from device name. 
Otherwise use

cryptomount ahci0

it works.

Thank you for report!


  reply	other threads:[~2015-09-13 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 17:39 Fwd: LVM/BTRFS on LUKS unreadable Klemens Nanni
2015-09-13 17:15 ` Andrei Borzenkov [this message]
2015-09-15 19:08 ` Klemens Nanni

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=55F5AF3E.1070709@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.