Directory located on a distinct storage device...
Directory located on a distinct storage device...
I'm uncertain about whether this was previously noted as a caution if you're using systemd. If not, please ensure you don't rely solely on it; otherwise, systemd will automatically detect and scan for GUIDs of partitions. When partitioning the drive correctly, you can still use (c/s)gdisk at any time without data loss. For example, with an NVMe layout like my first one, even if /home isn't defined, choosing 8302 or 8312 as the type will still mount it to /home, and many GUIDs don’t require entries in fstab. This might not be ideal if you prefer not to have /home mounted but still want a corresponding GUID. Additionally, the filesystem you select must be enabled in the kernel or installed as a module for fstab to work. Most agree UUIDs are preferred, except for me who find them meaningless. Instead, I label all my filesystems with a unique label—if you're careful, duplicates should be avoided. For those without labels, cgdisk can set a PARTLABEL that works in fstab. You can locate partitions by their label in /dev/disk/by-label/ or /dev/disk/by-partlabel/, and include them in fstab (for instance: if using NTFS directories, you may need to use ntfs3 driver; most distros come with ntfs-3g, but support can be limited).
You're considering opening fstab via the Linux shell on the lock screen. While you can set drives in fstab, the approach you tried earlier led to problems. After a full reset, it didn't work twice, which makes you cautious. Since I don’t have access to the system right now beyond the operating system, I’m willing to explore more experimental methods.