Search results

There are very few reasons, if ever, for a home-laber running on mini-pc to upgrade from a known stable kernel. Figuring out the reason would require Kernel bisect to find the differences, comparing modules across two kernels, possibly compiling an older Realtek driver, reaching out to Kernel...

Thats great to hear! Thank you for the update. If you edit your original post there should be a drop down near the subject to mark it solved. It makes the forum presentation more uniform (vs typing in prefix). Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

Hi @Nick Carter , welcome to the forum! I doubt there are many mental health professionals who visit proxmox forum, so I would not take anyone's diagnosis from here :-) Get 3 nodes in different locations and implement application level redundancy - do not create a bolt-on, latency-sensitive HA...

The NICs are Realtek. I know historically people have been having issues with Realtek based NICs and newer Kernels. Note that I have not followed this issue closely as I am not personally affected. Given that OP upgraded the system, perhaps a Kernel upgrade also came in. The quickest way is to...

Can you please explain what configuration you started with? What is the goal? Provide the requested information, as well as "qm config [vmid]". Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The first step is to review the output of: cat /etc/pve/storage.cfg pvesm status The two disks are located on different storage pools (local-lvm vs local-pbs). It is not strictly necessary to match the name of the disk to the index id of the VM. It certainly makes sense to do so from a hygiene...

Perhaps check this thread and the one referred in it: https://forum.proxmox.com/threads/solved-proxmox-8-0-rescue-boot-help-needed.132978/ Creating a vanilla Debian/Ubuntu rescue disk is also an option. There is nothing PVE specific in what you are trying to do. Blockbridge : Ultra low...

One other point - the output from "lsscsi" on server1 does not actually show two devices which would indicate a healthy multipath device. Your "multipath -ll" also shows single path. So although you now have an "mpath" device it may actually be in reduced functionality state and would not...

It would be incorrect to say that 7.0 "is not affected". It is affected but patches have been released. Including in the PVE distribution. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

We've been running our CI/CD for PVE9 with Kernel 7 since it was announced on the forum and have not had any issues. Note that our testing is targeted at storage functionality of the PVE. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

As it seems relevant here: We've been running our CI/CD for PVE9 with Kernel 7 since it was announced on the forum and have not had any issues. Note that our testing is targeted at storage rather than networking functionality of the PVE. Cheers Blockbridge : Ultra low latency all-NVME shared...

Proxmox is based on Debian Linux with a curated Ubuntu Kernel. The LVM is part of standard Linux implementation. There are no Proxmox-specific steps when dealing with LVM. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @iPanini , The qcow you found is likely NOT your VM. It seems to be located in your home directory. More than likely it is the installation download you got originally. The 2003 date of the file is another confirmation. The LVM error message indicates some metadata corruption that often...

Hi @ASM-Network , thank you for reporting back. I am glad to hear your issue is resolved. You can mark this thread as "SOLVED" by editing the first post and selecting the appropriate prefix from the subject dropdown. This helps in keeping the forum tidy, and assists future users. Cheers...

Hi @zero-skill, welcome to the forum. This has been covered a few times, for example: https://forum.proxmox.com/threads/joining-unlicensed-pve-node-to-cluster-that-is-licensed-what-happens.108160/post-465204 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

You did not configure your system properly. As you noted, you are not using shared storage functionality. There is no value in continuing to troubleshoot beyond this discovery. Your best course of action is to: remove all VMs remove all storage entries zap/wipe the disk configure everything from...

I think it would help if you share the /etc/pve/storage.cfg as well as "qm config [id]" output of the "old" and "new" VM. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Congrats on the new release! Great to see new security functionality! Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @angry_beaver , If I understood you correctly, you need to enable this attribute: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#:~:text=remote%20iSCSI%20server.-,saferemove,-Called%20%22Wipe%20Removed Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

As you can see in your output, server 2 does not see a Fujitsu device. This is most likely a zoning issue in Fujitsu. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox