Hi @Niraat , this is a good example why one should be careful with assigning VMs as HA resources, i.e. not having local disks.
Is the VM currently stopped? qm status 109
Does the original host have the referenced disks? (pvesm list local-lvm)...
Alright,
NFS, migration, ESXi, network - all of that is extraneous and not related to your problem.
It really boils down to this: you have a RAID-backed LVM group, and you’re not happy with its performance inside the VM. It didn’t get worse -...
Hi @wifi75 ,
This does not seem to be PVE specific and there are a few discussions online about the warning:
https://askubuntu.com/questions/1299499/warning-pv-dev-sda3-in-vg-ubuntu-vg-is-using-an-old-pv-header-modify-the-vg-t...
Hi @dan.ger ,
Are you able to SSH/CURL directly from PVE host into itself at the time when the issue manifests? What about between PVE hosts?
I.e.: ssh root@localhost ; ssh root@LAN_IP ; ssh root@pve-02; curl -k https://localhost:8006 ; etc
The...
Yes, your physical disk (sda) is failing. It could be a bad cable, a faulty motherboard slot, or even a power issue, but most likely it’s simply a dying disk.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Hi @powersupport ,
It's been a while since I looked at this thread due to being away. It seems the last deliverables are for you to clarify your setup and retest at all points to establish the baseline.
After giving the original post another...
Hi @thewrath009 , welcome to the forum.
Your output shows that the interface has no link. Are you sure the cable is plugged in? Into the right port? Is the cable itself working? Have you checked the link light on the NIC?
It’s possible you have...
Hi @deepakvidyadharan , welcome to the forum.
One way to find the answer to your question is to check the code:
root@pve-1:/usr/share/perl5/PVE# grep -R mac|grep prefix
...
DataCenterConfig.pm: if ($mac_prefix !~...
Thank you for sharing your findings. The "community" scripts are indeed number one cause of GUI breakage in 99% of reports.
In fact, this ^ was pretty much the guarantee that the scripts were the cause.
Blockbridge : Ultra low latency all-NVME...
You missed "debsums -c" request.
What does "pveversion --verbose" show?
You can also try to force reinstall all pve* and proxmox* packages in the list above.
The starting point is that there are hundreds of thousands of users for whom PVE...
You are welcome. You can mark the thread solved, to help with forum presentation, by editing your first post and selecting "SOLVED" next to the subject.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
There are a few reasons to keep the disks:
- you don't trust the migration process and want to have that last backup
- you want to do a test and then throw away any changes on new storage
- you want to re-use the old data in some way
None of the...
Hi @cypherfox , the cloud-init file can be in many different formats: yaml, shell, etc. Merging different styles and formats is complicated and is simply not worth it.
As you found, using an external orchestrator like TF to drive VM creation...
The dump command does not consider your custom files. It will only output built-in values, regardless of whether there is an overriding custom setting.
The idea might be that you already have access to custom files, but may want to look at what...
Hi @cypherfox, welcome to the forum!
Thanks for sharing your experience, I’m sure it will be useful for others working with cloud-init.
My own experience has been a bit different: when using a custom cloud-init file, the internal (GUI)...
The issue is not the same, but some of the commands and troubleshooting steps are applicable.
So you had a pre-existing broken installation and hoped that an upgrade might fix it but it didn't?
Have you, by chance, used one of the community...
Technically this is a one-liner:
for node in $(pvesh get /nodes --output-format=json | jq -r '.[].node'); do for vmid in $(pvesh get /nodes/$node/qemu --output-format=json | jq -r '.[].vmid'); do pvesh get /nodes/$node/qemu/$vmid/config...