readyspace's latest activity

  • readyspace
    I think that's definitively an important topic. The PDM is certainly a "lucrative" target due to being a single point of entry to one's whole Proxmox infrastructure, that's actually a big reason for it's a pull based design, i.e., the PDM can be...
  • readyspace
    We're very excited to present the first stable release of our new Proxmox Datacenter Manager! Proxmox Datacenter Manager is an open-source, centralized management solution to oversee and manage multiple, independent Proxmox-based environments...
  • readyspace
    Great to see this!
  • readyspace
    readyspace reacted to tstrenk's post in the thread Cluster Issues with Like Like.
    After wiping the 4th node, reinstalling, and then adding it to the cluster with the transport: udpu setting already in place, it worked great. No issues at all and now my 4 node cluster is working. So it turns out the issue was the switch not...
  • readyspace
    readyspace reacted to tstrenk's post in the thread Cluster Issues with Like Like.
    I was able to set Transport: udpu but I also needed to set crypto_cipher and crypto_hash to none in order for corosync to start back up. By making these changes to the corosync.conf file, I was able to get the 3 nodes connected. I'm currently...
  • readyspace
    The fix turned out to be using seaBIOS and no Q35. https://forum.proxmox.com/threads/cannot-passthrough-h100-pcie-gpu-to-vms.141084/
  • readyspace
    A few stray checksum errors right after replacing a bad cable can be normal — ZFS is still verifying and repairing blocks that were previously affected. Run another zpool scrub and monitor if the CKSUM count stays stable or resets to zero. If...
  • readyspace
    readyspace replied to the thread Cluster Issues.
    Yeah — that behavior pretty much screams Corosync identity or network conflict, not hardware. When two nodes work fine but adding a third (or fourth) causes the whole cluster to fall apart, it’s usually one of these: 1. Duplicate nodeid or...
  • readyspace
    readyspace replied to the thread USB Lan Adapter.
    @luke94x i think it was due to underpower. After you turned on the power on USB, it worked.
  • readyspace
    readyspace reacted to luke94x's post in the thread USB Lan Adapter with Like Like.
    Thanks a lot. I have switched to another usb port and turned off Intel Dynamic Power Technology, also turned on Power on usb on S4/S5 state and it worked. Dunnno which one helped but one of this for sure. Thanks a lot readyspace!!
  • readyspace
    @verishare , you've heard the guys above saying. And I totally agree, just buy enterprise SSD. ;)
  • readyspace
    readyspace reacted to UdoB's post in the thread How to Reduce SSD Wearout in Proxmox? with Like Like.
    @verishare : just note that ZFS adds a lot of capabilities/features *I* don't want to live without: https://forum.proxmox.com/threads/fabu-this-is-just-a-small-setup-with-limited-resources-and-only-a-few-disks-should-i-use-zfs-at-all.160037/ Of...
  • readyspace
    That did the trick! Thanks a lot, @readyspace !
  • readyspace
    Yep, that’s actually normal — it’s how unprivileged LXC containers isolate files. The container’s root is mapped to a high UID range on the host (like 101000+), so files written from inside can look “hidden” or owned by unknown users outside...
  • readyspace
    Looks like the issue is caused by volatile EFI/TPM devices — OVMF loses the TPM state after save, so Secure Boot and attestation can’t complete. Please try recreating both efidisk0 and tpmstate0 on a persistent storage pool (not volatile:)...
  • readyspace
    And forgot to reply I got it working a few minutes after this post. TY so much @readyspace couldn't have done it without you, for real! onto the next problem now :D
  • readyspace
    Hi, glad it’s sorted. The root cause was indeed UID/GID mapping mismatch — when files were written by the host, they got ownerships outside the container’s mapped range, making them effectively invisible from inside unprivileged LXCs. Copying...
  • readyspace
    Based on the error, it means enp1s0 is still configured as a normal interface instead of being in manual mode, so it can’t be used as a bridge port. Edit /etc/network/interfaces, remove any IP lines under enp1s0, and make it look like this: auto...
  • readyspace
    another update, I found from going down another rabbit whole this post that showed how to reinstall the keyring. Next ran apt update and apt install proxmox-ve pve-manager. The web portal is up, neat! still googling furiously to figure out...
  • readyspace
    Hi, it seems like a TPM attestation issue caused by how QEMU emulates TPM 2.0 in Proxmox. Try switching your VM’s TPM device to version=v2.0,model=crb and ensure Secure Boot is enabled with Microsoft keys (not pre-enrolled-keys=1). Also make...