LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (http://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Lilo install failed (http://www.linuxquestions.org/questions/slackware-installation-40/lilo-install-failed-282091/)

gmartin 01-25-2005 12:39 PM

Lilo install failed
 
I went through and rebuilt my Slack 10 system and after I went through the final config i recieved an error that lilo failed. And of course on boot there is no OS.

I have two drives in the system, but only partitioned one (/dev/hda). I put a small swap partition as the first partition (/dev/hda1) on the drive and the rest is root (/dev/hda2). I suspect this is the issue. Do I need to have a linux partition as the first partition on my boot drive?

320mb 01-25-2005 01:08 PM

Re: Lilo install failed
 
Quote:

Originally posted by gmartin
Do I need to have a linux partition as the first partition on my boot drive?
Nope...........you can put the /boot partition anywhere you'd like...............

gmartin 01-25-2005 01:28 PM

And will lilo put the MBR in the correct place regardless?

DaHammer 01-25-2005 01:52 PM

It will write to the MBR of whatever device you tell it too in lilo.conf.
Code:

boot="/dev/hda"
Tells lilo to install to the MBR of hda. Anyway, you can install it manually by booting to the rescue disk, CDROM, bootdisks/rootdisks, or some other recovery disk. Once booted just manually mount /dev/hda2, edit the lilo.conf file on it and run lilo with the -C option telling it where the lilo.conf is. An example:

Code:

mkdir -p /mnt/hda2
mount /dev/hda2 /mnt/hda2
---- edit /mnt/hda2/etc/lilo.conf to suit your needs ----
ln -sf /mnt/hda2/boot /boot
/mnt/hda2/sbin/lilo -C /mnt/hda2/etc/lilo.conf
umount /mnt/hda2
reboot

Edit: The above method has potential for problems. Use one of the below methods instead:

Code:

mkdir -p /mnt/hda2
mount /dev/hda2 /mnt/hda2
chroot /mnt/hda2
---- edit /etc/lilo.conf to suit your needs ----
/sbin/lilo
exit
umount /mnt/hda2
reboot

Or if you're using the Slackware CD or bootdisk/rootdisk combo, then you could also just boot straight into your root, by typing "mount root=/dev/hda2" and the boot: prompt. Then just edit the /etc/lilo.conf, run lilo and reboot. However, you must have the modules for whatever kernel version the CD or bootdisk/rootdisk uses installed on /dev/hda2 if you need any of them. Otherwise you'll get errors, may still work well enough though.

glaz 01-26-2005 10:13 PM

I am encountering the exact same problem!

when i do the following:
/mnt/hda2/sbin/lilo -C /mnt/hda2/etc/lilo.conf

it gives me a message:
Fatal: Sorry, don't know how to handle device 0x0100

any clues on what this error might mean?

DaHammer 01-27-2005 03:40 AM

Quote:

Originally posted by glaz
I am encountering the exact same problem!

when i do the following:
/mnt/hda2/sbin/lilo -C /mnt/hda2/etc/lilo.conf

it gives me a message:
Fatal: Sorry, don't know how to handle device 0x0100

any clues on what this error might mean?

I replied to your thread in the main Slackware forum. Also notice I updated my post above.

gmartin 02-01-2005 09:56 PM

I need to work on this more often...

When I boot this system, I get a message that says:
No boot signature in partition
Operating System not found

Here's what I did:

- I booted to slackware install. Ran install allowed it to run lilo and it failed

- I rebooted to the slack install and based on above, I mounted /dev/hda2 as /u/

- ran chroot /u/

- cd /sbin

- lilo -C /etc/lilo.conf -M /dev/hda - v

- results:
/boot/boot.0300 exists - no /dev/hda backup copy made
The Master Boot Record of /dev/hda has been updated


Here's what I know:

- /dev/hda2 is marked as bootable

Contents of lilo.conf:

lba32
boot = /dev/hda (also tried /dev/hda2 - which is correct?)
message = /boot/boot_message.txt
prompt
timeout = 1200

change-rules
reset
vga = 790

image = /boot/vmlinuz
root = /dev/hda2
label = Linux
read-only

on running liloconfig
If I chroot to /u (see above) and run liloconfig, it tells me it returned an error and won't run. If I capture stderr, I see references to "cannot open /proc/partitions". Which of course it cannot because /proc is not under this chroot.

If I try liloconfig without chroot it does nothing and simply drops back to the prompt

Any thoughts on this madness?


All times are GMT -5. The time now is 12:35 PM.