Recent content by bbgeek17

  1. bbgeek17

    losing dirty-bitmaps during Live Migration

    Hi @aday , welcome to the forum. The journal line Cannot find device='z…' nor node-name='z…' on the target comes from the incoming dirty-bitmap migration: it couldn't find the block node the bitmap was attached to, so QEMU dropped the bitmap and let the migration finish normally. The z… names...
  2. bbgeek17

    data corruption on shared-lvm

    I'd recommend trying to reproduce this directly on the PVE host, bypassing the VM. Allocate a raw volume with pvesm alloc and test against the block device directly (or mkfs and mount it). My suspicion is that LVM doesn't clear extents on delete (with saferemove 0) or before reuse. Combined...
  3. bbgeek17

    Proxmox PVE will crash out when Win Server 2025 and MS SQL 2025 is used.

    Hi @eatonjb, welcome to the forum. The first thing I would check is the system log:journalctl. There may be some clues there. If the customer has to manually power-cycle the server, that may indicate that there are messages on the console. If a monitor is not currently connected, it may be...
  4. bbgeek17

    Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810

    Hi @mira, I’ll check with the developers on the current status. They are currently working through a number of existing deliverables, so this is in the queue but is not something I expect to be completed immediately. Since we have not seen this issue directly reported by our common...
  5. bbgeek17

    qcow2 file is bigger as hdd config

    You could try virt-sparsify on your file to see if that helps. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
  6. bbgeek17

    Error when trying to remove a previously physically removed node

    Sorry, I missed the forum name - that documentation/procedure is for the PVE Cluster. If you have collection of single nodes under PDM, take a look at this thread: https://forum.proxmox.com/threads/how-to-remove-node-from-remotes.163437/ Blockbridge : Ultra low latency all-NVME shared storage...
  7. bbgeek17

    Error when trying to remove a previously physically removed node

    Hi @bishoptf , Have you checked the cluster guide? https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_remove_the_cluster_node Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
  8. bbgeek17

    Feature idea: saferemove mode to skip forced zero-write (blkdiscard --zeroout) on storage that guarantees zero-after-discard (e.g. NVMe DLFEAT)

    Hi Mike, It's a good idea, but it's worth noting that discard has a rough history. SATA TRIM often didn't guarantee zeros, a bunch of drives corrupted data on queued TRIM and are still on the kernel blacklist, and arrays have been all over the place with UNMAP. NVMe cleaned some of that up with...
  9. bbgeek17

    Proxmox Virtual Environment now available for 64-bit ARM (arm64)!

    A new article for ARM system users covering performance troubleshooting Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
  10. bbgeek17

    [TUTORIAL] PVE 9.2 arm64 on ASUS GX10 (GB10): SoC throttled to 20 W, affecting performance

    Now that the system is "stable" after dealing with the black screen and the watchdog resets, we've started looking at performance. Our first look at storage performance was absolutely terrible. And after some head scratching, learning a bit more about why. It turns out, the machine was slow at...
  11. bbgeek17

    [TUTORIAL] Why LVM-Thin Cannot Be Shared Storage in Proxmox

    Hi @alexskysilk , you know I love a good bash loop, but ACL toggling is vendor-specific. It often only gates new logins, so an established session keeps writing until the target decides to drop it, and whether it does that on revoke is up to the array. lol, the only reason I'm replying is that...
  12. bbgeek17

    [SOLVED] 3rd party scripts question

    Hi @300cpilot, There is no official place to post third-party scripts. In this context, "official" generally implies that the material is endorsed or supported by someone in an authoritative capacity. Proxmox cannot reasonably endorse or support third-party scripts that it does not control...
  13. bbgeek17

    Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810

    Ok @huganega , I think we've figured this out. It takes a combination of things to trigger: - A link that's "fast" (i.e., 25GbE) relative to your CPU (Skylake or Cascade Lake) - A backup load running at full queue depth - An array that doesn't actively probe for TCP window updates The bug is a...
  14. bbgeek17

    Idempotence of ansbile modules

    A few comments about your observations: There is absolutely no "valid DNS name" requirement for a VM name in the PVE, cluster or solo. This is Ansible creator's choice, not Proxmox's. A clone creates an identical copy of a VM, resizing a disk is a completely separate operation. If some other...
  15. bbgeek17

    Idempotence of ansbile modules

    You should by all means discuss any concerns you have with PVE directly, either with Proxmox or a reseller during the pre-sales process. There is nothing inherently impossible about changing software architecture. Whether a particular change represents a worthwhile investment, and how it could...