I've learned a lot more about LVM in the past couple of days than I used to know :)
Do I lose any functionality by treating them as different storages?
I don't get that option, just the target node (maxiserver).
There is an option under maxiserver "local-lvm", but right know the status is unknown. I can fix this by changing vgname in /etc/pve/storage.cfg from "pve" to "maxiserver-vg" but then the "local-lvm" in my other node, miniserver, gets...
I reinstalled and configured everything in the Debian installer, now I just have the problem that my VG isn't named PVE (see my new thread).
This is an odd one, because it freezes the entire machine during the EFI screen boot picker (doesn't even reach it if the USB is plugged in during boot)...
When I try to migrate a VM between Nodes I get the follow error: "ERROR: found stale volume copy 'local-lvm:vm-102-disk-0' on node 'maxiserver'"
I think that most likely the issue is that node 1 has a VG with name "pve" and node 2 has a VG with name "maxiserver-vg"
What is the easiest way to...
Yeah I got my system into read only mode so I'll just reinstall when I'm home.
What steps do I need to follow to during the Debian installation so I already create the data LV for when I convert the install to Proxmox?
Or is there any easy fix to get the installer to boot on the mini?
I managed to reduce the Root LV file size by 400G using lvreduce. However now I can't create a new LV as it gives me " Cannot archive volume group metadata for maxiserver-vg to read-only filesystem."
I've been looking at this for a while now and I can't wrap my head around adding a new LV for the Local-LVM thin-pool (if I understand correctly this is what I need to do).
The reason I installed Proxmox over Debian is because the Proxmox installer freezes my 2010 Mac Mini's EFI (doesn't happen...
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.