Search results

Hello everyone, after upgrading the package `zfsutils-linux/stable 2.2.0-pve3` I get following errors with `arc_summary`: # arc_summary ------------------------------------------------------------------------ ZFS Subsystem Report Sun Nov 19 12:32:54 2023 Linux...

You're welcome, but, if you aren't sure, what every piece of that config does, you shouldn't just copy&paste it. So try to understand, would be my advise. You trusted some stranger on the internet, so trust again, when I say, sure, it'll be ok ;)

Yes and then reboot.

sorry, I didn't pay enough attention. Those lines should be added to kernel cmdline: So the workaround is this: echo " i915.fastboot=1 drm.edid_firmware=edid/1280x1024.bin" >> /etc/kernel/cmdline update-initramfs -u -k all && pve-efiboot-tool refresh My config looks like this: # cat...

I have the same cpu, it has an intel igpu, so the config above should just work as it is.

Yes, but the config is for intel igpu. Don't forget to do this afterwards: update-initramfs -u -k all

Until the bug gets fixed, the workaround described in edit2 is the way to go.

I don't think so, not every proxmox user is in some enterprise environment. For me, it's for home lab use, I passthrough my gpu to VMs or containers. It's a long standing bug, and it might get fixed after all.

Just wanted to give feedback and some advice for my future self: Don't use cheap patch cables from amazon. It was a faulty cable.

My board is E3C246D2I, so the NIC its intel i219LM. I already tested and turned off everything you mentioned. It still flaps...

Sadly the problem is returned after upgrading to proxmox 8. I had a success with: iface eno2 inet manual post-up /usr/sbin/ethtool -K $IFACE gso off tso off 2> /dev/null Now it flaps every now and then, if there is enough last.

Hello everyone, after upgrading to proxmox 8 (to kernel 6.2.16-3-pve) the syslog is flooded with following messages: ... Jun 23 15:12:42 Proxmox kernel: EDID has corrupt header Jun 23 15:12:42 Proxmox kernel: EDID block 0 is all zeroes ... This is a headless server, no monitor is connected...

You’re welcome.

For me there was no reboot needed, I just had to clear my browser history and cache.

I just did the update as well and can confirm that the issue is now resolved.

Yes, the error comes only by clicking "Run Now" on the Web-UI. I'm extracting the necessary package logs from backup, it takes a while. In the mean time I tested with a fresh installed browser. Same issue.

Hey aaron, I can't say. I'm using my pve not in a cluster, it's just one server and I had to reinstall the proxmox (SSDs exchanged). After reinstalling with the newest ISO, I've run one dist-upgrade. I'll take a look at the logs (or to the ones in the backup), which version was updated (after...

Can confirm, the scheduled jobs ran fine.

I had to reinstall the os, so there is for me no way to revert the affected packages. Other workaround is to manually individually backup one by one.

After reinstalling my pve I tried to run my backup job, which should backup everything on my pbs. I can't run the job however, I get following error: Some errors have been encountered: Proxmox: Parameter verification failed. (400) next-run: property is not defined in schema and the schema...