Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Jan 2004 09:53:09 -0800
From:      "Keith Kelly" <c0d3h4x0r@hotmail.com>
To:        hhasenbe@techfak.uni-bielefeld.de
Cc:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD/FDisk geometry problems - SOLVED!
Message-ID:  <Sea1-F50NLK2iw6lxKt000136b8@hotmail.com>

next in thread | raw e-mail | index | archive | help
See my comments in-line.


>From: Hendrik Hasenbein <hhasenbe@techfak.uni-bielefeld.de>
>To: Keith Kelly <c0d3h4x0r@hotmail.com>
>CC: freebsd-bugs@freebsd.org,  freebsd-questions@freebsd.org
>Subject: Re: FreeBSD/FDisk geometry problems - SOLVED!
>Date: Sat, 24 Jan 2004 10:43:17 +0100
>
>Keith Kelly wrote:
>>I've found a bug in FDisk which is responsible for all the problems I've 
>>had trying to get FreeBSD installed.  I also found a work-around, and I'm 
>>happy to report I'm typing this message from Konquerer inside FreeBSD 
>>5.1-RELEASE right now.
>
>Gratulation.
>
>>Basically, the problem is that FreeBSD's FDisk and the motherboard BIOS 
>>independently calculate a set of CHS values (Cylinders/Heads/Sectors) 
>>based on the total sector count of the disk, but they do it in different 
>>ways and thus end up with different values.
>
>Yes. That is because there are different ways to calculate that.

Then FDisk should be updated to include awareness of ALL the different ways, 
so as to work on a wider variety of hardware.

>
>>So, the problem is that FDisk makes *different* assumptions than my BIOS 
>>does about what the sectors and heads values should be.
>
>That has always been the problem for CHS conversions.

Then why do Windows, BeOS, Linux, and SkyOS all get it right, while 
FreeBSD's fdisk is the only one that gets it wrong?

>
>>I ran across some information on a BIOS manufacturer's site which claimed 
>>that for "LBA mode" SCSI drives (more accurately known as "LBA-Assist 
>>translation mode"), that it is safe to assume that sectors should be 63 
>>and heads should be 255.  Given that FreeBSD's roots and developer 
>>community seems historically SCSI-centric, I can see how these assumptions 
>>would have been picked up and used in FDisk and considered acceptable.  
>>But these assumed values are clearly not correct for how CHS gets 
>>calculated by many PC BIOSes for IDE drives.
>
>LBA is the only common mode known to all BIOS vendors, Harddrive 
>manufactures and so on, because at least someone made up some assumptions 
>and published them instead of developing their own CHS translation. SCSI 
>was first to breach the BIOS CHS barrier on PCs and so they defined that 
>method. If your BIOS is in auto mode, it tries to get the current format 
>from the harddisk most times uses CHS, but will also find a disk with LBA. 
>So in a modern system LBA would be the safe pick and not CHS. Most likely 
>it picks it from disk (the partition table uses entries for cylinders, 
>heads and sectors to describe the partitions), so the first fdisk sets the 
>addressing the bios chooses. So to avoid conflicts and enhance the usabilty 
>of your drive in different PCs and with different systems use LBA.

As I've said multiple times now, LBA was already enabled on all my drives.
>
>>Furthermore, I believe that the reason FDisk rejects the manually entered 
>>CHS of 19618/16/255 is because either (1) it tries to enforce those bad 
>>assumptions about heads and sectors, or (2) it gets confused by the 
>>rounding error.  In other words, in the case of rounding error, FDisk may 
>>be taking the manually-entered values, multiplying them together, and 
>>seeing that it doesn't exactly match (or come close enough to, in its 
>>humble but flawed opinion) the total sector count for the drive.  The way 
>>Fdisk's geometry validation ought to work is like this:
>>
>>- Divide the total sector count of the drive by (H*S), where H and S are 
>>the user-supplied values.
>>- Round the result to the nearest whole number.
>>- Compare that result to the user-supplied value for cylinders.
>>- If the result matches, accept the user's input as good.
>
>The test will ensure that the user dont make typos, but it can't ensure 
>that the C. H and S are arranged the same in both conversions.

Uh, what?

>
>>In the meantime, the workaround for anyone experiencing this problem is to 
>>go into their BIOS and set the hard drive to "User" mode, and manually 
>>enter the same C/H/S settings that FDisk calculated for the drive.  
>>Unfortunately, I think this means that if you have to repartition and 
>>reformat the entire drive, since the BIOS will now be addressing the drive 
>>using different C/H/S settings and will be unable to read any partitions 
>>that were formatting using different C/H/S addressing.  So while there is 
>>a workaround, it is far from an ideal user experience.
>
>Better solution, put the IDE drives to LBA and you'll see that you

All my drives already were set in the BIOS with LBA-mode "On".  This isn't 
just an issue with having LBA mode enabled or not in the BIOS.  This is an 
issue with FDisk being deficient in how it calculates values for LBA IDE 
drives.

>get the same CHS every time and on every system except MSDOS < 6.3. If you 
>got a filesystem which doesnt bother about CHS and uses linear addressing 
>you 'only' need a new partition table. After redoing the drive you can put 
>the IDE back to Auto.
>
>Hendrik
>
>

_________________________________________________________________
Check out the coupons and bargains on MSN Offers! 
http://shopping.msn.com/softcontent/softcontent.aspx?scmId=1418



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Sea1-F50NLK2iw6lxKt000136b8>