Search results

Yes, i figured it was your bug. It was more for the wider audience here on the forum who will come across this thread in the future. Cheers. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The fix is in process: https://lore.proxmox.com/pve-devel/20260310091141.814416-1-d.csapak@proxmox.com/T/#t https://lore.proxmox.com/pve-devel/20260310091141.814416-1-d.csapak@proxmox.com/T/#m47eaa3b51d88a1ecbb4b21401c6ad834ec9aaaf4 https://bugzilla.proxmox.com/show_bug.cgi?id=7386...

Hi @fettmasta . It sounds like you are using iscsiadm to establish the connection. Please keep in mind that there is nothing specific to PVE in the operations you are performing. PVE runs on a Debian userland with a Proxmox-maintained Linux kernel, and the iSCSI stack itself is a standard...

Here is a thread that may be helpful: https://forum.proxmox.com/threads/proxmox-ve-web-gui-is-a-blank-page.172804/ I used the following google search terms : proxmox reinstall web toolkit helper script Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

@Viper_Prime , it was not my intention to get into a "fight" through proxy with someone on discord before noon on Monday. #wget https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pve-install.sh #grep /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js...

Hi @choidazzi , welcome to the forum. One possibility is that someone used qm disk unlink (see man qm). This command can detach a disk from the VM while leaving the underlying volume on storage. There are likely other situations as well, simply because users occasionally come to the forum...

Great, feel free to mark this thread as Solved by editing the first post and selecting the appropriate prefix from the subject drop-down. This will assist in keeping the forum tidy. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I think it is possibly related to the code changes discussed here: https://lore.proxmox.com/pve-devel/DGZ5VVU45RP2.UJNEF7OMOJ0Q@proxmox.com/T/#t Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

One option that is always available to you is to contact the authors of the scripts and ask them for assistance. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thank you for letting the forum know. This is very helpful for the others as they run into similar issues. I am not aware of any. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The scripts put a "helpful" service that runs in the background and "fixes" your PVE installation every time it gets "unfixed". There are multiple threads about this on the forum, I don't have them saved - if I come across one I will place it here. You may be able to find the steps faster...

Did you previously install "PVE helper scripts" ? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

From the console of the PVE after you logged in via SSH? Perhaps you can share your configuration, i.e. "ip a", etc. standard list of questions: What is the IP of the PVE server? What is the IP of your workstation? What is the IP of your gateway? Can you ping the PVE server? Can you ssh into...

Check you router/firewall. Did you update the anything in your network? Try "curl" on your LAN IP as a confirmation. Try to direct connect a PC to your PVE to bypass your router. Users often report a case where they use an IP for PVE that is located within a DHCP range of their smart router...

This means that you are trying to delete a Virtual Disk/Image that matches the index ID of an existing VM. If you cannot see this disk in the VM hardware platform then you need to scan the disk in: qm disk rescan (man qm). Or, if you insist doing doing it manually, rename the disk to any other...

It is the iSCSI target that advertises the portals (where IPs are asigned). The iSCSI Target is the TrueNAS, so its the TrueNAS that informs the Initiator (PVE) about possible connection options (Portals). Your situation is described as one of the options here...

Hi @mouk , It's not just not cluster-safe, it's not supported by PVE and you have to go out of your way to work around all the bumpers put in place to stop you. There are a number of commercial vendors in this space. It all depends on your requirements, budget, and supportability needs...

You keep missing the point that the ZFS exists on the storage device side. The storage device, in your case Ubuntu, has a ZFS pool implemented by you, manually. You specify the name of that pool in PVE config to let PVE know what you named that pool. There is no formatting with ZFS happening...

ZFS over iSCSI in PVE is a specific scheme that implies: a) There is an external storage device b) You can login to this server via SSH as root (this excludes Dell, Netapp, Hitachi, etc) c) There is internal storage in that server (HDD, SAS, NVMe, etc) d) The raw devices inside this storage are...

PVE is trying to connect to all Portals that are advertised by iSCSI Target. There is no mechanism in PVE today that allows for filtering of the Portal connectivity. You may want to look at the Truenas side to see if there is anything you can do there. Blockbridge : Ultra low latency all-NVME...