Search results

Hi Chris, thanks for responding :) yes I did run pve5to6 and I had 0 failures. I did get a few warnings (eg using ip adresses instead of names as ring0_addr and having a 2 node cluster). root@nb-pve1:~# apt update && apt list --upgradable Get:1 http://security.debian.org buster/updates...

my ceph.list deb http://download.proxmox.com/debian/ceph-octopus buster main NOTE: I know that I made an error here and it shoud been ceph-luminous. I don't have ceph installed.

my apt sources.list deb http://ftp.nl.debian.org/debian buster main contrib # security updates deb http://security.debian.org buster/security main contrib # PVE pve-no-subscription repository provided by proxmox.com, # NOT recommended for production use deb...

Hello, I wanted to upgrade an old 2 node system to current specs. One node was v4 andt the other v5. The plan is to make both nodes v7. Updating as per proxmox wiki the update from v4 to v5 went fine. Also updating to Corosync 3 was a breeze. One of the nodes updated from v5 to v6 but the one...

7 months later and still no solution, makes me wonder why I pay for support.

Yes it was possible, have done this many times.

You still need help with this? I had the same issue and figured out the solution. I my case the logical volumes (the raw disks) where activated on the physical partition of my disk instead of the drbd device (/dev/sdb1 instead of /dev/drbd0).