Search results

  1. D

    Windows server 2016 disk active time becomes 100% suddenly

    we delete dell devices hba then we do ZFS at the end https://fohdeesha.com/docs/perc.html :) I use 2 3 nvems and ram is very important to me so I use btrfs and LVM-thin
  2. D

    Windows server 2016 disk active time becomes 100% suddenly

    GIVES btrfs the best IOPS. btrfs0 4 samsung ssd 870 evo. 1 tb. Hardware RAID? + ZFS not recommended
  3. D

    Windows server 2016 disk active time becomes 100% suddenly

    btrfs raid 5 declared experimental btrfs raid 0 I'm using it and I've never had a problem
  4. D

    Windows server 2016 disk active time becomes 100% suddenly

    For your information, ssds do not break easily. The sata ssd working 900k hours is still working. give up raid 5. And ZFS consumes more ram. always use btrfs.
  5. D

    Windows server 2016 disk active time becomes 100% suddenly

    I manage 15 servers, 800 vm virtual servers, I disable km in all of them it also makes ksm cpu load it's a fact https://forum.proxmox.com/threads/ksm-is-using-about-30-of-cpu-time.3857/ Sorry, but this is expected behavior - KSM need to scan the whole memory all the time, so this need CPU (how...
  6. D

    Windows server 2016 disk active time becomes 100% suddenly

    swap ksm promlem please disable https://blog.lbdg.me/proxmox-best-performance-disable-swappiness/ https://pve.proxmox.com/wiki/Dynamic_Memory_Management Reboot okey
  7. D

    rrdcached promlem cluster

    I thought proxmox staff members had resigned welcome
  8. D

    HOST Summary time displaying different than host time

    i solved the problem solution inside timedatectl set-local-rtc 1 --adjust-system-clock cd /var/lib/rrdcached find . -type f -print -exec rm {} \; systemctl restart rrdcached systemctl restart pve-cluster
  9. D

    HOST Summary time displaying different than host time

    I'm having the same problem and couldn't find a solution. https://forum.proxmox.com/threads/rrdcached-promlem-cluster.102025/
  10. D

    rrdcached promlem cluster

    Hello Proxmox 7.1 promlem rrdcached helpp main server pve1 cluster I think it's like a clock problem graphics not working properly root@pve1:~# timedatectl Local time: Sun 2021-12-26 06:35:17 UTC Universal time: Sun 2021-12-26 06:35:17 UTC RTC time...
  11. D

    Install Proxmox VE via recovery on So you Start (OVH) Server

    proxmox v6 debian 10 ens81 proxmox v6 debian 11 eno1 SoYouStart install recover install proxmox 7.1 no promlem.
  12. D

    Install Proxmox VE via recovery on So you Start (OVH) Server

    I have sent you my contact information privately, contact me.
  13. D

    Install Proxmox VE via recovery on So you Start (OVH) Server

    This worked for you? I got a machine using this way, still stuck on boot. It boots fine within the VM, don't have an IPMI so I can't figure out why. you said that, you said there is no IPMI kvm I don't have it but the device turns on How do you know it's a boot problem? the server is...
  14. D

    Install Proxmox VE via recovery on So you Start (OVH) Server

    It wasn't opening for me, it turns out, the internet wasn't coming out, when I changed it to eno1 after the installation, the server got internet the server is actually booting. but not due to internet I can show AnyDesk if you want İnstall >>>>> qemu-system-x86_64 -net nic -net...
  15. D

    Install Proxmox VE via recovery on So you Start (OVH) Server

    the problem is because of the ethernet name :) vkvm install ens81 install finish edit nano /etc/network/interfaces eno1 + hwaddress auto lo iface lo inet loopback iface eno1 inet manual ens81 edit eno1 auto vmbr0 iface vmbr0 inet static address xxx gateway xxx...
  16. D

    Backup error .chunks delete :(

    I don't have to do it this way, I hope it happens this way.
  17. D

    Backup error .chunks delete :(

    INFO: skip external VMs: 100, 102, 103, 104, 106, 107, 108, 109, 110, 112, 113, 114, 115, 116, 118, 119, 120, 121, 129, 141, 149, 165, 173, 174, 181, 182, 185, 186, 189, 193, 194, 195, 196, 197, 198, 200, 205, 207, 208, 209, 210, 212, 213, 214, 217, 221, 222, 223, 224, 227, 230, 231, 232, 233...
  18. D

    Backup error .chunks delete :(

    I do not understand ? a system in a set proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve) pve-manager: 7.1-7 (running version: 7.1-7/df5740ad) pve-kernel-helper: 7.1-6 pve-kernel-5.13: 7.1-5 pve-kernel-5.11: 7.0-10 pve-kernel-5.13.19-2-pve: 5.13.19-4 pve-kernel-5.13.19-1-pve: 5.13.19-3...
  19. D

    Backup error .chunks delete :(

    so no other vm can backup ? What is your suggested solution?