Hello, I am in a bit of severe trouble here so I hope I can have help from you guys..
I have this CentOS VM that I backed up twice to a small backup storage of 300GB.. What I didnt realize when I backed up the VM a second time is that the backup storage was running low on space but nevertheless the backup finished without errors.
Then I went ahead to launch the VM and do some modifications which I didnt want to keep , so I decided to restore the latest backup. It worked (restore finished 100%) but when I launched the VM, centos crashed at bootup saying that a partition or drive was not found and dropped me to a CLI. The partition or drive that couldn't be found was in fact a logical volume at the node's level assigned to the VM via its .conf file such as
Then I deleted older backups of other VM's to free up some space, restored the latest backup of the CentOS machine:
Then launched the VM again only to see the same error (partition or drive cannot be found). Then I looked in the webgui to see if the missing partition or drive was still assigned to the VM and saw that It was missing!! Then I SSH'd into proxmox node and looked in the .conf file, the drive was commented out! Why??
I uncommented it but didnt help...
What can I do????
Thanks
I have this CentOS VM that I backed up twice to a small backup storage of 300GB.. What I didnt realize when I backed up the VM a second time is that the backup storage was running low on space but nevertheless the backup finished without errors.
Then I went ahead to launch the VM and do some modifications which I didnt want to keep , so I decided to restore the latest backup. It worked (restore finished 100%) but when I launched the VM, centos crashed at bootup saying that a partition or drive was not found and dropped me to a CLI. The partition or drive that couldn't be found was in fact a logical volume at the node's level assigned to the VM via its .conf file such as
Code:
virtio1: /dev/datastore/datastore, backup=no
Then I deleted older backups of other VM's to free up some space, restored the latest backup of the CentOS machine:
Code:
restore vma archive: vma extract -v -r /var/tmp/vzdumptmp11313.fifo /mnt/backups/dump/vzdump-qemu-101-2014_05_16-20_28_31.vma /var/tmp/vzdumptmp11313
CFG: size: 327 name: qemu-server.conf
DEV: dev_id=1 size: 128849018880 devname: drive-virtio0
CTIME: Fri May 16 20:28:32 2014
Formatting '/var/lib/vz/images/101/vm-101-disk-1.raw', fmt=raw size=128849018880
new volume ID is 'local:101/vm-101-disk-1.raw'
map 'drive-virtio0' to '/var/lib/vz/images/101/vm-101-disk-1.raw' (write zeros = 0)
progress 1% (read 1288503296 bytes, duration 2 sec)
progress 2% (read 2577006592 bytes, duration 5 sec)
progress 3% (read 3865509888 bytes, duration 8 sec)
progress 4% (read 5154013184 bytes, duration 12 sec)
progress 5% (read 6442450944 bytes, duration 15 sec)
progress 6% (read 7730954240 bytes, duration 19 sec)
progress 7% (read 9019457536 bytes, duration 23 sec)
...
progress 92% (read 118541123584 bytes, duration 575 sec)
progress 93% (read 119829626880 bytes, duration 582 sec)
progress 94% (read 121118130176 bytes, duration 590 sec)
progress 95% (read 122406567936 bytes, duration 598 sec)
progress 96% (read 123695071232 bytes, duration 606 sec)
progress 97% (read 124983574528 bytes, duration 614 sec)
progress 98% (read 126272077824 bytes, duration 622 sec)
progress 99% (read 127560581120 bytes, duration 632 sec)
progress 100% (read 128849018880 bytes, duration 642 sec)
total bytes read 128849018880, sparse bytes 17465548800 (13.6%)
space reduction due to 4K zero bocks 0.175%
TASK OK
Then launched the VM again only to see the same error (partition or drive cannot be found). Then I looked in the webgui to see if the missing partition or drive was still assigned to the VM and saw that It was missing!! Then I SSH'd into proxmox node and looked in the .conf file, the drive was commented out! Why??
I uncommented it but didnt help...
What can I do????
Thanks