I have been running server 2012 on a proxmox version 3.2-1 for a couple of years. My employee who set it up has left and now I am supporting with sporadic experience with linux and Proxmox.
Friday our server crashed and after lookinginto it I saw that Proxmox was reporting ecc errors. I purchased new memory and restarted the proxmox node. (single node system) The server tried to come up, showed as running and occasional shares would appear. It looked to me like the ecc errors probably grew the event log to a point that the system drive filled and would no longer would run. None of my remote tools worked and of course the java based console wouldn't work either. after spending a lot of time trying to get the java console running, I gave p and decided to build a 2nd server and backup and restore the VM's. The backup server is running version 4.2-2. After 7 hours of restore it failed and exited with an exit cone of 133. Any assistance with this would be greatly appreciated.
** (process:3779): ERROR **: restore failed - vma bdrv_flush drive-virtio3 failed
/bin/bash: line 1: 3778 Done lzop -d -c /mnt/backup2TB/dump/vzdump-qemu-100-2016_06_05-19_34_36.vma.lzo
3779 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp3776.fifo - /var/tmp/vzdumptmp3776
Logical volume "vm-100-disk-3" successfully removed
temporary volume 'local-lvm:vm-100-disk-3' sucessfuly removed
Logical volume "vm-100-disk-4" successfully removed
temporary volume 'local-lvm:vm-100-disk-4' sucessfuly removed
Logical volume "vm-100-disk-2" successfully removed
temporary volume 'local-lvm:vm-100-disk-2' sucessfuly removed
Logical volume "vm-100-disk-1" successfully removed
temporary volume 'local-lvm:vm-100-disk-1' sucessfuly removed
TASK ERROR: command 'lzop -d -c /mnt/backup2TB/dump/vzdump-qemu-100-2016_06_05-19_34_36.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp3776.fifo - /var/tmp/vzdumptmp3776' failed: exit code 133
Friday our server crashed and after lookinginto it I saw that Proxmox was reporting ecc errors. I purchased new memory and restarted the proxmox node. (single node system) The server tried to come up, showed as running and occasional shares would appear. It looked to me like the ecc errors probably grew the event log to a point that the system drive filled and would no longer would run. None of my remote tools worked and of course the java based console wouldn't work either. after spending a lot of time trying to get the java console running, I gave p and decided to build a 2nd server and backup and restore the VM's. The backup server is running version 4.2-2. After 7 hours of restore it failed and exited with an exit cone of 133. Any assistance with this would be greatly appreciated.
** (process:3779): ERROR **: restore failed - vma bdrv_flush drive-virtio3 failed
/bin/bash: line 1: 3778 Done lzop -d -c /mnt/backup2TB/dump/vzdump-qemu-100-2016_06_05-19_34_36.vma.lzo
3779 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp3776.fifo - /var/tmp/vzdumptmp3776
Logical volume "vm-100-disk-3" successfully removed
temporary volume 'local-lvm:vm-100-disk-3' sucessfuly removed
Logical volume "vm-100-disk-4" successfully removed
temporary volume 'local-lvm:vm-100-disk-4' sucessfuly removed
Logical volume "vm-100-disk-2" successfully removed
temporary volume 'local-lvm:vm-100-disk-2' sucessfuly removed
Logical volume "vm-100-disk-1" successfully removed
temporary volume 'local-lvm:vm-100-disk-1' sucessfuly removed
TASK ERROR: command 'lzop -d -c /mnt/backup2TB/dump/vzdump-qemu-100-2016_06_05-19_34_36.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp3776.fifo - /var/tmp/vzdumptmp3776' failed: exit code 133