Bug 107550 - lilo /boot/message doesn't exist
lilo /boot/message doesn't exist
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-10-20 11:03 EDT by Javier Ballesteros
Modified: 2007-04-18 12:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-20 11:19:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Javier Ballesteros 2003-10-20 11:03:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030516
Mozilla Firebird/0.6

Description of problem:
When the instalation process is started via ks=floppy, and a ks.cfg using lilo
to install on the mbr, all seems good, but at the final step when lilo is run
the console log shows an error:

Fatal error: open /boot/message: No such file or directory

That's is rigth, because in the directory /boot of the system installed there is
no message file, so I think there's an error in the lilo.conf, because has a
reference on a file that not exists, I mean the line:


You have to kill the message line from de lilo.conf.The 'dirty' solution, is to
put something like that in the %post section of the ks.cfg:


mv /etc/lilo.conf /tmp
cat /tmp/lilo.cong | grep -v message > /etc/lilo.conf
/sbin/lilo -v -v -v

With that lines the the lilo is executed in the instalation process, then
reboots and all it's O.K.  The mbr is finally written.

Another solution is reboot with the Red Hat CD in rescue mode, mount the
partitions and do a chroot over your root partition, edit lilo.conf, delete
message line, run lilo and then reboot. This is harder solution, but it's OK if
you have finished your intalation process and your system is not booting.


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install normally
2. Run the ks=floppy
3. When you reboot, mbr is 'untouched' (lilo is not run)

Actual Results:  You cannot boot, because when lilo througth the error , it's no
executed (so the mbr is clean)

Additional info:


#Generated by Kickstart Configurator

#System language
lang es_ES

#Language modules to install
langsupport es_ES

#System keyboard
keyboard es

#System mouse
mouse --emulthree genericps/2

#System timezone
timezone --utc Europe/Madrid

#Root password
rootpw --iscrypted $1$DbYZDtL.$ZoDZLb5l1lYEOwHCXxUpj/

#Modo texto

#Reboot after installation

#Install Red Hat Linux instead of upgrade

#Use CDROM installation media

#Clear the Master Boot Record
zerombr yes

#Clear all partitions from the disk
clearpart --all --initlabel 

#Disk partitioning information
part / --fstype ext3 --size 3000 --asprimary --ondisk sda
part swap --size 1000 --ondisk sda
part /var --fstype ext3 --size 1 --grow --ondisk sda
part /datos --fstype ext3 --size 1 --grow --ondisk sdb

#System bootloader configuration
bootloader --useLilo --linear --location=mbr

#Use static networking
network --device eth0 --bootproto static  --ip  --netmask  --gateway --hostname javi.prueba.es

#System authorization information
auth  --useshadow  --enablemd5

#Firewall configuration
firewall --disabled 

#Do not configure the X Window System

%packages --resolvedeps
@Spanish Support


mv /etc/lilo.conf /tmp
cat /tmp/lilo.conf | grep -v message > /etc/lilo.conf
/sbin/lilo -v -v -v
Comment 1 Jeremy Katz 2003-10-20 11:19:48 EDT
/boot/message is in redhat-logos, if you're using lilo, you should really
install the package.  Newer anaconda tries to be smarter and keep this from
causing a problem if it doesn't exist, though.

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