I had to reinstall my Win98 partition and wiped out the lilo in the MBR. I can boot with installation floppies and get to the menu screen where I can choose linux, rescue etc. If I choose to boot an installed system it just goes to windows and I don't have the choice to boot linux. If I do the rescue system I can boot that, mount my installed system, cd to /etc and execute lilo but it doesn't recognize where it is and apparently does not find the lilo.conf. If I move the lilo.conf to the ramdisk /etc and run lilo I get a message that it doesn't recognize device 0x8182. What am I doing wrong here? I have done all this in the past successfully but I guess I have gotten stale because all this isn't often necessary these days. Any help appreciated. Scott
On Thu, 2003-01-16 at 05:26, J. Scott Thayer, M.D. wrote:
I had to reinstall my Win98 partition and wiped out the lilo in the MBR. I can boot with installation floppies and get to the menu screen where I can choose linux, rescue etc. If I choose to boot an installed system it just goes to windows and I don't have the choice to boot linux.
From the initial CD boot screen you should select Installation. When YaST starts you'll get a new menu. From there, boot installed system should find your linux installation and boot it.
If I do the rescue system I can boot that, mount my installed system, cd to /etc and execute lilo but it doesn't recognize where it is and apparently does not find the lilo.conf.
Assuming you've mounted your system on /mount
cd /mount
chroot . (note the dot here, most people miss it. It's
chroot<space><dot>)
mount -a
/sbin/lilo
should work.
--
Anders Johansson
On Thursday 16 January 2003 05:33, Anders Johansson wrote:
Assuming you've mounted your system on /mount
cd /mount chroot . (note the dot here, most people miss it. It's chroot<space><dot>) mount -a /sbin/lilo
should work.
The same can be accomplished a bit simpler (see also man lilo): /sbin/lilo -r /mount I'm not saying one way is better than the other. I just happen to like the -r option because it is short and sweat. Laziness is not necessarily a bad thing. ;-) Paul.
On Thu, 16 Jan 2003 22:01:24 +0100
Paul Uiterlinden
On Thursday 16 January 2003 05:33, Anders Johansson wrote:
Assuming you've mounted your system on /mount
cd /mount chroot . (note the dot here, most people miss it. It's chroot<space><dot>) mount -a /sbin/lilo
should work.
The same can be accomplished a bit simpler (see also man lilo):
/sbin/lilo -r /mount
I'm not saying one way is better than the other. I just happen to like the -r option because it is short and sweat. Laziness is not necessarily a bad thing. ;-)
There is even another way to do it. :-) 1. boot from the rescue cd 2. mount /dev/hda3 /mnt (or wherever your root is) 3. /mnt/sbin/lilo -C /mnt/etc/lilo.conf That's the one I always remember, because it seems straightforward to my way of thinking. -- use Perl; #powerful programmable prestidigitation
On Thu, 2003-01-16 at 22:09, zentara wrote:
On Thu, 16 Jan 2003 22:01:24 +0100 Paul Uiterlinden
wrote: On Thursday 16 January 2003 05:33, Anders Johansson wrote:
Assuming you've mounted your system on /mount
cd /mount chroot . (note the dot here, most people miss it. It's chroot<space><dot>) mount -a /sbin/lilo
should work.
The same can be accomplished a bit simpler (see also man lilo):
/sbin/lilo -r /mount
I didn't know about that one, nice :)
I'm not saying one way is better than the other. I just happen to like the -r option because it is short and sweat. Laziness is not necessarily a bad thing. ;-)
There is even another way to do it. :-)
1. boot from the rescue cd 2. mount /dev/hda3 /mnt (or wherever your root is) 3. /mnt/sbin/lilo -C /mnt/etc/lilo.conf
hm. Will that find the kernel in /mnt/boot if lilo.conf references
/boot/vmlinuz?
And both methods will still need to mount /boot if it's on a separate
partition.
--
Anders Johansson
On Thursday 16 January 2003 22:20, Anders Johansson wrote:
There is even another way to do it. :-)
1. boot from the rescue cd 2. mount /dev/hda3 /mnt (or wherever your root is) 3. /mnt/sbin/lilo -C /mnt/etc/lilo.conf
hm. Will that find the kernel in /mnt/boot if lilo.conf references /boot/vmlinuz?
No, I don't think so. Therefore you need either the -r option of the chroot.
And both methods will still need to mount /boot if it's on a separate partition.
Sure thing! And make sure that you mount the boot partition on /mnt/boot, not on /boot. Paul.
On Thursday 16 January 2003 22:30, Paul Uiterlinden wrote:
On Thursday 16 January 2003 22:20, Anders Johansson wrote:
There is even another way to do it. :-)
1. boot from the rescue cd 2. mount /dev/hda3 /mnt (or wherever your root is) 3. /mnt/sbin/lilo -C /mnt/etc/lilo.conf
hm. Will that find the kernel in /mnt/boot if lilo.conf references /boot/vmlinuz?
No, I don't think so. Therefore you need either the -r option of ^^ Dooh! Typo: "or" that is.
the chroot.
And both methods will still need to mount /boot if it's on a separate partition.
Sure thing! And make sure that you mount the boot partition on /mnt/boot, not on /boot.
Paul.
On 16 Jan 2003 22:20:43 +0100
Anders Johansson
/sbin/lilo -r /mount
I didn't know about that one, nice :)
There is even another way to do it. :-)
1. boot from the rescue cd
mkdir /boot mount -t ext2 /dev/hda1 /boot
2. mount /dev/hda3 /mnt (or wherever your root is) 3. /mnt/sbin/lilo -C /mnt/etc/lilo.conf
hm. Will that find the kernel in /mnt/boot if lilo.conf references /boot/vmlinuz?
And both methods will still need to mount /boot if it's on a separate partition.
Ooops, that's right. I left out 1 step. mkdir /boot mount -t ext2 /dev/hda1 /boot I knew you would catch that Anders, :-) just like a watchdog. -- use Perl; #powerful programmable prestidigitation
On Thursday 16 January 2003 22:09, zentara wrote:
There is even another way to do it. :-)
1. boot from the rescue cd 2. mount /dev/hda3 /mnt (or wherever your root is) 3. /mnt/sbin/lilo -C /mnt/etc/lilo.conf
That's the one I always remember, because it seems straightforward to my way of thinking.
I don't think that will work correctly. If you run lilo that way, it will still install its stuff in /boot, instead of /mnt/boot. The -C option just overrides the use of the default config file, /etc/lilo.conf. You really need the -r option, or do the chroot before invoking lilo. Paul.
On Thu, 16 Jan 2003 22:27:00 +0100
Paul Uiterlinden
On Thursday 16 January 2003 22:09, zentara wrote:
There is even another way to do it. :-)
1. boot from the rescue cd 2. mount /dev/hda3 /mnt (or wherever your root is) 3. /mnt/sbin/lilo -C /mnt/etc/lilo.conf
That's the one I always remember, because it seems straightforward to my way of thinking.
I don't think that will work correctly. If you run lilo that way, it will still install its stuff in /boot, instead of /mnt/boot. The -C option just overrides the use of the default config file, /etc/lilo.conf. You really need the -r option, or do the chroot before invoking lilo.
Well I did forget to add to mount /boot. It's just another way, it works for me; but it's probably not the best solution. -- use Perl; #powerful programmable prestidigitation
On Friday 17 January 2003 02:02, zentara wrote:
I don't think that will work correctly. If you run lilo that way, it will still install its stuff in /boot, instead of /mnt/boot. The -C option just overrides the use of the default config file, /etc/lilo.conf. You really need the -r option, or do the chroot before invoking lilo.
Well I did forget to add to mount /boot. It's just another way, it works for me; but it's probably not the best solution.
Ah, ok, now I see: you mount your boot partition on /boot, not /mnt/boot. That's why your method works as well. Interesting, so many ways to do something correctly. Paul.
participants (4)
-
Anders Johansson
-
J. Scott Thayer, M.D.
-
Paul Uiterlinden
-
zentara