bbgeek17's latest activity

  • bbgeek17
    Hi @unsichtbarre , My guess is that the majority of people will never need this package, so there is no reason to create dependencies, or install it by default. Otherwise, it will be part of initramfs management on all installs. Blockbridge ...
  • bbgeek17
    The snapshot support sits above the FC/Multipath layers. It requires LVM to be placed on top of the Multipath device, as well as, snapshot-as-volume-chain 1 attributed on the storage pool. This attribute is present on the referenced page, however...
  • bbgeek17
    Thank you for the update @Elleni . There could be many possibilities, for example: https://forum.proxmox.com/threads/vms-loosing-network.180650/#post-838011 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
  • bbgeek17
    Thank you for the update @naps1saps . You can mark the thread as SOLVED by editing the first post and updating the subject prefix. Best of luck in your endeavors. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
  • bbgeek17
    Hi @Elleni, The first step is to go through standard Linux network troubleshooting. Capture the network state when everything is functioning correctly, then capture it again when the network is "broken". Compare the two states. Access the...
  • bbgeek17
    bbgeek17 replied to the thread PVE-root is full.
    It will skip the mounted paths and it will not show the space occupied by the directory in pre-mounted state. One can make some inference regarding the space usage but the safest method is to unmount the external device and check again...
  • bbgeek17
    What version of PVE are you running on each node? In PVE9 most of the database has moved to /var/lib/iscsi How are you managing iSCSI sessions? Are you using PVE storage pool or manual configuration? If former, is your cluster healthy? If later...
  • bbgeek17
    bbgeek17 replied to the thread VMs loosing network.
    That's great news! Love it when root cause is found regardless of what it's! Thank you for the update! Cheers, Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
  • bbgeek17
    bbgeek17 replied to the thread VMs loosing network.
    Were windows Event logs checked? Can the VM ping/access another VM located within the same VLAN and same hypervisor? Perhaps you should have rolling network capture, or be prepared to start one at various points in the network (hypervisor...
  • bbgeek17
    bbgeek17 replied to the thread VMs loosing network.
    Hi @Drunkm0nk , welcome to the forum. It does not seem probable that an upgrade of BIND9 package installed on a hypervisor would affect intermittent connectivity issue on random VMs. You have not provided nearly sufficient information to get...
  • bbgeek17
    It does sound like an MTU issue. In addition to 28 byte IP header size, there is also a 4 byte VLAN header that may be playing a role here. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
  • bbgeek17
    Great, thanks for sharing. You can mark the thread as solved by editing the first post and selecting an appropriate subject prefix Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
  • bbgeek17
    I figured it out. There was a symlink missing under /etc/systemd/system/multi-user.target.wants for mnt-pve-dir1.mount Once this was created, dir1 shows up after a reboot.
  • bbgeek17
    Then check why the disk is not mounted on boot, if indeed it is not mounted: journalctl -u mnt-pve-dir1.mount systemctl status mnt-pve-dir1.mount Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
  • bbgeek17
    You should check and match /etc/fstab from old nodes to new node. The filesystem will not be mounted by PVE, it has to be mounted already when PVE starts. If you are mounting through Systemd, you should check the log for any errors related to...
  • bbgeek17
    The "qm" command only operates on local VMs. You are executing it from host A, you said the VM is on host C - the error is expected. You can run "qm list" to see what VMs you can access locally. You can run "pvecm status" to check the status of...
  • bbgeek17
    Your timeout error is between your client and PVE machine. QM command only operates on VMs that are local to the host where you execute the QM. It seems like one of the hosts in your cluster is down. Blockbridge : Ultra low latency all-NVME...
  • bbgeek17
    You are trying to stop VM 220, and then status check 221 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
  • bbgeek17
    bbgeek17 reacted to gfngfn256's post in the thread PVE to PBS with Like Like.
    I hope you mean you have a PBS VM on PVE- because as it looks you mean literally on the same Host bare metal! This would be bad!
  • bbgeek17
    bbgeek17 replied to the thread PVE to PBS.
    Hi @BigBadBlack , welcome to the forum. You do not. It would be helpful if you provided actual information that you tried to input, errors you received, etc. If you are unable to provide accurate information in text format (please use CODE...