Search results

No idea, but please put the output of pveversion -v. If you are not using the latest packages (as it seems from your previous posts/video), troubleshooting is almost impossible, and insist in doing setups with outdated/bugged packages is not a good way to go either. Before doing anything, just...

Disable hardware checksum offload http://pve.proxmox.com/wiki/PfSense_Guest_Notes

As suggested in the wiki (is about pfSense), you have to “Disable hardware checksum offload” (System > Advanced > Networking). http://pve.proxmox.com/wiki/PfSense_Guest_Notes

I have it :) root@proxmox:~# ls -l /etc/default/grub -rw-r--r-- 1 root root 1279 Aug 19 2015 /etc/default/grub

I've seen your vide, the probmem OMHO is that you did not ugraded your installation, so you have very old/broken packages. You should have issued an apt-get dist-upgrade after the apt-get update (see http://pve.proxmox.com/wiki/Downloads )

I've no idea, just a guess: a) are you sure you ssh as root from EACH server into ALL THE OTHER servers? (i.e. from node1 ssh into node 2 and 3, from node2 into node 1 and 3, from node3 into node 1 and 2) b) are you sure you have issued the command "drbdmanage add-node" ONLY AND ALWAYS from node1?

I've seen that ZFS as local storage for qcow2 images (and maybe for whatever file based else) is not a good idea, better follow the wiki and create a dedicated pool for volumes (like zfs create rpool/zfsdisks and then Datacenter -> [Storage] -> Add, ZFS, as "ZFS Pool" select "rpool/zfsdisks"...

A bug report has already been issues some days ago https://bugzilla.proxmox.com/show_bug.cgi?id=895 is just a "display" error, the setting is correct in config file, but don't know if will be overwrite if you change something else in that dialog, so let's hope will be fixed soon :)

Wondering if not installing the package thin-provisioning-tools would have got the same effect. In short, thin provisioning seems badly broken at the moment, better avoid it

You always have to fight to migrate vms (I've asked multiple times to be able to do it through GUI, search the forum), you have to "mv" config files in the cluster path of the surviving server, having the quorum or not. Without quorum you just have, in addition, to manually force it to 1 to be...

I've a 3 node cluster, 2 nodes with drbd9 storage (I cross my fingers...), and the 3° is a cheap Mitac Pluto E220 with a small mSata ssd and 8GB of RAM. The only drawback so far is that if you buy enterprise repository access, the key for the cheap node must also be included in the purcase.

What if you plug to a PC with Gbit nic? Maybe is a switch fault...

Wondering if 9.0.1 (and utils 8.9.6) can solve some of the above problems, seems that the "thin" thing is just supported there: http://www.gossamer-threads.com/lists/drbd/announce/27742 but maybe this thread is interesting too http://www.gossamer-threads.com/lists/drbd/users/27722

Sigh, I've the same issue, see my unasnwered posts of yesterday: https://forum.proxmox.com/threads/restored-vm-on-thin-provisioned-drbd9-storage-is-no-more-thin.26165/ https://forum.proxmox.com/threads/drbd9-replication-is-not-thin-on-replicated-node.26169/ I'm really scared with all this...