OK...make sure you have "jdb" and "ext3" listed for INITRD_MODULES in /etc/rc.config. I have it as: INITRD_MODULES="lvm-mod jbd ext3" Then: # mk_initrd; lilo The ext3 modules depends on jbd (Journaling Block Device) module to load properly. so, if jbd is not available in initrd, ext3 module will not load and the filesystem would be mounted as an ext2. HTH. Cheers, -- Nadeem Hasan nhasan@nadmm.com http://www.nadmm.com/ Purple Shirt wrote:
the changelog for aa_base does. ok. but the changelog within mk_initrd is useless then and confusing. It just compounds to what I described before as less than stellar way to handle a bugfix. I guess they should change the ext3 web page and point to the update aaa_base package instead of mk_initrd script itself.
anyhow this still doesn't solve my problem of my /dev/root being mounted as ext2 even though I set it up as ext3 at time of installation.
mk