Search results

Hello this is a english speaking forum, plöease post in english. There are multiple reasons why a PVE system could shut down / reboot. Is this a cluster or single-node system? Have you checked your logs (journalctl)? Is network stable? Any errors on the server/ipmi/bmc?

Why would you prefer broadcast mode over frr or routed setup? Why are you needing open-v switch for your ceph meshed network?

Please post your firewall-rules in your security-group so people have the possibility to check it out in more detail. Did you put the security-group on a specific level (datacenter / host / vm)-level?

Your VM-100-Disk-2 is raw, and is only allowed to be qcow2. Seems like a vTPM-disk. I personally also did not set "Use LUNs directly" not sure, if its a requirement though.

Ill add my forum-post to this list: https://forum.proxmox.com/threads/pve-9-beta-pve-nested-upgrade-from-8-to-9-breaks-boot.168662

I just tested the PVE-8 to PVE-9 Upgrade on a freshly installed PVE-8 Installation (Nested, VM) so not on physical hardware. After upgrading and rebooting, the VM does not boot anymore and goes to VM-BIOS. Thats the proxmox-boot-tool status output before rebooting: root@pve-2:~#...

After upgrading to the beta, I get an error on all my vms regarding cloudinit + also for my ct, that are on a lvm-thin pool. all vms and ct cant start: TASK ERROR: activating LV 'pve/vm-103-cloudinit' failed: Check of pool pve/data failed (status:64). Manual repair required! TASK ERROR...

The wiki-post says: How to do that? running apt policy seems not to be the full command? Might be useful adding an example on howto check. Also apt update brings up the following, might be related to check seeing if the new repo-format is used or not. My sources.list still contains pvetest...

Yes thats it! Thanks, it was not much of a problem I outed them manually. At least we know now why that happened, thanks!

I know but it does not rebuild but should

Hi I tested a scenario with 5 pveceph nodes: * 5 PVE-CEPH nodes * 4 OSDs per node * 5 Ceph MON * SIZE 3 / MINSIZE 2 If I shutoff one of the 5 pveceph nodes, ceph will automatically recover after 10 minutes and sets osds down & out. everythings green again. After shutting of another one, ceph...

Yes, Immich works fine, im running it on a homeserver.

Is this still valid in 2025. Can we somehow show accepts as well?

You can define what network(s) should be used for ceph-public and ceph-cluster network. This has nothing to do with where your proxmox ve managment-ip is configured. if you want to limit the web-ui access, check: https://pve.proxmox.com/pve-docs/pveproxy.8.html#pveproxy_host_acls

Have you tried not to tag the virtual adapter, afaik if you do so, you can then and must tag INSIDE the vm (os) to actually get vlans working.

Just know that if you wanna using a fc storage with proxmox ve, you cant snapshot vms and ct that are placed on fc-based storage-luns. https://pve.proxmox.com/wiki/Storage

Hello, I would recommend testing this in a virtual pve enviroment first! At first, you need to assign a different device class to the 5 different osds. like hdd-2 for example. Then create two custom crush rules for the setup, as the default crush-rule takes all hosts/osds in consideration. After...

https://www.thomas-krenn.com/de/wiki/Proxmox_Node_aus_Cluster_entfernen_und_erneut_hinzuf%C3%BCgen might use translation of your browser, this is a step by step tutorial.

I cant see any problem, you should be able to loose 2 nodes without interrupting vms that are NOT running on those 2 now offline nodes. 8.1d1 1204 0 0 0 302431820 0 0 2629 3000 active+clean 11m 34115'48729 34298:60681...

Thanks and also: ceph osd pool ls detail