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...
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...
7.0 already contained the relevant commit upstream prior to it being cut:
https://git.kernel.org/linus/a664bf3d603dc3bdcf9ae47cc21e0daec706d7a5 (7.0-rc7)
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 -...
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...
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...
Since you didn't mentioned it: Do you have a qdevice in your cluster? Otherwise you might run into a split-brain-situation: https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_external_vote_support
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 -...
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...
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...
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...
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...
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...
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
Hi @ofry770 , welcome to the forum.
In my experience with running nested ESXi in KVM/Openstack - the driver handling the vmxnet3 type adapter is intentionally limited by VMware in MTU handling. In fact the behavior varies across various patch...
Please use CODE tags, available in the edit box menu. It makes reading large configuration blocks easier.
Before Multipath can form, the server needs to see raw block devices. Those should be listed via:
lsblk
lsscsi
Are the outputs the same...
Hi Stefan, the most likely reason is that the 2nd server is not configured properly in one way or the other.
However, that is based only on your brief report. If you provide some system information from both servers, perhaps a better suggestion...
There may be a time limit. It has been quiet a while since your original post.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox