Recent content by t0mz

I kept on getting an access denied message from BIOS and no boot drive was found. Long story short, if you get the same error, disable secure boot in the VMs bios and off you go.

Looks like it didn't make it into PBS v3.2 either? I need to do something about this and am considering setting up either a dedicated server/VM/LXC and have PBS access the backup drives over the network or in case performance doesn't work out stop using PBS for the time being.

Thanks both of you. I also found this thread by now, https://forum.proxmox.com/threads/random-6-8-4-2-pve-kernel-crashes.145760/page-2 and changed GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=off" Also installed kernel 6.5 via apt install pve-kernel-6.5 and created a MemTest USB stick which I...

For a while now I am dealing with frequent kernel crashes, sometimes twice within minutes, sometimes once every 2 weeks. Couldn't really pin it down but was getting severe filesystem errors (BTRFS) which now look like they are an effect of the crashes not the actual issue. I replaced the NVME...

Very pleased to read. Have been sifting through todays 40k proxmox-backup-proxy entries this morning again :-/

Is there any chance that this https://forum.proxmox.com/threads/enhancement-suggestion-log-levels.130080/ is addressed with this "bigger scope"?

I'd like to suggest adding log levels to PBS because the default is completely spamming my journal with what seems to be rather useless information? I got only 3 clients hitting PBS which led to 21574 lines of "successfully added chunk" while the whole journal for today is just 25877 entries. I...

Great, that makes sense. /var/lib/pve-cluster/config.db is the file in question, right? Given that my db is small, I will add /etc/pve so it's easier to get to individual files. Thank you for your prompt response!

Sorry for bringing this one back from the death. But I am currently preparing for my upgrade to PVE 8.0 and one requirement as stated in https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 is to backup all files in /etc/pve. Now I just realized that my host backup has skipped /etc/pve ever since I...

I am making my first steps with PVE on a btrfs filesystem. When trying to set up a backup location it appears that @ in a file path is not accepted. I get the following error: illegal path for directory storage: /media/raid/@data2/backup (500) While not a requirement, @ is often used to signify...

I came to the conclusion that I am not yet ready to migrate over to PVE. I think need to wait for virtiofsd support. My showstopper is 4TB of Nextcloud data. Without virtiofsd support the only way I think I can make this work, is by creating a 4TB VM or add a 4TB raw disk to the VM. And then...

Ah, that's it. /boot is VFAT all the way down to /boot/EFI. I can't really remember why though. This server used to be on GRUB, later converted to Sytemd-Boot and, aside from daily :) kernel updates, I haven't touched this part of the system for the last 4 years or so.

Yup, I know, but wasn't sure if PVE maybe does something unusual here :) The log file is still around and I am happy to share. You can find those errors at the very end of the log. ln: failed to create hard link '/boot/initrd.img-6.1.15-1-pve.dpkg-bak' => '/boot/initrd.img-6.1.15-1-pve'...

So far so good. Migration worked, dual boot is working and PVE is up and running. There were some error messages during kernel install and setting up of proxmox-boot-tool related to not being able to create a link, which makes sense given that my ESP is vfat. Next step is to figure out how to...

I see, this is very helpful! From your output I can see that most of what the tool is doing is already there, except these two: Created EFI boot entry "Linux Boot Manager". Adding '/dev/nvme0n1p2' to list of synced ESPs.. I keep copies of the ESP so I can happily play around with things, as...