Search results

Update: Now (15:55) I can now only open the GUI on one node. Login fails on the others. From the node I can log into, all other nodes are showing with a '?' If I actually click on them, after a long delay, they do show the content, but I occasionally get connection errors. There's no change to...

I've just brought up a new node with ZFS as its store. I updated it and then added it to an existing cluster. I did see an error about "unable to create directory /etc/pve/nodes" but it was fleeting and I didn't get to capture it properly. The other nodes are all OK, and all nodes report that...

Thanks. I did that, but a different problem has occured. I'll open a new thread as the symptoms are different.

I have a 4-node cluster where one of the nodes has dropped out. The contents of /etc/pve/corosync.config on the failed node differs from the other nodes, pve-cluster.service is reporting errors and corosync.service fails. Any ideas on how to resolve this? root@pve5:~# systemctl status...

DOH!

I have a number of qemu and lxc "vms" running on a PVE 7 host. Another node in the cluster is running PBS to backup said qemus and lxc. I now want to add an LXC that uses a bind-mount to another ZFS dataset outside of PVE (so that the data can be shared by more than one lxc). I can't see how...

I finally got it working, though I'm still not sure what it was that I did to fix it. It may have been that booted into a linux live usb and resetting both SSDs back to being ex-factory state, but more likely it was that I disabled legacy boot in the BIOS so that I had to boot the USB in EUFI...

Did you ever resolve this? I have a very similar problem installing Proxmox ZFS on a T5810

Thanks for that, @dcsapak. You're right of course. At some point the bios changed - no idea when.

I had a running 7.1 server in a cluster with 3 VMS running. This afternoon, I needed to reboot the server and it failed, saying it couldn't find any boot disks. It's Dell T 5810 and configured to use EUFI with 2 x 1TB SSDs. After a lot of faffing about and finding I couldn't boot from USB...

agent: 1 balloon: 2048 boot: order=ide0;sata0 cores: 4 efidisk0: local-lvm:vm-102-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M hostpci0: 0000:03:00 ide0: local:iso/VeeamRecoveryMedia_DESKTOP-VGN663M.iso,media=cdrom,size=685568K ide2: local:iso/virtio-win.iso,media=cdrom,size=543390K machine...

I have a daily backup job running across two nodes with 5 VMs - a mix of LCX and QEMU. One VM is failing, a QEMU running Windows 10. The job fails on the efidisk (it usaes efi because I'm passing through PCI cards) Any ideas?

Did you resolve this? I am having the same shutdown problem if I connect a USB3 drive so I can use Time Machine.