Basics

Resizing the LVM

LVM is quite complicated and need much knowledge to administer. This is just a quick glimpse into that.

Resize a LVM PVE Root

If you do not switch to the preferred ZFS at install, you end up using LVM storage. It gives a lot of storage to pve-data which is a volume-storage and not a lot for pve-root, and pve-root it’s where your file system is mounted. Proxmox doesn't need much space for pve-root. But sometimes it's too little.

You can check current situation by lvdisplay.

For example, if we want to resize our pve-data to be 200 GiB and also give pve-root the rest of the space, we can do it by do it as follows:

Remove the pve-data logical volume.

lvremove /dev/pve/data -y

Create the pve-date with new size

lvcreate -L 10G -n data pve -T

Allocate the remaining space to pve-root

lvresize -l +100%FREE /dev/pve/root

And then Resize pve-root

resize2fs /dev/mapper/pve-root

Check for Success

lvdisplay

Proxmox Markdown Guide

Markdown is a text-to-HTML conversion tool for web writers. It allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML). — John Gruber

UpSnap

Anyone who do remote work will have the need to start a remote machine at some point in their career. I'm using UpSnap in my Tailscale VM in Docker to perform WoL of some of the Servers. This VM is on an always on server and runs: Portainer, Tailscale and UpSnap.

Rice PVE Login and Banner

If you want to show Copyright and other warning or display system information in the Login or Banner Page, you definitely can do it.

Export/Import of ZFS Pools

Upgraded your server, but you need your old ZFS pools. How to import your olde files. Sometimes it's better to reinstall the Proxmox rather than trying to fix a broken system.