Search results

Hey , I wonder you re mixing many thinvs in one, and forgot steps. You re sayi g you ve only 1 public ip adress. Well, you cannot use vmbr0 for any orher VM, EXCEPT THAT YOU TAKE ANOTHER IP PUBLIC @ dedicated to thia VM ( with a /32 submask) What are you really want to do? If pfsense need to...

Hum, great :) We're not wizards.... Where're screenshots / cfg screens / log extracts??

Hum.... maybe use this bond in vmbr for try??

maybe more details /screens/cfg running? We re not wirards...

Unload ipv6.

Hi, Go to proxmox shell, and tr, a zpool import -a.

Hi, Did you simply authorised the ct to do cifs mount ? (Do that via option ct tab )

Hi, Just go to the "options" tab of your win VM, and set qemu-agent yes....

Hi, This is not a proxmox VE related question. You just need to follow the network standarda and all gonna be good themselve. OR, you wanna create a cluster between yours proxmox, and then another kind of solution are available IF you have good hardware material between them

Hi, Check with only 1 socket activated. I think you need to enable numa with this kind of VM with more than 1 socket processor

Pve hosts in cluster mode? Or standalone?

Hey, Primilarly, it s seems (for me) an network load error WHEN real load for compression /bckp/filetranfrt rate. Can you launch a glances monitoring in your proxmox host when your lxc container is loaded by bacula ? If you have a big io-wait, all explained by this :) ( process paused while io...

Hey, Check permissions of your nextcloud service user and permissions on your mountpoint :)

Hey, Update your defaut grub timeout of 6 at 8 sec, and it gonna do the job ;) (Not working ? Increase more time :) it s hardware initializing time prblm )

Hey, How did you have declared yours pbs on yours two nodes? 1 or 2 declarations in datastore view?

Hey, You readen me too fast x'D You need to do this thing in your /etc/fstab file ;) Don t forguet the space between mountpoint and filesystem type ;)

Hey, it doesn't seem's to be a proxmox bug ... Private me if you wanna a little bit help on your situation. I prevent, i answer only in english ^^

Hey, Did you tried to stop your cluster, and reboot 3 node first ? see if quorum come back. If yes, continue to boot one by one yours node, with a small delay between to node booting. For each booted node, check if quorum staying alive

Hey, Your problem isn't clear... In your Proxmox VM configuration (gui or cli), what did you have on declared disks ?

Hey, on one of your screenshots, i only see two of your four drives bugging. Check your IOMMU groups, and see whos ssd are connected on 0000:80:03:1 and 0000:80:03:2 If you can check the output more descrively, verify if output screen give that on 0000:80:03:0 and 0000:80:03:3 (or 0000:80:03:4...