Hello I would like to recompile initrd on f19 without qla2xxx that is giving me problems on boot. How to do it? Dracut seems to ignore blacklist in .conf file under modprobe.d Thanks Gianluca
On 19.11.2013 14:07, Gianluca Cecchi wrote:
Hello I would like to recompile initrd on f19 without qla2xxx that is giving me problems on boot. How to do it? Dracut seems to ignore blacklist in .conf file under modprobe.d Thanks Gianluca
man 5 dracut.conf -> section: omit_drivers
Mateusz Marzantowicz
On Tue Nov 19 13:30:32 UTC 2013 Mateusz Marzantowicz wrote:
man 5 dracut.conf -> section: omit_drivers
It seems not to work. Created /etc/dracut.conf.d/qla2xxx_omit.conf # cat /etc/dracut.conf.d/qla2xxx_omit.conf omit_drivers+="qla2xxx "
dracut --force "initramfs-3.11.8-200.fc19.x86_64.img" 3.11.8-200.fc19.x86_64 I continue to see qla2xxx inside the generated initrd and server has problems to boot.
Tried also from command line: dracut --omit "qla2xxx" --force "initramfs-3.11.8-200.fc19.x86_64.img" 3.11.8-200.fc19.x86_64
but again qla2xxx is inside initrd and booting I have problems.. # gunzip < /boot/initramfs-3.11.8-200.fc19.x86_64.img | cpio -itdmuv|grep qla2xxx drwxr-xr-x 2 root root 0 Nov 19 15:28 usr/lib/modules/3.11.8-200.fc19.x86_64/kernel/drivers/scsi/qla2xxx -rw-r--r-- 1 root root 822783 Nov 13 17:55 usr/lib/modules/3.11.8-200.fc19.x86_64/kernel/drivers/scsi/qla2xxx/qla2xxx.ko 54688 blocks
BTW: where is the old "init" script that loaded the kernel modules in the past? WHat if I want to manually remove qla2xxx from generated initrd? Gianluca
On Tue, 19 Nov 2013 16:06:15 +0100 Gianluca Cecchi wrote:
WHat if I want to manually remove qla2xxx from generated initrd?
I'm pretty sure the initrd files are really just gzip compressed cpio archives, so you could uncompress it, extract the files, and do anything you want to them, then rebuild it (probably a good idea to keep the original in case everything goes wrong :-).
On Tue Nov 19 15:13:24 UTC 2013 Tom Horsley wrote:
I'm pretty sure the initrd files are really just gzip compressed cpio archives, so you could uncompress it, extract the files, and do anything you want to them, then rebuild it (probably a good idea to keep the original in case everything goes wrong :-).
I see it. But before dracut days I was able to: 1. extract the archive 2. remove module.ko file from /lib 3. remove from init file the line "insmod module.ko" 4. re-create archive
Now the "init" file inside initrd seems to be systemd and so I'm not sure if only removing qla2xxx.ko is ok or not.
On Tue, Nov 19, 2013 at 3:06 PM, Gianluca Cecchi gianluca.cecchi@gmail.com wrote:
BTW: where is the old "init" script that loaded the kernel modules in the past?
# lsinitrd /boot/initramfs-3.13.0-0.rc0.git6.1.fc21.x86_64.img | grep 'init ->' lrwxrwxrwx 1 root root 24 Nov 19 16:40 init -> /usr/lib/systemd/systemd lrwxrwxrwx 1 root root 24 Nov 19 16:40 usr/sbin/init -> /usr/lib/systemd/systemd
On 19.11.2013 16:06, Gianluca Cecchi wrote:
On Tue Nov 19 13:30:32 UTC 2013 Mateusz Marzantowicz wrote:
man 5 dracut.conf -> section: omit_drivers
It seems not to work. Created /etc/dracut.conf.d/qla2xxx_omit.conf # cat /etc/dracut.conf.d/qla2xxx_omit.conf omit_drivers+="qla2xxx "
dracut --force "initramfs-3.11.8-200.fc19.x86_64.img" 3.11.8-200.fc19.x86_64 I continue to see qla2xxx inside the generated initrd and server has problems to boot.
Tried also from command line: dracut --omit "qla2xxx" --force "initramfs-3.11.8-200.fc19.x86_64.img" 3.11.8-200.fc19.x86_64
but again qla2xxx is inside initrd and booting I have problems.. # gunzip < /boot/initramfs-3.11.8-200.fc19.x86_64.img | cpio -itdmuv|grep qla2xxx drwxr-xr-x 2 root root 0 Nov 19 15:28 usr/lib/modules/3.11.8-200.fc19.x86_64/kernel/drivers/scsi/qla2xxx -rw-r--r-- 1 root root 822783 Nov 13 17:55 usr/lib/modules/3.11.8-200.fc19.x86_64/kernel/drivers/scsi/qla2xxx/qla2xxx.ko 54688 blocks
BTW: where is the old "init" script that loaded the kernel modules in the past? WHat if I want to manually remove qla2xxx from generated initrd? Gianluca
This doesn't resolve you're problem but it might help you diagnose what is going on there. In /etc/dracut.conf enable logging by removing comment from:
logfile=/var/log/dracut.log
In /var/log/dracut.log, you should have results of running dracut command. Maybe this will tell you something useful.
Mateusz Marzantowicz
-
Gianluca Cecchi -
Mateusz Marzantowicz -
Michael Cronenworth -
Tom H -
Tom Horsley