Proxmox🔗

In addition to being a hypervisor, it is also used for storage hosting.
One could argue that there should be a dedicated NAS or at least a VM running a NAS OS, but I have it set up as a RAID 0 ZFS storage for my media stack - yolo. I don't think there's a need to migrate to another OS, or if I did, it would probably be a TrueNAS Scale VM.

Configuration🔗

Here is what I have done; it doesn't mean you have to follow it.

Proxmox commands to run post-install🔗

zfs set compression=lz4 rpool

systemctl disable ksmtuned cronosync pve-ha-lrm.service corosync.service pve-firewall.service pvefw-logger.service pvefw-logger.service pve-ha-crm.service

Creating a storage pool🔗

Create the pool as a Single Disk via CLI, because the GUI doesn't offer this option

zpool create yourpoolname /dev/disk/by-id/your-sdb-identifier /dev/disk/by-id/your-sdc-identifier

After creating the pool, change the compression to lz4:

zfs set compression=lz4 POOL-NAME

Limiting Arc🔗

Limit the ARC, info can be found here - https://pve.proxmox.com/wiki/ZFS_on_Linux

echo "$[2 * 1024*1024*1024]" >/sys/module/zfs/parameters/zfs_arc_max

Create the mount point via the GUI so it becomes a subvol:

mp0: HDD-pool:subvol-101-disk-1,mp=/root/media-compose/media,size=965G

Changing VMID name🔗

If you ever need to change a VMID - https://www.youtube.com/watch?v=uLA3fCdK1Bk
cd /etc/pve/nodes/PROX-NAME/qemu-server or /lxc
For example: cp 100.conf 200.conf
Edit the contents of the conf file so that the disk also uses the new ID number
cd /dev/pve/
lvrename /dev/pve/vm-100-disk-0 /dev/pve/vm-200-disk-0
And if there are multiple disks, you must repeat this for each disk