[lkml]   [2003]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Disk Geometries reported incorrectly on 2.6.0-testX
    On Sat, Nov 29, 2003 at 01:34:51PM +0100, Andries Brouwer wrote:
    > On Sat, Nov 29, 2003 at 07:16:31AM +0200, Szakacsits Szabolcs wrote:
    > >
    > >
    > > 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.

    Let me continue to stress: geometry DOES exist.

    It is an abstract construct that is stored in your BIOS that some
    configurations use and need for booting.

    > Consequently, it cannot change.

    The geometry can be changed in many BIOSes.

    > fdisk does not set any geometry, it writes a partition table.

    But the way it writes the partition table is affected by what it
    believes the geometry to be. If its beliefs don't match the BIOS,
    there can be trouble. However, since fdisk isn't typically used to
    resize Windows partitions, you don't see problems so much.

    > 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).

    You mean "modern software". I'm not sure how true this is. Have you
    got any evidence?

    (i.e. have you got any evidence that, say, that 99.x% of Windows XP
    installations use LBA to bootstrap?)

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


    Moreover, booting can fail while reading the file system. I reverse
    engineered several of the Microsoft boot loaders (Windows
    95/9x/ME/2000/NT). The boot sector understands FAT, and depending
    on the configuration, may use CHS to load in info.

    I wrote about this in the doc/FAT file in the Parted tarball.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:59    [W:0.033 / U:10.620 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site