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?

What can I do if neighbor is blocking my solar panels intentionally?

Relations between two reciprocal partial derivatives?

Does Parliament need to approve the new Brexit delay to 31 October 2019?

In horse breeding, what is the female equivalent of putting a horse out "to stud"?

Hopping to infinity along a string of digits

Problems with Ubuntu mount /tmp

What's the point in a preamp?

Make it rain characters

Why did all the guest students take carriages to the Yule Ball?

How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time

Did the new image of black hole confirm the general theory of relativity?

Is every episode of "Where are my Pants?" identical?

He got a vote 80% that of Emmanuel Macron’s

Finding the path in a graph from A to B then back to A with a minimum of shared edges

Change bounding box of math glyphs in LuaTeX

How to prevent selfdestruct from another contract

The variadic template constructor of my class cannot modify my class members, why is that so?

ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?

How to test the equality of two Pearson correlation coefficients computed from the same sample?

Semisimplicity of the category of coherent sheaves?

How does this infinite series simplify to an integral?

How are presidential pardons supposed to be used?

How do you keep chess fun when your opponent constantly beats you?

Why can't wing-mounted spoilers be used to steepen approaches?



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 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?










share|improve this question






























    1















    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?










    share|improve this question


























      1












      1








      1


      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?










      share|improve this question
















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 45 mins ago









      Peter Mortensen

      91959




      91959










      asked 6 hours ago









      bejobejo

      387




      387




















          1 Answer
          1






          active

          oldest

          votes


















          4














          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
            5 hours ago











          • So for this one that would be VolumeSerialNumber here, also 4 bytes.

            – A.B
            4 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









          4














          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
            5 hours ago











          • So for this one that would be VolumeSerialNumber here, also 4 bytes.

            – A.B
            4 hours ago
















          4














          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
            5 hours ago











          • So for this one that would be VolumeSerialNumber here, also 4 bytes.

            – A.B
            4 hours ago














          4












          4








          4







          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 5 hours ago

























          answered 5 hours ago









          A.BA.B

          6,11211030




          6,11211030












          • Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.

            – bejo
            5 hours ago











          • So for this one that would be VolumeSerialNumber here, also 4 bytes.

            – A.B
            4 hours ago


















          • Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.

            – bejo
            5 hours ago











          • So for this one that would be VolumeSerialNumber here, also 4 bytes.

            – A.B
            4 hours ago

















          Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.

          – bejo
          5 hours ago





          Thanks - understood. In my case sda1 indeed is a fat32 partition whereas sdb1 is an exfat partition.

          – bejo
          5 hours ago













          So for this one that would be VolumeSerialNumber here, also 4 bytes.

          – A.B
          4 hours ago






          So for this one that would be VolumeSerialNumber here, also 4 bytes.

          – A.B
          4 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

          Ружовы пелікан Змест Знешні выгляд | Пашырэнне | Асаблівасці біялогіі | Літаратура | НавігацыяДагледжаная версіяправерана1 зменаДагледжаная версіяправерана1 змена/ 22697590 Сістэматыкана ВіківідахВыявына Вікісховішчы174693363011049382

          ValueError: Error when checking input: expected conv2d_13_input to have shape (3, 150, 150) but got array with shape (150, 150, 3)2019 Community Moderator ElectionError when checking : expected dense_1_input to have shape (None, 5) but got array with shape (200, 1)Error 'Expected 2D array, got 1D array instead:'ValueError: Error when checking input: expected lstm_41_input to have 3 dimensions, but got array with shape (40000,100)ValueError: Error when checking target: expected dense_1 to have shape (7,) but got array with shape (1,)ValueError: Error when checking target: expected dense_2 to have shape (1,) but got array with shape (0,)Keras exception: ValueError: Error when checking input: expected conv2d_1_input to have shape (150, 150, 3) but got array with shape (256, 256, 3)Steps taking too long to completewhen checking input: expected dense_1_input to have shape (13328,) but got array with shape (317,)ValueError: Error when checking target: expected dense_3 to have shape (None, 1) but got array with shape (7715, 40000)Keras exception: Error when checking input: expected dense_input to have shape (2,) but got array with shape (1,)

          Illegal assignment from SObject to ContactFetching String, Id from Map - Illegal Assignment Id to Field / ObjectError: Compile Error: Illegal assignment from String to BooleanError: List has no rows for assignment to SObjectError on Test Class - System.QueryException: List has no rows for assignment to SObjectRemote action problemDML requires SObject or SObject list type error“Illegal assignment from List to List”Test Class Fail: Batch Class: System.QueryException: List has no rows for assignment to SObjectMapping to a user'List has no rows for assignment to SObject' Mystery