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;








1















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?










share|improve this question






























    1















    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?










    share|improve this question


























      1












      1








      1


      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?










      share|improve this question
















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 4 hours ago







      bejo

















      asked 4 hours ago









      bejobejo

      386




      386




















          1 Answer
          1






          active

          oldest

          votes


















          3














          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





          share|improve this answer

























          • 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












          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
          );



          );













          draft saved

          draft discarded


















          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









          3














          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





          share|improve this answer

























          • 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
















          3














          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





          share|improve this answer

























          • 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














          3












          3








          3







          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





          share|improve this answer















          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






          share|improve this answer














          share|improve this answer



          share|improve this answer








          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


















          • 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


















          draft saved

          draft discarded
















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Era Viking Índice Início da Era Viquingue | Cotidiano | Sociedade | Língua | Religião | A arte | As primeiras cidades | As viagens dos viquingues | Viquingues do Oeste e Leste | Fim da Era Viquingue | Fontes históricas | Referências Bibliografia | Ligações externas | Menu de navegação«Sverige då!»«Handel I vikingetid»«O que é Nórdico Antigo»Mito, magia e religião na volsunga saga Um olhar sobre a trajetória mítica do herói sigurd«Bonden var den verklige vikingen»«Vikingatiden»«Vikingatiden»«Vinland»«Guerreiras de Óðinn: As Valkyrjor na Mitologia Viking»1519-9053«Esculpindo símbolos e seres: A arte viking em pedras rúnicas»1679-9313Historia - Tema: VikingarnaAventura e Magia no Mundo das Sagas IslandesasEra Vikinge

          What's the metal clinking sound at the end of credits in Avengers: Endgame?What makes Thanos so strong in Avengers: Endgame?Who is the character that appears at the end of Endgame?What happens to Mjolnir (Thor's hammer) at the end of Endgame?The People's Ages in Avengers: EndgameWhat did Nebula do in Avengers: Endgame?Messing with time in the Avengers: Endgame climaxAvengers: Endgame timelineWhat are the time-travel rules in Avengers Endgame?Why use this song in Avengers: Endgame Opening Logo Sequence?Peggy's age in Avengers Endgame

          Are there legal definitions of ethnicities/races? 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)Legal definitions in the United StatesAre there truly legal limits on US interest rates?Are gender identity and sexual orientation federally protected?Why is there an apparent legal bias against digital services?What limits are there to the powers of individual judges in the United States legal system?Are women only scholarships legal under Irish / EU law?Is the term “race” defined by Public Law enacted by Congress of the United StatesIs there a legal definition of race in the US?Neighbors are spying for landlord on Renters is it legal?Are Protected Classes Bi-directional?