From: Klaus Lichtenwalder <lichtenwalder@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM problem: Unable to mount encrypted Luks HDs after reinstalling Ubuntu; Error: unknown filesystem type 'LVM2_member'
Date: Fri, 12 Jun 2015 22:03:26 +0200 [thread overview]
Message-ID: <557B3B0E.4050009@gmail.com> (raw)
In-Reply-To: <20150530054508.Horde.UHD8nrE6gSp5bNvnIOGDQA5@webmail.df.eu>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Am 30.05.2015 um 05:45 schrieb st@ateneto.com:
> Hallo,
>
> thank you very much for anyone taking the time to read this.
>
> I am using a Thinkpad Edge E145 with Ubuntu 14.04 installed.
> I have recently reinstalled Ubuntu to a new HD. This installation is
> LUKS encrypted LVM and works without problems.
>
> My old installation on a LVM Luks encrypted drive would no longer start up.
> I had deleted old kernels. Maybe the problems are related to that.
> ...
> sog@sog-workstation:~$ sudo mount /dev/mapper/encrypted
> /media/encryptedmount: unknown filesystem type 'LVM2_member'
> sog@sog-workstation:~$
>
Hi,
this looks like there's a vg and/or a lv in your encrypted partition also.
You might check with pvscan, vgscan, lvscan, whether there's anything of
interest.
Because "unknown filesystem type "LVM2_member"" seems to imply this is a
LV instead of a "pure" filesystem.
Klaus
--
------------------------------------------------------------------------
Klaus Lichtenwalder, Dipl. Inform., http://www.lichtenwalder.name/
PGP Key fingerprint: 0CF4 4A47 355A DD36 65B3 56F3 2696 79B2 7F3D 1020
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-06-12 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 3:45 [linux-lvm] LVM problem: Unable to mount encrypted Luks HDs after reinstalling Ubuntu; Error: unknown filesystem type 'LVM2_member' st
2015-06-01 8:40 ` Ondrej Kozina
2015-06-12 20:03 ` Klaus Lichtenwalder [this message]
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=557B3B0E.4050009@gmail.com \
--to=lichtenwalder@gmail.com \
--cc=linux-lvm@redhat.com \
/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 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).