Linux + Linux multiboot

[webstop]

I have RedHad running on hda and want to install another Linux on hdc to multiboot with LILO. For some reason, any attempt to boot into Linux installed on hdc results in all sorts of error messages related to improperly mounted/unmounted file systems.
If someone has multi-linux setup on his box, please consider posting the content of his lilo.conf file here. This will help me to figure out, what am I doing wrong.
Thank you.

[webstop]

Anyone?

[furrycat]

Well if you can get as far as seeing an error about mounting filesystems LILO is obviously working. You didn't by any chance install the second copy of Linux and then change the disks over did you? If you did then it's possible your /etc/fstab contains incorrect values, ie /dev/hdaX instead of /dev/hdcX. Of course, it could be something else... Post the exact errors you're getting and someone might recognise the problem.

[webstop]

Thanks for response, furrycat.
Here is what happening.

1. The very first attempt to boot into the second Linux on hdc brings the following message: "hdc1 was not clearly unmounted. Check forced. ... 6% non-contiguous".
During the following shutdown phase: "unmounting OK"
Second and subsequent boots: "hdc1 is mounted. Running e2fck on mounted
filesystem may cause filesystem damage. Yes or No?"

2. My current Lilo.conf on hda contain the following lines:
boot = /dev/hda
...
map = /boot/map
install = /boot/boot.b
image = /boot/vmlinuz-2.2.14-5.0
label = Red Hat Linux
root = /dev/hda5
image = /boot/vmlinuz
label = Second Linux
root = /dev/hdc1

3. Hardware:
Pentium 166
Soyo 5TF mobo
SB 16 sound
Cirrus Logic 5430 video
Realtek NE2000 compatible card
HDA 1023 cyls, 64 heads in LBA mode or 4092 cyls and 16 heads in Normal mode.
HDC 621 cyls and 64 heads in LBA mode or 2484 cyls and 16 heads in Normal mode.
Both hard disks are set in LBA mode.

4. I did not change hard disks.

[furrycat]

Well if the partition was unmounted OK then you shouldn't see "/dev/hdc1 is mounted". Maybe it's confused because you didn't put the option "read-only" in that install's section of lilo.conf. Try that.