short and long uuids under /dev/disk/by-uuid The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsLinux Mint: drives' map changing at reboot brings fstab errorUUID Of A drive that won't show up in /dev/disk/by-uuid or blkidHow to convert grub config to use kernel device names instead of UUID/dev/disk/by-uuid/ not working on one machineExternal disk partitions with identical UUIDsreference whole disk (/dev/sda) using UUIDIs UUID really unique? why can we assign multiple UUIDs to single slice of diskhow can I see the uuid of a disk in my system WHEN IS NOT LISTED IN /dev/disk/by-uuidHow do I add /home to arch with uuid if I messed up while installing?I have a dedicated with 2 SSDs, how to I group them to behave as 1?
Simulating Exploding Dice
How to prevent selfdestruct from another contract
Keeping a retro style to sci-fi spaceships?
Relations between two reciprocal partial derivatives?
Can a novice safely splice in wire to lengthen 5V charging cable?
Why does concentrated shear force on a beam influence the whole beam?
Does the AirPods case need to be around while listening via an iOS Device?
How are presidential pardons supposed to be used?
Word for: a synonym with a positive connotation?
Make it rain characters
How does this infinite series simplify to an integral?
Problems with Ubuntu mount /tmp
Synthesis of a weinreb amide from an acid
He got a vote 80% that of Emmanuel Macron’s
How can I define good in a religion that claims no moral authority?
Finding the path in a graph from A to B then back to A with a minimum of shared edges
Why can't devices on different VLANs, but on the same subnet, communicate?
Mortgage adviser recommends a longer term than necessary combined with overpayments
Do warforged have souls?
How many people can fit inside Mordenkainen's Magnificent Mansion?
University's motivation for having tenure-track positions
system call string length limit
How to pronounce 1ターン?
Semisimplicity of the category of coherent sheaves?
short and long uuids under /dev/disk/by-uuid
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election ResultsLinux Mint: drives' map changing at reboot brings fstab errorUUID Of A drive that won't show up in /dev/disk/by-uuid or blkidHow to convert grub config to use kernel device names instead of UUID/dev/disk/by-uuid/ not working on one machineExternal disk partitions with identical UUIDsreference whole disk (/dev/sda) using UUIDIs UUID really unique? why can we assign multiple UUIDs to single slice of diskhow can I see the uuid of a disk in my system WHEN IS NOT LISTED IN /dev/disk/by-uuidHow do I add /home to arch with uuid if I messed up while installing?I have a dedicated with 2 SSDs, how to I group them to behave as 1?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
There are several hard disk partitions my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux) is working with:
bejo@josDeb:~$ ls -l /dev/disk/by-uuid
yields:
total 0
lrwxrwxrwx 1 root root 10 Apr 13 16:20 00FB-604A -> ../../sdb1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 4425-7572 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 8dc07aba-5729-4525-883f-09c32d1a9e98 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 13 16:19 95a8efff-92d2-4e31-8632-bf7a640e100f -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 13 16:19 f5a05b5e-c3ed-4227-bb62-fe4576b72643 -> ../../sda4
Some partition uuids are long - some are short. I would like to understand why. I thought, uuids always have 16 bytes. How come I have uuids of different sizes?
disk block-device uuid
add a comment |
There are several hard disk partitions my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux) is working with:
bejo@josDeb:~$ ls -l /dev/disk/by-uuid
yields:
total 0
lrwxrwxrwx 1 root root 10 Apr 13 16:20 00FB-604A -> ../../sdb1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 4425-7572 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 8dc07aba-5729-4525-883f-09c32d1a9e98 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 13 16:19 95a8efff-92d2-4e31-8632-bf7a640e100f -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 13 16:19 f5a05b5e-c3ed-4227-bb62-fe4576b72643 -> ../../sda4
Some partition uuids are long - some are short. I would like to understand why. I thought, uuids always have 16 bytes. How come I have uuids of different sizes?
disk block-device uuid
add a comment |
There are several hard disk partitions my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux) is working with:
bejo@josDeb:~$ ls -l /dev/disk/by-uuid
yields:
total 0
lrwxrwxrwx 1 root root 10 Apr 13 16:20 00FB-604A -> ../../sdb1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 4425-7572 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 8dc07aba-5729-4525-883f-09c32d1a9e98 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 13 16:19 95a8efff-92d2-4e31-8632-bf7a640e100f -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 13 16:19 f5a05b5e-c3ed-4227-bb62-fe4576b72643 -> ../../sda4
Some partition uuids are long - some are short. I would like to understand why. I thought, uuids always have 16 bytes. How come I have uuids of different sizes?
disk block-device uuid
There are several hard disk partitions my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux) is working with:
bejo@josDeb:~$ ls -l /dev/disk/by-uuid
yields:
total 0
lrwxrwxrwx 1 root root 10 Apr 13 16:20 00FB-604A -> ../../sdb1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 4425-7572 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 13 16:19 8dc07aba-5729-4525-883f-09c32d1a9e98 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 13 16:19 95a8efff-92d2-4e31-8632-bf7a640e100f -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 13 16:19 f5a05b5e-c3ed-4227-bb62-fe4576b72643 -> ../../sda4
Some partition uuids are long - some are short. I would like to understand why. I thought, uuids always have 16 bytes. How come I have uuids of different sizes?
disk block-device uuid
disk block-device uuid
edited 4 hours ago
bejo
asked 4 hours ago
bejobejo
386
386
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Actual UUIDs are supposed to be 128-bit long and meant to be unique. Prior to this, various systems provided various serial numbers of various size to be distinguishable. So Linux just takes whatever serial it can find and sticks them in the /dev/by-uuid/ directory even if they aren't matching the UUID definition. That's the case for the FAT32 volume ID:
Sector offset FAT32 EBPB offset Length (bytes) Contents
0x043 0x38 4 Cf. 0x027 for FAT12/FAT16 (Volume ID)
Historical description:
Volume ID (serial number)
Typically the serial number "xxxx-xxxx" is created by a 16-bit
addition of both DX values returned by INT 21h/AH=2Ah (get system
date)[nb 7] and INT 21h/AH=2Ch (get system time)[nb 7] for the high
word and another 16-bit addition of both CX values for the low word of
the serial number. Alternatively, some DR-DOS disk utilities provide a
/# option to generate a human-readable time stamp "mmdd-hhmm" build
from BCD-encoded 8-bit values for the month, day, hour and minute
instead of a serial number.
This is a 32 bits value, which can be displayed for example as 4425-7572. Most likely those two partitions are EFI System partitions since they have to be FAT32.
You can get better informations (probably coming from parsing several /dev/disks/by-*/ entries) with the blkid command instead:
# blkid
or limited to those short entries:
# blkid /dev/sda1 /dev/sdb1
The manual suggest to use lsblk instead which doesn't require root. So with the right options that would be lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1.
E.g. here:
$ lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID FSTYPE
sda1 8:1 0 200M 0 part /boot/efi 1234-5678 vfat
sdb1 8:17 1 200M 0 part 9ABC-DEF0 vfat
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
3 hours ago
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
3 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f512283%2fshort-and-long-uuids-under-dev-disk-by-uuid%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Actual UUIDs are supposed to be 128-bit long and meant to be unique. Prior to this, various systems provided various serial numbers of various size to be distinguishable. So Linux just takes whatever serial it can find and sticks them in the /dev/by-uuid/ directory even if they aren't matching the UUID definition. That's the case for the FAT32 volume ID:
Sector offset FAT32 EBPB offset Length (bytes) Contents
0x043 0x38 4 Cf. 0x027 for FAT12/FAT16 (Volume ID)
Historical description:
Volume ID (serial number)
Typically the serial number "xxxx-xxxx" is created by a 16-bit
addition of both DX values returned by INT 21h/AH=2Ah (get system
date)[nb 7] and INT 21h/AH=2Ch (get system time)[nb 7] for the high
word and another 16-bit addition of both CX values for the low word of
the serial number. Alternatively, some DR-DOS disk utilities provide a
/# option to generate a human-readable time stamp "mmdd-hhmm" build
from BCD-encoded 8-bit values for the month, day, hour and minute
instead of a serial number.
This is a 32 bits value, which can be displayed for example as 4425-7572. Most likely those two partitions are EFI System partitions since they have to be FAT32.
You can get better informations (probably coming from parsing several /dev/disks/by-*/ entries) with the blkid command instead:
# blkid
or limited to those short entries:
# blkid /dev/sda1 /dev/sdb1
The manual suggest to use lsblk instead which doesn't require root. So with the right options that would be lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1.
E.g. here:
$ lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID FSTYPE
sda1 8:1 0 200M 0 part /boot/efi 1234-5678 vfat
sdb1 8:17 1 200M 0 part 9ABC-DEF0 vfat
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
3 hours ago
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
3 hours ago
add a comment |
Actual UUIDs are supposed to be 128-bit long and meant to be unique. Prior to this, various systems provided various serial numbers of various size to be distinguishable. So Linux just takes whatever serial it can find and sticks them in the /dev/by-uuid/ directory even if they aren't matching the UUID definition. That's the case for the FAT32 volume ID:
Sector offset FAT32 EBPB offset Length (bytes) Contents
0x043 0x38 4 Cf. 0x027 for FAT12/FAT16 (Volume ID)
Historical description:
Volume ID (serial number)
Typically the serial number "xxxx-xxxx" is created by a 16-bit
addition of both DX values returned by INT 21h/AH=2Ah (get system
date)[nb 7] and INT 21h/AH=2Ch (get system time)[nb 7] for the high
word and another 16-bit addition of both CX values for the low word of
the serial number. Alternatively, some DR-DOS disk utilities provide a
/# option to generate a human-readable time stamp "mmdd-hhmm" build
from BCD-encoded 8-bit values for the month, day, hour and minute
instead of a serial number.
This is a 32 bits value, which can be displayed for example as 4425-7572. Most likely those two partitions are EFI System partitions since they have to be FAT32.
You can get better informations (probably coming from parsing several /dev/disks/by-*/ entries) with the blkid command instead:
# blkid
or limited to those short entries:
# blkid /dev/sda1 /dev/sdb1
The manual suggest to use lsblk instead which doesn't require root. So with the right options that would be lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1.
E.g. here:
$ lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID FSTYPE
sda1 8:1 0 200M 0 part /boot/efi 1234-5678 vfat
sdb1 8:17 1 200M 0 part 9ABC-DEF0 vfat
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
3 hours ago
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
3 hours ago
add a comment |
Actual UUIDs are supposed to be 128-bit long and meant to be unique. Prior to this, various systems provided various serial numbers of various size to be distinguishable. So Linux just takes whatever serial it can find and sticks them in the /dev/by-uuid/ directory even if they aren't matching the UUID definition. That's the case for the FAT32 volume ID:
Sector offset FAT32 EBPB offset Length (bytes) Contents
0x043 0x38 4 Cf. 0x027 for FAT12/FAT16 (Volume ID)
Historical description:
Volume ID (serial number)
Typically the serial number "xxxx-xxxx" is created by a 16-bit
addition of both DX values returned by INT 21h/AH=2Ah (get system
date)[nb 7] and INT 21h/AH=2Ch (get system time)[nb 7] for the high
word and another 16-bit addition of both CX values for the low word of
the serial number. Alternatively, some DR-DOS disk utilities provide a
/# option to generate a human-readable time stamp "mmdd-hhmm" build
from BCD-encoded 8-bit values for the month, day, hour and minute
instead of a serial number.
This is a 32 bits value, which can be displayed for example as 4425-7572. Most likely those two partitions are EFI System partitions since they have to be FAT32.
You can get better informations (probably coming from parsing several /dev/disks/by-*/ entries) with the blkid command instead:
# blkid
or limited to those short entries:
# blkid /dev/sda1 /dev/sdb1
The manual suggest to use lsblk instead which doesn't require root. So with the right options that would be lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1.
E.g. here:
$ lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID FSTYPE
sda1 8:1 0 200M 0 part /boot/efi 1234-5678 vfat
sdb1 8:17 1 200M 0 part 9ABC-DEF0 vfat
Actual UUIDs are supposed to be 128-bit long and meant to be unique. Prior to this, various systems provided various serial numbers of various size to be distinguishable. So Linux just takes whatever serial it can find and sticks them in the /dev/by-uuid/ directory even if they aren't matching the UUID definition. That's the case for the FAT32 volume ID:
Sector offset FAT32 EBPB offset Length (bytes) Contents
0x043 0x38 4 Cf. 0x027 for FAT12/FAT16 (Volume ID)
Historical description:
Volume ID (serial number)
Typically the serial number "xxxx-xxxx" is created by a 16-bit
addition of both DX values returned by INT 21h/AH=2Ah (get system
date)[nb 7] and INT 21h/AH=2Ch (get system time)[nb 7] for the high
word and another 16-bit addition of both CX values for the low word of
the serial number. Alternatively, some DR-DOS disk utilities provide a
/# option to generate a human-readable time stamp "mmdd-hhmm" build
from BCD-encoded 8-bit values for the month, day, hour and minute
instead of a serial number.
This is a 32 bits value, which can be displayed for example as 4425-7572. Most likely those two partitions are EFI System partitions since they have to be FAT32.
You can get better informations (probably coming from parsing several /dev/disks/by-*/ entries) with the blkid command instead:
# blkid
or limited to those short entries:
# blkid /dev/sda1 /dev/sdb1
The manual suggest to use lsblk instead which doesn't require root. So with the right options that would be lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1.
E.g. here:
$ lsblk -o +UUID,FSTYPE /dev/sda1 /dev/sdb1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID FSTYPE
sda1 8:1 0 200M 0 part /boot/efi 1234-5678 vfat
sdb1 8:17 1 200M 0 part 9ABC-DEF0 vfat
edited 3 hours ago
answered 4 hours ago
A.BA.B
6,10211030
6,10211030
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
3 hours ago
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
3 hours ago
add a comment |
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
3 hours ago
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
3 hours ago
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
3 hours ago
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
3 hours ago
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
3 hours ago
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
3 hours ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f512283%2fshort-and-long-uuids-under-dev-disk-by-uuid%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown