Search results

I was just responding to OP's statement that: I agree that this is just basic network troubleshooting. As always, start reducing complexity and systematically check for good communication. Good luck Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

You should plug the wipefs error into google and go through the suggestions available there, i.e.: https://askubuntu.com/questions/926698/wipefs-device-or-resource-busy https://askubuntu.com/questions/649052/error-wiping-newly-created-partition-dev-sdb1 It also sounds like you used this disk...

Hi @petardimic , welcome to the forum. This inquiry is not really PVE configuration and installation related. Nevertheless, what is the output of: mount df lsblk Please use text copy/paste and encode it with CODE tags </> available from the menu of the edit box. Blockbridge : Ultra low...

a 3 second timing means things are misconfigured... In fact, it most likely means that things have timed out along the way. I would suspect your switch/VLAN configuration first. !H means host is not reachable via ICMP. After the trip time, some additional annotation can be printed: !H, !N, or...

Good hint @andrzejf1994 Again, keep in mind that this is not reboot persistent. One should check that their network configuration file contains correct route definition, and if it does - troubleshoot further as to why it did not come up on boot. Cheers Blockbridge : Ultra low latency...

PVE is a set of original packages providing a great Hypervisor experience on top of Debian Linux. The DHCP interaction is not customized by PVE developers. It is essentially Linux DHCP with PFSense, i.e., basic Linux system administration. I am not an expert on PFsense, perhaps, someone else...

@PwrBank Our plugin is effectively an API bridge. So, the plugin isn't going to help with general iSCSI implementations. And, we added important Proxmox-inspired features to our API, iSCSI, and NVMe virtualization to make everything rock solid based on years of experience supporting PVE in...

Great. It clearly changed at some point, since the first IP recorded by the PVE was different. There is a service that supposed to update the file but even if it did not - the console information is not in the critical path of IP networking. You have not described what "can't access the...

Hi @manwealmighty , welcome to the forum. There are a few things to consider: a) DHCP is not a recommended way to assign IP to the PVE appliance b) The fact that your DHCP server reports a different active IP for PVE than the one reported in the shell implies that the IP has changed over time...

Hi @PwrBank , to be technically correct: the threads listed above show implementation limitations of Proxmox storage pool type of "iSCSI", not iSCSI as a protocol. For example, Blockbridge PVE storage plugin implements access over iSCSI (as well as NVMe/TCP) but provides snapshots, thin...

Hi @Testani, You have classic symptoms of a receive network issues. Based on the previous post, your performance is asymmetric. Write performance is acceptable, but read performance is poor. This correlates directly to the implementation complexities of TCP. Sending a packet has much lower...

Hi @Testani, We've noticed unusually high numbers of network errors in your output, indicating something isn't right. Your iSCSI traffic is passing through a bridge, potentially involving VLANs and other network layers? Any of these factors could contribute to high network errors and, as a...

Hi @pbo198 , welcome to the forum. Rather than hijacking an existing solved thread, you should open your own. Place as much information as possible into the opening post. If you read through this thread you will find the questions commonly asked that require input from you. That said, it sounds...

Can you post your: /etc/network/interfaces Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi Testani, I can help you debug this. However, I recommend opening your own thread. You can start there with : Please provide the output from the following commands in text format as CODE or SPOILER: `lscpu` `ip a` `netstat -s | egrep -i "retrans|loss|time"` `iscsiadm -m session -P 3`...

Hi @Mattacke , welcome to the forum. Are you using the correct authentication domain - PAM vs PVE? Have you tried changing your password from console/command line to something very simple? Good luck Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

I am following up and closing this out. Based on our testing, the corruption issues with the backup data have been resolved by the Veeam software update. We ran the following test cases with full backups on lvm, zfs, and Blockbridge to prove the fix: I/O sequence analysis internal to a single...

@Testani Its extremely unlikely that there is something wrong with Linux iSCSI implementation used by PVE. We have a ton of it in production and continuously test every release going back to PVE6. We're not seeing any issues anywhere. My recommendation would be to double-check your network...

Hi @jtremblay, thank you for your inquiry. I appreciate your thoughts on repurposing hardware. However, it's important to keep in mind that end-of-life equipment can present challenges. It's more susceptible to failure, no longer supported by the manufacturer, and replacement parts can be hard...

Hi @PwrBank , welcome to the forum. You may want to take a look at these knowledgebase articles we wrote, covering block storage and performance, for some tips: Low Latency Storage Optimizations for Proxmox, KVM, & QEMU...