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?

Am I ethically obligated to go into work on an off day if the reason is sudden?

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

Match Roman Numerals

How can I protect witches in combat who wear limited clothing?

What aspect of planet Earth must be changed to prevent the industrial revolution?

What do you call a plan that's an alternative plan in case your initial plan fails?

Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?

Would an alien lifeform be able to achieve space travel if lacking in vision?

How to delete random line from file using Unix command?

How to tell if two pearson correlations from the same sample differ significanly

Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?

How do I add random spotting to the same face in cycles?

Chern class of a vector bundle and the associated projective space bundle

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

What information about me do stores get via my credit card?

How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?

How are presidential pardons supposed to be used?

Is a pteranodon too powerful as a beast companion for a beast master?

How does this infinite series simplify to an integral?

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

Problems with Ubuntu mount /tmp

Is there a writing software that you can sort scenes like slides in PowerPoint?

short and long uuids under /dev/disk/by-uuid

Can a novice safely splice in wire to lengthen 5V charging cable?



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






























    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


























      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
















      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














      share












      share



      share








      edited 5 hours ago







      bejo

















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





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

          – bejo
          4 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

          Best approach to update all entries in a list that is paginated?Best way to add items to a paginated listChoose Your Country: Best Usability approachUpdate list when a user is viewing the list without annoying themWhen would the best day to update your webpage be?What should happen when I add a Row to a paginated, sorted listShould I adopt infinite scrolling or classical pagination?How to show user that page objects automatically updateWhat is the best location to locate the comments section in a list pageBest way to combine filtering and selecting items in a listWhen one of two inputs must be updated to satisfy a consistency criteria, which should you update (if at all)?

          Тонконіг бульбистий Зміст Опис | Поширення | Екологія | Господарське значення | Примітки | Див. також | Література | Джерела | Посилання | Навігаційне меню1114601320038-241116202404kew-435458Poa bulbosaЭлектронный каталог сосудистых растений Азиатской России [Електронний каталог судинних рослин Азіатської Росії]Малышев Л. Л. Дикие родичи культурных растений. Poa bulbosa L. - Мятлик луковичный. [Малишев Л. Л. Дикі родичи культурних рослин. Poa bulbosa L. - Тонконіг бульбистий.]Мятлик (POA) Сем. Злаки (Мятликовые) [Тонконіг (POA) Род. Злаки (Тонконогові)]Poa bulbosa Linnaeus, Sp. Pl. 1: 70. 1753. 鳞茎早熟禾 lin jing zao shu he (Description from Flora of China) [Poa bulbosa Linnaeus, Sp. Pl. 1: 70. 1753. 鳞茎早熟禾 lin jing zao shu he (Опис від Флора Китаю)]Poa bulbosa L. – lipnice cibulkatá / lipnica cibulkatáPoa bulbosa в базі даних Poa bulbosa на сайті Poa bulbosa в базі даних «Global Biodiversity Information Facility» (GBIF)Poa bulbosa в базі даних «Euro + Med PlantBase» — інформаційному ресурсі для Євро-середземноморського розмаїття рослинPoa bulbosa L. на сайті «Плантариум»

          Вунгтау (аеропорт) Загальні відомості | Див. також | Посилання | Навігаційне меню10°22′00″ пн. ш. 107°05′00″ сх. д. / 10.36667° пн. ш. 107.08333° сх. д. / 10.36667; 107.0833310°22′00″ пн. ш. 107°05′00″ сх. д. / 10.36667° пн. ш. 107.08333° сх. д. / 10.36667; 107.083337731608Vinh AirportVinh airport facelift improves serviceвиправивши або дописавши їївиправивши або дописавши їїр