Hi
This "unreadable (pending) sectors" is a sign of a bad drive. You are using consumer drives and this is expected. Even I have seen this with consumer drives, I have tried using the Crucial MX500 series as boot drives and did not have a great experience with a mirrored setup, you keep them as...
like i need to do ---
mokutil --import /usr/share/nvidia/nvidia-modsign-crt-DAE5E38B.der
or
mokutil --import /var/lib/dkms/mok.pub
The guide is not nvidia specific but generic from a dkms signing perspective, something more specific would be more helpful
Sorry for my late reply, i was busy with something else, I am fully confused seeing this post. In my understanidng the post is to sign the boot files during upgrade from 8 to 8.1.
Can somebody give me the list of commands to be run, I don't want to break a working cluster as it's a 3 node...
Hi Folks,
Got Proxmox 8.1 Running with Secure Boot and CEPH, added an Nvidia A40 GPU, this supports vGPU
was following the below guide - i dont need vgpu-unlock as its a supported card.
https://gitlab.com/polloloco/vgpu-proxmox
iommu is enabled - verified by below command...
I created a fresh Windows 2019 VM now and did updates, and it consumed about 20 GB space, also reflected by ceph usage.
I downloaded a 10 GB DVD ISO image and the utilization jumped to 37 GB in ceph (why 37G and not 30G is a different story), now I deleted this image but the ceph utilization...
We made a test VM, with 13 GB utilization in it - Windows Server 2022
checked the space in the ceph
copied some 2GB of data into it.. now it reports
I deleted the copied data to verify its usage, but no impovement, it still reports 15GB
I ran disk optimisation inside the OS to trim...
I have installed Proxmox 8.1 and updated it with the enterprise repo too so I am on the latest stable updates version of packages.
I have installed a few VM and I noticed the below messages on the console like the below.
kvm_amd: kvm [processid]: vcpu0 guest rIP: 0xfffff8e8f14d08e6 Unhandled...
Hello,
We have a strange issue, the vm was not starting and kept giving errors.
we did a
#rbd cp RBD-ceph/vm-3242-disk-0 RBD-ceph/vm-3242-disk-1
- this worked - took 15-min and copied the volume data over.
and made a manual change in the /etc/pve/qemu-server/3242.conf and changed the...
Hello folks,
We have a proxmox cluster running ver. 7.4 - not yet upgraded to 8.1 - will do shortly after we resolve the ceph issue.
Its a 4 node cluster with ceph on 3 nodes. with 6.4TB NVME * 2 for each host for ceph osd. means total of 6.4TB * 6 drives in the pool.
3 way replicated with 2...
Hi Folks,
Congrats on the release of release 8.1
Now that we have Proxmox 8.1 supporting Secure boot, I understand that we can certainly have secure boot enabled and have a clean install of Proxmox 8.1
But what about a upgrade to Proxmox 8.1, I don't think going into the bios and enabling...
Yes Sir, I do have a subscription for the full cluster.
E: The repository 'https://enterprise.proxmox.com/debian/ceph-reef bookworm Release' does not have a Release file.
But still get the error. Concerned about this below...
Err:10 https://enterprise.proxmox.com/debian/ceph-reef bookworm...
Hi Folks,
Congrats on the new release of Proxmox 8.1
was following the below guide to upgrade from Quincy to Reef
https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef#Important_Release_Notes
# apt update
Hit:1 https://packages.wazuh.com/4.x/apt stable InRelease
Hit:2 http://ftp.debian.org/debian...
Hi Folks,
We are on a enterprise repo (just want to inform that we are on tested stable repo) but faced the below screenshot, want to know if its a proxmox issue or a hardware issue.
node was pinging but - not able to ssh or communicate with the host, but a few vm inside were working...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.