Bug 161406

Please attach your /etc/modprobe.conf ?

I had similar problem to that described in several fora: 
http://forums.fedoraforum.org/showthread.php?t=59320
mount: error 6 mounting ext3.

I have an acer laptop, and found I had to add the following modules to the
initrd that comes with fc4, in order to recognise my root partition:

ata_piix, libata, sr_mod, sd_mod, scsi_mod

Matt Davey

I have included my regular /etc/modprobe.conf. I have to question its relevance
to this problem though, as we are talking about mkinitrd running in the install
system setup and not the regular running filesystem (does in use chroot to run
under the filesystem?). I am attaching my mkinitrd just for reference as to what
my system needs, but I don't know if it is what my system sees during install
time when running from the installation disk. I found that when the install disk
goes into rescue mode, there is no /etc/modprobe.conf file on the filesystem
(the original modprobe.conf will be available at /mnt/sysimage/etc). You will
find a shortened version of modprobe.conf  on /tmp/modprobe.conf. I am attaching
that too for your reference. But I checked, and they both contain the necessary
modules. It could be that for some reason the modprobe.conf file was not
available or was messed up only during the system upgrade. I only had a chance
to look at the installation's modprobe.conf file now, by putting it in rescue
mode with the installation disk. 

I do not know how mkinitrd is being called within the root system. I suspect
that the way that mkinitrd is called within the install system is not the same
as it normally would be called. This is in part because the modprobe.conf is not
in its normal place, and the modules are also not in their normal place. I could
be wrong about this if they 'chroot' into the filesystem first. Since the
problem that I had with mkinitrd only came up while the installer was running,
and not at other times, I thought that the problem that I experienced was a
result of mkinitrd being called improperly or some of the files such as
modprobe.conf being set up improperly by the install system. That is why I
originally assigned this problem to the anaconda people. They reassigned it to
mkinitrd.

Created attachment 116515 [details]
/etc/modprobe.conf - of the normal filesystem

Created attachment 116516 [details]
/tmp/modprobe.conf - of the install/resuce system

You might notice that this modprobe.conf also contains modules for sata_promise
as oppose to the filesystem's modprobe.conf. Please be assured that it is not
what is making a difference for two reasons:
1- it is anyway the one that would be available to the install system.
2- I don't use the sata_promise module, it is for the raid controller and I
don't have any raid disks on my system.

mkinitrd won't autodetect LVM if you have LABEL=/ in your fstab. Change it to
/dev/vg0/root (or whatever is appropriate) and re-mkinitrd, and you're golden.

Not sure if that is what's up here, but that just solved some of my headaches.

Thanks for the comments. This goes back a year ago. I hope that it isn't still
an issue on the newer versions of Fedora. In any case, I was not using LVM.

This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

I have not experienced this problem with FC5 and FC6, so pursuant to Christian
Iseli's request, I am marking this bug "WONTFIX".