So I have a 4TB NVME SSD in my Pi5 + NVME Base setup. It's great and wicked fast except...
When i imaged the drive there were no volume options, except for one teensy weensy problem...
Everything is in /boot and /, no other volumes. Not a problem per se in a personal device, but certainly NOT how I am used to seeing a Linux system divided up... But even more importantly, of my 4TB drive, only 2TB was actually configured...
It is going to take a while to fill /home in that 2TB volume, but I would actually like to extend the /partition to the full 4TB OR slice out maybe 120GB for the system, logs etc... and just slice the remainder out for /home...
Just to note, the Pi is being used a s a mobile multimedia workstation so it will have a mess of video and audio clip files.
So where does LVM come into it?
The installation method and install are different to a standard Linux install on x86.
The image gets written to the target device replacing all of its contents*. On initial boot it is resize to fill the available space subject to limitations imposed by MBR partition tables.
Personally though because of the nature of an OS (re)install on PI I'd keep the OS and data on separate physical devices. Not just separate partitions. Or, worse, keeping it all in the root (/) partition.
I've no idea if LVM can cope with FAT32 partitions but I very much doubt the bootloader can cope with LVM. If you want your root partition on LVM you'll need a custom kernel or custom initramfs as IIRC LVM is not built into the kernel and the module is not included in the default initrd.
Or you could just create a third primary partition and mount it somewhere.
Or keep the boot partition on SD then reconfigure the NVMe drive with a GPT partition table and 4TB partition and copy the contents of the root partition to it. You'll need to update cmdline.txt and /etc/fstab on the NVMe drive if you got this route.
Statistics: Posted by thagrol — Sun Apr 21, 2024 2:02 am