Yesterday I ran online update, and when I updated the kernel, there was a message that told me to run /sbin/lilo after the update but before the reboot. So, I ran /sbin/lilo before I rebooted, but it said that there was an error, the default image didn't exist. Therefore I took a look in /etc/lilo.conf. Before the update there were three entries for the bootloader menu, but now there was one new entry added for the new kernel version, which was marked as the default booting choice. Then I went to the /boot folder and as there was a file named something like (don't remember exactly right now) vmlinuz-2.6.* (where * is the rest of the kernel version number) it seemed to me that the file actually existed.

Then I rebooted and when entering lilo I noticed that there was only the three old entries, the new one wasn't there... So when I chose the old default and continued booting, the computer stopped pretty soon and told me that no file systems could be mounted. There it stopped...

I suppose that the error I got from lilo the before I rebooted was correct then... How do I fix it?

I guess the procedure is to boot off a livecd, mount the /boot or / partition and then change the lilo configuration in some way.

At the moment I'm stuck at mounting /boot and /, both these are software raid volumes, which by the way is the reason why I use lilo instead of grub. My Suse 10.2 livedvd had a kernel panic when it was trying to boot, so I'm trying with a Kubuntu-dvd instead, but at the moment I'm stuck...

Is there some way to use the boot option command line in lilo to boot from something that's not mentioned in lilo.conf, or do I have to use a livecd and reconfigure lilo?


EDIT:
The problem is now solved. If anyone is interested, here is what I did:
  1. Booted from a Kubuntu 6.10 live-dvd
  2. Installed mdadm on the live-dvd system with the live-dvd package manager
  3. Activated the raid volumes:
    Code:
    mdadm --assemble /dev/md0 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
mdadm --assemble /dev/md1 /dev/sda5 /dev/sdb5 /dev/sdc5 /dev/sdd5
  4. Mounted /dev/md1:
    Code:
    mkdir /mkt/md1
mount /dev/md1 /mnt/md1
  5. Used chroot to mount /dev/md1 as / and mounted /dev/md0 as /boot:
    Code:
    chroot /mnt/md1
mount /dev/md0 /boot
  6. After using chroot there where only md devices in /dev, no devices like sda, sdb or so. A workaround:
    Code:
    mknod /dev/sda b 8 0
mknod /dev/sdb b 8 16
mknod /dev/sdc b 8 32
mknod /dev/sdd b 8 48
mknod /dev/sda3 b 8 3
mknod /dev/sdb3 b 8 19
mknod /dev/sdc3 b 8 35
mknod /dev/sdd3 b 8 51
  7. After correcting the spelling mistake in /etc/lilo.conf, lilo was tested:
    Code:
    /sbin/lilo -v -t -C /etc/lilo.conf
  8. Then the MBR was overwritten:
    Code:
    /sbin/lilo -v -C /etc/lilo.conf


Now my system works again, I hope someone will get any use of what I just put down.