I don't know if this will help but here follows the lists of modules
that are included in the initrd of two systems.
The first system, Duo1, has a SATA disk and does not use LVM --
[r...@duo1 ~]# gunzip < /boot/initrd-$(uname -r).img | cpio -it
2>/dev/null | grep ko$ | sort
lib/ahci.ko
lib/ehci-h
On 09/01/2010 03:17 PM, Akemi Yagi wrote:
> I don't remember where I saw the description about the omit options.
ok.
> In any event, that approach apparently did not work for you.
very true.
> The unpacking/repacking method is a sure way to remove modules from
> the .img file. Your system mig
On Tue, Aug 31, 2010 at 10:54 PM, g wrote:
> On 09/01/2010 05:10 AM, Akemi Yagi wrote:
>
>
>> I understand mkinitrd would not honor the options if the system sees
>> certain hardware.
>
> from where do you get this?
>
> to my knowledge, i have in/on/around this system box to give any
> indication
On 09/01/2010 05:10 AM, Akemi Yagi wrote:
> I understand mkinitrd would not honor the options if the system sees
> certain hardware.
from where do you get this?
to my knowledge, i have in/on/around this system box to give any
indication of raid.
--
peace out.
tc,hago.
g
.
in a free
On Tue, Aug 31, 2010 at 8:06 PM, g wrote:
>> On 08/31/2010 11:33 PM, Akemi Yagi wrote:
> # mkinitrd --omit-raid-modules --omit-lvm-modules \
> /boot/initrd-2.6.18-164.11.1.el5.img 2.6.18-164.11.1.el5
>
> dm-* modules load on boot.
>
> added
>
> blacklist dm-[module names]
>
> to "modprobe.co
> On 08/31/2010 11:33 PM, Akemi Yagi wrote:
thank you for reply.
>> Are you using LVM?
>
> no. i dislike lvm almost as much as ms bs os.
>
>> If not, you might want to run mkinitrd with the following options:
>>
>> --omit-raid-modules
>> --omit-lvm-modules
tried;
# mkinitrd --omit-raid-mo
On 08/31/2010 11:33 PM, Akemi Yagi wrote:
> Are you using LVM?
no. i dislike lvm almost as much as ms bs os.
> If not, you might want to run mkinitrd with the following options:
>
> --omit-raid-modules
> --omit-lvm-modules
it had been a while from last using "mkinitrd", so i read "man" again.
On Tue, Aug 31, 2010 at 3:49 PM, g wrote:
>> So a mkinitrd would probably need to be done after making
>> /etc/modprobe.conf.
>
> which i did.
> i thank you for your help.
>
> i am open to other suggestions.
Are you using LVM? If not, you might want to run mkinitrd with the
following options:
On 08/31/2010 04:35 AM, Chris Stevens wrote:
> Some suggestions. First, I think that renaming the dm directory won't
> do what you want because a "modprobe -a" will rebuild the dependencies
> with the new directory names.
sounds logical.
> That's just a theory of mine that's unproven.
a go
On 8/30/2010 11:14 PM, g wrote:
On 08/31/2010 03:01 AM, Alan Bartlett wrote:
As a scientist, I would perform the experiment but now, I suspect, it
will not make any difference. :-/
i am not a scientist, but i do know how to 'swag'. ;)
will give mkinitrd a run tomorrow.
I right out of ide
On 08/31/2010 03:01 AM, Alan Bartlett wrote:
> As a scientist, I would perform the experiment but now, I suspect, it
> will not make any difference. :-/
i am not a scientist, but i do know how to 'swag'. ;)
will give mkinitrd a run tomorrow.
> I right out of ideas. Perhaps someone else may ha
On 31 August 2010 03:18, g wrote:
> in other words, *all* that relates to 'raid' is commented out.
>
> only thing i have not done is run 'mkinitrd'.
>
> so, should i run 'mkinitrd' or not?
As a scientist, I would perform the experiment but now, I suspect, it
will not make any difference. :-/
On 08/31/2010 01:24 AM, Alan Bartlett wrote:
> Did you recreate the relevant initrd for the kernel?
no. you did no mention, and i did not think of it. [see bellow]
> Ah, I've just noticed something. Initially your were referring to
> dmraid -- the device mapper RAID. Latterly you have been r
On 08/31/2010 12:37 AM, g wrote:
> so, to see what is loading modules, i have renamed;
>
> "/lib/modules/2.6.18-164.11.1.el5/kernel/drivers/md/"
>
> to
>
> "/lib/modules/2.6.18-164.11.1.el5/kernel/drivers/00.md/"
>
> this should/may/i hope, give an error message during boot.
"why me Lor
On 31 August 2010 01:37, g wrote:
> easy first:
>
> On 08/30/2010 06:00 PM, Alan Bartlett wrote:
>
>> Also, I forgot to mention creating a "noraid" file in your
>> /etc/sysconfig/mkinitrd/ directory with one line that reads:
>>
>> DMRAID=no
>
> created, raid loads.
Did you recreate the relevant
alan,
i thank you for your help.
easy first:
On 08/30/2010 06:00 PM, Alan Bartlett wrote:
> Also, I forgot to mention creating a "noraid" file in your
> /etc/sysconfig/mkinitrd/ directory with one line that reads:
>
> DMRAID=no
created, raid loads.
On 08/30/2010 05:12 PM, Alan Bartlett wr
On 30 August 2010 18:12, Alan Bartlett wrote:
> On 30 August 2010 12:45, g wrote:
>> running sl 5.4.
>>
>> i have never used raid drives and i am not using raid, so i want to stop
>> dm-* modules and associated files from loading at boot.
> I would suggest that you consider using the boot line
On 30 August 2010 12:45, g wrote:
> running sl 5.4.
>
> i have never used raid drives and i am not using raid, so i want to stop
> dm-* modules and associated files from loading at boot.
I would suggest that you consider using the boot line parameter "nodmraid".
To see what that parameter does,
greetings,
running sl 5.4.
i have never used raid drives and i am not using raid, so i want to stop
dm-* modules and associated files from loading at boot.
i have read 'man modprobe', 'man mdadm', and understand how they work.
problem is, man pages do not tell which /etc/rc.d/rc?.d files are us
19 matches
Mail list logo
