Recent content by kovaga

Please take time to read what I wrote, I dont use NFS share for the VM storage anymore. only for the backups. In addition to "umount -l" I would also consider adding "-f " switch.

nfs >>>hard<<< link result in the completely unacceptable hanging of the client. the soft mount option at least allows you to gracefully umount and remount the directory. Anyway, NFS for the last month and a bit is used only for storing the Backups and fetching the ISOs, the VM disks are moved...

What I've done is I have started mounting nfs via /etc/fstab and use the soft vs hard mode, so that the system does not completely halts when there is an issue with the NFS. and add the directory as a local storage in PVE. the fstab mount options are...

I am on 8.3.1 and kernel 6.11.0-2-pve Will keep an eye and will try to test again in couple of days, as I have updated and rebooted all three hosts today.

What is interesting, this seems to happen only if I mount NFS share via Proxmox Storage menu. If I mount the share via NFS in fstab and add the Directory Storage, everything runs smoothly, at least today I have written and read couple of terrabytes in and the 10G link saturated to 100%...

I have the same problem. Upgraded from 7.4 to 8.3, fresh install and that when the FUN started. I have each of the 3 hosts export local 1TB NVME drive via NFS, so that the VM can be migrated between hosts, without the need to migrate storage. In 7.4 this setup had run without problems for...

replaced the CPU and the problem was gone.

I have two identical home "servers" running ASRock X570 Pro4, AMD Ryzen 5600G, 2x32GB DDR4 3200 and 10Gb cards. One of the machines started randomly rebooting about 10 days ago. There is absolutely no correlation between reboots and anything that I could think off. Sometimes it would reboot...

so it seems that the easiest solution is to do a global rewrite at the postfix level. add to /etc/postfix/main.cf #adress rewrite smtp_generic_maps = hash:/etc/postfix/generic and to /etc/postfix/generic root@yourdomain.com pve1@somedomain @yourdomain.com...

Hi List, the problem i noticed recently is that the email generated by cron are not being sent to the email of the root@pam user specified during the installation. Started digging and it seems that by default /root/.forward contains |/usr/bin/pvemailforward that should take place of the...

Ok, so now the BIOS on both MB is at its latest. It seems that the situation is a bit better, but a random crash can still occur. What I observed is that idling VM is much less likely to crash, while a VM that is doing "cat /dev/urandom > /dev/null" would crash almost certainly. So I guess no...

Good point! Could be the clue The current BIOS release date on the AMD MB is August 2020 while the release date for AMD Ryzen 7 5800X was November 2020 I will try updating it to the latest one and try again.

Hi Mira, thanks for the hint, unfortunately it didnt work. The VM continues to kernel panics straight after live migration. I am running the latest 5.11.22-3-pve on both hosts. The intel cpu runs the updated microcode. The amd cpu is pretty new, while the latest package with amd microdes is...

Hi list, I have recently introduced and joined "AMD Ryzen 7 5800X" to my home prox cluster running on "Intel(R) Core(TM) i5-8400". I was under assumption, that providing you set the emulated CPU type to KVM64 or QEMU64, the live migration would work, however its not been my case. Pretty much...

I had a similar issue on an HP Proliant BL465c G7 with Emulex10Gb UNDI card. it was getting stuck at scsi host5: BC_295 : MBX Cmd Completion timed out Jan 13 16:24:41 ais-cloudhost1 kernel: [ 607.271584] INFO: task systemd-udevd:336 blocked for more than 241 seconds. So i solved the issue by...