Re: Partition(s) do not end on cylinder boundary

[Charles Galpin <cgalpin lighthouse-software com>]

Wow! Excellent. I troed a number of things, but not expert :)

All I ended up doing was deleting the partitions and recreating them. For
some reason the newly created partitions *did* end on a cylinder
boundry. I'm assuming some change has occured in fdisk.

I had one strange thing happen - which probably isn't related to this, but
occured during this fiasco - my win98 wouldn't boot anymore, complaining
himem.sys was missing (it was there). It seems to be a common problem
after installing antivirus software, and a device= line in my config.sys
fixed it. funny though.

Anyway, glad you solved this without starting from scratch.

Now if I could only get my X working again :)

charles

On Sat, 28 Apr 2001, Geoffrey Knauth wrote:

> I had this problem on upgrading my laptop from RH7.0 to RH7.1:
> 
>      An error occurred reading the partition table for the block
>      device hda.  The error was:
> 
>      Partition(s) do not end on cylinder boundary
> 
>      This occurs because the drive geometry detected by the kernel
>      used by the installer is
>      different that the drive geometry used when the drive was
>      partitioned.  This can be
>      corrected by specifying the drive geometry on the kernel
>      command line when booting the
>      installer.
> 
> In all my previous updates, I never had this problem.  I noticed Charles
> Galpin had a similar problem from his 2 redhat-list messages with the
> subject line, "Redhat 7.1/kernel 2.4.2 & disk geometry on boot."
> 
> Like him, I was wondering what C/H/S values I should use.  I've seen
> different values, 16383/16/63 and 33521/16/63.
> 
> Not exactly knowing what to do, I tried the "expert" option when booting
> RH7.1 CD1, expecting to have to enter something special at some point.
> 
> Well lo and behold, I really didn't have to enter anything special at
> all.  This time anaconda figured out the geometry of /dev/hda OK and
> proceeded with the rest of package selection and installing software,
> instead of bombing out with the error message I noted at the top.