Bug 24012

Summary: upgrading "lilo" leaves system in non bootable state
Product: [Retired] Red Hat Raw Hide Reporter: Jaroslaw Sosnicki <slavko>
Component: liloAssignee: Doug Ledford <dledford>
Status: CLOSED WONTFIX QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: high    
Version: 1.0CC: slavko
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-01-15 01:14:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jaroslaw Sosnicki 2001-01-15 01:14:16 UTC
1. I am running:
Linux server.domain.com 2.4.0-0.43.12smp #1 SMP Wed Dec 27 18:23:19 EST
2000 i686 unknown
2. I upgraded lilo to:
# rpm -q lilo
lilo-21.4.4-12

3. After rebooting I never get complete boot prompt, it hangs displaying
only
"LIL 

4. Booted with floppy boot disk
OK!
5. executed 
# lilo
Added smp240-043.12 *
Added lin240-043.12

6. Rebooted
OK!

I suggest that you modify RPM script to execute lilo automatically after
upgrade to rewrite boot record

Comment 1 Jeremy Katz 2002-06-04 06:13:58 UTC
Unfortunately, it's impossible to definitively tell whether or not grub or lilo
is being used as the bootloader so running lilo has a very legitimate
possibility of hosing someone's bootloader configuration as well.