Search results

Our ceph.conf [global] auth client required = cephx auth cluster required = cephx auth service required = cephx cluster network = xx fsid = aef995d0-0244-4a65-8b8a-2e75740b4cbb # keyring = /etc/pve/priv/$cluster.$name.keyring mon allow pool delete = true...

Hi, till last Wednesday we had a cute high performing litte CEPH cluster running on PVE 6.4. Then i started the upgrade to Octopus as given in https://pve.proxmox.com/wiki/Ceph_Nautilus_to_Octopus. Since we did an online upgrade, we stopped the autoconvert with ceph config set osd...

We managed a successful migration by uplinking the 40GE Switches to the old 10GE Storage VLAN and then moving each host's IP from the 10GE NIC to the 40GE NIC

Thanks, right now they are in seperate vlans. routed L3 communication should be sufficient no? What i understand is, if mon1 will be migrated to the new subnet but can still talk (via TCP) to the other mons, i should be fine?

Hi, we are in the following productive situation 5 x PVE CEPH Storage with 2x1GE NIC and 1 x dual 10GE NIC (LACP) for the CEPH public network 5 x PVE Compute Nodes with 2x1GE NIC and 2 x dual 10GE NIC (LACP), one is for the CEPH public network 2 x MLAG/LACP connected 10GE Switches (Lenovo, low...

[SOLVED]: Another update : after upgrading RAM and adapting the so Called NPS Settings in the BIOS (https://downloads.dell.com/manuals/common/dellemc-balanced-memory-2ndgen-amd-epyc-poweredge.pdf) We ended up with a "balanced" NUMA setup. Since then at least the login console (mgag200 loads...

Next update to the issue : proxmox 6.4 install on top of debian works, but the console output does not as soon as the PVE kernel 5.4.114-1 gets installed and booted. blindly logging into the non-responding console and running commans works as well as logging in via SSH! The error is still [...

Short update to the issue : debian buster 10.9 installs without any issue, i guess i can go on from here

Thanks Stoiko, - the patching of the initrd was for debug purposes only to figure out the root of the problem. - the kernel config issue is not the problem, both, the fedora 34 as well as the default pve kernel do not have CONFIG_X86_SYSFB=y set - mgag200.nomodeset=0 parameter did not help i...

after patching the initrd, adding all modules and booting it into a shell i found the following error while inserting the mgag200 module mgag200 0000:62:00.0: [drm] *ERROR* can't reserve VRAM another last try was to simply boot the default 6.4 installer and log everything to the serial console...

i guess this is the reason for the non-working rescue shell on the serial console in debug mode (init script from initrd) debugsh() { setsid sh -c '/bin/sh </dev/tty1 >/dev/tty1 2>&1' }

i just double-checked with my Fedora Install, the console itself seems to work Fedora 34 (Server Edition) Kernel 5.11.20-300.fc34.x86_64 on an x86_64 (ttyS0) Web console: https://fedora:9090/ or https://xxx:9090/ fedora login: root Password: Last login: Wed May 19 19:35:14 from xxx...

you are right, its not, i copied the kernel and the initrd out and tried a manual boot. so, i attached the virtual com port now and can see the full boot log (attached). but in debug mode it tells me i'm in a shell but when i type commands, they do not get executed. comparing the boot log to...

Booting the PVE 5.11 Kernel with earlycon=efifb gives me (a horribly slow) console and shows the kernel output. but at the end it disables the bootconsole efifb0 and im stuck (or rather blind) again ...

btw, @Stoiko Ivanov : the double post is a result of a fail of the forum while hitting the post button

Stoiko, thanks for the quick response! just tried that verision but it gets stuck as well. the Virtual Disk does not load anymore but no output on the bootloader ... please let me know if i can be of any help to debug the issue

Hi, we just got our brand new Baby from Dell, a R6525 with a Dual Epyc 7543 (Milan) set of CPU's. Since it will become part of our PVE cluster, i tried to install Proxmox 6.3 on it without success, the same with Proxmox 6.4. The system gets stuck after the boot message, at least nothing...

Hi, we just got our brand new Baby from Dell, a R6525 with a Dual Epyc 7543 (Milan) set of CPU's. Since it will become part of our PVE cluster, i tried to install Proxmox 6.3 on it without success, the same with Proxmox 6.4. The system gets stuck after the boot message, at least nothing...