Bug 798 - boot fails after install if older lilo left at sda
Summary: boot fails after install if older lilo left at sda
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-13 12:03 CEST by Tony Blackwell
Modified: 2011-04-13 12:05 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Tony Blackwell 2011-04-13 12:03:10 CEST
Description of problem:
Boot failed after install due to issues between old lilo and current lilo.

Previously:
I have lilo from Mandriva 2009 installed on sda.  At various subsequent linux installs into sda2, sda3 or sda5 I've installed the boot code into that sda partition rather than root of sda, then just edited lilo.conf in the 2009 partition with a couple of "other=" and "label=" lines and re-run lilo to access the newly installed partition.

Now: did the same, installing mageia lilo into sda2, but reboot failed with that old L 99 99 99 99 screenful. Booting older rescue DVD, chroot to the older mounted partition, running lilo didn't fix.  Using old Mandriva rescue DVD's to reinstall old windows boot didn't fix.


Fix was ultimately simple.  Just replace the old 2009 or 2010 lilo at sda with current lilo from the mageia DVD.  Worked like a charm after that.

The issue that stumped me for a while was how installing lilo only to the mageia sda2 partition and not touching the sda lilo from 2009 could kill the system booting.  Any ideas?  Any ongoing issues?


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


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Tony Blackwell 2011-04-13 12:05:47 CEST
I'm marking this as resolved but filed the bug in case others get caught

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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