mount: unknown file system type LVM2_member
Posted 09 December, 2016
So I’m planning on making a series, “mount: unknown file system type $TYPE”. I already have how to mount a ntfs partition, also how to mount a nfs on proxmox, now to be continued by another fun file system. I was going through old disks, so I came across one that had LVM2_member.
[email protected]:~# mount /dev/sdd2 /mnt/disk mount: unknown filesystem type 'LVM2_member'
The fdisk -l already told me it is a LVM :
[email protected]:~# fdisk -l /dev/sdd Disk /dev/sdd: 233.8 GiB, 251000193024 bytes, 490234752 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0009345d Device Boot Start End Sectors Size Id Type /dev/sdd1 * 63 208844 208782 102M 83 Linux /dev/sdd2 208845 488247479 488038635 232.7G 8e Linux LVM
(/dev/sdi1 is /boot partition, /dev/sdi2 is where the /home data resides)
Seems lvm2 tools also provide a way to check if it is lvm or not, using lvmdiskscan (/dev/sdd2 here)
[email protected]:~# lvmdiskscan /dev/sdb1 [ 1.82 TiB] /dev/sdc2 [ 149.04 GiB] /dev/sdd1 [ 101.94 MiB] /dev/sdd2 [ 232.71 GiB] LVM physical volume 0 disks 4 partitions 0 LVM physical volume whole disks 1 LVM physical volume
Fine, now let’s scan what lv’s (logical volumes) are to be found using lvscan
[email protected]:~# lvscan inactive '/dev/VolGroup00/LogVol00' [230.75 GiB] inherit inactive '/dev/VolGroup00/LogVol01' [1.94 GiB] inherit
Since this is an old disk in an enclosure, it is not activated on system boot. So we need to “activate” this lvm volume.
[email protected]:~# vgchange -ay 2 logical volume(s) in volume group "VolGroup00" now active
and bam, ready to mount :
[email protected]:~# lvscan ACTIVE '/dev/VolGroup00/LogVol00' [230.75 GiB] inherit ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GiB] inherit
now to mount :
mount /dev/VolGroup00/LogVol00 /mnt/disk
success !
If you enjoyed this article, please consider buying me a Dr Pepper.
Fuel the beast!
Buy me a Dr Pepper
[…] mount: unknown filesystem type LVM2_memberfull ZFS filesystem : No space left on device Search for: […]
22 January, 2017 at 17:04thanks a lot my brother
24 July, 2018 at 09:56You’re welcome
25 July, 2018 at 10:33Thank you, man!
1 September, 2018 at 04:14so i have 3 hard drives, 1 160, 1 2tb and 1 1tb. My 2tb hard drive is where my boot is and it is debian but it broke, so in order to save my files I tried the 160 as my boot and mount the file system of my 2 tb hard drive on there. My question is, if I do vgchange or any steps in here, will it wipe off the contents of my 2 tb?
15 September, 2018 at 13:14Wonderfully explained, a tricky subject like that made sooo easy to work with ^^, thanks a lot !!! You saved my day :P.
17 October, 2018 at 19:42[…] used native linux tools to inspect the LVM such that I could mount the disks and see my data. Here is a good tutorial on that with the key commands listed […]
20 January, 2019 at 22:08Moving VMs from VirtualBox to Hyper-V I ended up creating a new VM on Hyper-V then mounting the disk from VirtualBox to copy over files. I can see the disk and that there is a LVM physical volume but no /dev/path to mount. I think this may be because the names would be duplicates in the /dev path … so they just aren’t showing up. blkid shows the UUID of the LVM2_member I’m looking for … not sure how to list the LVM partition on this disk so I can mount them. Some way to do it specifying the UUID?
29 January, 2019 at 20:31Interesting issue, if you have no /dev/* path, it means udev rules did not catch it for some reason.
You could try to get UID :
vgdisplay
mount it :
vgrename $UID volgroup
if that is successful activate it :
vgchange -a y
But that’s just a guess. I don’t use many VM’s and have no exp. with Hyper-V
1 February, 2019 at 11:25Thanks a lot
13 May, 2019 at 17:05Thanks for leaving a reply 😉
16 May, 2019 at 11:20Wrong fs type, bad option, bad super lock on /dev/mapper/fedora-home, missing codepage or helper program, or ither error
16 May, 2019 at 14:31yea I’m having the same issues using proxmox. It is complaining about the wrong filesystem type. I’m using lvm thin provisioning and I think that is what is screwing it up.
The attributes from the lvs command:
[email protected]:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-aotz– 392.00g 0.00 0.04
root pve -wi-ao—- 20.00g
swap pve -wi-ao—- 8.00g
vm-500-omv pve Vwi-a-tz– 120.00g data 0.00
any thoughts on this?
4 June, 2019 at 23:47Is this add-on storage ? Might be tricky.
11 June, 2019 at 10:53It worked, thank you so much!
9 August, 2019 at 03:08Thank you 🙂
23 October, 2019 at 09:45Saved my bacon (actually the company’s), thanks!!!
20 November, 2019 at 23:32happy to help!
21 November, 2019 at 09:45Good, it is solved issue
26 November, 2019 at 16:55[…] disk sounds like an easy task, but there are glitches all the time. This post is very […]
25 January, 2020 at 21:17thank you for this !
1 May, 2020 at 17:18Thank you. This was driving me crazy.
3 May, 2020 at 00:15