Recent content by jolly

To follow up on this turned out to be some weird hardware issue, if I move the same disks and put them in a different machine it works perfectly. This is despite me switching ports, cables, power supply, fully testing memory..m

If I connect only the OS disk and the ZFSWD disk, copy /etc/pve/qemu-server/ over, and do a zpool import -f ZFSWD, that sorta works, but 192.168.40.100 Mar 3 21:45:38 pve daemon err pvedaemon[1890] storage 'ZFSWD' does not exist 192.168.40.100 Mar 3 21:45:38 pve...

I can't blacklist ZFS as my VM drive "ZFSWD" uses ZFS. There is no raid as far as I can tell, I'm not sure where it's picking this up from. Bios says AHCI, not raid mode. The new proxmox install def did not have any raid setup. I can't copy /etc/pve/qemu-server directly, since that only...

Hi, thanks again for your help. The server had been running for two years without incident. The core proxmox install consists of: 1 128gig SSD for proxmox to boot from - Toshiba. I believe this is the md127 device, I think I used to have it in a raid config. If memory is right, it was raided...

I believe I passed through the two disks to truenas, and then had truenas create the storage pool - which is why it says 1x mirror 2 wide. I don't think I ever created a linux mdadm raid array, which is why I was surprised to get that e-mail. Unless thats just how proxmox interprets the...

I'm quite confused trying to recover my proxmox install, and would greatly appreciate any assistance. The server is mostly unresponsive. I've reinstalled Proxmox, (to a new different ssd) which worked fine, but if I try restoring config.db and reboot, it immediately gives the same sort of...

Jun 29 20:19:21 192.168.40.100 pve daemon err pvestatd[3624] authkey rotation error: cfs-lock 'authkey' error: got lock request timeout Jun 29 20:19:21 192.168.40.100 pve daemon info pvestatd[3624] status update time (9.954 seconds) Jun 29 20:19:26...

I'm having a weird issue, where sometimes proxmox will refuse to let me log in. The VM's are running fine. If I hard reboot the node, I can log in just fine. This is the second time it's happened, so I'm pretty confused.

Can you enable thin provisioning on PVE or only on Proxmox backup server? I'm looking at datacenter-storage, and the zfs pools but cant find an option to enable thin provisioning

Why does proxmox write a lot to the OS disk? I was expecting minimal use after install, and was planning on using an old SATA drive to boot, and NVME for vm storage.

I'm having the exact same issue installing, with a 3090. Unfortunately I do not have a different video card I can use.