Search results

@vlab, forgot to mention, try copying the VM backup file from NFS to local disk storage and try restoring.

@vlab. Before you blew away the existing hosts, were you still on Proxmox 4.4? I would verify the backup as LnxBil mentioned, and if possible, try and restore the backup files to another test server based on the same version as your original host. Or you can try booting up with an older kernel...

I think your VPS provider is having network related issues. I can't even ping srv.iwebhosting.com.br, or https://solusvm.iwebhosting.com.br. Even nameservers are not responding: ns1.iwebhosting.com.br

Hi Chalan, you need to install package "sysstat" first #apt-get install sysstat run a clone operation and then run: #iostat -x 5 then watch for a disk with any unusually high values under these columns | await | r_await | w_await | % util

Is the /public/ ZFS pool local storage? What happens if you temporarily remove (offline) /public/ ZFS pool, pull the drives out, reboot, and then re-run pveperf with just the 4 disks in raid10? Do you remember running pveperf before adding /public/?, and if it was better?

fsync for pool /public/ looks about right. fsync for pool /rpool/ looks terrible. REGEX/SECOND for both seem lower than normal. Can you check ashift settings for pool /rpool/ and also pool /public/ Check ashift settings: #zdb -C rpool | grep ashift and #zdb -C public | grep ashift The...

I don't know if syntax makes a difference, what happens to fsync rate if you do: #pveperf /rpool/

If you want additional ZFS tips & tweaks, gkovacs has an excellent write-up on his ZFS settings here: https://forum.proxmox.com/threads/single-server-storage-recommendations.35148/#post-172410 Otherwise if everything's running fine, I'd leave well enough alone. And if you do change anything...

As I understand it, ZFS requires more memory to reach full potential. So if you have 16gb, expect 8GB to be dedicated to ZFS, with 8GB left to be divided between your VM's. Please see this port for more information...

@Saihtam If this is non-production server, you can try enabling pve-test repository which uses a newer kernel. https://pve.proxmox.com/wiki/Package_Repositories Good Luck!

I agree with Alwin, I would remove the card, use eraser to gently scrub the contacts, and then isopropyl alcohol or windex on the contacts. Can you also try another PCI-E slot? Also, if you aren't using the onboard motherboard NIC, try disabling it in BIOS. And also update your motherboard's...

How much memory (total) does the server have? And how much memory is allocated to the VM?

I would check network stats from each node, to check for network card errors: #ip -s link Also do you have another 1GB switch and/or Cat6 cables to switch out and retest? Is the switch using VLAN and/or is there any QOS or bandwidth throttling enabled?

Correct, your proxmox 4.4 test VM should have sources.list pointing to debian Jessie pve-nosubscription repos, and pve-enterprise also disabled, then dist-upgrade to latest updates. Once no more updates available for 4.4, modify sources again to debian stretch pve-no subscription and...

@crazy-to-bike, I took a look at my current lvmetad settings on standalone server, this is what I found: from /etc/lvm/lvm.conf use_lvmetad = 0

"Can I stop lvm2-lvmetad while the server is in use and VM are running?" In my case I stopped lvm2-lvmetad while2 VM's were running (Windows and ClearOS VM) and I didn't notice any issues during the updates. This is on a standalone (non cluster) server with pve-nosubscription repository. I...

Hello, I encountered the same issue awhile back. It sounds scary, but actually harmless. If I interpret correctly, this happens because "pvscan --cache" can't run while the service "lvm2-lvmetad" is running. Here's what I did to make sure apt-get update/dist-upgrade went smooth: #service...

In your picture (the small popout window) click the small arrow on the left side of the window, it will expand and show the controls in Gosha's shot.

I'm not the expert, but I recall using ZFS requires adding more memory. Maybe ZFS used more ram during file copies than it free'd up, causing the crash. see here: https://forum.proxmox.com/threads/zfs-server-crash.32675/...

If its not too much trouble, can you setup a Samba share on that CentOS target, add to ProxMox storage and retest and post results?