- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: errors after editing lilo..conf
Operating System - Linux
1822512
Members
2459
Online
109642
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2002 03:51 PM
02-15-2002 03:51 PM
errors after editing lilo..conf
Can someone tell me what the
below error messages mean from running "lilo" after making
modifications to the /etc/lilo.conf file? I have included the entries made to /etc/lilo.conf here. I made each entry singularly, then
ran /sbin/lilo on each line.
I have installed RH Linux 7.0, and RH Linux 7.2 on the respective partitions listed in /etc/lilo.conf and
can boot from both partitions
using its bootable floppy disks created after installing
Os'es. Here's the lilo.conf file here:
prompt
timeout=50
default=linux7_2
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
image=/boot/vmlinuz-2.4.7-10
label=linux7_2
initrd=/boot/initrd-2.4.7-10.img
read-only
root=/dev/hda7
#First entry made, then lilo is run. 1st entry was
#commented out before second entry is made and lilo
#ran.
#Fatal: First sector of /dev/hda1 doesn't have a valid boot signature
#other=/dev/hda1
#label=linux7_0
#Second entry made.
#Fatal: open /boot/vmlinuz-2.2.16-22: No such file or directory
#image=/boot/vmlinuz-2.2.16-22
#label=linux7_0
#initrd=/boot/initrd-2.2.16-22.img
#read-only
#root=/dev/hda1
below error messages mean from running "lilo" after making
modifications to the /etc/lilo.conf file? I have included the entries made to /etc/lilo.conf here. I made each entry singularly, then
ran /sbin/lilo on each line.
I have installed RH Linux 7.0, and RH Linux 7.2 on the respective partitions listed in /etc/lilo.conf and
can boot from both partitions
using its bootable floppy disks created after installing
Os'es. Here's the lilo.conf file here:
prompt
timeout=50
default=linux7_2
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
image=/boot/vmlinuz-2.4.7-10
label=linux7_2
initrd=/boot/initrd-2.4.7-10.img
read-only
root=/dev/hda7
#First entry made, then lilo is run. 1st entry was
#commented out before second entry is made and lilo
#ran.
#Fatal: First sector of /dev/hda1 doesn't have a valid boot signature
#other=/dev/hda1
#label=linux7_0
#Second entry made.
#Fatal: open /boot/vmlinuz-2.2.16-22: No such file or directory
#image=/boot/vmlinuz-2.2.16-22
#label=linux7_0
#initrd=/boot/initrd-2.2.16-22.img
#read-only
#root=/dev/hda1
Life is beautiful
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2002 02:20 PM
02-17-2002 02:20 PM
Re: errors after editing lilo..conf
Hello,
The problem here is very simple : let's suppose you are currently running RedHat 7.2. Of course, your /boot is available for lilo to find the kernel, the initrd, the map file, and other information needed to build a boot sector.
However, the /boot you are using does not contain anything related to RedHat 7.0, because as you may have noticed, the partitions are not the same.
Now, let's find a way to solve this problem.
1. The bad way
Manually mount the /boot from RedHat 7.0, then copy the files needed by lilo to take the kernel 2.2.16 into account.
Why is it bad ? When booted on RedHat 7.0, imagine that you have to change something in the kernel or lilo configuration : you will have to do the same thing (mount the /boot from RedHat 7.2, etc...).
2. The good way
Boot on RedHat 7.0 and upgrade LILO program (from RedHat 7.2 cdroms) to make sure you have the same version of lilo on both versions.
Manually mount the /boot partition from RedHat 7.2, then copy the kernel and System.map-2.2.16... from 7.0 to 7.2's /boot directory.
Edit your /etc/fstab to make the /boot partition from 7.2 being your /boot on 7.0.
Move /etc/lilo.conf into the newly mounted boot, and create a symbolic link from /etc/lilo.conf to /boot/lilo.conf.
Edit your /boot/lilo.conf and make it boot both 7.0 and 7.2.
Use /sbin/lilo to refresh bootable sectors on the disk.
Reboot in 7.2, remove /etc/lilo.conf and make /etc/lilo.conf being a symlink to /boot/lilo.conf.
Good luck.
Kodjo
The problem here is very simple : let's suppose you are currently running RedHat 7.2. Of course, your /boot is available for lilo to find the kernel, the initrd, the map file, and other information needed to build a boot sector.
However, the /boot you are using does not contain anything related to RedHat 7.0, because as you may have noticed, the partitions are not the same.
Now, let's find a way to solve this problem.
1. The bad way
Manually mount the /boot from RedHat 7.0, then copy the files needed by lilo to take the kernel 2.2.16 into account.
Why is it bad ? When booted on RedHat 7.0, imagine that you have to change something in the kernel or lilo configuration : you will have to do the same thing (mount the /boot from RedHat 7.2, etc...).
2. The good way
Boot on RedHat 7.0 and upgrade LILO program (from RedHat 7.2 cdroms) to make sure you have the same version of lilo on both versions.
Manually mount the /boot partition from RedHat 7.2, then copy the kernel and System.map-2.2.16... from 7.0 to 7.2's /boot directory.
Edit your /etc/fstab to make the /boot partition from 7.2 being your /boot on 7.0.
Move /etc/lilo.conf into the newly mounted boot, and create a symbolic link from /etc/lilo.conf to /boot/lilo.conf.
Edit your /boot/lilo.conf and make it boot both 7.0 and 7.2.
Use /sbin/lilo to refresh bootable sectors on the disk.
Reboot in 7.2, remove /etc/lilo.conf and make /etc/lilo.conf being a symlink to /boot/lilo.conf.
Good luck.
Kodjo
Learn and explain...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP