This should be fixed now with the latest repository state with proxmox-kernel-helper package in version 9.0.2.
Basically there was a reinit of the proxmox-boot-tool missing when the grub/shim update got pulled in by the major update, thus causing...
Usually the most important feature to look for is the PLP (Power Loss Protection) so ssd-cache does not get lost on power-failure. This ssd according to google has power loss protection. I personally dont have experience with Kingston SSDs.
I'll have to take another closer look tomorrow - since it seems like the FRR change detection failed. Is it possible you had a PVE 8 and a PVE 9 instance clustered and applied the SDN configuration from the PVE 8 host?
I think that might...
UPDATE: it turns out that the gateway was not correct, I stupidly copied the broadcast of my subnetwork instead. Now I changed it and everything looks fine. Thank you anyway to everyone for such impressive reactivity !
Thanks we changed nic1 to fit the mac, rebootet and also changed frr.
This is how my /etc/frr/daemons file looks like, should all the lines with "yes" be switched to "no" and then systemctl restart frr?
root@PMX7:~# cat /etc/frr/daemons
# This...
What's the content of /usr/local/lib/systemd/network?
listing + contents of the files.
FRR seems to be an issue when upgrading from 8 to 9 - I'll look into it more closely.
*With pinning where a NIC is then not being created/detected, lets please avoid overly generic/misleading error description - and let's check that out in your dedicated thread.
1. We do not have ip-communication on all vms and ct since upgrading to pve9 (cant reach 10.26.0.1)
-- untouched pve8.4.5 clusters work well on the same subnet including their vms/ct
2. the same lan works well on the pve-hosts itself (they can...
Possible issue: after using nic-naming-tool no ip-communication inside vms and ct via vmbr0 since upgrade to pve9 (test-cluster)
I did made a new post, because it seems to be a lot to post here...
I can confirm at a customers site, where I just made a test restore: yeah - roughly 10x improvement in restore speed ! That is so nice to see :)
THANK YOU @kaliszad !
PBS is now kicking it, finally !
It would be awesome if some great soul would...
It does not. At least not under every circumstance. There's zero guarantee that you will get that second copy done to any OSD: if the primary OSD fails/breaks/can't reach/whatever and/or the secondary OSD is unable to write the data and before...
Using more than one OSD per drive allowed to workaround internal processing limits in the OSD services themselves. Your Intel P4610 aren't the fastest drives ever, so chances are that you won't hit those limits. With recent versions of Ceph this...
proxmox does generate a whitelist, you can check it via "pve-firewall localnet". Host on that Subnet are automatically allowed for 22/8006 and some other ports aswell.
Hard to tell, I cant remember If I had set that option before. Might be the case, so I overwrote the LVM.conf by confirming it with "yes" on upgrade-question.
Good that you were able to fix this! I ran a quick upgrade test with an overprovisioned LVM-thin with and without running the migration script pre-upgrade, and didn't see this issue. Could it be the case that the custom thin_check_options had...
We normally focus on those configs that get asked for even if the admin did not make any local changes.
I still added a hint for now, the section is not that crowded yet so it doesn't really hurt. As noted in the hint it'd be best to move your...