Bug 932 - No HDD partitions marked Active after install; cannot boot
No HDD partitions marked Active after install; cannot boot
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
5.2
i386 Linux
medium Severity high
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-01-23 16:28 EST by Adam Thompson
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:
Environment:
Last Closed: 1999-02-05 20:27:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Adam Thompson 1999-01-23 16:28:05 EST
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.
Comment 1 dank 1999-02-05 12:24:59 EST
Is this a duplicate of #909?
http://developer.redhat.com/bugzilla/show_bug.cgi?id=909
Comment 2 David Lawrence 1999-02-05 20:27:59 EST
*** This bug has been marked as a duplicate of 909 ***

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