Search results

When i have more time i will rewrite the whole post so it reflects all expeciences and gives a full documentation which (should) reflect a one-shot install without issues , including the setup of the shared LVM volumes.

Ok tested the reinstall of the last node (Node04) and changed a bit in the order in which i performed it. Just to be sure i always pull the connection to the shared storage to never make a mistake in overwriting so i always perform a local installation ! Basically as soon as i install / switch...

Again i reinstalled another node (node03) whilst changing out the local disks ... install went fine, but again it joined the cluster , but somehow PVE kept complaining on wiating on Quorum, somehow it kept thinking it needed 4 votes, i ended up setting it to 1 on the newly added node ( pvecm...

I have reinstalled Node #1 according to the https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster (after i had pulled out the SAS connection to the MSA2040, to be absolutely sure i would not overwrite anything on the shared storage) docks provided, then set up my dlm, lvmlockd...

i had the reverse a few days before, i killed a LUN on my storage which held the disk of a CT , trying to delete it gave the 'error unable to find storage xxxxx' and the CT remained what i bluntly did was go into /etc/pve/lxc and delete the *.conf file ... PVE picked it up and removed the CT...

Seems i have solved my 'kernel-panic'ing on Node 04 , i still had the debian kernel available on the system, i removed it, as mentioned in the https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster as optional. Then restarted it ( ofc a panic came up) and then wanted to record the...

Are you willing to try a debian-install and moving to PVE6 after ? .. as i am using this type of install for all my PVE machines (4) in a cluster-setup , and i have not faced the issues you are experiencing, next to the fact that i feel more 'in control' when installing PVE and configuring it...

Been playing around a bit more, the behaviour of the newly installed node04 ( the one i directly installed with Buster and switched to Pve6 after) is still kernel-paniccing when issueing a reboot.... i have freed up a 2nd node to play with ( node03 ) which is a upgraded node ( jessie/Pve5 to...

Not saying it should'nt work, but when i setup the cluster i did it all over commandline - following https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_create_cluster last node i (re-)added was one i took out cause of disk-replacements and reinstalled it on Deb 10 , then switched to Pve 6.x ...

Strange behaviour found: As in my previous post i am now facing kernel-panics when issueing a 'reboot' on the one node where i tested/gone thu the whole setup. Whereas i am facing other issues on a 2nd node whilst implementing this .. it hangs on shutdown/reboot on shutting down the lockmanager...

Been running a 4-node cluster now without huge problems for over 1.5 years, just the perils i usually create myself. And till now with help of the docs / forums i've alway been able to get it all back to a 'nice and tidy' state.

check the following : - on the node you are trying to 'create the cluster' run : pvecm nodes from commandline/console session If this returns information the node you are trying to create the cluster on already is acting like a member of a previous attempt to create a cluster. To be quick on...

Hello, Just a question : - when you upgraded, did you run the prerequisite script 'pve5to6' and if yes did it reveal/show any issues ?

Update : Seems that this configuration somehow upsets dlm. Every time i now reboot the node ( as i did a few times) it generates a panic Sep 2 22:39:39 node04 kernel: [ 1828.032673] dlm_controld[11954]: segfault at 0 ip 00007f13d2006206 sp 00007ffe68835a08 error 4 in...

Another bit of progression ... To define the shared LV's and their mountpoints i created /etc/lvm/lvmshared.conf /dev/cluster02/backups:/data/backups The one thing that (at the moment) still is a catch is the file should not contain a carriage return ! After that i started working on a...

Made some progress, basically i found out that lvmlockd (by running it in debug mode) tries to retrieve lock information from dlm , and if dlm is not available it 'assumes' it is the master and starts its own lockspace ignoring an already exisiting lockspace on the other remaining clusternodes...

Hi all, I've been working on setting up my MSA2040 (SAS) to be available in more then just sharing a raw LVM due to the fact that offering a raw lvm only supports diskimages and containers. The idea was to also have (shared) storage (directory)presented to pve for backup/snippets/templates (...

Then this means the filter i had set on the NFS storage in the PVE webinterface to backups only is not honored by the underlying process. imho by setting that it _should_ also have restricted the search for disks in those places. i have had the storage shared like this for a long time, only...

Situation : - 3 standalone nodes with VM's on XFS storage - No Shared storage. - NFS shares on all 3 nodes to eachother to restore backup files from one node to the other. (added as NFS storage, with backup files only selected in PVE) Task : - Introduce new node and setup first cluster node...

Just as a comparison i re-installed the machine with the Debian Jessie version from scratch ( as it was not functioning anyways i have room to play) Hardware : DL380 Generation 5 2x Quad core cpu / 32M ram Yes i know its out-dated hardware, still its more then sufficient for my needs :)...