Lustre discuss - Feb 2011 - Kernel Panic error after lustre 2.0 installation

Hi there,
I have got an error after installing lustre 2.0 on the MGS server with RAID
controller card.
The server OS is centOS 5.4 x86_64 and has 1.2TB storage which has
configured by RAID 1+0.
After installing lustre rpm packages and rebooting machine, I face with the
errors below at linux startup:

Unable to access resume device (LABEL=SWAP-sda3)
mount: could not find filesystem ''dev/root''
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
swirchroot: mount failed: No such file or directory
Kernel Panic - not syncing: Attempted to kill init!

I have no problem with the original kernel installed by centos. I guessed
this may be related to RAID controller card driver which may not loaded by
the patched lustre kernel. so I have added the driver into the initrd.img
file. But it didn''t solve the problem.

Should I install the lustre by building the source? Or any other clue to
this problem?

Thanks in advance...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110217/a5df89b2/attachment.html

On Thu, 2011-02-17 at 23:26 +0330, Arya Mazaheri wrote:
> Hi there,
Hi,
> Unable to access resume device (LABEL=SWAP-sda3)
> mount: could not find filesystem ''dev/root''
> setuproot: moving /dev failed: No such file or directory
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> swirchroot: mount failed: No such file or directory
> Kernel Panic - not syncing: Attempted to kill init!
> 
> I have no problem with the original kernel installed by centos. I
> guessed this may be related to RAID controller card driver which may
> not loaded by the patched lustre kernel.
That seems like a reasonable conclusion given the information available.
> so I have added the driver into the initrd.img file.
Where did you get the driver from?  What is the name of the driver?
> But it didn''t solve the problem.
Depending on where it came from, yes, it might not.
> Should I install the lustre by building the source?
That may be required, but not necessarily required.  We need more
information.

b.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110217/64d14c5a/attachment.bin

The driver name is "arcmsr.ko" and I extracted it from driver.img
included
in RAID controller''s CD. The following text file may clarify better:

ftp://areca.starline.de/RaidCards/AP_Drivers/Linux/DRIVER/RedHat/FedoraCore/Redhat-Fedora-core8/1.20.0X.15/Intel/readme.txt

Please tell me, if you need more information about this issue...

On Thu, Feb 17, 2011 at 11:33 PM, Brian J. Murrell <brian at
whamcloud.com>wrote:
> On Thu, 2011-02-17 at 23:26 +0330, Arya Mazaheri wrote:
> > Hi there,
>
> Hi,
>
> > Unable to access resume device (LABEL=SWAP-sda3)
> > mount: could not find filesystem ''dev/root''
> > setuproot: moving /dev failed: No such file or directory
> > setuproot: error mounting /proc: No such file or directory
> > setuproot: error mounting /sys: No such file or directory
> > swirchroot: mount failed: No such file or directory
> > Kernel Panic - not syncing: Attempted to kill init!
> >
> > I have no problem with the original kernel installed by centos. I
> > guessed this may be related to RAID controller card driver which may
> > not loaded by the patched lustre kernel.
>
> That seems like a reasonable conclusion given the information available.
>
> > so I have added the driver into the initrd.img file.
>
> Where did you get the driver from?  What is the name of the driver?
>
> > But it didn''t solve the problem.
>
> Depending on where it came from, yes, it might not.
>
> > Should I install the lustre by building the source?
>
> That may be required, but not necessarily required.  We need more
> information.
>
> b.
>
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110217/60651888/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110217/60651888/attachment.bin

Yep.  All you have to do is rebuild the driver for the Lustre kernel.

First, bring the system back up with the non-Lustre kernel.



See the bottom of the readme:

    # cd /usr/src/linux/drivers/scsi/arcmsr
    (suppose /usr/src/linux is the soft-link for 
/usr/src/kernel/2.6.23.1-42.fc8-i386)
    # make -C /lib/modules/`uname -r`/build CONFIG_SCSI_ARCMSR=m 
SUBDIRS=$PWD modules
    # insmod arcmsr.ko

Except instead of "uname -r" substitute the lustre kernel''s
''uname -r'',
as you want to build for the Lustre kernel.  Be sure you have the Lustre 
kernel-devel RPM installed.

Note that the "insmod" will not work (you already have it for the 
running kernel, and the one you built for the Lustre kernel will not 
work).  You will need to rebuild the initrd for the Lustre kernel (see 
the other instructions in the readme, using the Lustre kernel).

Kevin


Arya Mazaheri wrote:
> The driver name is "arcmsr.ko" and I extracted it from driver.img
> included in RAID controller''s CD. The following text file may
clarify
> better:
>
>
ftp://areca.starline.de/RaidCards/AP_Drivers/Linux/DRIVER/RedHat/FedoraCore/Redhat-Fedora-core8/1.20.0X.15/Intel/readme.txt
>
> Please tell me, if you need more information about this issue...
>
> On Thu, Feb 17, 2011 at 11:33 PM, Brian J. Murrell 
> <brian at whamcloud.com <mailto:brian at whamcloud.com>> wrote:
>
>     On Thu, 2011-02-17 at 23:26 +0330, Arya Mazaheri wrote:
>     > Hi there,
>
>     Hi,
>
>     > Unable to access resume device (LABEL=SWAP-sda3)
>     > mount: could not find filesystem ''dev/root''
>     > setuproot: moving /dev failed: No such file or directory
>     > setuproot: error mounting /proc: No such file or directory
>     > setuproot: error mounting /sys: No such file or directory
>     > swirchroot: mount failed: No such file or directory
>     > Kernel Panic - not syncing: Attempted to kill init!
>     >
>     > I have no problem with the original kernel installed by centos. I
>     > guessed this may be related to RAID controller card driver which
may
>     > not loaded by the patched lustre kernel.
>
>     That seems like a reasonable conclusion given the information
>     available.
>
>     > so I have added the driver into the initrd.img file.
>
>     Where did you get the driver from?  What is the name of the driver?
>
>     > But it didn''t solve the problem.
>
>     Depending on where it came from, yes, it might not.
>
>     > Should I install the lustre by building the source?
>
>     That may be required, but not necessarily required.  We need more
>     information.
>
>     b.
>
>
>
>     _______________________________________________
>     Lustre-discuss mailing list
>     Lustre-discuss at lists.lustre.org
>     <mailto:Lustre-discuss at lists.lustre.org>
>     http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>

Woooow! Thanks for your suggestion. The only thing needed to do is to make
the ''arcmsr.c'' and ''arcmsr.h'' and finally
make the ram disk.
Now everything is working smoothly...

Thanks again... ;)

On Fri, Feb 18, 2011 at 1:16 AM, Kevin Van Maren <kevin.van.maren at
oracle.com
> wrote:
> Yep.  All you have to do is rebuild the driver for the Lustre kernel.
>
> First, bring the system back up with the non-Lustre kernel.
>
>
>
> See the bottom of the readme:
>
>   # cd /usr/src/linux/drivers/scsi/arcmsr
>   (suppose /usr/src/linux is the soft-link for
> /usr/src/kernel/2.6.23.1-42.fc8-i386)
>   # make -C /lib/modules/`uname -r`/build CONFIG_SCSI_ARCMSR=m SUBDIRS=$PWD
> modules
>   # insmod arcmsr.ko
>
> Except instead of "uname -r" substitute the lustre
kernel''s ''uname -r'', as
> you want to build for the Lustre kernel.  Be sure you have the Lustre
> kernel-devel RPM installed.
>
> Note that the "insmod" will not work (you already have it for the
running
> kernel, and the one you built for the Lustre kernel will not work).  You
> will need to rebuild the initrd for the Lustre kernel (see the other
> instructions in the readme, using the Lustre kernel).
>
> Kevin
>
>
> Arya Mazaheri wrote:
>
>> The driver name is "arcmsr.ko" and I extracted it from
driver.img included
>> in RAID controller''s CD. The following text file may clarify
better:
>>
>>
>>
ftp://areca.starline.de/RaidCards/AP_Drivers/Linux/DRIVER/RedHat/FedoraCore/Redhat-Fedora-core8/1.20.0X.15/Intel/readme.txt
>>
>> Please tell me, if you need more information about this issue...
>>
>> On Thu, Feb 17, 2011 at 11:33 PM, Brian J. Murrell <brian at
whamcloud.com<mailto:
>> brian at whamcloud.com>> wrote:
>>
>>    On Thu, 2011-02-17 at 23:26 +0330, Arya Mazaheri wrote:
>>    > Hi there,
>>
>>    Hi,
>>
>>    > Unable to access resume device (LABEL=SWAP-sda3)
>>    > mount: could not find filesystem ''dev/root''
>>    > setuproot: moving /dev failed: No such file or directory
>>    > setuproot: error mounting /proc: No such file or directory
>>    > setuproot: error mounting /sys: No such file or directory
>>    > swirchroot: mount failed: No such file or directory
>>    > Kernel Panic - not syncing: Attempted to kill init!
>>    >
>>    > I have no problem with the original kernel installed by centos.
I
>>    > guessed this may be related to RAID controller card driver
which may
>>    > not loaded by the patched lustre kernel.
>>
>>    That seems like a reasonable conclusion given the information
>>    available.
>>
>>    > so I have added the driver into the initrd.img file.
>>
>>    Where did you get the driver from?  What is the name of the driver?
>>
>>    > But it didn''t solve the problem.
>>
>>    Depending on where it came from, yes, it might not.
>>
>>    > Should I install the lustre by building the source?
>>
>>    That may be required, but not necessarily required.  We need more
>>    information.
>>
>>    b.
>>
>>
>>
>>    _______________________________________________
>>    Lustre-discuss mailing list
>>    Lustre-discuss at lists.lustre.org
>>    <mailto:Lustre-discuss at lists.lustre.org>
>>
>>    http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>
>>
>>
------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110218/4ef47b55/attachment-0001.html