Show us the configuration of the faulty machine and the working machine. You can call it with the command
qm config 103.
And additionally how storage cat /etc/pve/storage.cfg is configured. Maybe something could be deduced by comparing.
The messages indicate that the machine's disk is located on a shared NFS share. Is the storage on this NFS visible and accessible from the node on which you are making the backup?
your ssd is at /dev/nvme0n1
smart
4 Start_Stop_Count 0x0012 098 098 000 Old_age Always - 3247
Maybe a bit too many start/stop events. Unless it's some kind of energy saving. Possibly check the cables and power supply of this disk. It's possible that there are...
Where virtual machine images are stored is defined by the configuration in the /etc/pve/storage.cfg file
and you probably have local-zfs content images,rootdir there.
Your command looks correct to me.
Please revmove fingerprint from you answer, at forum, it you security.
Yor machine are at local-lvm, type thinpool. Example VM declare 200G, data on this 1G. Real data is 1G
If you transfer from local-lvm to VMS (storage directory type) real data is 200G
/vms what mount at this?
You need to...
The directory storage do not support thin provisioning.
Look at this https://pve.proxmox.com/wiki/Storage
Show your configuration of storage
cat /etc/pve/storage.cfg
It seems to me that some device may be accessing the same IP address that Proxmox has. If this happens, start examining the ARP table to see if the MAC address from this table matches the Proxmox host address. If possible, show your network configuration from the /etc/network/interfaces file
If I had the option of putting in just one SSD, I would do it as a cache and not think too much about it. I don't see any particular disadvantages of this solution.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.