Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 7929 - Error message "Boot partition too big" is misleading
Error message "Boot partition too big" is misleading
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Depends On:
  Show dependency treegraph
Reported: 1999-12-21 11:29 EST by Toby Haynes
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-14 12:23:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Toby Haynes 1999-12-21 11:29:20 EST
In Disk Druid, when trying to set up the Linux partitions on my 20GB hard
drive (split into 11GB Win98SE FAT32 and the rest for Linux) an error
message is given when trying to set up a partition for /boot, or if there
is no /boot partition, for /. This error message states "Boot partition too
big". Even shrinking the partition to 1MB does not solve this problem, so
whatever is causing the generation of this error message is not consistent
with the error message received. I believe my machine (Aptiva 865) has an
extended BIOS to allow access to beyond the 1023rd cylinder, so my Linux
partition starts at cylinder 1444 and ends at 2489.

Scans through the newsgroups reveal this is a common problem with recent
installs, most of which seem to involve Win98, Win98SE and larger drives.
Common suggested fixes include making sure that the /boot partition lies
within the first 1024 cylinders or switching to fdisk.
Comment 1 Jay Turner 2000-02-22 14:42:59 EST
This issue has been added to a list of feature requests.
Comment 2 Michael Fulbright 2001-09-14 12:23:44 EDT
Fixed in the current release.

Note You need to log in before you can comment on or make changes to this bug.