Re: RFC: disk geometry via sysfs

["linux-os \(Dick Johnson\)" <linux-os@analogic.com>]

On Wed, 15 Feb 2006, Phillip Susi wrote:

> Alan Cox wrote:
>> On Mer, 2006-02-15 at 11:20 -0500, Phillip Susi wrote:
>>> Why do you say the partitioning tool needs to know the disk reported
>>> C/H/S?  The value stored in the MBR must match the bios reported values,
>>> not the disk reported ones, so why does the partitioner care about what
>>> the disk reports?
>>
>> You answered that in asking the question.  "The value stored in the MBR
>> must match the ...". What if the MBR has not yet been written ?
>>
>
> The value in the MBR must match the _bios_ value, not the value that the
> disk reports in its inquiry command ( which often will be different ).
> When creating a new MBR you need to get the geometry from the bios, not
> the drive itself.
>
>> (Also btw its *should*...) most modern OS's will take a sane MBR
>> geometry and trust it over BIOS defaults.
>>
>
> If the value in the MBR differs from the geometry that the bios reports,
> then boot code using int 13 in chs mode will fail because it won't be
> using the geometry that the bios expects.
>

If the disc is a modern disk, and the BIOS is modern as well,
it won't care. For instance, if we attempt to seek to cylinder
10, sector 10, and there are only 9 sectors, then the supplied
head number is incremented, the sector to be read becomes 1
(dumb ones based), and everything is fine. If the head number
can't be incremented, it wraps to 0. Problems occur if the BIOS
has been set to "physical" mode for access. In this mode, the
CHS are absolute and "you can't get there from here." In the
physical mode, you can't have more than 1024 cylinders because
they need to fit into 10 bits.

As long as the BIOS is set for LBA, the boot sequence should not
care.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.66 BogoMips).
Warning : 98.36% of all statistics are fiction.
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
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/