Bug#1116325: Some more info about the missing UUID, etc

[Andy Smith]

Hi,

Not to speak for OP but OP had previously discussed this at:

    https://mailman.lug.org.uk/pipermail/gllug/2025-September/083705.html

and we didn't find a solution.

In that thread it was established that OP was able to find the UUID on
the block device of their /home using tune2fs:

# tune2fs -l /dev/sda6 | grep UU
Filesystem UUID:          23ba8ae2-5f38-43e7-959a-8495f6889302

Yet "lsblk" and "udevadm info" knew very little about it:

root at laptop:~# lsblk --fs
NAME   FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat   FAT32       640F-F0C9
─sda2 ntfs         Vida  60F07CFFE675BC45
sdb
├─sdb1 ext4   1.0         bf15ddf4-5d58-4048-a23f-36261dbbd60c    5.2G    51%  /
├─sdb2
├─sdb5 swap   1           3e79cbc6-22d3-4b7c-9da5-89f8f3ded61b                 [SWAP]
└─sdb6                                                           87.7G     1% /home

root at laptop:~# udevadm info --query=property --name=/dev/sdb6 | grep -E "LABEL|UUID|DEVLINKS"
ID_PART_TABLE_UUID=a1771adb
DEVLINKS=/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0-part6 /dev/disk/by-diskseq/2-part6 /dev/disk/by-id/wwn-0x50026b766b039cd2-part6 /dev/disk/by-path/pci-0000:00:1f.2-ata-2-part6 /dev/disk/by-path/pci-0000:00:1f.2-ata-2.0-part/by-partnum/6

(These outputs are from OP's emails in that thread, not my own; I have
never experienced this. But I thought these questions are likely going
to come up pretty quickly.)

Thanks,
Andy