On 11/25/24 10:21, David Wright wrote: > On Mon 25 Nov 2024 at 10:07:35 (-0500), eben wrote: >> On 11/25/24 02:26, George at Clug wrote: >>> I would create a folder into which to mount the HD's relevant >>> partition, then used "blkid" to find the UUID and manually added a >>> mount point to "/etc/fstab". The resulting paths may be a bit ugly, >>> but I am lazy. >> >> I find PARTLABELs to be a lot more human-friendly than UUIDs. > > Can you put PARTLABELs on an MBR disk?
Ah, apparently you have to use LABEL, but otherwise yes, at least in fstab: eben@cerberus:~$ sudo fdisk -l /dev/sdc | grep label Disklabel type: dos eben@cerberus:~$ sudo blkid /dev/sdc1 /dev/sdc1: LABEL="Partition_1" UUID="ab7e9bee-27f4-4f4f-94c4-5d19d8413074" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b1604273-01" eben@cerberus:~$ grep Partition_1 /etc/fstab LABEL=Partition_1 /mnt/temp2 ext4 defaults,noauto 0 0 eben@cerberus:~$ mount | grep temp2 eben@cerberus:~$ sudo mount /mnt/temp2 eben@cerberus:~$ mount | grep temp2 /dev/sdc1 on /mnt/temp2 type ext4 (rw,relatime,stripe=8191) > (I'm not condoning such a disk. I'd take the opportunity to > switch to UEFI booting from a GPT SSD if that's possible. > Some explanation of the partitioning would be useful, rather > that slavishly copying them.) I repartitioned in GPT because the 4 partition limit in MBR without jumping through hoops made them hard to deal with. My motherboard doesn't boot in UEFI, but still.