I'm trying to switch a red-hat enterprise box from booting with a ram
disk (initrd) to boot without it. And I got some problems with e2fsck.

I'm booting with lilo, if in lilo.conf I leave the kernel option for
read-only then I can see a few errors (like hwclock) reporting that
files cannot be opened or used, and then at the point that fsck will
check the file system integrity I see a log saying that fsck just
failed and then I'm presented with this sort of interactive recovery
console.

Now, if instead of read-only I change lilo.conf to read-write then the
first errors goes away, but again the fsck section fails. This time
with an error reporting that the file system is already mounted.

Now, if in /etc/rc.d/rc.sysinit I comment out the fsck check (keeping
read-write in lilo) then the system will boot successfully. In
rc.sysinit fsck is program to run as 'fsck -T -a $rootdev $fsckoptions'

Is there some help for booting without an initrd?

thanks,
Rodrigo