were did 10 GiB go using fdisk?

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • were did 10 GiB go using fdisk?

      Hi I have just installed OMV. Through SSH I created a partition on a external HD following this instruction tecmint.com/fdisk-commands-to-manage-linux-disk-partitions/ (writtten in 2015)

      The result is as follows:


      Source Code

      1. Command (m for help): p
      2. Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
      3. Units: sectors of 1 * 512 = 512 bytes
      4. Sector size (logical/physical): 512 bytes / 512 bytes
      5. I/O size (minimum/optimal): 512 bytes / 512 bytes
      6. Disklabel type: gpt
      7. Disk identifier: 5727599A-FE1E-4BCE-BA6B-C91125A1C955
      8. Device Start End Sectors Size Type
      9. /dev/sda1 2048 312581774 312579727 149.1G Linux filesystem
      As you can see there is a gap of around 10 GiB for space counted in bytes vs space counted in GiB. During the procedure it said the default cylinder to start was 63. So I started searching. I found this information:

      confluence.wartungsfenster.de/…+Force+sector+63+boundary (written in 2013)

      superuser.com/questions/352572…sector-2048-instead-of-63 (written in 2011)

      jdebp.eu./FGA/disc-partition-alignment.html (written in 2011)


      This is all old information and I don't whether it relates to the 'loss' of 10 Gib. The instruction i followed did not mention a default cylinder start at 63. So the question is what do I need to do to get the 10 Gib back? Is it at all possible? Should I use a different disk partionner / formatting program? Maybe ignore the default cylinder and set it to start at a cylinder 1?

      BTW Previously the disk was formatted Mac OS Extended (Journaled) and indicated 160 Gib. A second disk I have which is exactly the same and still formatted Mac OS Extended (Journaled) still indicates 160 GiB.
    • 160041885696 bytes / 1024 kB / 1024 MB /1024 GiB = 149,05 GiB

      Absolutely correct. The conversion factor of the binary system is 1024. 210=1024

      The marketing guys are using 1000 as conversion factor. Therefore every data carrier is smaller in reality as advertised. But that´s a different story.
      OMV 3.0.99 (Gray style)
      ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1)- Fractal Design Node 304

      The post was edited 3 times, last by cabrio_leo ().