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 https://www.tecmint.com/fdisk-…ge-linux-disk-partitions/ (writtten in 2015)


    The result is as follows:



    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:


    http://confluence.wartungsfens…+Force+sector+63+boundary (written in 2013)


    https://superuser.com/question…sector-2048-instead-of-63 (written in 2011)


    http://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.100 (Gray style)

    ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1) - Fractal Design Node 304 -

    3x WD80EMAZ Snapraid / MergerFS-pool via eSATA - 4-Bay ICYCube MB561U3S-4S with fan-mod

    3 Mal editiert, zuletzt von cabrio_leo ()

  • Ok, thanks all for answering my question. I knew the conversion factor isn't 109, but simply didn't realize that the difference would seem so big. Also interesting to see how Apple is handling this. That didn't help figuring this out.


    Thanks again.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!