From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461) Description of problem: The root filesystem will only make the transition from ext2 to ext3 if I use initrd=/boot/initrd-2.4.9-31.img in lilo.conf, initrd=/boot/initrd-2.4.9- 31enterprise.img will mount root as ext2. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.change lilo.conf to initrd=/boot/initrd-2.4.9-31enterprise.img 2.lilo -v 3.reboot Actual Results: cat /proc/mounts shows root as ext2, even though /etc/fstab was changed and tune2fs -j was run on root If I change lilo.con back to initrd=/boot/initrd-2.4.9-31.img then cat /proc/mounts shows root as ext3 Expected Results: root should have mounted as ext 3 Additional info:
Created attachment 47360 [details] /etc/fstab
Created attachment 47361 [details] /etc/lilo.conf
The attached lilo.conf looks correct. Is this the one before or after your change (eg is this the one that works or the one that broke ?)
The attached lilo.conf is the one that does NOT mount root as ext3, it is broken in other words. If I reboot and use the linux-up label then root is mounted as ext3 but of course I lose the smp features of the kernel.
This looks like the initrd is corrupt. It's possible to recreate it by hand but if you still have the kernel rpm handy it's easier to rpm -e kernel-smp-2.4.9-31 and then rpm -i it again
Case closed, thank you for the tip. Here is what I did: 1. rpm -e kernel-enterprise-2.4.9-31 2. rpm -ivh kernel-enterprise-2.4.9-31.i686.rpm 3. rm /boot/initrd-2.4.9-31enterprise.img 4. mkinitrd /boot/initrd-2.4.9-31enterprise.img 2.4.9-31enterprise 5. lilo -v 6. reboot and root was mounted as ext3 Upon reflection, I may have initially been careless in mkinitrd and created the image with 2.4.9-31 instead of 2.4.9-31enterprise. In any case it works now and I appreciate your help.
Note that rpm -i is *supposed* to make the proper initrd for you already ;)