Search results

Yes, but the error message in question is about memory management (pfn = page frame number) so an issue with RAM is more likely here imo.

Sounds like it given the multiple power outages, but without proper diagnostics it's hard to tell for certain.

You should do a memtest to see if your memory is still working properly.

Well, the roadmap mentions this specifically: The idea being, that this is different from the host backups you can create with proxmox-backup-client already. So yeah, restoring a cluster config and integrating backup and restore on the PVE side will likely be part of this project.

It is on our roadmap already [1]. :) [1]: https://pbs.proxmox.com/wiki/index.php/Roadmap

Well there is the self-generated web ui certificate, but those aren't automatically trusted as they are self-signed anyway. So most things in the stack rely on the fingerprints of certificates rather then expiry dates. Ther are also the apt key's but they are valid for ten years or so for each...

Das klingt so, als hättee die IP auf der das PMG läuft keine Reputation die genug für t-online.de ist. Sprich der Mailserver von t-online.de geht davon aus, dass es sich bei dem PMG um ein nicht vertrauenswürdiges System handelt und verweigert die Annahme von Mails. Eventuell kann eine...

looking through the code superficially, nothing obvious comes up, beside this. however, i'm not an expert on how these serial numbers are supposed to be used, so i don't want to say anything definitive about whether this is an issue on the OEMs side or not. even if that's a faulty...

yes mirroring the debian repositories is also possible, the setup wizzard even has options to simplify setting that up. not directly no, apt will simply use the latest packages it finds. however, you can use different medias that you sync with specific snapshots to approximate that [2]. [2]...

one option would be to laverage POM and it's snapshots [1]. you could simply take a snapshot, update your dev cluster from it and then once you consider that stable enough use the same snapshot to update your production cluster. [1]: https://pom.proxmox.com/

hm yeah, this seems to be an exception to an unwritten rule kind of situation. anyway, i send a patch that should fix this [1]. [1]: https://lore.proxmox.com/pve-devel/20250312083819.15379-1-s.sterz@proxmox.com/T/#u

can you post the full output of udevadm info -p /sys/block/nvme0n1 --query all? the regex in question does seem to expect there to be no leading spaces [1]. however, there also needs to be a leading E:, that is missing from your output too. [1]...

I am not sure why this can't be incorporated into a PBS setup, do you have a specific reason why you can't use a local PBS for that? Either a machine or even a VM could work. You could use a removable datastore, ifyou need to be able to detach the media sometimes [1]. [1]...

The installer complains about a checksum issue. This indicates that the installer was probably not downloaded correctly or the file was corrupted in some other way. You should try to download the ISO from here again [1]. And if it happens again, try to verify the ISO by following this guide [2]...

Hey, have you tried the opt-in 6.11 kernel [1]? [1]: https://forum.proxmox.com/threads/opt-in-linux-6-11-kernel-for-proxmox-ve-8-available-on-test-no-subscription.156818/

No, they won't be restarted automatically, that would be the point of HA. So if you don't use HA for your guests, they won't be restarted automatically. You still have a distributed file system with redundancy. So you can manually restart the VMs without starting the missing node again. It also...

Hey, yeah, the regex gets “anchored” by PMG. Meaning that it always adds a “^” at the beginning and a “$” at the end. “^” matches the beginning of a line and “$” matches the end of a line. So the regex you provide matches a string that starts with “@schimmel” followed by an arbitrary character...

Well if you want proper fault tolerance of a node, I'd highly recommend three nodes as a three node cluster can handle the loss of a single node much better. Both in-terms of the way that Corosync clustering works and also, because the HA resources can be distributed better. Think of it this...

Hallo, hast du den Upgrade Guide zu 8 gut durchgelesen und die Schritte dort befolgt [1]? Sonst fällt in dem Screenshot auf, dass das aktive Proxmox Repo noch das für bullseye, also Proxmox VE 7 ist. Bitte dieses deaktivieren und das für bookworm aktivieren. Sonst kann das Upgrade nicht...

Hi, since you are hosting Proxmox VE on top of Virtualbox, the most likely cause to me here, would be that Virtualbox does not pass through some necessary extension to PVE. Since the screenshot is in Russian, not sure if I can help you much further there, though.