Description of problem: When root filesystem is of type XFS, mkinitrd fails to include ext2, ext3 and ext4dev modules. Version-Release number of selected component (if applicable): mkinitrd-6.0.52-2.fc9.i386 any FC9 kernel How reproducible: 100% Steps to Reproduce: 1.mkinitrd 2.reboot Actual results: System fails to start, because it cannot mount the ext3 filesystems(/boot and /home) Expected results: Make mkinitrd include all necessary modules. Additional info: Workaround is to run mkinitrd with additional arguments: -preload=ext2 --preload=ext3 --preload=ext4dev
They should then later get loaded when the filesystem tries to be mounted. What does your /etc/fstab look like?
UUID=e4e9bf00-4a21-48fe-9d8d-b36ebc33d574 / xfs defaul ts 1 1 UUID=dc20a23b-44a7-4f1a-9ebd-b73111e6edea /boot ext3 defaul ts 1 2 UUID=2f90cf80-334c-11dd-9a1c-00265411f72f /home ext3 defaul ts 1 2 UUID=ade3ac12-334d-11dd-ab99-00265411f72f /var/www/html ext3 defaul ts 1 2 UUID=42467476-339d-11dd-9ceb-00265411f72f /tmp ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 UUID=2ba8cdf5-764f-475e-bd69-4b9afb053e96 swap swap defaul ts 0 0 Error message is that the sysyem cannot resolve the UUID for the ext3 file systems.
I have switched to a different motherboard and eliminated a SCSI controller and a SCSI disk, and now system boots OK.
These modules aren't needed by the initrd; rc.sysinit mounts those filesystems. As such, this appears to be an initscripts bug.
initscripts doesn't need to do anything for the modules - they're on the normal system at that point. Closing re comment #3.