bbgeek17's latest activity
-
Is there some documentation for that plugin? It should show details about the supported protocols and features, right? -
bbgeek17 replied to the thread Proxmox VE exit codes meaning.Hi @TheAncientMariner , Exit code 1 is a generic non-success return value. Any non-zero exit code usually indicates a failure. Some applications use a range of exit codes to represent specific error conditions, but as far as I am aware, PVE...
-
bbgeek17 replied to the thread [SOLVED] Proxmox - VM io-error.Presumably you saw the IO error somewhere. You should post exactly what you saw and describe where (inside VM, in Hypervisor, elsewhere?). It could be a log snippet, a screenshot, anything that can help describe your situation. For all we know...
-
bbgeek17 replied to the thread Datastore was on CIFS, remounted on NFS, rolling back -> Permission denied (os error 13).Great to hear! You can mark the thread as solved by editing the first post and selecting the appropriate subject prefix. That will help organize things for other readers in the future. Cheers Blockbridge : Ultra low latency all-NVME shared...
-
bbgeek17 reacted to sgw's post in the thread Datastore was on CIFS, remounted on NFS, rolling back -> Permission denied (os error 13) with
Like.
@bbgeek17 thanks! You point at the right issue, and I had solved it a few minutes before you wrote ;-) I disabled the NFS-sharing and looked into the permissions on the NAS, for the CIFS-users there. The write-permission for our user... -
bbgeek17 replied to the thread Datastore was on CIFS, remounted on NFS, rolling back -> Permission denied (os error 13).Hi @sgw, Having dealt with MultiProtocol access in prior life with multiple enterprise storage products I can tell you things are not simple there. Each vendor implements permissions mappings differently. Some store additional metadata in the...
-
bbgeek17 replied to the thread Restoring vmware vm to a proxmox.Hi @ebarrios08 , welcome to the forum. The error message is produced by Veeam, I would recommend starting with their support to help zoom in on a particular part of the process that failed. I don't know the compatibility requirements for...
-
bbgeek17 replied to the thread [SOLVED] Proxmox - VM io-error.Hi @m.gaggiano , welcome to the forum. It seems as you may have omitted the actual complete error from your post. The "I/O" error is a generic symptom. It can be caused by many different things. Please provide an actual error message, system...
-
bbgeek17 replied to the thread [SOLVED] Problem connecting Proxmox 9.1 to the storage ESXi for migrate VM's from ESXI.Thank you for coming back and sharing your findings - they will assist others who run into similar situation. You can mark the thread as Solved by editing the first post and selecting the appropriate subject prefix. This assist with keeping the...
-
bbgeek17 replied to the thread Correcting Storage.Hi @nleistad, Confidently attributing the issue to NFS, QCOW, ZFS, network, or any other component requires proper analysis. This typically includes log review, reproducible testing, and potentially network trace reading. There are known edge...
-
bbgeek17 replied to the thread [SOLVED] Problem connecting Proxmox 9.1 to the storage ESXi for migrate VM's from ESXI.Hi @Vladyslav , There is no documentation, as far as I am aware, that can guide you to use a non-root account. That said, you can use a tool (for example "govc") that uses the same network/API path as PVE and troubleshoot the connectivity easier...
-
bbgeek17 replied to the thread MTU Settings for NAS storage.Hi @Eric Thornton , welcome to the forum. MTU size is not tied to network speed. You can use non-standard MTU values on 1 Gbit just as well as on 25 Gbit or higher links. The key point is consistency: all devices participating in the same...
-
bbgeek17 replied to the thread Proxmox and Veeam Backup and Replication worker issue.I recommend that you figure out a curl based way to upload a file to local storage with the same account that Veeam is using. Run it local to PVE first, if that works - run it from the Veeam network segment. If that works, convert it to PS...
-
bbgeek17 replied to the thread Proxmox and Veeam Backup and Replication worker issue.post your /etc/pve/storage.cfg Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread LCAP LAG Not Working.Hi @Bones558 , welcome to the forum. There could be multiple issues that affect your connectivity. For example, you have two interfaces on the same network segment. This will lead to confusion and unpredictable results, like the ones you are...
-
bbgeek17 replied to the thread How to configure HA to shut down specific VMs before migration in Proxmox VE 9.1?.That really defeats the primary goal of the HA subsystem. Plus it would only work in a managed migration. As you can imagine on node failure there will be no way to either shutdown or live-migrate the VM. If you are only looking to address...
-
bbgeek17 replied to the thread Proxmox and Veeam Backup and Replication worker issue.Hi @acsinc , welcome to the forum. Veeam is a partner of PVE and they theoretically have access to PVE support to assist with common customer issues. However, you seem to be a Veeam only customer at this point. You may benefit from the help from...
-
bbgeek17 replied to the thread Suddenly unable to access web UI.Have you tried 127.0.0.1 ? It would be helpful if you posted your configuration and commands you run here, rather than just reporting the results. The output of these commands in text format and encoded with CODE tags is a good start: pveversion...
-
bbgeek17 replied to the thread Opt-in Linux 7.0 Kernel for Proxmox VE 9 available on test and no-subscription.Great news! We will get it into our automated testing asap! Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread Iscsi for Virtual Machine Storage in Proxmox.Sounds like they resolved the problem. I agree that their original issue was likely network configuration related, perhaps MTU was misconfigured. Your iSCSI storage is a "storage pool" of iSCSI type in PVE speak. The LVM storage is the LVM...