As far as I can tell: sdb1 is used as PV (physical volume) for VG (volume group) “HDD5TB”. This VG holds one logical volume (LV) = disk for vm 101.
A PV can not be mounted as a “normal” file system. If your goal was to mount the disk of the vm in the host, do the following:
- make sure the vm is turned off
- use
losetup --partscan /dev/loop0 /dev/HDD5TB/vm-101-disk-0to tell the kernel, that this “file” should be treated as a disk - use
mount /dev/loop0<partition> /<mountpoint>to mount this partition - do stuff
- use
umount /dev/loop0<partition>to unmount - use
losetup -d /dev/loop0to detach the disk
https://forum.proxmox.com/threads/mount-error.88580/
Mounting LVM disk under proxmox hypervisor
https://www.x24u.com/mounting-lvm-disk-under-proxmox-environment
Sometimes you need to get/change/analyse some files/data/logs from the virtual machine which running under lvm.
We are going to mount the disk under Proxmox hypervisor, which is running debian as a base OS.
Imagine, we have situation like that:
On vm-100-disk-1 we have the data which we need, but its under lvm control, so its not so easy to mount that volume simply using mount command, because we will get this error message:
To get around this problem, we will need to create a loop device where our vm disk will be bound to:
Now, scan the volume groups and check if you have new vgs there
Yes, we have a new vmvol volume group here, which we actually need. Ok, then activate that group so you can mount it afterwards:
Ok, the volume group is now active. All volume groups are located under /dev/mapper/. So we just mount it (i.e.: under /mnt/vmvol (path should exist)) like: