I am trying to get mol running on my debian potato install. I downloaded
the mol rpm of version 0.9.53-2, aliened and installed it. After a few
other steps I, molstart notified me that it needs kernel 2.0.4-test10. So
I found a pre-compiled version on the net, and set it up as follows:
As root, I put the vmlinux produced by untarring and unzipping the tar.gz
file of linux-ppc in the /boot. I also placed the System.map file accompanying
vmlinux in /boot. I also placed the modules that came with it in
/lib/modules/2.0.4-test10. I also put a copy of vmlinux on my MacOS
partition in folder /System Folder/kernel images for bootx. I also created
a symbolic link between /vmlinux and /boot/vmlinux (the new kernel).
Now I get the following error message upon rebooting, and I don't know what my
next step should be:
--begin excerpt
Parallelizing fsck version 1.18 (11-Nov-1999)
fsck.ext2: No such file or directory while trying to open /dev/sdb5
(null):
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock
e2fsck -b 8193 <device>
fsck failed. Please repair manually and reboot. Please note
that the root file system is currently mounted read-only. To
remount it read-write:
# mount -n -o remount,rw/
CONTROL-D will exit from this shell and REBOOT the system
--end excerpt
Now /dev/sdb5 is my root partition. How can I fix this problem? What should
I do next? And when I do it, can I easily go back to kernel 2.2.17 which
came from my stable potato? Although I want to run MOL, I don't want to lose
any functionality with a newer unstable kernel.
