TLDR; This is an excellent go-through the requirements of corosync-tuning for larger clusters by @fweber (which is in fact part of linked thread by @bbgeek17)
You could use pve-zsync but it doesn't allow auto-failover aka HA:
https://pve.proxmox.com/wiki/PVE-zsync
So you would need to launch the vms on your offsite cluster manually in case of a failover event.
The Datacenter-Manager doesn't have it...
I tried a basic install of PBS 4.1 and PVE 9.1 on both a Fujitsu Futro S920 (AMD GX-222GC, mSata) and S940 (Intel J5005, Sata SSD) with default options. All installations fail on first boot with this kernel panic:
Unable to mount root FS on...
Glad that cleared up your question!
For completeness sake - and if someone runs into this thread in the future - you can upgrade your subscription to a higher level in our shop quite easily...
Hi,
have you tried seeing if there are firmware upgrades (both for the controller and the UEFI/system firmware itself) available?
That often can already help, having these on the latest firmware.
You can also try to see if stock Debian 13 boots...
just to not misunderstand something - do you mean a Community level subscription, instead of a Basic Level Subscription? https://www.proxmox.com/en/products/proxmox-mail-gateway/pricing
Your posts mixes the terminology (license, subscription...
You could use pve-zsync but it doesn't allow auto-failover aka HA:
https://pve.proxmox.com/wiki/PVE-zsync
So you would need to launch the vms on your offsite cluster manually in case of a failover event.
The Datacenter-Manager doesn't have it...
hey
I was very happy to read your discussions.
There's a post here : proxmox-unprivileged-lxc-coral-usb.md explaining how to deal with coral usb in unpriviledged mode LXC.
Works like a charm on my Proxmox / LXC Frigate.
Hope this may help anyone...
Hi all !
Even if I know that there is more than 1 way to do it, here is a way that worked for me. Please note that since it was on a POC I found it useful to use self signed certificate, don't do this on production cluster ;)
apt install...
I rebooted the server after fixing the max sizes and just before doing the CLI test.
The DKIM test is OK, there's no issue with it (so says the test I made using CLI).
I think there's something broken in my SA (but don't know what.
I eventually...
Das möchte ich unterstreichen. Diese verlinkte Anleitung auf Youtube ist ja wirklicher Unsinn...
Ja, ich verzweifle wirklich. Können junge Menschen geschriebenes nicht mehr verstehen, dass man sich alles nur noch von irgendwelchen Dumpfnasen...
I saw that but didn't think it pertained to this particular problem o_O
Thank you very much for pointing it out. I have changed it to Header now and after restarting the pmgspamreport.service, I am no longer seeing those errors. I will check on...
Check how your unbound resolves the dkim with dig or something vs external dns
dig @127.0.0.1 TXT dkim._domainkey.domain.com
dig @8.8.4.4 TXT dkim._domainkey.domain.com
Try flushing the DNS.
unbound-control flush_zone .
or
unbound-control flush
Your cpupower frequency-info output on the R740 is the key here:
no or unknown cpufreq driver is active on this CPU
Your working R730 has intel_cpufreq with the performance governor. The R740 has no frequency scaling driver at all. So the Xeon...
Interwebs say this happens when the on-disk block size is going from 4k source to 512b destination.
Is reformatting the destination volume a possibility?
Noch was zu großen Clustern und was man dann ggf. an den Corosync-Einstellungen anpassen muss:
https://forum.proxmox.com/threads/proxmox-with-48-nodes.174684/post-825826
Hi @Chris
This message:
2025-05-12T13:39:01-03:00: warning: unable to access non-existent chunk 780f82546e91812e1b1c04815c2afbf73ad963bc99650502b8c2b379093e3407, required by...