Recent content by Ramalama

Its a raid1 (2 disks). Youre absolutely right, i seen this Message in other Servers and simply unmounted /boot/efi... The Problem ist Just, on such big Upgrades where you Upgrade 600 packages, you wont See the log and simply reboot :) And bam, you have to recover with the iso xD Ist there...

You are only wrong in one Point, that you didnt fixed the key issue, why it falls, instead you simply excluded the Volume. Otherwise i agreed with everything else. Lxc backups are terrible. Zfs send/receive ist truly amazing, but no GUI... So its Not a solution for "Not Linux affine" admins in...

But i found another pretty hefty Bug: If a backup runs, the snapshot of an LXC container gets created always under /mnt/vzsnap0 So in the case like above, where the snapshot wont get removed, and the directory not deleted (because of the error), all following lxc backups will fail in that...

Found the issue. rm -rf /Storage-Default/subvol-180-disk-0/opt/kerio/* -> Fixed it. The root disk (the mountpoint of it, was not empty. In my Case there were whyever empy folders, dunno why, maybe from beginning before i created a subvolume to that mountpoint inside the container... But for...

Found the issue. rm -rf /Storage-Default/subvol-180-disk-0/opt/kerio/* -> Fixed it. The root disk (the mountpoint of it, was not empty. In my Case there were whyever empy folders, dunno why, maybe from beginning before i created a subvolume to that mountpoint inside the container... But for...

INFO: Starting Backup of VM 180 (lxc) INFO: Backup started at 2025-08-12 04:17:21 INFO: status = running INFO: CT Name: mail INFO: including mount point rootfs ('/') in backup INFO: including mount point mp0 ('/opt/kerio') in backup INFO: backup mode: snapshot INFO: ionice priority: 7 INFO...

Hi with PBS 4, there is an issue with backup'ing running LXC Containers. When the Container is Running, i get this: {{guestname}} INFO: starting new backup job: vzdump 180 --notes-template '{{guestname}}' --notification-mode notification-system --storage Backup-SAS --remove 0 --mode snapshot...

lol, thank you, so easy :-)

Sorry for the late reply, yes uefi+secure boot. I Installed the Server on 10.Okt.2023 at 16:09:27, with Kernel 6.2.16-3, Debian 12.2.0-14 (Thats info from the oldest boot log) So it was the Proxmox 8.0 ISO. there is maybe broken text in the term.log -> that was the ncurses window, which asks...

@t.lamprecht ./find-old-packages2.sh cpufrequtils libaio1:amd64 libapt-pkg6.0:amd64 libassuan0:amd64 libcbor0.8:amd64 libcpufreq0 libflac12:amd64 libfmt9:amd64 libfuse3-3:amd64 libglib2.0-0:amd64 libglusterd0:amd64 libicu72:amd64 libldap-2.5-0:amd64 libmagic1:amd64 libpcre3:amd64...

Hi Thomas, its sadly not fixed for btrfs root systems still. Im just upgrading all Servers to PVE9 and only those on btrfs fail. Cheers

Okay i have a solution, was actually pretty easy: 1. Download the Proxmox VE 9 ISO (Or 8) and mount it either with your KVM/Ipmi or make an USB-Drive 2. Boot from it and select "Install Proxmox VE (Graphical, Debug Mode)" -> Press CTRL+D when it asks... 3. Check your partitions: lsblk -o...

Same with btrfs as root Filesystem. I Blacklist by Default the zfs modules, since i dont need zfs in my Home Servers... Im on the Minisforum MS-02 which doesnt have legacy boot / csm sadly. Now i have to find Out how i can fix the bootloader :-)

Thats sad, then i have to dig further for the issue :-)

@t.lamprecht Can you maybe include this fix in the 6.14 Kernel: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?id=bc0b828ef6e5 i Stumbled on one Server against this, with an I219-LM that i passthrough to opnsense (Its a hetzner Server). Its only an issue on Kernel 6.14...