Latest activity

  • S
    Still helping folks out in 2025, cheers :D
  • S
    It worked! I used the following commands, in case someone needs it in the future: sgdisk -e /dev/vdb sgdisk -d 1 /dev/vdb sgdisk -N 1 /dev/vdb apt install parted partprobe /dev/vdb resize2fs /dev/vdb1 Screenshots:
  • B
    Dein Verständnis ist absolut korrekt. Die Einstellung aio=threads ist eine Option pro virtueller Festplatte in der jeweiligen VM-Konfiguration (z.B. scsi0: dein-storage:100,aio=threads). Du kannst diese Option auch auf den Nodes mit dem alten...
  • B
    Hello, I've attached the files to my original post. I've created a separate text file for each command. Please let me know if you would like me to change around the formatting or make it easier to read.
  • shanreich
    Hi! Adding a rule for an IP range should work through the GUI. The available options for this parameter are documented here. Are you unable to even create the rule? If so, are you seeing any errors? Are you using nftables tech preview or...
  • B
    Naja, an irgendeinen Punkt müssen die Leute sich aber doch (wohl oder übel) mit der Technik dahinter beschäftigen. Wenn docker-volumes (die ja auch nicht mehr sind als "Benutze Ordner x an Ort y") schon zu kompliziert sind, warum setzen sie dann...
  • shanreich
    Setting the gateway directly on the bond does not work the first time, if the bond is member of a VLAN-aware bridge. You need to create the stanza for the vmbr1 interface instead: auto vmbr1.6 iface vmbr1.6 inet static address 192.168.1.53/25...
  • T
    @shanreich thanks. I've tried that, so far it worked, I just wanted to know that there is no magic kung-fu with root-fs/boot params/deeper systemd configuration.
  • B
    @Johannes S, du hast mich auf den richtigen Weg gebracht, die Wartbarkeit der Bare-Metal-Installationen genauer zu betrachten. Dein Einwand bezüglich der komplexen, manuellen Updates ist bei klassischen Bare-Metal-Installationen absolut...
  • S
    OK, ich nehme den Impuls ernst ;-) und hab das grade mit dem Kunden abgesprochen. Vielleicht muss ich in den anderen Thread mit meinen Fragen, ich stelle sie mal, auch weil ich vorsichtig bin: Das Setting betrifft die Storage-Settings der VM...
  • E
    From what I can see, it only supports Debian. I'll see if I can install it on other distros like Ubuntu and Arch. I guess Windows is out of the question, right? (That's really where I would use it most to prevent disasters caused by incautious...
  • shanreich
    For reverting the pinning itself, it should suffice to remove the generated link files from /usr/local/lib/systemd/network Additionally you would also need to check at least /etc/network/interfaces for any mentions of the name that you tried to...
  • K
    Hello, what I thought was non-functional passthrough is in reality a problem with my imported volume: I created a backup of my stopped windows vm (650GB) and copied that to a fileserver. Then I reinstalled proxmox and imported the backup...
  • B
    They do indeed have seperate WAL/DB disks, so that will probably be it. Would you expect the size to go down when stopping osd's?
  • shanreich
    You are using overlapping subnets across three interfaces and two different VLANs, which is asking for trouble. Use a separate subnet for VLAN 149 at least. bond0 is most likely not coming up due to a typo in your ifupdown2 configuration (auto...
  • shanreich
    You have configured the VLAN 10 on the physical interface already: auto bond0.10 iface bond0.10 inet static address 192.168.0.79/24 gateway 192.168.0.1 This causes the traffic to never reach vmbr0.10 - and in turn vnet0. If you configure the IP...
  • K
    kobold81 replied to the thread Passthrough:.
    I found out why it did not work: I imported my 650GB windows volume from the previous proxmox server and it seems it is unreadable.
  • shanreich
    Can you please post the full FRR / ifupdown2 configuration from all 3 nodes, as well as the output of the following commands: ip a ip r
  • shanreich
    shanreich replied to the thread Problem - SDN.
    The generated configuration depends on whether the bridge is VLAN-aware enabled, so on the hosts where you have pr_ / ln_ interfaces the bridge is not VLAN-aware. It should work in both cases though, so if you have any issues they are most likely...
  • A
    with the instruction you gave DNS is functioning, and present /etc/resolv.conf the version of Almalinux is: LXC default image for almalinux 10 (20250930)