Move VMs from old disk.

diager0357

Member
Jan 15, 2022
4
0
6
34
Hello
I installed new server of Proxmox. I would like to move my VMs from disk of my old server.
Unfortunatelly, I don't know how to ucomplish.
I have disks like this:


root@local:/mnt/bak# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 512M 0 part └─sda3 sdb ├─sdb1 8:17 0 1007K 0 part ├─sdb2 8:18 0 512M 0 part /boot/efi └─sdb3 ├─pve-swap 253:0 0 8G 0 lvm [SWAP] ├─pve-root 253:1 0 ├─pve-data_tmeta 253:2 0 3.5G 0 lvm 338.4G 0 lvm └─pve-data_tdata 253 └─pve-data 253:4 0 338.4G 0 lvm sr0 11:0 1 1024M 0 rom


My old disk is sda. And when I am trying to mount it on my system I am receiving:


root@local:/mnt/bak1# mount /dev/sda3 /mnt/bak2 mount: /mnt/bak2: unknown filesystem type 'LVM2_member'.


Can someone help my how to mount my old data on new server of Proxmox?

Thanks in advance.
 
Last edited:
Hey,

All is in the return of your "problem" ^^

First of all, this is not a Proxmox "problem". It's a storage missendestanding.

On your old installation, you've installed it in "LVM configuration".

LVM => Logical Volume Manager.

You cannot mount a disk LVM used directly. You need to mount theses logical volumes.

Check theses commands in CLI:
logical volume scan short: lvs
logical volume scan "extended": lvdisplay

Logical group scan short: vgs
Logical group scan extended: vgdisplay

Physical volume scan short: pvs
Physical volume scan extended: pvdisplay.

You can found theses logicals volumes links in /dev/mapper/idk-actually

Your mount command seem to be like that:
mount /dev/mapper/VG_name/lv_name /your/mountpoint

(ps: i don't really remember the syntaxe in the folder /dev/mapper/, it could be like VG_NAME-LV_name )

Bests rresgards
 
I have simmilar problem but it is not easy task for me, so how to activete this images again in proxmox?
root@mila:/dev/mapper# ls
control drive2-vm--105--disk--0 drive2-vm--108--disk--0 drive2-vm--111--disk--0 drive2-vm--118--disk--0 pve-data pve-data-tpool
drive2-vm--100--disk--0 drive2-vm--106--disk--0 drive2-vm--109--disk--0 drive2-vm--113--disk--0 drive2-vm--119--disk--0 pve-data_tdata pve-root
drive2-vm--104--disk--0 drive2-vm--107--disk--0 drive2-vm--110--disk--0 drive2-vm--117--disk--0 drive2-vm--124--disk--0 pve-data_tmeta pve-swap
root@mila:/dev/mapper# cd ls -l
-bash: cd: too many arguments
root@mila:/dev/mapper# ls -l
total 0
crw------- 1 root root 10, 236 Sep 9 19:41 control
lrwxrwxrwx 1 root root 7 Sep 10 09:17 drive2-vm--100--disk--0 -> ../dm-4
lrwxrwxrwx 1 root root 7 Sep 9 19:41 drive2-vm--104--disk--0 -> ../dm-5
lrwxrwxrwx 1 root root 7 Sep 9 19:41 drive2-vm--105--disk--0 -> ../dm-6
lrwxrwxrwx 1 root root 7 Sep 9 19:41 drive2-vm--106--disk--0 -> ../dm-7
lrwxrwxrwx 1 root root 7 Sep 9 19:41 drive2-vm--107--disk--0 -> ../dm-8
lrwxrwxrwx 1 root root 7 Sep 9 19:41 drive2-vm--108--disk--0 -> ../dm-9
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--109--disk--0 -> ../dm-10
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--110--disk--0 -> ../dm-11
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--111--disk--0 -> ../dm-17
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--113--disk--0 -> ../dm-14
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--117--disk--0 -> ../dm-12
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--118--disk--0 -> ../dm-13
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--119--disk--0 -> ../dm-16
lrwxrwxrwx 1 root root 8 Sep 9 19:41 drive2-vm--124--disk--0 -> ../dm-15
lrwxrwxrwx 1 root root 8 Sep 9 19:41 pve-data -> ../dm-19
lrwxrwxrwx 1 root root 7 Sep 9 19:41 pve-data_tdata -> ../dm-3
lrwxrwxrwx 1 root root 7 Sep 9 19:41 pve-data_tmeta -> ../dm-2
lrwxrwxrwx 1 root root 8 Sep 9 19:41 pve-data-tpool -> ../dm-18
lrwxrwxrwx 1 root root 7 Sep 9 19:41 pve-root -> ../dm-1
lrwxrwxrwx 1 root root 7 Sep 9 19:41 pve-swap -> ../dm-0

root@mila:/dev/mapper# mount /dev/mapper/drive2-vm--100--disk--0 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mapper/drive2-vm--100--disk--0, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
root@mila:/dev/mapper#
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!