Re: Can't get fs recognized as ext3
* Mark Roach <mrroach@okmaybe.com>, 2002-08-08 10:47 -0400:
> On Wed, 2002-08-07 at 16:48, Andre Berger wrote:
> > > Q. Why isn't my root fs mounting as ext3? I already ran tune2fs -j on
> > > it and updated /etc/fstab, and all my other volumes mount as ext3,
> > > but the root insists on remaining ext2.
> > >
> > > A. The problem is most likely that ext3 is not available when your
> > > root fs is being mounted, so the kernel defaults to ext2. You
> > > probably have ext3 built as a module. If you use initrd, then make
> > > sure the ext3 module is included in it. If you do not use initrd,
> > > recompile your kernel for built-in ext3 support (or start using
> > > initrd, making sure to include ext3).
> >
> > I use initrd, how can I "make sure the ext3 module is included in
> > it"?
> >
>
> Hi, Andre. I haven't seen this asked and just thought I'd check (no
> offense) Is your bootloader passing the initrd option to your kernel?
>
> in lilo, that means putting the line initrd=/initrd.img
> in grub, it's initrd /initrd.img
Yes, here in /etc/lilo.conf:
image=/boot/vmlinuz
initrd=/boot/initrd.img
label=Linux
read-only
restricted
with the correct symlinking.
> Like I said, wasn't sure if you knew to do that or not. Also, to add a
> little fuel to the initrd-vs-static fire, I have heard that compiling
> modules statically will not be possible at some future point and that
> initrd will be the standard pre-boot modules loading method.
I don't really have an opinion on that, but I think the documentation
should be improved.
-Andre
Reply to: