bbgeek17's latest activity
-
bbgeek17 replied to the thread Cannot log in via GUI, ssh does not respond.Proxmox Virtualization Environment is, indeed, a collection of custom packages. However, it runs on Debian Linux with an Ubuntu-derived kernel. Those two components, primarily the kernel, are what directly interact with your hardware. SSH is a... -
bbgeek17 replied to the thread Cannot log in via GUI, ssh does not respond.Imagine calling an auto shop and telling them that your car sometimes just stops running. You need to turn it off and on to get going, is this something well known? Good luck in your research Blockbridge : Ultra low latency all-NVME shared...
-
bbgeek17 replied to the thread Cannot log in via GUI, ssh does not respond.What you described are generic symptoms that could be caused by many different things. Some examples are: failing disk, full disk, failing memory, etc. If the system is not responsive, the first step is to reboot it. Once it is up, you can...
-
bbgeek17 replied to the thread [SOLVED] iSCSI multipath does not use/recognize all paths..Thank you for the update @Tom123 ! Sounds like the original diagnosis was correct. If you feel comfortable to share the details with the community - please do so. But no worries if you don't. Cheers Blockbridge : Ultra low latency all-NVME...
-
bbgeek17 replied to the thread Double and triple input of characters from the keyboard.Have you tried to restart your ILO console? Use a different ILO method? Make sure you have up to date firmware? In most cases this would be an ILO issue. Make sure you only have one open. Blockbridge : Ultra low latency all-NVME shared storage...
-
bbgeek17 replied to the thread Dedicated Proxmox network interface connectivity issue.@AndyKosh , There is a lot going on here, and none of it is related to PVE. This is purely Linux network management. The output you provided is extremely difficult to read. You must have noticed the ASCII encoding issues in your copy/paste. The...
-
bbgeek17 replied to the thread What are everyone's experience with IBM SANs?.You may be facing a few challenges when dealing with IBM support in conjunction with PVE, as there are several layers where issues can arise: While IBM has performed some interoperability testing with PVE, their storage team may not be as...
-
bbgeek17 replied to the thread Atomic rename error.It sounds like you have a user-mapping issue between Synology and PBS. Or perhaps root folder permission issue. You could open it up to the world as a test: chmod 777 /mnt/backupsit/ My Multiprotocol (NFS/CIFS) file access are long behind me. I...
-
bbgeek17 replied to the thread Ethernet interface not coming up after installation of Proxmox.Thank you for sharing @dstachur . It does not seem like your post is related to the topic of this thread. I recommend opening a new thread if you have a question. In the meantime, you can take a look here...
-
bbgeek17 replied to the thread ZFS over iSCSI: Multipath alternatives.It is an interesting approach @joaquinv898 . Keep us updated on your progress. cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread network card not visible, driver or hardware error?.First, none of the challenges you are describing are related to the Proxmox Virtual Environment. To clarify: dusting your PC was not a contributing factor, and the on-board integrated NICs never worked previously. It is possible that the NICs...
-
bbgeek17 replied to the thread network card not visible, driver or hardware error?.If the system was working previously and the NICs were being detected, then it is more likely than not that you are dealing with a hardware or firmware issue. You may need to try a different PCIe slot for the cards you removed, or temporarily...
-
bbgeek17 replied to the thread Dedicated Proxmox network interface connectivity issue.Hi @AndyKosh , It is impossible to draw any conclusions about the behavior of your network without detailed technical information about your environment. This should include network configuration files, the current state of the systems involved...
-
bbgeek17 replied to the thread Atomic rename error.Have you checked the ownership and permissions of the entire path of the offending file? Can you perform same operations in that path? With that file? Have you checked your NAS log files? Can you increase verbosity of the logs on the NAS side...
-
bbgeek17 replied to the thread Delete orphaned VM DIsk.Please provide: cat /etc/pve/storage.cfg pvesm status mount lsblk qm config [id] pvesm list [storage] As requested, provide full unredacted commands that you run: rm, ls, etc Direct and file listing on : vm-9000-disk-1.qcow2 (if that is the disk...
-
bbgeek17 replied to the thread Atomic rename error.The "cp/mv", "ls", "touch" Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread [SOLVED] VM Migration issue.You may need to run this command, as suggested by the log. Or manually update these files with new keys. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread Atomic rename error.Based on the Path to the file this particular error seems to come via NFS. Have you examined the file? Try a few operations manually. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread Is a 3-node Full Mesh Setup For Ceph and Corosync Good or Bad.In a Node Down scenario, you are left with two nodes that can still communicate directly with each other, since this is a mesh network. Additional load only becomes a factor in a Link Down scenario. In that case, depending on the topology and...
-
bbgeek17 replied to the thread Snapshot of VM Freezes All Other VMs on Node.It’s possible that you’re experiencing what is commonly referred to as “VM stunning.” In many virtualization environments (ESXi, PVE, etc.) it is most often caused by slow or congested storage. As suggested earlier, try performing the operation...