Hello,
I was moving the proxmox to a new arrays from ZFS powered backend. I am now running on LVM-Thin on top of an Adaptec-7805 card with ZMM/BBU.
When i was restoring our old zimbra installation i was hit with this bug. The previous installation was Proxmox-ve 5.0 some version i am not sure about. I have 5 backups all worthless, because the backup is missing the partition table for the drives. I was able to restore backup with testdisk, rewrite partitions, activate lvm, redo grub and fix the failed backup from within, but that never happened before. I am able to provide the failed backup file (it has about 50 gigs, but ill send it only in private message, because its mailserver backup i dont want to spread that over the internet).
I am also able to provide any logs you wish.
I have a proxmox-ve standalone server running
I was moving the proxmox to a new arrays from ZFS powered backend. I am now running on LVM-Thin on top of an Adaptec-7805 card with ZMM/BBU.
When i was restoring our old zimbra installation i was hit with this bug. The previous installation was Proxmox-ve 5.0 some version i am not sure about. I have 5 backups all worthless, because the backup is missing the partition table for the drives. I was able to restore backup with testdisk, rewrite partitions, activate lvm, redo grub and fix the failed backup from within, but that never happened before. I am able to provide the failed backup file (it has about 50 gigs, but ill send it only in private message, because its mailserver backup i dont want to spread that over the internet).
I am also able to provide any logs you wish.
Code:
root@proxmox:~# cat /etc/pve/qemu-server/1050.conf
boot: c
bootdisk: sata0
cores: 4
ide2: none,media=cdrom
memory: 8192
name: mail.bolicek.cz
net0: e1000=02:6D:F0:DF:81:B2,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
sata0: local-lvm:vm-1050-disk-1,size=50G
smbios1: uuid=929f825a-7f6b-4057-972f-167e1f648b4c
sockets: 1I have a proxmox-ve standalone server running
Code:
root@proxmox:~# pveversion -v
proxmox-ve: 5.1-31 (running kernel: 4.13.13-1-pve)
pve-manager: 5.1-40 (running version: 5.1-40/ea05b379)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.13.13-1-pve: 4.13.13-31
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9