Solved

Mandrake 9.2 lilo "9A 9A" on boot

Posted on 2004-08-23
1
509 Views
Last Modified: 2013-12-15
I recently created a boot diskette following the directions on the Mandrake site: "...install LILO onto the MBR of a floppy by executing the following as root:

lilo -v -b /dev/fd0

But now it will only boot from this diskette. Without it I am getting a screen full of "9A 9A..." and then a freeze.

Looking at the manual, I see that the -b has changed the boot device to the floppy which was intended to serve as a backup only. Also from the manual: "...map file is not readable, likely because LILO was not re-run after some system change."

Starting this week the server is now hosting some websites, so more experiments are out. Does anyone have the exact "re-run" parameters to set it to boot from the hard disk and still retain the floppy for emergencies?

The lilo.conf:
boot=/dev/hdc
map=/boot/map
default="linux"
keytable=/boot/us.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
        label="linux"
        root=/dev/hdc1
        initrd=/boot/initrd.img
        append="devfs=mount splash=silent acpi=ht splash=silent"
        vga=788
        read-only
image=/boot/vmlinuz
        label="linux-nonfb"
        root=/dev/hdc1
        initrd=/boot/initrd.img
        append="devfs=mount splash=silent acpi=ht"
        read-only
image=/boot/vmlinuz-secure
        label="linux-secure"
        root=/dev/hdc1
        initrd=/boot/initrd-secure.img
        append="devfs=mount splash=silent acpi=ht splash=silent"
        read-only
image=/boot/vmlinuz-smp
        label="linux-smp"
        root=/dev/hdc1
        initrd=/boot/initrd-smp.img
        append="devfs=mount splash=silent acpi=ht splash=silent"
        read-only
image=/boot/vmlinuz-2.4.22-10mdk
        label="old_linux-nonfb"
        root=/dev/hdc1
        initrd=/boot/initrd-2.4.22-10mdk.img
        append="devfs=mount acpi=ht"
        read-only
image=/boot/vmlinuz
        label="failsafe"
        root=/dev/hdc1
        initrd=/boot/initrd.img
        append="devfs=nomount splash=silent acpi=ht failsafe"
        read-only
other=/dev/fd0
        label="floppy"image=/boot/vmlinuz-2.4.22-10mdk
        label="old_linux-nonfb"
        root=/dev/hdc1
        initrd=/boot/initrd-2.4.22-10mdk.img
        append="devfs=mount acpi=ht"
        read-only
image=/boot/vmlinuz
        label="failsafe"
        root=/dev/hdc1
        initrd=/boot/initrd.img
        append="devfs=nomount splash=silent acpi=ht failsafe"
        read-only
other=/dev/fd0
        label="floppy"
        unsafe

0
Comment
Question by:apgw
1 Comment
 
LVL 17

Accepted Solution

by:
owensleftfoot earned 125 total points
ID: 11879024
Just running the command "lilo" from the console should fix it.
0

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Linux users are sometimes dumbfounded by the severe lack of documentation on a topic. Sometimes, the documentation is copious, but other times, you end up with some obscure "it varies depending on your distribution" over and over when searching for …
Fine Tune your automatic Updates for Ubuntu / Debian
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question