Search results

Hi @zahmad , As a suggestions : please use CODE tags available from the toolbar of the editbox, they make your post much easier to use. No, neither mandatory nor needed. PVE central lock management is taking care of those responsibilities. Blockbridge : Ultra low latency all-NVME shared...

It does reference the newer article. Additionally, there is some useful information here: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/#understand-multipath-reporting-for-your-device Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

I don't believe the service was ever called "multipath-tools". It may be a package name, but the service has always been "mutipathd". You can check via : systemctl|grep multipath Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @tessierp , You are confusing an attribute that declares to PVE that the storage is already shared with actually creating shared storage. Please read the following paragraph: https://pve.proxmox.com/pve-docs/chapter-pvesm.html#:~:text=guest%20hook%20scripts-,shared,-Indicate%20that%20this...

Sounds like you are on the right path. Remove the PVE storage entry, unmount the disk, find and remove the automatic mount (fstab?). This should unstuck the PVE. You can then try to mount the disk and save the data prior to throwing the disk into a bin. Cheers PS It could, theoretically, be...

You don't normally run "pvestatd" directly. Based on the log snippet , one of your disks is failing and possibly tripping the daemon. Examine your /etc/pve/storage.cfg, save the file, then remove all non-essential entries. Or, if you know the entry using "sdb" - start with that one. Good...

Continue troubleshooting with the commands @shanreich is providing you. You've had a failed upgrade and the software is not properly installed Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

You need to also: echo "nameserver 8.8.8.8" > /etc/resolv.conf Additionally, now that you've set the IP - you should be able to SSH into the host and collect/provide text output, rather than literal screen shots. Also, check the date/time of your system and fix it if its off: date -s...

Great, you can mark this thread as solve to help others by editing first post and changing the prefix of the subject via drop-down The important line change is likely: machine: pc-i440fx-8.1 | machine: pc-i440fx-10.0 Blockbridge : Ultra low latency...

Hi @bluezeta , Yes there are ways to do this. Which one to pick depends on your prior storage configuration (LVM, ZFS, etc). There are more than a few articles covering various configuration, you should review them...

While your symptoms are similar, the cause is likely not the same. I'd recommend opening your own thread. There you should add output of "cat /etc/network/interfaces" Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I suspect that the old VM is still running under old QEMU binary and needs a cold start. Perhaps someone from Proxmox staff will confirm and will add this as a caveat. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I've posted a recommendation there - give it a try as well. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Is this a VM that existed before upgrade? If yes, post it's configuration here: qm config Also, try to create a new VM (it does not have to have an OS), turn it on and try to snapshot. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Looks like your report may be related to: https://forum.proxmox.com/threads/lvm-thick-with-iscsi-pve-9-0-3.169319/#post-788971 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @vitamin-pxx , The possible issue is the failure to mount your "hdd" to /mnt/pve. You may need to boot into rescue mode and disable the mount service. Or investigate why that mount fails, perhaps you disconnected your disk? Blockbridge : Ultra low latency all-NVME shared storage for...

Hi @xbluethunderx , No one else has reported a similar issue recently, so this appears to be specific to your environment. That said, you’re making solid progress in narrowing down the combination of factors causing the fault, I'd encourage you to keep pursuing that line of investigation...

There is likely a lot of useful data in the system's log/journal: journalctl -b0 You may also get some info from "systemctl status [service-name]" You can slo zoom in on a particular service: journalctl -xe -u <service-name> Since you have a system-wide failure, the cause is likely...

No problem. Feel free to mark this thread SOLVED by editing your initial post and selecting the drop-down next to subject. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Are you asking about storage? That selection is two "Next" clicks later, under "Disks" tab. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox