Search results

I'd like to follow this as my etc/modprobe.d/zfs.conf doesn't exist either, and when my ZFS pool scrubs, it kills my guests. Just curious if we create zfs.conf there if it'll have an effect.

Mine turned out to be the display I was using. In my case, a Samsung TV. Once I connected to a normal monitor, all went well.

So I had one of my engineers bring over a monitor, and Proxmox installed flawlessly. I didn't even have to use nomodeset. Lesson: What kind of monitor you're using matters...even when not loading the driver (nomodeset)

Based on that log, it looks like a display issue for me. I'm using a Samsung TV in a corporate apartment while all of my normal gear is shipped from another country. I've just ordered 3 800x480 screens specifically for computers, so we'll see if that works.

I'll post updates as I go to hopefully help someone in the future. I found these and tried both in the same go: <lower RAMDISK size> (not sure why I thought this might help, but :shrugged: https://forum.proxmox.com/threads/6-0-installation-aborted-after-binding-dhcp-lease.57321/post-279042...

G'day! I'm installing VE 6.1-2 (latest ISO on the site) on an Intel NUC i7 with 32gb RAM and 2 512gb nvme drives which I've removed the partitions from (used to be a vmware host). I have another identical NUC running Proxmox already, which worked flawlessly. I've updated the BIOS and reset to...

This worked for me...as well as updating the BIOS.