On Sun, Sep 21, 2025 at 12:32:33PM -0700, Ron via GLLUG wrote:
Henrik Morsing via GLLUG wrote on 2025-09-21 11:57:
I'm a bit puzzled by Linux' (Debian) reluctance to assign a UUID
to / home. I even re-installed Debian with a smaller /home and I
have tried all the known tools for assigning a UUID to /home.
Nothing works
Which "known tools" have you tried? I believe the UUID is read-only
for a block device.
tune2fs and mke2fs were defintely tried.
Does the laptop find your intended /home in `ls -l /dev/disk/by-uuid`?
It does not:
root@laptop:~# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Sep 21 2025 3e79cbc6-22d3-4b7c-9da5-89f8f3ded61b ->
../../sdb5
lrwxrwxrwx 1 root root 10 Sep 21 2025 60F07CFFE675BC45 -> ../../sda2
lrwxrwxrwx 1 root root 10 Sep 21 2025 640F-F0C9 -> ../../sda1
lrwxrwxrwx 1 root root 10 Sep 21 2025 bf15ddf4-5d58-4048-a23f-36261dbbd60c ->
../../sdb1
root@laptop:~#
It's odd. Setting a UUID is silently ignored and blkid also ignores
the device.
The part about `blkid` ignoring the device is, indeed, odd.
I'd try booting a USB thumb drive to manually mount preferred /home on
/mnt/home to get the options and UUID (manually retrieved from
/dev/disk/by-uuid) and pay attention to any errors.
I have no problems mounting /home. I can find any option you are after.
Curious to hear how you solve this - please keep us posted.
It's strange why Debian does this on my laptop during two separate installs, first
one choosing separate /tmp/, /var & /home (var and tmp were both assigned U
UIDs), second one opting only for separate /home, and also strange that Google
indicates no-one else has this problem.
--
Regards,
Henrik Morsing
--
GLLUG mailing list
[email protected]
https://mailman.lug.org.uk/mailman/listinfo/gllug
