Changing journaling mode on root / loop-aes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 08, 2002 at 11:40:26AM -0700, Tener, Stuart B., IT3 , USNR-R wrote:
> 	(c) I then made sure that /etc/fstab had the "data=journal"
> option in the root partition entry. Then I verified that
> "rootflags=data=journal" was placed in the /etc/grub/grub.conf file
> properly, and rebooted. However, the same result occurred the "03:06"
> boot error...AGAIN!?! ARGH!!!

Sorry to join this party late, but ....

You say elsewhere in this thread that you are using a RH7.3ish system
with an initrd.  But the rootflags=data=journal flag is only for use
when ext3 is compiled into the kernel.  [Someday Rusty Russell will
unify param handling, $DEITY willing.]  When using an initrd with the
ext3 and jbd modules, you need to place the appropriate options in
/etc/fstab, and remake the initrd.  Caveat: the version of mkinitrd
that shipped with RH7.3 does not do this automatically.  In fact, it
was added on 2002/05/21 by Erik Troan:

   * Tue May 21 2002 Erik Troan <ewt@redhat.com>
   - use options from fstab for root filesystem (56071)

[Courtesy of "rpm -q --changelog mkinitrd" on my box.]

The number in parentheses is the bugzilla number; see
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=56071

So what you have to do is go to Rawhide and grab a recent mkinitrd,
install it with rpm -Uvh mkinitrd-*.i386.rpm,
then rebuild your initrd.

Something like:

   rpm -Uvh mkinitrd-3.4.12.i386.rpm
   cp /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.sav
   mkinitrd -v /boot/initrd-`uname -r`.img `uname -r`

and reboot.

Regards,

   Bill Rugolsky






[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux