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?
Re: Lilo install failed
And will lilo put the MBR in the correct place regardless?
It will write to the MBR of whatever device you tell it too in lilo.conf.
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 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
/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:
boot = /dev/hda (also tried /dev/hda2 - which is correct?)
message = /boot/boot_message.txt
timeout = 1200
vga = 790
image = /boot/vmlinuz
root = /dev/hda2
label = Linux
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:38 AM.|