Hi @F4R , welcome to the forum.
You need to "qm disk rescan --vmid 100" to bring the disk into VM configuration as "unused0". Then you can remove it from the VM hardware page.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox...
If someone is submitting a request via API they might as well use API to query the task status ;-)
pvesh get /nodes/$NODE/tasks --output-format json| jq -r '[.[] | select(.type == "clusterjoin")] | sort_by(.endtime) | .[-1] | .status'...
You can perform this directly from the console or via VNC.
From what you’ve described, you are following all the correct steps. No one else has reported a similar issue. Since your environment has not yet been fully excluded and there’s no...
As a temporary test/fix, given you can create VMs, build a Linux desktop one and try from there, if you can.
Install debsums and run it (apt install debsums), man debsums.
Depending on the result of the debsums run, you may still want to...
Hi @Charrat, welcome to the forum.
Other users in your situation reported that they were able to restore functionality once the automated patching was removed, and proper packages were reinstalled. So it seems like that should be a possibility...
You have a possible race where "pvesm" status is possibly not yet propagated to PVE cluster view.
I've asked Claude to help you, obviously I have not tested this for you.
Good luck
#!/bin/bash
# ─── CONFIG...
I think OP is likely in a situation where their hypervisor hosts do not have significant internal storage. They, or their customers, already own an entry- to mid-level SAN solution and want to maximize ROI from it. Typically, people in this...
It is possible that OP did not permission the user/token properly. A quick way to check is to run:
curl -k \
-H "Authorization: PVEAPIToken=<USER>@<REALM>!<TOKENID>=<SECRET>" \...
There are 3 disks in the VM, they have different ctime's. The value is the same across API responses for corresponding disks.
That said, OP should use the latest Veeam "agent"/patch for PVE. And make sure that the PVE version is in the supported...
You can mark the thread as SOLVED by editing the first post and selecting an appropriate subject prefix.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
@bbgeek17
Thank you for your reply
You're right, can check in task list, the job is skipped (recenlty verified). It means the job was executed but it didn't re-verify.
I tried with the option ignore-verified=true, but it is still skipped.
I...
Adding a Hyper-V–based PVE host just for quorum is short-sighted. You are introducing additional, unnecessary, management overhead:
Storage pools will now need to be restricted to specific nodes.
If you add NAS storage later and do not restrict...
Hi @pbujarbarua , welcome to the forum.
You should use the OS that fulfills your goal requirements.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
It is an appropriate way to achieve your goal.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Short of authentication, permission, or syntax error the API calls do not return failures. The task can be long running and the fact that you submitted it is not a success yet. You need to query task status to determine its state.
A quick check...
Try to find a workstation with a different browser. Try incognito mode. Create a VM via CLI, install a more modern browser and try from there.
You mentioned in your original post that you have been changing permissions. That may be a red...
Downgrading is not supported, or recommended. It's a manual task that is quiet advanced, and can completely break your system.
Is this a business production environment?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...