[linux-lvm] LVM problem: Unable to mount encrypted Luks HDs after reinstalling Ubuntu; Error: unknown filesystem type 'LVM2_member'

[s***@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.

Now I can no longer mount the old LVM Luks encrypted drive when I plug
it in to the notebook through a USB port.

Here is the present situation in nautilus:
http://postimg.org/image/4cq099iej/

cog wheels.
Bottom left:
Format
Create Disk image
Restore Disk image
Benchmark

Top right:
Create Disk image
Restore Disk image
Benchmark
Power Off

http://postimg.org/image/6shypz5th/

Here I have the additional cog wheel options to:
Edit partition
Change pass phrase
Edit Encryption options

This is the situation in the terminal:
***@sog-workstation:~$ sudo cryptsetup luksOpen /dev/sdb5 encrypted
Enter passphrase for /dev/sdb5:
***@sog-workstation:~$ sudo mkdir /media/encrypted
***@sog-workstation:~$ sudo mount /dev/mapper/encrypted /media/encrypted
mount: unknown filesystem type 'LVM2_member'

***@sog-workstation:~$ sudo vgscan --mknodes
Reading all physical volumes. This may take a while...
Found volume group "it-vg" using metadata type lvm2
Found volume group "it-vg" using metadata type lvm2
***@sog-workstation:~$ sudo vgchange -ay
device-mapper: create ioctl on it--vg-root failed: Device or resource busy
device-mapper: create ioctl on it--vg-swap_1 failed: Device or resource busy
0 logical volume(s) in volume group "it-vg" now active
2 logical volume(s) in volume group "it-vg" now active
***@sog-workstation:~$ sudo lvscan -a
inactive '/dev/it-vg/root' [462.20 GiB] inherit
inactive '/dev/it-vg/swap_1' [3.27 GiB] inherit
***@sog-workstation:~$ sudo ls -l /dev/mapper /dev/it-vg
/dev/it-vg:
total 0
lrwxrwxrwx 1 root root 7 5月 30 07:52 root -> ../dm-1
lrwxrwxrwx 1 root root 7 5月 30 07:52 swap_1 -> ../dm-2

/dev/mapper:
total 0
crw------- 1 root root 10, 236 5月 30 07:52 control
lrwxrwxrwx 1 root root 7 5月 30 07:57 encrypted -> ../dm-3
lrwxrwxrwx 1 root root 7 5月 30 07:52 it--vg-root -> ../dm-1
lrwxrwxrwx 1 root root 7 5月 30 07:52 it--vg-swap_1 -> ../dm-2
lrwxrwxrwx 1 root root 7 5月 30 07:52 sda5_crypt -> ../dm-0
***@sog-workstation:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/it--vg-root 47G 4.7G 40G 11% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 1.6G 4.0K 1.6G 1% /dev
tmpfs 316M 1.3M 315M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.6G 156K 1.6G 1% /run/shm
none 100M 44K 100M 1% /run/user
/dev/sda1 236M 83M 141M 38% /boot
/dev/sdb1 236M 48M 176M 22% /media/sog/4e1bce6a-3555-4b0e-a7e2-4dfc81831bfc
***@sog-workstation:~$ mount
/dev/mapper/it--vg-root on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sda1 on /boot type ext2 (rw)
systemd on /sys/fs/cgroup/systemd type cgroup
(rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse
(rw,nosuid,nodev,user=sog)
/dev/sdb1 on /media/sog/4e1bce6a-3555-4b0e-a7e2-4dfc81831bfc type ext2
(rw,nosuid,nodev,uhelper=udisks2)
***@sog-workstation:~$ sudo fsck -vy /dev/mapper/encrypted
fsck from util-linux 2.20.1
fsck: fsck.LVM2_member: not found
fsck: error 2 while executing fsck.LVM2_member for /dev/mapper/encrypted

***@sog-workstation:~$ sudo mount /dev/mapper/encrypted
/media/encryptedmount: unknown filesystem type 'LVM2_member'
***@sog-workstation:~$

Thank you!
Sebastian

[Ondrej Kozina]

Hi Sebastian,

I'm not familiar with Ubuntu so the only thing I can help you with is
trying to explain what went (probably) wrong.

Post by s***@ateneto.com
mount: unknown filesystem type 'LVM2_member'

This seems like you're about to mount lvm2 PV (VG member) instead of LV
with actual filesystem residing in.

You should always try to mount LVM2 LV like follows:
mount /dev/<your_vg_name>/<your_lv_name> /mnt/point

Could you paste here 'lsblk' output here so we have better picture about
your device stack?

Post by s***@ateneto.com
Reading all physical volumes. This may take a while...
Found volume group "it-vg" using metadata type lvm2
Found volume group "it-vg" using metadata type lvm2
device-mapper: create ioctl on it--vg-root failed: Device or resource busy
device-mapper: create ioctl on it--vg-swap_1 failed: Device or resource busy
0 logical volume(s) in volume group "it-vg" now active
2 logical volume(s) in volume group "it-vg" now active

Seems like an activation issue. We can't help you more without -vvvv
debug ouput. (vgchane -ay -vvvv). Also 'dmsetup table' and 'dmsetup
info' commands output would help after failure in any activation command.

Regards
Ondrej

[Klaus Lichtenwalder]

Post by s***@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.
...
/media/encryptedmount: unknown filesystem type 'LVM2_member'

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