Search results

That's a, it depends. You will need to check all endpoints of your workload/connection to see where it might be stuck.

See our documentation on the storage types. There you will find which storage supports snapshots. https://pve.proxmox.com/pve-docs/chapter-pvesm.html

Probably the partition table of the VM got defect. Depending of how it was setup, you might be able to recovery from a backup partition table. https://wiki.archlinux.org/index.php/GPT_fdisk#Recover_GPT_header

This is a ¯\_(ツ)_/¯. It could have been a multitude of things. Always hard to tell afterwards.

PVE 6.3 has acme support with a good portion of provider APIs. Namecheap is among them. So I don't quite understand what preparation you want to do.

It is as seen in the restore. You will need to install the vma binary on the nfs itself if you want to extract it directly. Then you need to handle the config files manually

The values, like S/N can be queried with smartctl. And /dev/disk/by-path/ might also have the slot id. Feature requests can be added on our bugzilla. https://bugzilla.proxmox.com/

I don't question that, besides the document doesn't talk about a use-case. ;) But it doesn't make it easier either. Since the connection check can't be reliably done.

No, not really. Since the rpcbind is not running, a simple connection check can't be done. You will need to mount the share and configure a directory storage on top (use option is_mountpoint). Or run rpcbind in the container. https://pve.proxmox.com/pve-docs/pvesm.1.html

Best go through our and Ceph's docs to see the hardware recommendations. Maybe it sheds more light. :) https://pve.proxmox.com/pve-docs/chapter-pveceph.html https://docs.ceph.com/en/nautilus/start/hardware-recommendations/

Did you try to mount it manually on the Proxmox VE? EDIT: for the showmount, I send a patch onto the pve-devel list. https://lists.proxmox.com/pipermail/pve-devel/2020-December/046508.html

The RFC states otherwise. https://tools.ietf.org/html/rfc7530#section-1.4 ~:# rpcinfo -t vm19180 nfs 4 program 100003 version 4 ready and waiting And this is a debian VM with an NFSv4 only server. Can the port 2049 reached, at least? EDIT: though, you are correct. showmount doesn't work with...

Hm... not much. :) rpcinfo -u <server> nfs 3 rpcinfo -t <server> nfs 4 And what do the commands show?

What message do you get with pvesm status? And is there something in the logs?

ashift is autodetect and volblocksize is 8K. Both are the default values.

Please in English, otherwise it will be hard for all non-Chinese speaking people. ;)

And don't do this. Each storage will degrade the performance of the other. Aside from side effects that get introduced.

Did you sync the hardware clock (hwclock) with the time of the node? And is the timezone correct, timedatectl?

The mac address usually changes when cloning a VM. It seems there is some misconfiguration in your DHCP (range, lease time,...).

Well, as the package name might already suggests, it is for qemu (VMs). It will do nothing in a container.