Bug 909
Summary: | The Linux Installer failed to activate the boot partition | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | mfranz |
Component: | installer | Assignee: | Matt Wilson <msw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | athompso |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-03-13 21:36:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
mfranz
1999-01-21 15:55:42 UTC
We have observed this to be a bug and have verified it on machines in our test lab. It is being assigned to a developer for further review. One of six users at LULA's Jan 99 installfest ran into this. A fix would benefit real users. *** Bug 932 has been marked as a duplicate of this bug. *** When using the built-in "Server" installation type, the first reboot FAILS, despite having LILO installed. None of the partitions on either /dev/hda or /dev/hdb were marked active. I'm not sure if the interaction is with LILO, or with a "smart" BIOS in some newer PCs. There are two solutions: 1) re-boot off the CD-ROM (or the install floppy), get to the point where you can pick between fdisk and Disk Druid, run fdisk on /dev/hda, mark the partition active, WRITE changes to disk, wait for disks to sync, then press the RESET button (ie. hard boot) 2) boot of the boot floppy that got created during install (if you made one :-) and re-run LILO. I have no idea why re-running LILO fixes this problem. This method did *NOT* fix the problem on one PC with a *single* root partition that was over the 1024 cylinder mark. There may have been some other interaction there. I'm not certain, but I believe that the same behaviour happens when using Disk Druid instead of fdisk. Last time I tried was a while back, so I could be wrong. ------- Additional Comments From dank.edu 02/05/99 12:24 ------- Is this a duplicate of #909? http://developer.redhat.com/bugzilla/show_bug.cgi?id=909 Fixed in the next release. |