by Hi all,
I performed an upgrade yesterday from Redhat 5.2 to Redhat 6. After
completion my system wouldn't boot anymore. When I tried to boot Linux
with lilo, it asked for a bootdisk. While the same boot option (with
select-it) always was able to start Linux. It seems that lilo isn't
installed or can't be executed.
So I reinstalled Redhat 6.0 (no upgrade this time) and I installed
Lilo on the MBR of the boot partition (I got the option 'install lilo
on the first sector of the root partition', this option seems to be
disappeared with Redhat 6.0).
After booting I got the same results I had before the installation.
Select-it finds Linux but when I select Linux, I got the same 'insert
bootdisk error'.
Here's my lilo.conf:
boot=/dev/hdc1
map=/boot/map
install=/boot/boot.b
prompt
timeout
linear (this doesn't help, same error without linear)
timeout=50
image=/boot/vmlinuz-2.2.5-15
label=linux
root=/dev/hdc2
read-only
fdisk summary (linux)
Device boot start end blocks Id System
/dev/hdc1 * 1 21 10552+ 83 Linux
/dev/hdc2 * 22 3880 1944936 83 Linux
/dev/hdc3 3881 4092 106848 82 Swap
Disks, cdrom
channel 0: Master: Quantum Fireball SE 6.5Gb (4 partitions, 1
FAT16, two fat32 and one NTFS partitions)
Slave: Creative DVD
channel 1: Master: Quantum Bigfoot CY 2,2Gb (4000+ cyls)
Slave: HP 8100 CDRW
Everything needed to boot is located in the /boot partition, /dev/hdc2
is the root partition.
All partitions on /dev/hdc where made by fdisk/linux.
It seems that the system can't find Lilo. Although installed in the
MBR of /dev/hdc1 (during installation), it isn't there at all.
Does it help if I create a separate /sbin partition within the 1024
cyl limit? I never had this problem before, I use this setup for more
then 2 years.
Any help would be appreciated.
Regards,
Frank