Bug 232463

What version of mkinitrd do you have?

Can you post your initrd file?

Created attachment 150147 [details]
initrd

(In reply to comment #1)
> What version of mkinitrd do you have?
> 
> Can you post your initrd file?
> 
mkinitrd-5.1.19.0.3-1

Where did that mkinitrd come from?

Latest I can find is 5.1.19.0.2-1

It came from updates.

Something is seriously wrong with your kernel dependencies file.
I would first try uninstalling and then reinstalling the kernel.

Also please post contents of your /etc/modprobe.conf.

(In reply to comment #6)
> Something is seriously wrong with your kernel dependencies file.
> I would first try uninstalling and then reinstalling the kernel.
> 
> Also please post contents of your /etc/modprobe.conf.
> 
> 
I tried it twice, but it doesn't change anything.

Here is my /etc/modprobe.conf :
alias eth0 r8169
alias eth1 forcedeth
alias scsi_hostadapter sata_sil
alias scsi_hostadapter1 sata_nv
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0 
options snd-intel8x0 index=0 
options snd-pcm-oss dsp_map=2 adsp_map=2 
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-intel8x0
alias snd-card-2 quickcam_messenger
options snd-card-2 index=2 
options quickcam_messenger index=2 
remove quickcam_messenger { /usr/sbin/alsactl store 2 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove quickcam_messenger
# I2C module options
alias char-major-89 i2c-dev

For some reason libata.ko, sd_mod.ko and scsi_mod.ko are missing from your initrd.

It's almost as if it decided to ignore all the dependancies.
Peter, any ideas why mkinitrd would do that ?

Well, we only pull in sd_mod if we see scsi_mod being pulled in, because there's
no real dependency there, but I don't know why the others wouldn't be pulled in.

Paul, if you run these commands, what do they print:

modprobe --set-version 2.6.20-1.2925.fc6 --show-depends ext3
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_sil
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_nv

And once you've done that, could you also do:

depmod -a 2.6.20-1.2925.fc6
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends ext3
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_sil
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_nv

# modprobe --set-version 2.6.20-1.2925.fc6 --show-depends ext3
FATAL: Could not load /lib/modules/2.6.20-1.2925.fc6/modules.dep: No such file
or directory
# modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_sil
FATAL: Could not load /lib/modules/2.6.20-1.2925.fc6/modules.dep: No such file
or directory
# modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_nv
FATAL: Could not load /lib/modules/2.6.20-1.2925.fc6/modules.dep: No such file
or directory

# depmod -a 2.6.20-1.2925.fc6
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends ext3
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/fs/jbd/jbd.ko 
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/fs/ext3/ext3.ko
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_sil
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/drivers/scsi/scsi_mod.ko 
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/drivers/ata/libata.ko 
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/drivers/ata/sata_sil.ko
modprobe --set-version 2.6.20-1.2925.fc6 --show-depends sata_nv
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/drivers/scsi/scsi_mod.ko 
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/drivers/ata/libata.ko 
insmod /lib/modules/2.6.20-1.2925.fc6/kernel/drivers/ata/sata_nv.ko 

You should be able to boot if you make a new initrd now that depmod
has created the dependency information.

It is what I thought but unfortunately I get the same error when I try to boot
with kernel 2-6-20-1.2925.fc6.

Did you make the new initrd correctly? It will default to building
one for your current kernel.

mkinitrd <file name> <kernel version>

mkinitrd /boot/initrd-2.6.20-1.2925.fc6.img 2.6.20-1.2925.fc6

No, I did not do it. After doing it, it works.
I have got the same problem with the new kernel update.
Yum says that it can not write /boot/System.map-2.6.20-1.2933.fc6 due to an
access error.
In /var/log/messages I get :
Mar 24 10:48:26 gen2 kernel: audit(1174729706.929:4): avc:  denied  { search }
for  pid=3923 comm="depmod" name="/" dev=hdb1 ino=2
scontext=user_u:system_r:depmod_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir
Mar 24 10:48:37 gen2 kernel: end_request: I/O error, dev fd0, sector 0
Mar 24 10:48:38 gen2 Installed: kernel.i686 2.6.20-1.2933.fc6

(In reply to comment #14)
The exact message given by yum is : "FATAL: Could not open
'/boot/System.map-2.6.20-1.2933.fc6': Permission denied"

I think the filesystem needs to be relabeled when these access errors happen.

The boot partition's label is "/boot", what label should I set ?

Filesystem relabeling is an selinux operation.
Create a file called /.autorelabel and reboot to start the
relabel. It could take a while.

It fixed the problem. Thank you.