Recent content by inDane

it was an ip address conflict... It was a IP on the switch itself for debugging purposes in that network, that hasnt been removed by the network-admin after the debugging....

i cant really narrow down to what it is. We've redone the switch config and the local network configs. Sometimes ssh just works and other times it doesnt. When it works, its says debug2: peer server KEXINIT proposal debug2: KEX algorithms...

Thanks for your input! Yes, this is what I initially thought too. But no, unfortunately not. At this point I'm glancing towards broken tranceivers/nics/switchports... I've had this problem before with the same node. I did a fresh reinstall and the same problem is coming up again. I am going...

that is odd, they are allowed and its only one out of 8 identical installations, that shows this behavior. And also, it is not permanently, sometimes it works, sometimes it doesn't.

Hey all, one of my nodes is causing my cluster to break sync every now and then. When that is happening, it usually does not want me to access it via SSH and gives this error: Unable to negotiate with 10.168.61.21 port 22: no matching key exchange method found. Their offer...

on the network device you mean? How should that affect the underlying NFS? Client -> SSH -> Container -> fio-command -> IOs towards NFS. If you are talking about the network device, then it would only affect the "client -> ssh" part.

i can reliably crash my system if i put IO load inside a container that has its image as raw on the nfs share...

Dear Proxmoxers, i have two boxes, one is running truenas with ZFS RaidZ1 and exporting via NFS. The other one is running Proxmox 7.2. (pve-host) If I am running i.e. fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --bs=4k --iodepth=64 --readwrite=randrw...

Hi, I accidentally found a workaround. Usually there is a regular disk created with the VM. The default size for a Win10 VM is 32GB. Delete/Detach this disk. Boot the machine, go into the EFI settings, change the boot order again and voilá, it works. Best regards inDane

Hi fellas, im using OVMF (UEFI) and id like to boot directly from a NVMe drive, which is passed-though. it basicly works, but not automatically. I don't know where to change it. If i change anything in the boot menu of EFI, it will "forget" it at next boot of the VM. I can manually boot it via...

oh my god, i've spent so much time. Thanks, this is the solution! WRONG RIGHT video=vesafb:off video=efifb:off

I've had no success. Thank you very much for your input. To not extend this any further, i just grabbed an RX 480 from another computer and installed it with that one.

nomodeset ... doesnt show these artifacts on the screen, but it wont continue either. It shows that it got an IP via DHCP and now it just sits there.

Maincomponents are: - Ryzen 3950X - ASUS X570 ROG x570-F - Nvidia RTX 2060 Super (Gigabyte) you mean, with "e" going to the edit the boot menu and add vga=791 to the line, starting with /boot/linux26, right? That didn't help unfortunately. Do you have more ideas I could try? Best

Is this a known bug? Can you tell me what I need to do to make this work? My guess is, that it doesn't like my GPU. Nvidia and Linux is just not a good match.