Search results

Backups ran last night and it happened again. Can anyone please help?

Yes, all vm's have it. LZO compression and Snapshot mode Underlying storage for the VM's are ZFS on 4k block NVMe drives. (see attached screenshots)

# pveversion pve-manager/6.1-3/37248ce6 (running kernel: 5.3.10-1-pve) I can't seem to figure out why this is happening, but every time our backups run, the vm's that were backed up come back up with read-only filesystems and I have to restore form the backup to get them working again. This is...

I have verified 100% that the port on the switch this is connected to is correct I have replaced the cable (even though there were no errors on the switch - just in case) Both the switch and the server (ethtool) say the port is ip When the cable is unplugged, both the server and the switch show...

Anyone? I could really use some help here. Our cluster is still down.

Nothing there. Nothing in dmesg either.

Anyone out there?

I can't figure out why this is happening. I have 3 servers and all can ping the backend cluster vlan except for the primary The primary - 192.168.29.14 can ping all other nodes on their other vlans: vlan 29 - cluster comms - no ping vlan 28 - works vlan 10 - works As a result, the cluster won't...

I ran into this problem today. It is a symlink issue and my proxmox server are up to date. This fixed it: find /mnt/pve/SOMEMOUNT -type l ! -exec test -e {} \; -print If any results show there, it means there's a broken symlink. Remove it and all will be well.

Hi Tom, is there a link to documentation for this new method?

Working server (pve4): cartman:/volume1/proxmox on /mnt/pve/cartman type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.16.28.2,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=10.16.28.2) pve5 server...

dmesg says: [Tue Apr 9 10:45:01 2019] nfs: server cartman not responding, timed out [Tue Apr 9 10:45:01 2019] nfs: server cartman not responding, timed out [Tue Apr 9 10:45:07 2019] nfs: server cartman not responding, timed out [Tue Apr 9 10:45:07 2019] nfs: server cartman not responding...

Which version should it be in once released?

/mnt/pve/cartman does exist on all nodes, but on pve5, I can't `ls` or `df` because it's hung. if I `umount -l` and then mount it from the shell using `mount -t nfs cartman:/volume1/proxmox /mnt/pve/cartman`, it mounts and works in the shell, but not in the gui. Storage config: root@pve5 [~]...

Everything has been working until I made some changes on the network, but now I don't know what I messed up :( If I remove the NFS share for all nodes and re-add it, all nodes except one (name is pve5) map it fine. On pve 5, I see this in the logs: Apr 8 15:25:02 pve5 pvestatd[3411]: unable...

Ah, ok. Is there a release data set for that yet?

I've successfully set up a cloudinit image, but in the GUI, there doesn't seem to be a way to use a `runcmd` to install software after a cloned image boots up. Is there some way to do something like: runcmd: - apt install qemu-guest-agent

I fixed it. I can't even begin to imagine how this happened. But the fix was: apt purge cloud-init Then I restored the /etc/hosts file from a backup and rebooted and it came up. In 20+ years of IT, this is easily the strangest thing I've seen.

##################### # FSTAB ##################### # <file system> <mount point> <type> <options> <dump> <pass> /dev/pve/root / ext4 errors=remount-ro 0 1 #/dev/pve/swap none swap sw 0 0 proc /proc proc defaults 0 0 /dev/sdb1 /mnt/disk2 ext4 errors=continue,noatime 0 0...

I sure would look like that, but I did not. That cloudinit was created within the PVE Admin UI. I remember doing it months ago to experiment with that feature. Never did anything in the shell for that.