From: Henrik.Carlqvist@deadspam.com
On Fri, 10 Mar 2023 08:01:50 +0000, root wrote:
> Henrik Carlqvist wrote:
>> /sbin/lilo -r /sda2
> I have seen many times that Lilo fails if it can't find the kernel
> mentioned in lilo.conf, or if a partition is called for that it can't
> find.
Yes, that can happen if your /boot directory lives on another partition
than the / directory. I so, you will need to mount also the /boot
partition correctly below the directory you point out with the -r option.
In short lilo needs the file /etc/lilo.conf and any file that
configuration file points to. Usually all files pointed to by lilo.conf
resides below /boot.
So if you from your live media mount your root partition at /sda2 and you
have /boot on a separate partition you will also need to mount that
partition below /sda2/boot. When called with "lilo -r /sda2" lilo
initially expects to find:
/sda2/etc/lilo.conf
Once that file has been parsed lilo will probably expect to find kernels
and stuff below
/sda2/boot
> I do the mkinitrd when I change the kernel being used by lilo. In this
> case lilo on sda2 was using a custom kernel I built and it had not been
> changed.
Lilo is not supposed to break unless the MBR has been tampered with in
some way or the files pointed to by lilo has been removed or moved to
other blocks on the disk. Lilo in the MBR does not parse file systems, it
remembers the position on disk that the kernel resides on. Doing things
like "mv /boot/vmlinuz /tmp; mv /tmp/vmlinuz /boot" might from a users
point of view on the /boot file system look as if nothing has changed but
will most likely break lilo as the kernel might have moved to another
block on the disk.
regards Henrik
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
