I added one dracut module into initial ramdisk, but it is not called

I added one dracut module into initial ramdisk, but it is not called

[Min Jun,Xi]

Hi,

I am using the NFS directory as the root file system, and it works
now. I have worked to make the warning/error messages away during the
node is booting up.  Now, I am trying to create and add my own dracut
modules, but I find it doesn't run during the node is booting up.

I created one directory named "48xcat", and there're 5 files in it:

    "check  install  premount  prepivot  xcatroot"

All of them are simple, the contents of "install" is:
"
#!/bin/sh
    echo "installing xcat dracut modules..."
    dracut_install mount umount
    inst "$moddir/xcatroot" "/sbin/xcatroot"
    inst_hook pre-mount 10 "$moddir/premount"
    inst_hook pre-pivot 88 "$moddir/prepivot"
"
premount will mount another NFS directory to the mount point in the
file system, like this:
"
    #!/bin/sh
    echo "in pre-mouting script"
    mount 192.168.11.107:/tftpboot /.statelite/ro
"
prepivot only has one line to echo something there.

xcatroot only has several lines:
"
    #!/bin/sh
    echo "xcatroot is running..."
    #inject new exit_if_exists
    echo 'settle_exit_if_exits="--exit-if-exists=/dev/root"; rm
"$job"' > /initqueue/xcat.sh
    > /initqueue/work
"
Then, I added the module "xcat" into dracut.conf, and finally I
created the initrd.gz file by the "dracut" command, I also added
"rdshell rdinfo rdinitdebug" into the kernel commandline parameters,
however when the node was booting up, I couldn't see the scripts in my
own "xcat" module run.
Can anyone tell me what's wrong here? Thank you in advance. Is there
some naming restrictions in the module?
--
best regards,
Xi Minjun
xCAT Development Team Member in CDL,IBM
Notes ID: Min Jun Xi/China/IBM/

Re: I added one dracut module into initial ramdisk, but it is not called

[Harald Hoyer]

On 06/17/2010 02:59 PM, Min Jun,Xi wrote:
> Hi,
>
> I am using the NFS directory as the root file system, and it works
> now. I have worked to make the warning/error messages away during the
> node is booting up.  Now, I am trying to create and add my own dracut
> modules, but I find it doesn't run during the node is booting up.
>
> I created one directory named "48xcat", and there're 5 files in it:
>
>      "check  install  premount  prepivot  xcatroot"
>
> All of them are simple, the contents of "install" is:
> "
> #!/bin/sh
>      echo "installing xcat dracut modules..."
>      dracut_install mount umount
>      inst "$moddir/xcatroot" "/sbin/xcatroot"
>      inst_hook pre-mount 10 "$moddir/premount"
>      inst_hook pre-pivot 88 "$moddir/prepivot"
> "
> premount will mount another NFS directory to the mount point in the
> file system, like this:
> "
>      #!/bin/sh
>      echo "in pre-mouting script"
>      mount 192.168.11.107:/tftpboot /.statelite/ro
> "
> prepivot only has one line to echo something there.
>
> xcatroot only has several lines:
> "
>      #!/bin/sh
>      echo "xcatroot is running..."
>      #inject new exit_if_exists
>      echo 'settle_exit_if_exits="--exit-if-exists=/dev/root"; rm
> "$job"'>  /initqueue/xcat.sh
>      >  /initqueue/work
> "
> Then, I added the module "xcat" into dracut.conf, and finally I
> created the initrd.gz file by the "dracut" command, I also added
> "rdshell rdinfo rdinitdebug" into the kernel commandline parameters,
> however when the node was booting up, I couldn't see the scripts in my
> own "xcat" module run.
> Can anyone tell me what's wrong here? Thank you in advance. Is there
> some naming restrictions in the module?
> --
> best regards,
> Xi Minjun
> xCAT Development Team Member in CDL,IBM
> Notes ID: Min Jun Xi/China/IBM/

what's the output of:
$ lsinitrd <image file> | grep xcat

and please rename "premount" to something like "xcat-premount"

then you can do in the dracut shell after booting with "rdinitdebug":

$ dmesg |grep xcat

Re: I added one dracut module into initial ramdisk, but it is not called

[Min Jun,Xi]

On Thu, Jun 17, 2010 at 9:06 PM, Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> On 06/17/2010 02:59 PM, Min Jun,Xi wrote:
>>
>> Hi,
>>
>> I am using the NFS directory as the root file system, and it works
>> now. I have worked to make the warning/error messages away during the
>> node is booting up.  Now, I am trying to create and add my own dracut
>> modules, but I find it doesn't run during the node is booting up.
>>
>> I created one directory named "48xcat", and there're 5 files in it:
>>
>>     "check  install  premount  prepivot  xcatroot"
>>
>> All of them are simple, the contents of "install" is:
>> "
>> #!/bin/sh
>>     echo "installing xcat dracut modules..."
>>     dracut_install mount umount
>>     inst "$moddir/xcatroot" "/sbin/xcatroot"
>>     inst_hook pre-mount 10 "$moddir/premount"
>>     inst_hook pre-pivot 88 "$moddir/prepivot"
>> "
>> premount will mount another NFS directory to the mount point in the
>> file system, like this:
>> "
>>     #!/bin/sh
>>     echo "in pre-mouting script"
>>     mount 192.168.11.107:/tftpboot /.statelite/ro
>> "
>> prepivot only has one line to echo something there.
>>
>> xcatroot only has several lines:
>> "
>>     #!/bin/sh
>>     echo "xcatroot is running..."
>>     #inject new exit_if_exists
>>     echo 'settle_exit_if_exits="--exit-if-exists=/dev/root"; rm
>> "$job"'>  /initqueue/xcat.sh
>>     >  /initqueue/work
>> "
>> Then, I added the module "xcat" into dracut.conf, and finally I
>> created the initrd.gz file by the "dracut" command, I also added
>> "rdshell rdinfo rdinitdebug" into the kernel commandline parameters,
>> however when the node was booting up, I couldn't see the scripts in my
>> own "xcat" module run.
>> Can anyone tell me what's wrong here? Thank you in advance. Is there
>> some naming restrictions in the module?
>> --
>> best regards,
>> Xi Minjun
>> xCAT Development Team Member in CDL,IBM
>> Notes ID: Min Jun Xi/China/IBM/
>
> what's the output of:
> $ lsinitrd <image file> | grep xcat
>
Only one line exists in the output:
[root@ca4lpar01 tmp]# lsinitrd initrd.gz |grep xcat
-rwxr-xr-x   1 root     root          175 Jun 17 16:19 sbin/xcatroot

> and please rename "premount" to something like "xcat-premount"
I found in the "README.modules",
/pre-mount/*.sh
   scripts to run before the root filesystem is mounted
   Network filesystems like NFS that do not use device files are an
   exception. Root can be mounted already at this point.
Does it mean that it won't be called because the root filesystem is
mounted with NFS?

>
> then you can do in the dracut shell after booting with "rdinitdebug":
>
> $ dmesg |grep xcat
>



-- 
best regards,
Xi Minjun
xCAT Development Team Member in CDL,IBM
Notes ID: Min Jun Xi/China/IBM/

Re: I added one dracut module into initial ramdisk, but it is not called

[Min Jun,Xi]

I made the changes you mentioned, and have re-generated the initrd,
and rebooted the node;

I also run "dmesg|grep xcat", but I couldn't get anything.

On Thu, Jun 17, 2010 at 9:06 PM, Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> On 06/17/2010 02:59 PM, Min Jun,Xi wrote:
>>
>> Hi,
>>
>> I am using the NFS directory as the root file system, and it works
>> now. I have worked to make the warning/error messages away during the
>> node is booting up.  Now, I am trying to create and add my own dracut
>> modules, but I find it doesn't run during the node is booting up.
>>
>> I created one directory named "48xcat", and there're 5 files in it:
>>
>>     "check  install  premount  prepivot  xcatroot"
>>
>> All of them are simple, the contents of "install" is:
>> "
>> #!/bin/sh
>>     echo "installing xcat dracut modules..."
>>     dracut_install mount umount
>>     inst "$moddir/xcatroot" "/sbin/xcatroot"
>>     inst_hook pre-mount 10 "$moddir/premount"
>>     inst_hook pre-pivot 88 "$moddir/prepivot"
>> "
>> premount will mount another NFS directory to the mount point in the
>> file system, like this:
>> "
>>     #!/bin/sh
>>     echo "in pre-mouting script"
>>     mount 192.168.11.107:/tftpboot /.statelite/ro
>> "
>> prepivot only has one line to echo something there.
>>
>> xcatroot only has several lines:
>> "
>>     #!/bin/sh
>>     echo "xcatroot is running..."
>>     #inject new exit_if_exists
>>     echo 'settle_exit_if_exits="--exit-if-exists=/dev/root"; rm
>> "$job"'>  /initqueue/xcat.sh
>>     >  /initqueue/work
>> "
>> Then, I added the module "xcat" into dracut.conf, and finally I
>> created the initrd.gz file by the "dracut" command, I also added
>> "rdshell rdinfo rdinitdebug" into the kernel commandline parameters,
>> however when the node was booting up, I couldn't see the scripts in my
>> own "xcat" module run.
>> Can anyone tell me what's wrong here? Thank you in advance. Is there
>> some naming restrictions in the module?
>> --
>> best regards,
>> Xi Minjun
>> xCAT Development Team Member in CDL,IBM
>> Notes ID: Min Jun Xi/China/IBM/
>
> what's the output of:
> $ lsinitrd <image file> | grep xcat
>
> and please rename "premount" to something like "xcat-premount"
>
> then you can do in the dracut shell after booting with "rdinitdebug":
>
> $ dmesg |grep xcat
>



-- 
best regards,
Xi Minjun
xCAT Development Team Member in CDL,IBM
Notes ID: Min Jun Xi/China/IBM/

Re: I added one dracut module into initial ramdisk, but it is not called

[Dave Stone]

Min Jun,Xi <xi.minjun@...> writes:

> 
> I made the changes you mentioned, and have re-generated the initrd,
> and rebooted the node;
> 
> I also run "dmesg|grep xcat", but I couldn't get anything.
> 

Hi Min,

I'm new to dracut as well.  But here is a couple of things that might help you.
1. Make sure "check" and "install" and other scripts are executable
2. Dracut has -v --debug output options which can be redirected to a file.  
Then you can look for problems that might have prevented dracut to include 
your module.

Regards,

-Dave 

Pruned....