Bug 6985 - Linuxconf not accepting root partition after compiling new kernel
Linuxconf not accepting root partition after compiling new kernel
Status: CLOSED DUPLICATE of bug 5737
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-13 00:51 EST by Keith E. McComb
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-19 16:36:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Keith E. McComb 1999-11-13 00:51:51 EST
I have kernel 2.2.12-20 running on two machines - a HP 7280 Pavilion, and a
separate one built using a Celeron 450 MHz and a Maxtor 20G drive.  On both
machines, after compiling a kernel specific for the machine, whenusing
linuxconf to set it up as bootable, it informs me that either the partition
is bad or is not a valid ext2 partition.  It works just fine if I manually
edit /etc/lilo.conf then run /sbin/lilo.  I have only recently upgraded
from the RedHat 6.0 to the 6.1 package.  linuxconf worked fine when I was
using the 6.0 kernel.  (I believe the kernel was 2.2.5-15.)
Comment 1 martin 1999-11-15 15:27:59 EST
The same happended to me (Toshiba 4000CDT Laptop, ran under RH 5.2 with
self-compiled 2.2.13-Kernel before). After RH install had destroyed my
lilo.conf, I couldnt4t enter the exisiting 2.2.13 Kernel into lilo.conf anymore
Comment 2 martin 1999-11-15 15:30:59 EST
The same happended to me (Toshiba 4000CDT Laptop, ran under RH 5.2 with
self-compiled 2.2.13-Kernel before). After RH install had destroyed my
lilo.conf, I couldnt4t enter the exisiting 2.2.13 Kernel into lilo.conf anymore
with linuxconf, as /dev/hda5 was, according to linuxconf, an invalid partition.
(Nor could I set /dev/hda5 as default root partition for lilo). Hand editing
worked fine.
(sorry I submitted my last incomplete comment - Bugzilla newbie. please delete!
Martin Wilck, Inst. for Tropospheric Research, Leipzig, Germany
Comment 3 martin 1999-11-16 15:04:59 EST
Just the same on a networked workstation with SCSI disks - linuxconf doesn4t
accept /dev/sda5 as root partition any more.
Comment 4 martin 1999-11-16 15:06:59 EST
Just discovered that this seems to be the same bug as 5737.
Comment 5 Michael K. Johnson 1999-11-19 16:36:59 EST
*** This bug has been marked as a duplicate of 5737 ***

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