Search results

First, I would normally expect two paths per lun. You are showing 2 individual LUNs that the OS only sees once. So while its ok to have Multipath sitting there, I do not think you actually have multipath. You already posted "multipath -ll" and it also appears to show single path per LUN...

@fba is correct. For several OS generations now, official cloud images have disabled password authentication by default. SSH key authentication is the standard. Beyond that, custom cloud-init is extremely powerful and can be used to customize virtually any aspect of the OS. Blockbridge: Ultra...

the originally attached VM config: scsi0: local-lvm2:vm-121-disk-1,size=1T The VM configuration you attached contains only one virtual disk/image - "scsi0". It is located on storage called "local-lvm2". You subsequently provided your storage configuration that shows: Which is a node-specific...

Hi Spirit, Thank you for your hard work! I especially appreciate how cleanly the feature is integrated, with no excess knobs or tunables. Great job by the whole team! We're aligned on the QEMU caching. Larger caches can help somewhat, but it's worth considering how the extra memory footprint...

I presume this isn’t a VM running on the same PVE host? From what you’ve described, you have two storage pools: iSCSI and LVM-Thin. One depends on the other, but PVE currently has no built-in way to declare that dependency. This creates a very likely race condition when bringing up storage...

Hi @caslanx , please note you must use the multipath device (mpath) and never the underlying sdX device. In your case it seems to be str01_pool_a_sssd. But, the device already contains VMFS structure and you do need to wipe the "mpath" device if you wanted to re-use it. You may be able to mount...

The allocation of disks (LVs) is not done manually, PVE does that automatically. However, it will likely produce the same error if you were to try to create a 100G VM disk via PVE GUI. Since we have no information about your current configuration - the warning you get may be appropriate for...

There are few times when using an older or common architecture is needed: - moving between Intel and AMD (never guaranteed to be seamless) - moving VM from newer Hypervisor CPU to Older. Absence of some flags/commands can cause OS crash - using specialized Os/App that relies on Architecture...

Hi @caslanx , welcome to the forum. This is the primary source of your issues. There is no such thing as iSCSI SAS cable. iSCSI is a storage protocol designed to run over TCP/IP. SAS is a point-to-point serial protocol for direct-attached storage, not something that runs over Ethernet or shares...

Keep in mind that the banner that shows "connect to this IP" at the console does not always reliably update. You should login via the console and confirm the IP "ip a". Sounds like you moved the PVE between different tenants, so your network interface could have changed. This requires a...

Hi Everyone, I'm excited to share a deep dive into one of the notable new feature in PVE9: the enhanced snapshot functionality designed for legacy SANs. This feature represents a meaningful step forward in expanding PVE's compatibility with traditional enterprise storage setups, something many...

Can you share your "/etc/pve/storage.cfg" ? Also, what is serving your iSCSI? Finally, what version of PVE are you running: pveversion -v Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @powersupport , Would you clarify your setup for me? You moved from local SSD to NFS hosted in a VM on ESX backed by spinning rust? At the very least, I’d suggest starting your fio testing inside the ESX VM. Your VM configuration file shows a single disk on storage called "local-lvm2". The...

Hi @Amila, welcome to the forum. To receive an official response from Proxmox GmbH, you should contact them directly via shop.proxmox.com. That said, your proposed architecture looks fine. Proxmox GmbH will likely support it as far as PVE is concerned. The storage connection itself is between...

It should start. Likely will be ok, as much as it can be on 7yo pc no, you should not run into issues. But if you were to use some other ARCH than host, you could. The 7yo PC will not support CPU commands introduced in younger generations. Use "host" Blockbridge : Ultra low latency all-NVME...

Hi @daus2936 , yes, of course. Please see this article for some guidance: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/ Best regards, Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Oh, the other easy workaround - use an IP in your PBS config. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

In Linux systems there is a specific order in which DNS resolution is done: cat /etc/nsswitch.conf|grep hosts hosts: files dns Each "service" is a caching device of a sort. The files (/etc/hosts) can cache your most used entry, the DNS service caches remote entries for TTL specified...

no, ZFS is not a cluster filesystem and is not suitable for multi-writer applications. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @Raja Sekhar , welcome to the forum. The best way to achieve your goal, based only on the information you supplied, is to use NFS over raw block SAN. Things become somewhat complicated if you are unable to use NFS. The standard use-case for block SAN is to provide a slice of the SAN to...