Short and long uuids under /dev/disk/by-uuidLinux 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?
Comment dit-on « I’ll tell you what » ?
Can a non-EU citizen travel within the Schengen area without identity documents?
If a problem only occurs randomly once in every N times on average, how many tests do I have to perform to be certain that it's now fixed?
Uncommanded roll at high speed
Fastest way to perform complex search on pandas dataframe
Future enhancements for the finite element method
What's the most polite way to say "shut up and let me work"?
How to properly maintain eye contact with people that have distinctive facial features?
Strange math syntax in old basic listing
Do you play the upbeat when beginning to play a series of notes, and then after?
Is this light switch installation safe and legal?
If a massive object like Jupiter flew past the Earth how close would it need to come to pull people off of the surface?
What is game ban VS VAC ban in steam?
What was this black-and-white film set in the Arctic or Antarctic where the monster/alien gets fried in the end?
Did airlines fly their aircraft slower in response to oil prices in the 1970s?
Why teaching kids Torah is the only forbidden profession for singles Yihud-wise?
Is it possible to change original filename of an exe?
How to prevent bad sectors?
Thousands and thousands of words
Yandex programming contest: Alarms
Is it possible to kill all life on Earth?
Why does the 6502 have the BIT instruction?
Biblical Basis for 400 years of silence between old and new testament
Adding strings in lists together
Short and long uuids under /dev/disk/by-uuid
Linux 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 on my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux). It 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, and 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
edited Apr 13 at 20:14
Peter Mortensen
93069
asked Apr 13 at 14:40
bejobejo
437
add a comment |
There are several hard disk partitions on my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux). It 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, and 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
edited Apr 13 at 20:14
Peter Mortensen
93069
asked Apr 13 at 14:40
bejobejo
437
add a comment |
There are several hard disk partitions on my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux). It 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, and 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
edited Apr 13 at 20:14
Peter Mortensen
93069
asked Apr 13 at 14:40
bejobejo
437
There are several hard disk partitions on my system (Linux josDeb 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux). It 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, and 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 Apr 13 at 20:14
Peter Mortensen
93069
asked Apr 13 at 14:40
bejobejo
437
edited Apr 13 at 20:14
Peter Mortensen
93069
asked Apr 13 at 14:40
bejobejo
437
edited Apr 13 at 20:14
Peter Mortensen
93069
edited Apr 13 at 20:14
Peter Mortensen
93069
edited Apr 13 at 20:14
Peter Mortensen
93069
93069
asked Apr 13 at 14:40
bejobejo
437
asked Apr 13 at 14:40
bejobejo
437
asked Apr 13 at 14:40
bejobejo
437
437
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
answered Apr 13 at 15:10
A.BA.B
6,89011333
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
Apr 13 at 15:51
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
Apr 13 at 16:06
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
answered Apr 13 at 15:10
A.BA.B
6,89011333
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
Apr 13 at 15:51
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
Apr 13 at 16:06
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
answered Apr 13 at 15:10
A.BA.B
6,89011333
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
Apr 13 at 15:51
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
Apr 13 at 16:06
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
answered Apr 13 at 15:10
A.BA.B
6,89011333
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
answered Apr 13 at 15:10
A.BA.B
6,89011333
edited Apr 13 at 15:27
answered Apr 13 at 15:10
A.BA.B
6,89011333
answered Apr 13 at 15:10
A.BA.B
6,89011333
answered Apr 13 at 15:10
A.BA.B
6,89011333
6,89011333
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
Apr 13 at 15:51
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
Apr 13 at 16:06
add a comment |
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
Apr 13 at 15:51
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
Apr 13 at 16:06
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
Apr 13 at 15:51
Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.
– bejo
Apr 13 at 15:51
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
Apr 13 at 16:06
So for this one that would be VolumeSerialNumber here, also 4 bytes.
– A.B
Apr 13 at 16:06
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
