Search results

Thanks for the update. In case you interested, there are some test 4.10/4.13 kernels posted with updated zfs 0.7.3 https://forum.proxmox.com/threads/zfs-cannot-import-rpool-after-reboot.37611/page-2

There's been some talk lately about certain Intel CPUs having issues with more recent KVM; See here about a test kernel: https://forum.proxmox.com/threads/pve-5-1-kvm-broken-on-old-cpus.37666/ This is another post about BSOD with VM on SSD...

Are you installing PVE 5.1 as root boot ZFS with UEFI? You have to change BIOS to use "legacy boot" for root boot ZFS: https://pve.proxmox.com/wiki/ZFS_on_Linux - "It is not possible to use ZFS as root file system with UEFI boot"

I would probably start at the hardware first. Have you tried smartctl long test per drive, and/or run memtest for about 1hour? CPU fan/case fan is clean/working, and not clogged up? What version proxmox you running, and have you tried VM CPU set for KVM64?

@Nemesiz Thanks for clarification! :rolleyes: And thanks for the ZFS sync info, I bookmarked those links

@sandqst , see this post if it may help: https://forum.proxmox.com/threads/pve-5-1-kvm-broken-on-old-cpus.37666/

@chalan, It looks like drive "zd64 " might be the bottleneck. I The w_await=426,00 which seems a little high. "w_await = The average time (in milliseconds) for write requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing...

Yes you can try choosing an older kernel. but DO NOT upgrade your zpool just yet.

Hello, It shouldn't update to 5.x, as long as your repository lists are pointing to "debian Jessie". If you change repository to "debian stretch", it will update to 5.1 however. https://pve.proxmox.com/wiki/Package_Repositories To check, existing repository type: #cat /etc/apt/sources.list...

Hi Matthew, That's an excellent question!, and I made note of these commands for myself just in case. First before doing anything, make a full backup of your VM's and also the data inside them (just in case) ;) For interrupted updates. I run the command: #apt-get clean this clears out the...

I had the same thoughts when I first read these steps. I found some info here: https://askubuntu.com/questions/57908/how-can-i-quickly-copy-a-gpt-partition-scheme-from-one-hard-drive-to-another From what I understand, bootable ZFS pool uses only 2 disks? So you copy from good boot disk to new...

ProxMox 5.1 official ISO released today if you want to retest: https://forum.proxmox.com/threads/proxmox-ve-5-1-released.37650

Good news Brian, proxMox 5.1 was just released if you want to retest swapping out the existing drive/s. https://forum.proxmox.com/threads/proxmox-ve-5-1-released.37650/

Sorry it didn't work, maybe try ProxMox 5.1 around late October/early November, it uses a 4.13 kernel that could work. You can also try ProxMox on top of Debian stretch if you want to try it: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch best wishes!

Since that's a desktop MB, perhaps check if virtualization is enabled. In BIOS, go to CPU configuration, then change "Secure Virtual Machine Mode", and set to enabled. On that MB, SVM is actually AMD Virtualization support. Also if the MB has GPU built-in, try removing any third party video...

Did you also try with PV ISO 4.4? I was thinking you can try 4.4, and if it works, upgrade to 5.

Do you have USB flash drive at least 4gb? https://pve.proxmox.com/wiki/Install_from_USB_Stick Otherwise, try downloading ProxMox via BitTorrent and verify checksums: SHA256SUMS for the ISO: 58006a1cf84fd8708bf5eaf34265ac45dc856b4608bcf13f2bc2a0679d288667

Might be worth checking, try running ip -s link on freenas and proxmox to check for network / nic errors. If you have a spare desktop PC, you can put proxmox 5 on that and try another restore from NFS.

Very strange. I run Promox 5 on Dell T300/24GB memory with 2008FE (Dell Windows Server 2008 SBS) no lagging issues. By chance does the server have an Nvidia card? see PVE 5.0 - locks/not responding YMMV as I have Nvidia card on an AMD server, and it works ok without blacklisting. Could be...

I believe that command works only for enlarging. For shrinking try this on a copy of your VM. https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files