Recent content by Kevo

On my motherboard I also have to use the downstream patch otherwise the sata controller gets lumped with the Ethernet controllers. Could be something else for your specific situation, but maybe it’s something common which should be in the wiki setup steps so check that if you haven’t already.

I ran into this today after updating. Found this thread about ROM-Bar and had high hopes, but it didn't work. After typing up a plea for help in this thread, but before hitting post I thought maybe I should just double check everything so people don't have to go through a bunch of initial...

Secure boot is not in use. The main server was installed in late June or early July of 2023. The original server which is now the backup that I upgraded was installed in June of 2021. It had a cpu failure in June of 23 and that's when we got the new server. After we got an RMA CPU we repaired...

I've checked a handful of servers, combination of intel and amd and every one, all installed from USB of the Proxmox ISO, all respond like this to the 'proxmox-boot-tool status': Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. E: /etc/kernel/proxmox-boot-uuids does...

I checked. It does not appear to have ever been installed. I couldn't find it on either machine. It appears to have been an artifact from an earlier install and incomplete install/fix of the grub-efi-amd64 package. On our backup server 'grub-efi-amd64 grub2/force_efi_extra_removable' was set to...

You might try turning on csm and legacy boot in BIOS to see if you can get it booted that way. If that works, check this thread. https://forum.proxmox.com/threads/help-with-uefi-boot-issue-after-pve-9-upgrade.169796/

The two links I posted explain most of it, but you will probably have to do a bit of further research based on your particular circumstances. I'd suggest reading through that first link and checking how things match up on your system. Depending on what you find you may need to investigate what...

I managed to get a screen recording of the failed boot and I saw the welcome to grub banner right before it went into bios. Hunting around I found this thread. https://forum.proxmox.com/threads/stuck-on-welcome-to-grub-after-update.164133/ That led to more searching and I found this page which...

After upgrading to PVE9 our backup server (hardware copy of main server which gets VM backups rsynced to it) would not boot. I managed to get it back by changing the BIOS CSM to enabled, enabling legacy boot, and setting the boot drive to the non-uefi entry in the boot priorities list. After...

I had a similar experience today on a remote backup server. Luckily I had IPMI on this one and logged in and found it booted into BIOS. After fiddling around for a while I enabled CSM and Legacy boot and changed the boot drive to use the non-UEFI entry and got it booted. I still need to figure...

Updated two test servers to 9.0 with no issues. Updated my main server which we use for internet, email, etc and it booted back up, but complained of an error activating pve/data. Had to run lvconvert --repair pve/data to get it back up and running. Not sure if it had anything to do with it, but...

The 8.2.6 update fixed the issue for me. No problem with the backups running early this morning.

I also have this problem. I think I'm just going to do manual backups for a few days to see if the fix comes out. I only have 2 machines running the latest patches, so only a handful of backups need to be done.

You might try the latest 6.5 kernel. I think problems started in 6.8, but search and check. I am not using thunderbolt so my problems with 6.8 were different. The latest 6.8 is working for my issues, but I had to stick with 6.5 for a while due to issues in 6.8.

I believe there was at least one or two other threads related to thunderbolt issues on the 6.8 kernel. It's not something that affects me so I'm not up on it, but you might want to search for the other threads to see if there is anything useful there. I think downgrading the kernel and waiting...