Content of storage drives is not showing up

[dslauter]

I have proxmox installed on a server in our work. Everything was working great for quite a while. I have automatic backups set to happen everyday spaced apart a few hours in the middle of the night. The backups are successful, except when i go to view the contents of either my local storage or my NFS the backups are not present. I don't know what could have caused this, but I need some help fixing it.

this is my pveversion -v


pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-17-pve
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-72
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1

all of your help is greatly appreciated!!

 

[tom]

first, update to latest:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.3

if its still not working, post your storage.cfg (cat /etc/pve/storage.cfg) and a backup log.

 

[dslauter]

first, update to latest:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.3

if its still not working, post your storage.cfg (cat /etc/pve/storage.cfg) and a backup log.

THANK YOU!!! I did the update and everything worked great! Thank you for the amazing customer service Tom!

 

[dslauter]

Hey Tom, that solved the problem. However now the webgui seems to have some flaws. The machines all show that they are off, but they are on. It is also not displaying the names of the machines. If i reinstall pve-manager it will fix it temporarily.

 

[tom]

Hey Tom, that solved the problem. However now the webgui seems to have some flaws. The machines all show that they are off, but they are on. It is also not displaying the names of the machines. If i reinstall pve-manager it will fix it temporarily.

post again your 'pveversion -v'

did you reboot after the update?

 

[dslauter]

Yes sir, i did reboot after the update.

pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-16-pve
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1

 

[tom]

you still have not the all latest packages.

follow this howto:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.3

and compare your package list with the list on that link.

 

[dslauter]

you still have not the all latest packages.

follow this howto:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.3

and compare your package list with the list on that link.

There were three options on the reboot, the one that i tried said i needed to load the kernel before i could boot it. So i went with the other option that loaded right up, I must have chosen the wrong one.

 

[Trimmings]

Fantastic bug, seems to cause backups not to be shown in the restore window.

This has impacted me too so it seems, the backup files should be 'open' for recovery rather than using a proprietary format - it clearly can't be relied on.

Looks like its downtime for updates again.

 

[tom]

Fantastic bug, seems to cause backups not to be shown in the restore window.

This has impacted me too so it seems, the backup files should be 'open' for recovery rather than using a proprietary format - it clearly can't be relied on.

Looks like its downtime for updates again.

which proprietary format? a new format does not mean that it is closed, all is open source.

 

[Trimmings]

which proprietary format? a new format does not mean that it is closed, all is open source.

Open source yes, but it's certainly not using any standard or industry accepted format so it's proprietary. It is not well documented and does not have any tools for manual extraction (requires the proxmox interface).


Since I think you're wondering why this is a problem, it needs a manual extraction method. Recovery of a single file from the drive (host stored in something like raw) is a right pain, it requires restore of the vm completely rather than being able to get the data out via command line/without impacting the vm configurations.

 

[dietmar]

Since I think you're wondering why this is a problem, it needs a manual extraction method. Recovery of a single file from the drive (host stored in something like raw) is a right pain, it requires restore of the vm completely rather than being able to get the data out via command line/without impacting the vm configurations.

The CLI tools is called 'vma' - feel free to send patches if you require additional functionality.