Recent content by fstrankowski

  1. fstrankowski

    Proxmox HA & "Start at boot"

    Moin! Wir nutzen HA für unsere VMs. Laut Dokumentation wird die Option "Start at boot" nicht verwendet, sobald eine VM im HA ist. Was jetzt passiert ist: Wenn durch Probleme eine Maschine umgezogen wurde auf einem neuen Host, aber noch auf einem anderen Host vorhanden ist (eine Art...
  2. fstrankowski

    [SOLVED] [TAGS] Datacenter wide tag color override not applied to vms/lxc

    You've pointed me in the right direction. Even though we only use LARGE written tags, which are UNIQUE, we still have to select the "Case-Sensitive" option, even though we only use LARGE tags. This is kinda misleading but i'm happy that we've found out. P.S.: By default, even though you only...
  3. fstrankowski

    [SOLVED] [TAGS] Datacenter wide tag color override not applied to vms/lxc

    While testing the 'new' possibility of setting up tags for different categories we've stumbled upon the fact that when we setup tags on a datacenter level and color-override them accordingly, those tags are then available for selection on lxc/vms but the predefinied colors are not correctly...
  4. fstrankowski

    [SOLVED] Stuck in "menu timeout set to"

    Found the answer in the archives: See here > https://forum.proxmox.com/threads/hot-to-modify-timeout-in-systemd-boot-menu-its-too-long-5-102-000-sec.124109/#post-544152
  5. fstrankowski

    [SOLVED] Stuck in "menu timeout set to"

    I have just setup two new "Tiny Mini Micro" servers (HP EliteDesk 800 G4 / i5 8500) and installed Proxmox. Idetical systems. One system is stuck at the bootloader screen. Problem: The "menu timeout set to" is constantly counting up (increasing) without any limit. When pressing any key the...
  6. fstrankowski

    [SOLVED] Proxmox 8 | Sporadic ICMP / Scheduler Problems

    I've found the problem: Reason for the behavior has been a faulty DNS server in the line. This caused the resolving reverse names for the ipv6 adresses to be slower than 1 second and thus caused the problem shown above.
  7. fstrankowski

    [SOLVED] Proxmox 8 | Sporadic ICMP / Scheduler Problems

    I've setup a fresh Proxmox 8 Box at Hetzner DC and have a new kind of problem with it i never had before. After setting up the box, i used to outward ping hosts to check the connectivity from time to time and its link latency - which is fine. But while pinging servers, waiting for the reply made...
  8. fstrankowski

    Proxmox 7.3.3 / Ceph 17.2.5 - OSDs crashing while rebooting

    So we can atleast say that our problem is unrelated to the kernel version. You're running 6.1 while we're at 5.15. Same issue on both systems.
  9. fstrankowski

    Proxmox 7.3.3 / Ceph 17.2.5 - OSDs crashing while rebooting

    We've recently (yesterday) updated our test-cluster to the latest PVE-Version. While rebooting the system (upgrade finished without any incidents), all OSDs on each system crashed: ** File Read Latency Histogram By Level [default] ** 2023-01-30T10:21:52.827+0100 7f5f16fd1700 -1 received...
  10. fstrankowski

    Ceph 17.2 Quincy Available as Stable Release

    You're indeed correct. So in the longrun it could be an idea to develop a ceph-ansible/cephadm inspired, proprietary Proxmox approach, to automatically calculate and adjust osd_memory_target values. Wdyt? Thats why i've been referring to it using values in between 0.1 <> 0.2 ;-)
  11. fstrankowski

    Proxmox 7.3 (LXC 5.0) using veth with multiple tagged and untagged vlans

    Since Proxmox 7.3 introduced LXC 5.0 i'm wondering when it will be possible to make use of LXC's feature of un/tagging VLANs on veth devices veth.vlan.id veth.vlan.tagged.id also IMHO it might be useful to add the rx/tx queues to the advanced tab veth.n_rxqueues veth.n_txqueues
  12. fstrankowski

    Ceph 17.2 Quincy Available as Stable Release

    Wondering why Proxmox does not enable osd_memory_target_autotune by default. Its advised if you're running Quincy >17.2.0 and for hyperconverged setups like Proxmox, we can scale it to between 0.1 and 0.2 to be on the safe side. Do you see any way to take advantage of autoscaling in the future...
  13. fstrankowski

    High disk usage in LVM-Thin

    Oneliner to trim all containers: pct list | awk '/^[0-9]/ {print $1}' | while read ct; do pct fstrim ${ct}; done
  14. fstrankowski

    windows server to VM

    Why is efidisk0 still pointing to your old volume?
  15. fstrankowski

    High disk usage in LVM-Thin

    You gotta enable discard in the VM disc mount options or run fstrim inside the VM to reclaim unused disc space.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!