Search results

There is no officially endorsed way to implement such boot from PVE installer. I have seen success stories reported in the forum from people installing Debian to boot from SAN. I have no recent personal experience with booting from FC SAN, so don't have a specific advice for you. Does your...

Thank you for the update @mikewich . As the OP you can now mark the thread as Solved by editing the first message and selecting the appropriate prefix for the subject. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

There is no storage level snapshot integration in a Veeam+PVE combination for any storage type. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thank you for the update @Oa4McvMTSo An assumption that user did at least the basic review of the system and would mention a major change they made, gets me every time... Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Could this be related to your issue? https://forum.proxmox.com/threads/apt-update-is-not-working.181181/#post-840788 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

This is not enough information. Given that you are using Pure and their support is known to be very good, perhaps you should reach out to them for help. Here is a list of things that you need to minimally provide so that forum volunteers can try to assist: - Proxmox version across each node...

In the thread you referenced the poster shows evidence of Kernel lock. While "pvestatd" is a userland process, it interacts with Linux Kernel, and specifically SMB/NFS infrastructure. If the Kernel is wedged, "kill -9" will not help. If you had HA properly configured and your other nodes are...

Have you restored your NAS services? If you have similar Kernel messages in your log as the other poster, and you have restored NAS services, then it seems that Kernel is unable to unwedge itself. Reboot is likely the only option in this case. Blockbridge : Ultra low latency all-NVME shared...

My recommendations for next steps are unchanged. There is nothing else I can suggest as you continue to avoid providing actual system output. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Given that "pvesm" talks somewhat directly to storage accessible to the node where you are running it from, chances are that you have an issue with storage access that trips up "pvestatd" and other components. I would remove all storage pools from storage.cfg, except "local" and "local-zfs/lvm"...

Hi @HenkS , welcome to the forum. This is an expected behaviour for QCOW snapshots over NFS. VMware does not use QCOW, their proprietary VMDK format employs completely different structure and snapshot architecture. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

That's great! Thank you for the update. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Type out your password in shell so you can confirm it is what you expect it to be. I suppose you don't have sudo for this user? You can always use the system recovery process to reset the root password. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

qm is in /usr/sbin which may not be included in a path of the new user: which qm /usr/sbin/qm When logged in as new user via SSH - try to ssh into localhost, ie: ssh root@localhost is the password still working? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

May be the admin of your MIMT had inadvertently broken things they didnt mean to proxy and now fixed it, or may be its the other way around. Good luck! PS you can run VPN for outside traffic and either punch holes for SSH, or run SSH over VPN. AI is not always smart and much depends on your...

Hi @mikewich, welcome to the forum. You sound a bit frustrated, I get it, rebuilding nodes is never fun. To help effectively, we'll need to see the actual system state from each node. A few things worth keeping in mind: FC connectivity and Multipath are standard Linux administration, not...

@alexskysilk You're right to call that out. "Very small environments" was a poor choice of words on my part. The distinction I was trying to make isn't about node count, it's about business value. We have customers running three node clusters with tens of millions of dollars of business value...

Hi @RoxyProxy, Since questions around pricing, company future, and so on came up, we felt it was appropriate to chime in. First, we'd like to thank the Blockbridge customers earlier in the thread for sharing their thoughts. To be honest, Blockbridge isn't a great fit for very small...

Good luck. It is a hard problem to solve, especially if there are FC switches involved - the SAN view can become skewed. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @nvanaert , There's quite a bit to unpack here. First and foremost, Proxmox VE does not monitor storage or network path health. An All Paths Down (APD) condition will not result in a node fence, nor does it interact with the VM HA subsystem in any way. To directly answer your VMware...