Search results

That usually is not a problem - as TLS in SMTP is opportunistic - if your downstream/backend mailserver does not advertise STATTLS PMG should simply transfer the mails without TLS. If you run into problems - please share the logs - then we might be able to help...

hm - there were a few posts about mismatched grub stages after an upgrade ... I'd check if you can look through the ESP (EFI service partition) and try the proxmox/shim / proxmox/grub or BOOTX64.efi entries on them - most UEFIs have an option to select these... (maybe that's what Super Grub2...

Thanks - will try reproducing it with the 8.0 ISO - afaics it's a single disk system? yeah it's not the most straight-forward to read - but it does contain the most information - and in that case it points us to the issue with your system: This system is booted via proxmox-boot-tool, running...

Do you remember when the breaking systems were initially setup? - there were changes to how booting is handled for btrfs installs during PVE 8.0 - so it would help to know which ones make problems for you. * Are those UEFI or legacy BIOS setups? * RAID configuration or single-disk installs...

Do the guests in question have a RNG device configured? (see the changelog for PVE 8.4 - UEFI PXE boot needs on in recent versions : https://pve.proxmox.com/wiki/Roadmap#8.4-known-issues)

Thanks for the reminder about this thread! both the pve8to9 check and our recommendation have changed (since I suggested to keep systemd-boot installed). Currently you should uninstall the package if you don't need it (no root on ZFS with uefi) - and install the meta package in all cases after...

The check was adapted in the mean time to deal with that situation: https://lore.proxmox.com/all/175466070754.625540.12444949078147201723.b4-ty@proxmox.com/T/#u (the current recommendation is to remove the systemd-boot meta-package after upgrading - and ensuring that `efibootmgr -v` points to a...

Thanks that does sound quite sensible indeed! - I tried adapting the docs accordingly: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Systemd-boot_meta-package_changes_the_bootloader_configuration_automatically_and_should_be_uninstalled

in this case it's not mounted, because you have ZFS on `/` and use proxmox-boot-tool for managing the boot-loader :) (similarly for pve-root and swap(on ZFS no swap is created) on systems installed on ext4+lvm-thin it needs to be mounted. I hope this helps!

just to be on the safe side - you mean /etc/sysctl.conf? theoretically yes - but see the man page sysctl.d(5): `It is recommended to prefix all filenames with a two-digit number and a dash, to simplify the ordering of the files` - so maybe `71-local.conf` I hope this helps!

Thanks! hm - not sure how grub deals with /boot/efi being a mdraid - I'd suggest: * checking `efibootmgr -v` * ensureing that bootx64.efi (a.k.a removable grub entry) gets updated as well: echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u *...

see https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Prerequisites: (that is before changing the sources to trixie - you should install all pending updates) I hope this helps!

hm - was sagt denn `journalctl -b -u systemd-modules-load.service` ? und bitte auch `journalctl -b` durchschauen ob fehler reported werden

not necessarily - the only thing that is odd about it as far as I can see is that you have both: * using proxmox-boot-tool for booting (ZFS system on legacy boot) * one of the ESPs mounted at /boot/efi (on a legacy boot system!) I'd recomment removing the fstab entry of /boot/efi - as...

that sounds odd (should not happen with our usual setups) - please share: * `proxmox-boot-tool status` * `mount |grep efi` (thanks for sharing the term.log!)

8 Months ago should have been bookworm - thanks for the info! Could you (and others affected by grub not booting after upgrade) - also share: grep grub /var/log/apt/term.log (unless your term.log has been rotated after the upgrade in which case please use the rotated variant which contains...

thanks - which version did you start with? any other specifics how this was setup? this would also help narrowing this down - s a stock debian bookworm system here has shimx64.efi as configured boot-entry and not grubx64.efi as in your case.

good find regarding the mismatch of grubx64.efi - how was this system setup? * proxmox VE ISO or on top of debian? * when was it setup ? (debian version PVE version)? This should help us in reproducing the issue. Thanks!

Yes Yes - because you're still on PVE-8 (bookworm) - I thought that the following part should explain that: which is also why the pve8to9 script does not warn you before upgrading to pve-9 (trixie): I will warn you after upgrading to 9 (at that point the system will have...

Yes your assumption is correct - removing the sytemd-boot meta-package is what we recommend - the patch for pbs3to4 was just a tad to late for the ISO today: https://lore.proxmox.com/pbs-devel/20250806114909.2143258-1-s.ivanov@proxmox.com/T/#u I hope this helps!