Re: Disk Geometries reported incorrectly on 2.6.0-testX

From: Andries Brouwer (aebr_at_win.tue.nl)
Date: 11/29/03

  • Next message: Andries Brouwer: "Re: Disk Geometries reported incorrectly on 2.6.0-testX" 
    Date:	Sat, 29 Nov 2003 13:34:51 +0100
To: Szakacsits Szabolcs <szaka@sienet.hu>

    On Sat, Nov 29, 2003 at 07:16:31AM +0200, Szakacsits Szabolcs wrote:

    > http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html#troubleshoot
    >
    > Some users, having problems, did mention the usage of 2.6 kernel. If the
    > geometry changed during the fdisk, etc process then it could result also
    > booting problem?

    Let me continue to stress: geometry does not exist.
    Consequently, it cannot change.
    fdisk does not set any geometry, it writes a partition table.

    Start and size of each partition are given twice: in absolute sector
    units (LBA) and in CHS units. The former uses 32 bits, and with 512-byte
    sectors this works up to 2TB. People are starting to hit that boundary now.
    The latter uses 24 bits, which works up to 8GB. Modern systems no longer
    use it (but the details are complicated).

    Usually booting goes like this: the BIOS reads sector 0 (the MBR)
    from the first disk, and starts the code found there. What happens
    afterwards is up to that code. If that code uses CHS units to find
    a partition, and if the program that wrote the table has different
    ideas about those units than the BIOS, booting may fail.

    Andries

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Andries Brouwer: "Re: Disk Geometries reported incorrectly on 2.6.0-testX"

    Relevant Pages

    • Re: Disk geom and freeBSD 6.2 on lenovoe T60 thinkpad laptop
      ... this is my second attempt to install freeBSD 6.2 on the ... At the sysinstall Main Menu which appeared next, ... Next is the fdisk message. ... A geometry of 232581/16/63 for ad4 is ...
      (comp.unix.bsd.freebsd.misc)
    • Re: Confused over disk geometry for 160GB disk
      ... But I didn't know what that geometry was. ... Look for partition "beg:" lines and see the head value! ... Looks like I used the correct 255 head geometry considering I've got some ... BIOS sector numbering starts with sector 1 ...
      (comp.unix.bsd.freebsd.misc)
    • Re: RFC: disk geometry via sysfs
      ... A sector with LBA of 1234 would have a CHS ... address using this geometry of 9/5/3. ... The BIOS takes these PHONY things, ... The important fact here is that Linux does not really depend on an MBR ...
      (Linux-Kernel)
    • Re: Why is disklabelng a new drive so difficult?
      ... I actually started writing my own partitioning/labelling tool based on libdisk, as part of a custom install CD I was building, but discovered that it did not support non-disk devices... ... explanation on disk geometry, and why it is/isn't relevant in this day and age. ... The big scary warnings sysinstall likes to throw up made me think it must have some significance, but from days of searching/reading, the general gist I came up with is that geometry was a largely obsolete concept, largely only relevant if you have other operating systems on the drive, in which case all OSes needed to agree on the drive geometry in order for the fdisk slice table to make any sense to all of them... ... If they are needed, should some of the sysinstall magic be added to the command line fdisk tool as well, so it can perform the same modifications if it detects non-sane BIOS C/H/S values? ...
      (freebsd-questions)
    • Re: 2.6.x partition breakage and dual booting
      ... In the ancient past a disk had a geometry ... well-determined geometry: the ATA command INITIALIZE DRIVE PARAMETERS ... A DOS-type partition table (see, e.g., ... One is the way used by Linux (the starting sector and length, ...
      (Linux-Kernel)