Migration of VM from Proxmox 3.x to 4.2 failed using a VZDump

Mannekino

New Member
Aug 23, 2014
14
0
1
Hello,

Currently I have a single Proxmox server in production with the following version:
Code:
pve-manager/3.3-5/bfebec03 (running kernel: 2.6.32-34-pve)

I am planning to replace the server I currently have with another server running Proxmox 4.2.
Code:
pve-manager/4.2-17/e1400248 (running kernel: 4.4.13-2-pve)

I am also planning on migrating my virtual machines using the backup feature. I created a backup of one of my virtual machines on the Proxmox 3.x server and tried to restore it on my Proxmox 4.2 server to test this. However the restore proces failed, see below.
Code:
restore vma archive: lzop -d -c /var/lib/vz/dump/vzdump-qemu-100-2016_07_22-14_52_35.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp4981.fifo - /var/tmp/vzdumptmp4981
CFG: size: 249 name: qemu-server.conf
DEV: dev_id=1 size: 42949672960 devname: drive-scsi0
CTIME: Fri Jul 22 14:52:35 2016
Formatting '/var/lib/vz/images/100/vm-100-disk-1.raw', fmt=raw size=42949672960
new volume ID is 'local:100/vm-100-disk-1.raw'
map 'drive-scsi0' to '/var/lib/vz/images/100/vm-100-disk-1.raw' (write zeros = 0)
progress 1% (read 429522944 bytes, duration 2 sec)
progress 2% (read 859045888 bytes, duration 4 sec)
progress 3% (read 1288503296 bytes, duration 7 sec)
progress 4% (read 1718026240 bytes, duration 10 sec)
progress 5% (read 2147483648 bytes, duration 13 sec)
progress 6% (read 2577006592 bytes, duration 16 sec)
progress 7% (read 3006529536 bytes, duration 18 sec)
progress 8% (read 3435986944 bytes, duration 19 sec)
progress 9% (read 3865509888 bytes, duration 19 sec)
progress 10% (read 4294967296 bytes, duration 22 sec)
progress 11% (read 4724490240 bytes, duration 22 sec)
progress 12% (read 5154013184 bytes, duration 25 sec)
progress 13% (read 5583470592 bytes, duration 27 sec)
progress 14% (read 6012993536 bytes, duration 30 sec)
progress 15% (read 6442450944 bytes, duration 32 sec)
progress 16% (read 6871973888 bytes, duration 37 sec)
progress 17% (read 7301496832 bytes, duration 53 sec)
progress 18% (read 7730954240 bytes, duration 67 sec)
progress 19% (read 8160477184 bytes, duration 82 sec)
progress 20% (read 8589934592 bytes, duration 90 sec)
progress 21% (read 9019457536 bytes, duration 98 sec)
progress 22% (read 9448980480 bytes, duration 157 sec)
progress 23% (read 9878437888 bytes, duration 194 sec)
progress 24% (read 10307960832 bytes, duration 200 sec)
progress 25% (read 10737418240 bytes, duration 204 sec)
progress 26% (read 11166941184 bytes, duration 208 sec)
progress 27% (read 11596464128 bytes, duration 211 sec)
progress 28% (read 12025921536 bytes, duration 215 sec)
progress 29% (read 12455444480 bytes, duration 266 sec)
progress 30% (read 12884901888 bytes, duration 279 sec)
progress 31% (read 13314424832 bytes, duration 283 sec)
progress 32% (read 13743947776 bytes, duration 287 sec)
progress 33% (read 14173405184 bytes, duration 291 sec)
progress 34% (read 14602928128 bytes, duration 296 sec)
progress 35% (read 15032385536 bytes, duration 300 sec)
progress 36% (read 15461908480 bytes, duration 343 sec)
progress 37% (read 15891431424 bytes, duration 366 sec)
progress 38% (read 16320888832 bytes, duration 369 sec)
progress 39% (read 16750411776 bytes, duration 373 sec)
progress 40% (read 17179869184 bytes, duration 376 sec)
progress 41% (read 17609392128 bytes, duration 379 sec)
progress 42% (read 18038915072 bytes, duration 382 sec)
progress 43% (read 18468372480 bytes, duration 393 sec)
progress 44% (read 18897895424 bytes, duration 442 sec)
progress 45% (read 19327352832 bytes, duration 454 sec)
progress 46% (read 19756875776 bytes, duration 457 sec)
progress 47% (read 20186398720 bytes, duration 461 sec)
progress 48% (read 20615856128 bytes, duration 464 sec)
progress 49% (read 21045379072 bytes, duration 468 sec)
progress 50% (read 21474836480 bytes, duration 478 sec)
progress 51% (read 21904359424 bytes, duration 527 sec)
progress 52% (read 22333882368 bytes, duration 529 sec)
progress 53% (read 22763339776 bytes, duration 554 sec)
progress 54% (read 23192862720 bytes, duration 556 sec)
progress 55% (read 23622320128 bytes, duration 574 sec)
progress 56% (read 24051843072 bytes, duration 586 sec)
progress 57% (read 24481366016 bytes, duration 589 sec)
progress 58% (read 24910823424 bytes, duration 591 sec)
progress 59% (read 25340346368 bytes, duration 593 sec)
progress 60% (read 25769803776 bytes, duration 595 sec)
progress 61% (read 26199326720 bytes, duration 598 sec)
progress 62% (read 26628849664 bytes, duration 652 sec)
progress 63% (read 27058307072 bytes, duration 655 sec)
progress 64% (read 27487830016 bytes, duration 675 sec)
progress 65% (read 27917287424 bytes, duration 682 sec)
progress 66% (read 28346810368 bytes, duration 684 sec)
progress 67% (read 28776333312 bytes, duration 687 sec)
progress 68% (read 29205790720 bytes, duration 690 sec)
progress 69% (read 29635313664 bytes, duration 692 sec)
progress 70% (read 30064771072 bytes, duration 697 sec)
progress 71% (read 30494294016 bytes, duration 755 sec)
progress 72% (read 30923816960 bytes, duration 768 sec)
progress 73% (read 31353274368 bytes, duration 772 sec)
progress 74% (read 31782797312 bytes, duration 776 sec)
progress 75% (read 32212254720 bytes, duration 778 sec)
progress 76% (read 32641777664 bytes, duration 809 sec)
progress 77% (read 33071300608 bytes, duration 829 sec)
progress 78% (read 33500758016 bytes, duration 862 sec)

** (process:4984): ERROR **: restore failed - bdrv_write to  failed (-28)
/bin/bash: line 1:  4983 Broken pipe             lzop -d -c /var/lib/vz/dump/vzdump-qemu-100-2016_07_22-14_52_35.vma.lzo
      4984 Trace/breakpoint trap   | vma extract -v -r /var/tmp/vzdumptmp4981.fifo - /var/tmp/vzdumptmp4981
temporary volume 'local:100/vm-100-disk-1.raw' sucessfuly removed
TASK ERROR: command 'lzop -d -c /var/lib/vz/dump/vzdump-qemu-100-2016_07_22-14_52_35.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp4981.fifo - /var/tmp/vzdumptmp4981' failed: exit code 133

My Proxmox 4.2 server has a very similar setup to my Proxmox 3.x server. I have a second disk which I configured as a physical device for LVM, then I create a single volume group which I added in Proxmox GUI. Here is the output of my storage.conf.
Code:
dir: local
        path /var/lib/vz
        maxfiles 8
        content backup,images,rootdir,vztmpl,iso
        shared

lvm: storage
        vgname storage
        content images,rootdir

I used these instructions to remove the default storage setup from my Proxmox 4.2 server so it would be the same as on my Proxmox 3.2 server. Below some additional information.

pvs
Code:
  PV         VG      Fmt  Attr PSize   PFree
  /dev/sda3  pve     lvm2 a--   69.12g      0
  /dev/sdb1  storage lvm2 a--  279.46g 279.46g

vgs
Code:
  VG      #PV #LV #SN Attr   VSize   VFree
  pve       1   3   0 wz--n-  69.12g      0
  storage   1   0   0 wz--n- 279.46g 279.46g

lvs
Code:
  LV   VG   Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data pve  -wi-ao---- 45.12g
  root pve  -wi-ao---- 16.00g
  swap pve  -wi-ao----  8.00g

/etc/fstab
Code:
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
/dev/pve/swap none swap sw 0 0
/dev/pve/data /var/lib/vz ext4 defaults 0 1
proc /proc proc defaults 0 0

Hopefully someone can help me troubleshoot this issue. If you need more information please let me know.
 
At this point it would be nice to be able to delete my own thread to hide my own stupidity :D

I forgot to point to my "storage" volume group when restoring and it used my local storage so disk space ran out.

I guess this thread can stay up to help people making the same stupid mistake.
 

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!