On Fri, 26 Mar 2004 03:02:37 +0530, "Ritesh Raj Sarraf"
> "Jemshad O K" <jm_list@...> wrote:
> > I had already posted my problem once in this list. Its like this:
> Got any success with the problem ?
not yet :-(
> > I compiled the new kernel, with ext3 as modules. I have the / filesystem
> > also ext3 - but I do have initrd. Now, the real problem is that, I
> > changed the fstab entries and made all partitions from ext3 to ext2. Then
> > also, the kernel was trying to mount the / file system as ext3 and it
> > failed at that point. :-\
> You define ext2 in your fstab. You complain that fstab is not being read
> by the kernel that is why it's mounting the root partition still as ext3.
> Doesn't the kernel, to read the fstab file, require to mount the root fs
> ? If I'm not wrong, fstab resides on the root partition.
> > So my questions are:
> > 1) Why is the kernel not loading the ext3 module when required
> Read /usr/src/linux-$VERSION/Documentation/initrd.txt
> > 2) Why is it trying to mount filesystems as ext3 even when I specified it
> > as ext2
> I hope there might be other errors, how have you enabled your IDE/SCSI
> disk support. How did you create your initrd image ? Did you miss any
> option while selecting the options in config/menuconfig/xconfig ?
I used the old .config, checked if everything is okay with menuconfig,
added some more features and juz compiled. So it should not be the case
of missing options. Also, as you said, since the kernel is unable to
mount / fs, it may not be reading fstab.
What I doubt is, kernel may be reading the partition information like
what tune2fs says
Filesystem features: has_journal filetype needs_recovery
and it is trying to mount as ext3 since the filesystem has got journal ?.
Jemshad O K http://jemshad.com
Deru Communications http//deru.net
"I know Karate, Kung Fu, and 47 other dangerous words"
http://www.fastmail.fm - Faster than the air-speed velocity of an
unladen european swallow