Search results

Is there a way to quickly test connectivity with a non-managed switch?

Do you have another NIC card to use instead of the onboard one? At least just to rule out the original NIC.

I just noticed something, are you doing backup to an NFS target hosted outside the server? I just did a proxmox full backup (snapshot) test on an old XP VM (40GB) on a server (with local lvm storage). And while backup is running, I can remote inside the VM and everything seems normal (ping times...

What is the output of #lvs? If you go to datacenter>storage, under ID "local", what is under the "Content" column? It should show Disk image, ISO image, Container, Container template like this picture. If it only says "ISO image" then it will only show your ISO files.

If you go to proxmox webgui>highlight datacenter>click storage, does the "content" column show "Disk image,Container"? If not, you have to click "edit" and add both Disk image,Container and click OK. Before doing anything, make sure you have backup of the raw disk, and backup of the VM's data...

Is the PC with KODI connected via wired or wireless? Do you have any QOS rules enabled in your router? In windows, there's a freeware utility to check lan speeds to/from network share. Do a search for "Totusoft LAN Speed Test lite 1.3" which is freeware. I agree with TheFunk, try a fresh install...

Does it still occur when you power off completely and hard reboot? Also I found a link that affected HP DL360 G8 servers. Perhaps it could help: https://unix.stackexchange.com/questions/354368/nmi-watchdog-bug-soft-lockup I would try replacing any cmos/BBU batteries (be sure to backup your...

Possible fix or maybe compare this file contents with previous version? "edit /etc/sysctl.conf and add: kernel.watchdog_thresh=30 reboot" https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5242143.html

Does the P410i controller have a battery you can replace? Or is it integrated? Also do you have 2 identical spare drives to test fresh install of ProxMox in the same RAID1, to see if it boots or show same issues? If it has issues with 2 spare discs in the same config after fresh install, it...

Hi Sam, In case this happens again, can you try these commands if it works for you? I put descriptions in parenthesis in case anyone new to linux/proxmox are reading this: #apt clean (cleans apt cache) #apt update (downloads latest package lists from repositories) #apt-get install -f...

Thanks for the update John, would you mind adding "[SOLVED] " in the front your thread subject name? That way everyone knows there was a solution. Thanks ;)

Make sure to full backup or snapshot the VM before changing VIRTIO drivers. I had a case where I forgot to backup, and the VM wouldn't start due to combo of beta VIRTIO drivers / PVEtest repository. Luckily it was just a test VM.

Out of curiosity, what values are you using for DNS under proxmox? I had a similar problem awhile back, and I was using OpenDNS family 208.67.222.123. As soon as I changed primary to Google DNS 8.8.8.8, secondary to 4.2.2.2 and rebooted, it resolved immediately.

Just to double check the obvious, the "Qemu Agent" checkbox is checked under proxmox gui>VM105>under options? Also what happens when you type the command "vssadmin list writers"? Do the last 2 lines say "stable" and "no error". The link below said to try windows server backup if vss gives...

"Shouldn't there be a line like "/dev/pve/data /var/lib/vz ext4 defaults 0 1" in fstab?" I can confirm on one of my PVE 5 servers with ext4 for system disk, the line above does exist in my fstab output

I'm not sure if this link is related, but see if it will help: https://forum.proxmox.com/threads/how-to-support-openvz-iptable_nat-modules.29968/ There's a workaround because "Containers have no control over kernel modules".

To me it sounds like a hardware issue. I would make sure the CPU/Case/PS fans are working normally, and run memtest a few hours (without any hard drives or HBA controller connected). If it's fine, try swapping out the power supply. If it still freezes, you could have a bad motherboard or HBA...

Sadly I don't think so. :( You'll need to ask a specialized recovery service provider. You could try recovery yourself, but cause further damage in the process. What was the backup policy before this happened? https://www.backblaze.com/blog/the-3-2-1-backup-strategy/

The Windows 7/Windows 2016 VM, do you have cache = "writeback" set to enabled in hardware>hard drive of proxmox? IIRC writeback has to be enabled when running Windows VM from a ZFS pool.

See if this applies to your situation: https://forum.proxmox.com/threads/live-migration-is-now-possible-with-local-zfs.35972/#post-176278