As obviously many users before me, I'm having trouble getting read/write access from a container to a zfspool. I have read through many of the posts concerning this topic both here within the forum and also on the internet. I've been following...
Following this, skipped memory tests pressing space to speed up the boot
Immediately spam ESC in virtual keyboard on idrac (20+ clicks)
Server inits firmware interfaces as it would normally
Server collects inventory etc as it would normally
No...
Thanks, I tried out removing quiet and adding nomodeset and attached picture right before the server reboots with the CPU 1 Machine Check error with the updated settings.
Yessss thank you for your advice.
All went OK. Update is finished and PVE 9.1.9 is running.
All my containers and vms are running again without problems.
Thank you all very much!
Hallo,
ich bin neu hier im Forum und bitte schon mal um Nachsicht von den Admins hier, falls ich nicht im richtigen Forum schreibe.
Außerdem bitte ich darum, dass sich Leute die besser englisch sprechen als ich, das Thema wenn erforderlich in der...
Yes I found this to be the case as well, Win 11 would update automatically but Server 2022 or earlier will need the reg key changed and wait 12 hours + reboot
Hmm on a WIN2019 Server I have an issue.
I updatred the efi-disk (The test "EFI disk without 'ms-cert=2023k' option, suggesting that not all UEFI 2023
certificates from Microsoft are enrolled yet. ..." is gone)
I then did the upper mentioned...
Well.., without more details it is difficult to say something.
There should be a boot menu before that message. There should be a "boot previous kernel" option.
Please post more details...
I think I met the same isseu like yours, all VMs are running with maximum cpu, then make host run with maximum cpu, it make the pve machine unstable, I have to pin 6.17 as boot kernel.
And I have another pve machine with 3090 GPU, the GPU cannot...
Well.., without more details it is difficult to say something.
There should be a boot menu before that message. There should be a "boot previous kernel" option.
Please post more details...
Hello everyone,
I am stuck in a difficult situation:
Server is running current and up-to-date Proxmox.
It is a LVM on LUKS on a fake hardware Raid (Intel Raid Controller) on a Supermicro Motherboard.
I upgraded the BIOS and failed to preserve...