Stoiko Ivanov's latest activity
-
Stoiko Ivanov replied to the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi..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... -
Stoiko Ivanov replied to the thread 2 warnings in pve8to9 check.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...
-
Stoiko Ivanov replied to the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi..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...
-
Stoiko Ivanov replied to the thread Proxmox Virtual Environment 9.0 released!.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!
-
Stoiko Ivanov reacted to jackbutton93's post in the thread First kernel update after upgrading 7.4 to 8.1 failing: /var/tmp/espmounts/... mounted read-only with
Like.
For anyone still looking for a solution, my /boot/EFI partition had some corruption. Running an fsck and fixing the errors on the partition resolved this for me. -
Stoiko Ivanov reacted to Stephan4711's post in the thread [SOLVED] FAIL: systemd unit 'pvescheduler.service' is in state 'inactive' with Like.
Ich war scheinbar zu ungeduldig nach dem boot. Erneut den Test durchgeführt, jetzt ist der scheduler geladen
-
Stoiko Ivanov replied to the thread Failed to start systemd-modules-load.service.hm - was sagt denn `journalctl -b -u systemd-modules-load.service` ? und bitte auch `journalctl -b` durchschauen ob fehler reported werden
-
Stoiko Ivanov replied to the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi..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...
-
Stoiko Ivanov reacted to Rapiere's post in the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi. with Like.
it looks like I could eventually fix it as I force-reinstalled grub-efi-amd64 which was broken during upgrade process. Phew ! Thanks for your assistance !
-
Stoiko Ivanov reacted to fabian's post in the thread [SOLVED] Grub-install error while upgrading from Proxmox 8 to 9 with Like.
it sounds like you are booting from the removable boot loader entry, and did not update that one, so now there is a mismatch between the first part of grub and the rest of grub on the ESP.. could you post the output of "efibootmgr -v" (from a...
-
Stoiko Ivanov replied to the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi..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!)
-
Stoiko Ivanov replied to the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi..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...
-
Stoiko Ivanov replied to the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi..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.
-
Stoiko Ivanov replied to the thread Upgrading from Proxmox 8 to 9 issues; Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi..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!
-
Stoiko Ivanov replied to the thread Proxmox Virtual Environment 9.0 released!.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...
-
Stoiko Ivanov replied to the thread Proxmox Backup Server 4.0 released!.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...
-
Stoiko Ivanov replied to the thread Proxmox Backup Server 4.0 released!.Thanks for the report! fixed that (and looked in the page for other mentions of pve this time)
-
Just a heads up, there are some references to pve filenames rather than pbs filenames in the repository sections - under both codeblock sections, listing: /etc/apt/sources.list.d/pve-enterprise.list & /etc/apt/sources-list.d/pve-install-repo.list
-
Solution is hier: https://forum.proxmox.com/threads/proxmox-virtual-environment-9-0-released.169258/post-788653
-
Hi, if you are on Proxmox VE 9 (based on Debian 13), you should not run the kernel for Proxmox VE 8 (based on Debian 12, the bpo12 means the package was backported for Debian 12). Also make sure the proxmox-default-headers package is installed.