Hi,
I wasn't able to reproduce this on my cluster.
A few questions from my side:
How did this look in the UI? Did you get an error on apply? Where there any pending changes? We didn't deprecate anything in the fabrics yet AFAIK.
You could try...
I've seen only parallel suspends which run into timeout, I use those most of the time.
Attached the log, interesting might be:
May 23 23:26:31 pve pveproxy[1089089]: got inotify poll request in wrong process - disabling inotify
...
May 23...
Example: I unplugged wrong OSD disk, how to reactivate it?
1. Stop OSD process ( systemctl stop ceph-osd@XX ) and unmount OSD dir ( umount /var/lib/ceph/osd/ceph-XX )
2. If OSD use encryption I need to close crypto mapper
cryptsetup close...
Hallo geordi,
leider gibt es keinen offiziellen Weg die Weboberfläche hier anzupassen. Du könntest CSS overrides über deinen Browser probieren, allerdings kann dies bei einem Update leicht kaputt gehen und andere unvorhersehbare Verhaltensweisen...
I'll try to reproduce the issue on my own server.
Aside from pveversion and VM config file, which commands shall I execute and which log files are required?
I remember that the logs, accessible from GUI are very short when hibernation fails...
like I said - this is a global problem the last few months (well, a bit longer now already I guess). anything with dynamic content that basically allows endless possibilities to query (like git forges, forums, ...) are hit particularly hard...
you should be able to enroll the keys using your bios, hopefully. alternatively, deploying your own PK via setup mode should also work, then you can sign all the key/cert updates you want yourself ;)
Are the new shims already available? I asked about this recently:
https://forum.proxmox.com/threads/new-secure-boot-shim-on-proxmox-host.183404/
I did a full update on my proxmox host (now running 9.2.2) and I can see that the shims are still...
Thank you t.lamprecht
Sadly, as janus57 mentioned, currently HP doesn't want to provide BIOS updates.
I'm going to try the recommendation I got to see if I can update the Certs without a BIOS update.
Hi,
Not sure, they ditched old computers (produced in 2018 and before, see https://support.hp.com/us-en/document/ish_13070353-13070429-16), and they will not provide any BIOS update (i know cause we have the issue with Windows instead of...
Hmm, OK, seems like this BIOS signature checking is broken, if you got some time and nerves you might want contact HP w.r.t. this, they are the ones that can help best. We'll look out for any other reports or findings to ensure we did not miss...
In my case I'm just a home labber so not a business using high end or enterprise equipment.
I'm using a HP EliteDesk 800 G1 TWR computer.
This PC doesn't have the 2023 CA keys. Only 2011.
I have another computer, same model, that I had to upgrade...
For now, I think I found the issue. The new shim is signed with both 2011 and 2023 keys and my pc only has the 2011 keys. For some reason my PC is rejecting the shim signed with both keys so I had to remove the 2023 signature. Maybe downgrading...
Now it won't boot unless I disable Secure Boot.
I think it's related to the 2023 CA Keys.
Probably 9.2 is using the 2023 but my BIOS only has the 2011 keys.
systemctl stop pve-cluster corosync
pmxcfs -l
rm /etc/corosync/*
rm /etc/pve/corosync.conf
killall pmxcfs
systemctl start pve-cluster
Was the way in Proxmox VE 6
https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node
Here it is again
Please use code blocks to preserve formatting and don't censor so much and needlessly. Using local for virtual disks is a bad idea too (IMHO).
Try to start the CT like this to get more information
lxc-start -n 101 -F -l DEBUG
Also try to enable...
What do your EFI partitions look like?
If it works sporadically maybe you have duplicate IDs and/or one of EFI partitions didn't update correctly.
Can you run:
cat /etc/kernel/proxmox-boot-uuids
lsblk -f |grep vfat