Great!
My own one was decommissioned last year. Finally, after (nearly) 15 years. Basically because I have much better gear for PVE now... and PBS is really hard to make it fly on such an old thing.
Have fun!
How to check if systemd-boot is being used — and how to safely remove it
Step 1: Check which bootloader is in use
(if it is grub for example it is saffe to remove systemd-boot)
Run the following command to inspect your current EFI boot...
I don't know where to give feature ideas for PROXMOX but I think it'd be really nice to when looking at images/isos/backups in the storage tab of a PROXMOX node to have the file path listed somewhere. I generally just use the GUI for everything...
Hey man, as today, i'm running one of this in my homelab (3 node cluster)! Yesterday i update to pve9 - i'm happy with this ultra-low energy choice. BTW, works for me too! ;)
solved it on my own:
as the entry
Boot0002* proxmox HD(2,GPT,a0e229a8-843d-4bdd-89f3-a9529fecbf35,0x800,0x200000)/File(\EFI\PROXMOX\GRUBX64.EFI)
is showing GRUB as bootloader, it should be save to delete 'systemd-boot'.
Therefore I did...
Could you try to capture a backtrace of the hanging state with lldb instead of gdb and send it via DM to @Chris ?
lldb -b -o 'bt all' -o quit -p $(pidof proxmox-backup-proxy) > proxy.backtrace
We already found a potential issue but would like...
My main unit is up 24/7 and I currently I do manual backups from time to time to my ZFS raid-z2 pool with cheap disks (which are also on my main machine). I never thought of setting up PBS as LXC on my Proxmox, but it sounds like an interesting...
They claim it doesn't mess with the network. So now I have no idea what could have caused this to happen because that's the only thing I can recall doing
We run a single nightly backup job to back up all of our VMs. At least one node every night will get stuck on a VM for hours and will sit there indefinitely until we cancel the job (and all other VMs that weren't backed up yet will not be done...
Die Beta 2 ist da. Neu wird unter anderem auch RHEL unterstützt (getestet mit dnf copr enable derenderkeks/proxmox-backup-client && dnf install proxmox-backup-client) sowie verschiedene weitere Anpassungen und Korrekturen umgesetzt.
No, you apparently have 2 EFI partitions configured, probably a mirrored disk setup.
Mount both EFI partitions:
mkdir /mnt/efi1 /mnt/efi2
mount /dev/disk/by-uuid/A437-70EE /mnt/efi1
mount /dev/disk/by-uuid/A438-D2C2 /mnt/efi2
Remove the old 6.*...
root@nas:/# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
A437-70EE is configured with: uefi (versions: 6.17.13-11-pve, 6.17.13-6-pve, 7.0.0-3-pve...
Can you post the output of the following commands?
ip a
Can you try reloading the network configuration via the following command and paste the full output?
ifreload -avd
Does anything odd pop up in the journal?
journalctl -u...
YES - it was as simple as that. apt install dbus && systemctl start dbus
So, I do NOT understand how this package can be missing. ok, my container is quite old (2021) made some upgrades ... even some major ones from 8 to 9.
Thanks a lot.