Unable to restore VM from a backup URGENT

[baamaster]

Hello forum!

yesterday I found my VM was not working, so I tried to restore it from a backup. When a restore is attempted, I get the following output:
​

restore vma archive: lzop -d -c /var/lib/vz/dump/vzdump-qemu-102-2015_04_02-00_00_02.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp79685.fifo - /var/tmp/vzdumptmp79685
CFG: size: 260 name: qemu-server.conf
DEV: dev_id=1 size: 429496729600 devname: drive-sata0
CTIME: Thu Apr 2 00:00:04 2015TASK ERROR: command 'lzop -d -c /var/lib/vz/dump/vzdump-qemu-102-2015_04_02-00_00_02.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp79685.fifo - /var/tmp/vzdumptmp79685' failed: command '/usr/bin/qemu-img create -o 'preallocation=metadata' -f qcow2 /var/lib/vz/images/102/vm-102-disk-14.qcow2 419430400K' failed: got timeout

The other thing I had found was that the original Virtual sata disk was gone, and the RAM was set to 128MB.

My goal now is to bring back the original disk, as I have found how to make the data on it work for me.

I did find the .qcow2 file, but how do I attach it to the VM?

Thank you whoever helps me

 

[udo]

I did find the .qcow2 file, but how do I attach it to the VM?

Hi,
simply edit the conf-file of the VM.

It's define the type of storage (ide/virtio), the storage (this is configured in /etc/pve/storage.cfg) + image for an filesystem and the name plus caching/size.

like:

virtio0: local:100/vm-100-disk-1.qcow2,cache=writethrough,size=32G

local:

grep -A 1 local /etc/pve/storage.cfg 
dir: local
        path /var/lib/vz

ls -l /var/lib/vz/images/100/vm-100-disk-1.qcow2 
-rw-r--r-- 1 root root 34365243392 Feb  6 15:11 /var/lib/vz/images/100/vm-100-disk-1.qcow2

Udo

 

[baamaster]

this is all the /etc/pve/storage.cfg contains

dir: local    path /var/lib/vz
    content images,iso,vztmpl,backup,rootdir
    maxfiles 50

 

[udo]

this is all the /etc/pve/storage.cfg contains

dir: local    path /var/lib/vz
    content images,iso,vztmpl,backup,rootdir
    maxfiles 50

And where is now the problem?

Udo

 

[baamaster]

I spoke too soon, I got the drive reattached, but now it is unable to boot from the drive

 

[udo]

I spoke too soon, I got the drive reattached, but now it is unable to boot from the drive

Hi,
and how looks your VM-config?

BTW. if you connect an live-boot-cd like grml, and boot from cd - do you see the hdd-content?

Udo

 

[baamaster]

Hi,
and how looks your VM-config?

BTW. if you connect an live-boot-cd like grml, and boot from cd - do you see the hdd-content?

Udo

bootdisk: sata1
cores: 4
memory: 10240
name: MC
net0: e1000=B2:67:FF:9B:9D:DF,bridge=vmbr0
ostype: other
sata0: local:102/vm-102-disk-1.qcow2,format=qcow2,size=400G
sata1: local:102/vm-102-disk-16.qcow2,format=qcow2,size=10G
sockets: 2

I used Ubuntu on a second drive, probably not the simplest way to go about it.
now how do I access the new drive?

 

[udo]

bootdisk: sata1
cores: 4
memory: 10240
name: MC
net0: e1000=B2:67:FF:9B:9D:DF,bridge=vmbr0
ostype: other
sata0: local:102/vm-102-disk-1.qcow2,format=qcow2,size=400G
sata1: local:102/vm-102-disk-16.qcow2,format=qcow2,size=10G
sockets: 2

I used Ubuntu on a second drive, probably not the simplest way to go about it.
now how do I access the new drive?

Hi,
any change, if you use ide or virtio?
like

bootdisk: ide0
cores: 4
memory: 10240
name: MC
net0: e1000=B2:67:FF:9B:9D:DF,bridge=vmbr0
ostype: other
ide1: local:102/vm-102-disk-1.qcow2,format=qcow2,size=400G
ide0: local:102/vm-102-disk-16.qcow2,format=qcow2,size=10G
sockets: 2

Udo