Proxmox doesn't like the Kaby Lake Xeon's with integrated graphics. A lot of random freezes with blank screens with no errors. After disabling integrated graphics in the BIOS everything worked fine. Only two whole nights of debugging (eventually I got a error to work with).
I tried proxmox 4.1...
I have exactly the same problem on my nodes with PVE4 and DRBD9. Not even after cloning alone, even after a reboot of the last node.
Node 1 and 2 say: everything uptodate
Node 3 says: some disks outtodate.
Do you have a solution already? I tried several times drbdadm adjust all but it doesn't...
I'm going to reboot the server in about a week because there are running some customers from those VM's.
The strange thing is that the disks of the running VM's are still shown in /dev/pve. After a shutdown of one of the running VMs they also don't want to boot up anymore.
When I run 'drbdmanage list-nodes' on my fresh proxmox drbd9 install I get this:
root@node1:~# drbdmanage list-nodes
+------------------------------------------------------------------------------+
| Name | Pool Size | Pool Free | Site | | State |...
Why? A stupid dedicated server provider who didn't do their job.
root@RCLL001:~# pvs
root@RCLL001:~# pvscan
No matching physical volumes found
root@RCLL001:~# vgscan
Reading all physical volumes. This may take a while...
No volume groups found
root@RCLL001:~# grep filter...
I need help with the following thing: We had a two node cluster with drbd and Proxmox 3.4. It worked fine until our second node failed. Because we were already transffering to a new cluster we took the disks out of the second node and let if offline. But after a while the node became active...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.