Recent content by vincent2

Same issue here, pinning the 6.5.13-5-pve kernel ( proxmox-boot-tool kernel pin 6.5.13-5-pve ) is indeed a (temporary) workaround for this issue.

Managed to isolate this issue down the the Intel integrated iGPU passthrough to a VM. Removing that configuration boots everything just fine in 6.8.8-2-pve for me. Same issue as reported here: https://forum.proxmox.com/threads/proxmox-8-2-kernel-6-8-breaks-igpu-passthrough-for-uhd630.146256/

Thanks for the suggestion @pschneider1968 , will report it at https://bugzilla.proxmox.com/. I saw this kernel bug report that looks very similar also https://forum.proxmox.com/threads/kernel-bug-kernel-null-pointer-dereference-address-0000000000000000.149342/ However, 6.8.8-2-pve fixes this...

Hi, I've upgraded (dist-upgrade) to PVE 8.2.4 today that comes with kernel 6.8.8-2-pve. After a reboot that I always perform after PVE dist-upgrade, PVE didn't come back up. I hooked it up to my TV (HDMI) and noticed that the only messages visible were: Booting Proxmox VE GNU/Linux Loading...

I think it must be grub version 2.06-13: root@pve:~# grub-install --version grub-install.real (GRUB) 2.06-13 root@pve:~# dpkg -l | grep grub | grep ii ii grub-common 2.06-13 amd64 GRand Unified Bootloader (common files) ii...

I'm away from the machine, and I don't have any out-of-bounds access to pre-OS consoles/output. I'll share the grub version when I get back. This is a dump of tail -c 4096 /tmp/lvmdump/metadata/sda3 thin_pool = "data" transaction_id = 121 device_id = 44 } } vm-9100-cloudinit { id =...

This is an upgrade from PVE 7 to 8 indeed. Sure, output below: root@pve:~# vgs -S vg_name=pve -o vg_mda_size VMdaSize 1020.00k root@pve:~# vgscan -vvv 2>&1| grep "Found metadata" Found metadata summary on /dev/sda3 at 20480 size 12624 for VG pve Found metadata seqno 943 in mda1 on...

Yeah, it runs on a Samsung 870.

Thanks for sharing your experience. I do think the risk of re-surfacing is higher when I reboot PVE every day (instead of keeping it up 24/7)…

Hi, I suffered from the same issue this morning. I shutdown PVE around midnight and start it in the morning again (rtcwake). I didn't touch PVE the day(s) before. Fortunately the steps over at Recovering from grub "disk not found" error when booting from LVM resolved the issue for me, but I'd...

Nevermind about the DNS issue, I was doing some other stupid thing on my side (on the Internet no one knows you're a dog, except when you ask questions :) ). All resolved, issue was my ip definition as pointed out by Stoiko. Thanks a lot for your support fast support Stoiko and Oguz. When on a...

Wow, never thought that would be the issue. Thanks so much Stoiko! I changed it to /24 and I can now initiate the VPN connection and it is functional. The only issue that still remains is that my DNS servers are not changed to use the ones the VPN server pushes. When connected to the VPN...

Hi, I have a Proxmox 5.3-6 running an unprivileged LXC container with Ubuntu 18.04, fully upgraded, running OpenVPN 2.4.4. It'd like to initiate an OpenVPN connection from this container, however, it's not fully working. I've followed the following steps to make tun0 available in the...