I just installed Mageia 2 RC 1 on a server system with the following hardware: Supermicro X8STE motherboard Intel "Westmere" Xeon CPU W3680 CPU WD 320 GB SATA OS drive 3x 3ware 9750 RAID cards Installed to the 320 GB WD SATA drive. At Bootloader installation, chose "Lilo" Rebooted system Got Lilo menu Stopped on second line "Starting Linux" and just sat there for a long time and didn't do anything. Reinstalled OS and this time chose "Grub" Worked fine, except for an error at the first boot screen: "ERST: Failed to get Error Log Address Range" That message sat on the screen for about 15-20 seconds until Grub continued to boot Mageia. (I will file another bug for that) Questions: 1. Is there a problem with lilo? 2. Had I waited longer with lilo, would I have indeed booted? Was the "ERST" error hidden? 3. Could the Lilo issue be related to the fact that I configured a password in the Bootloader configuration screen? This is a very confusing dialog box. It does not explain FOR WHAT you are setting a password. It does not say "Bootloader Password". It only says "Password"
Thierry, Pascal, a duplicate or a new bug about lilo ?
CC: (none) => pterjan, thierry.vignaud
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
I'm not the original reporter, but I can confirm I have seen the same problem on 2 of my systems using the official Mageia 2 release. Both systems were upgraded from Mageia 1 by using mgaapplet-upgrade-helper as directed in the release notes. Neither system could boot the 3.3.6 kernel after upgrade, but could boot the kernels left behind from the Mageia 1 installation (although with many problems due to the difference in initscripts etc). I believe the problem is due to creating a very large initrd. The post install initrd was about 18MB on both systems. I was able to use dracut -f to shrink the initrd to 7MB and after that lilo was able to boot the systems normally.
CC: (none) => rob
This may be a duplicate of bug 4912. How much free space is there in /boot?
CC: (none) => davidwhodgins
Plenty of free space: [root@jalapeno robt]# df /boot Filesystem Size Used Avail Use% Mounted on /dev/md1 147M 57M 84M 41% /boot
I am not bothering with lilo any more, so I am not going to retest. Sorry. But it sounds like the problem has been reproduced and diagnosed by Robert. Thanks Robert.
Keywords: NEEDINFO => (none)Summary: Lilo Bootloader Could Not Boot After Mageia 2 RC 1 Installation => Lilo Bootloader Could Not Boot After Mageia 2
Created attachment 4239 [details] Error messages shown when trying to boot with lilo. I'm getting the attached error trying to boot lilo on an i586 install, done using the Mageia 4 alpha 1 pre-release i586 kde live dvd. An install with lilo using the x86_64 dvd works.
CC: (none) => tmbWhiteboard: (none) => 4alpha1
Adding Colin. Not sure if the error shown in comment 7 is actually from "too large" an initrd, or a kernel problem, or a dracut problem.
CC: (none) => mageia
Since M4 installer won't change: did anyone see this in M5? If yes, please change summary & whiteboard. If improved, please close. Thanks.
Summary: Lilo Bootloader Could Not Boot After Mageia 2 => Lilo Bootloader Could Not Boot After Mageia 4
CC: (none) => nicSummary: Lilo Bootloader Could Not Boot After Mageia 4 => Lilo Bootloader Could Not Boot After Mageia 5
Summary: Lilo Bootloader Could Not Boot After Mageia 5 => Lilo Bootloader Could Not Boot After Mageia 4Whiteboard: 4alpha1 => 5Beta3
Appears to be fixed
Status: NEW => RESOLVEDResolution: (none) => FIXEDWhiteboard: 5Beta3 => (none)