Latest activity
-
UdoB reacted to Johannes S's post in the thread Way more NAGware, very little functionality, bugs galore with
Like.
If you don't like the nag screen and don't want to contribute to the development ( guess what developers need to pay bills too ) there is an easy fix: Don't use the software. For cross-cluster migration you can also use the pct remote-migrate and... -
Aabufrejoval reacted to leesteken's post in the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device with Like.
Don't run 'apt upgrade' as it might not pull in all dependencies; use the official instructions instead: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#system_software_updates And here is a (another) recent thread where the same problem...
-
Aabufrejoval replied to the thread Incorrect supported CPU flags.I guess you get thrown off by the "amd-ssbd" and the "amd-stibp" flags on Intel CPUs. I just had a look at those flags ony my mixed CPU infra, which includes some Goldmont Intel Atoms as well as Zen3/4/5 hosts and was somewhat thrown off by...
-
jsterr reacted to leesteken's post in the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device with Like.
Don't run 'apt upgrade' as it might not pull in all dependencies; use the official instructions instead: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#system_software_updates And here is a (another) recent thread where the same problem... -
jsterr replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.what about proxmox-boot-tool kernel remove? root@pveneo:~# proxmox-boot-tool kernel E: subcommand is mandatory for 'kernel'. /usr/sbin/proxmox-boot-tool kernel <add|remove> <kernel-version> /usr/sbin/proxmox-boot-tool kernel pin...
-
Aadris replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.No I keep getting the same error message: the /boot directory is full, and that's what's causing the problem. But since this involves a critical phase of the boot process, I don't want to make a mistake.
-
jsterr replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.is a apt autoremove not enough to fix this? did the job on my site a few weeks ago.
-
cwt replied to the thread Way more NAGware, very little functionality, bugs galore.I believe both points are valid to a certain extent. It is entirely reasonable that Proxmox developers are compensated for their work, and subscription models are clearly appropriate for production environments. The concern many users express is... -
Aadris replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.Thanks for your feedback. I'll give this a try. https://forum.proxmox.com/threads/kernel-upgrade-gets-no-space-left-on-device.133050/#post-585964
-
Aabufrejoval replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.I've run across the same issue myself and it's been a bit un-obvious to track down. If I remember correctly, the issue was that it's actually trying to write to the EFI partition via links from /var/tmp, while you wonder why it can't write...
-
JJohannes S replied to the thread Way more NAGware, very little functionality, bugs galore.If you don't like the nag screen and don't want to contribute to the development ( guess what developers need to pay bills too ) there is an easy fix: Don't use the software. For cross-cluster migration you can also use the pct remote-migrate and...
-
Aanarelion replied to the thread 9.2 idmap problem.why not? it works with the default config of 100000 -> 0
-
Ffrankz replied to the thread Kernel error after pihole update.root@pi-hole:~# systemctl status sys-kernel-config.mount ● sys-kernel-config.mount - Kernel Configuration File System Loaded: loaded (/lib/systemd/system/sys-kernel-config.mount; static) Active: failed (Result: exit-code) since Fri...
-
JJohannes S reacted to gyptazy's post in the thread Der Proxday 2026 in Deutschland, Mönchengladbach with Like.
Hey zusammen, gerne möchte ich (einige kennen mich sicherlich bereits von ProxLB, PegaProx und den Ansible Modulen für PVE) euch auf das Community-Event Proxday 2026 aufmerksam machen, der von der credativ GmbH veranstaltet wird. Das Konzept ist...
-
Aadris replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.root@nas:/# ls -al /boot/ total 4026592 drwxr-xr-x 1 root root 2650 May 22 11:57 . drwxr-xr-x 1 root root 186 Jan 31 20:00 .. -rw-r--r-- 1 root root 8940727 Mar 13 09:44 System.map-6.14.11-6-pve -rw-r--r-- 1 root root 8940842 Apr...
-
JJohannes S reacted to shanreich's post in the thread Proxmox Virtual Environment 9.2 available! with Like.
It's BGP unnumbered in particular, it can be used as underlay and works really well with Wireguard as well, or just for announcing routes from EVPN VRFs. It slotted really well into the existing fabrics and in conjunction with upcoming features...
-
Aadris replied to the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device.root@nas:/# dpkg --configure -a dpkg: dependency problems prevent configuration of proxmox-kernel-6.17: proxmox-kernel-6.17 depends on proxmox-kernel-6.17.13-11-pve-signed | proxmox-kernel-6.17.13-11-pve; however: Package...
-
Aadris posted the thread [SOLVED] kernel update fail 6.14 to 7.0 no space left on device in Proxmox VE: Installation and configuration.Hello, I'm having an update issue specifically with the Proxmox kernel. The `apt upgrade` command works for all packages but gets stuck on the Proxmox kernel version. specifically when trying to update from version 6.17.13-11-pve to 7.0.0...
-
JJohannes S reacted to Sviat's post in the thread [TUTORIAL] GuestPilot: lightweight Proxmox guest monitor, WOL listener, and control API in Rust with Like.
Hi, not sure that adding additional service with root permissions make PVE more reliable. A new root-level service with its own mini API, adding another component that could potentially be exploited, misconfigured, or become difficult to...
-
Ddaanw replied to the thread Kernel error after pihole update.At minimum the output of systemctl status sys-kernel-config.mount and systemctl status systemd-journald-audit.socket to have some more info on the failures.