Updated : Feb 11, 2016 in Linux

Checking the Health of LSI Logic / Symbios Logic MegaRAID SAS 2108 RAID Controller

Introduction: This HowTo show how to check the health of Hard Disks connected to a ‘LSI Logic/Symbios Logic MegaRAID SAS 2108’ RAID controller.

We look for its presence in the system:
lspci | grep RAID
Example Result:
01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 05)
Bingo!, we can work with this one.

Version 1

We add the repository:
echo "deb http://hwraid.le-vert.net/debian wheezy main" >> /etc/apt/sources.list
… get its gpg key and install the tool.
wget -O - http://hwraid.le-vert.net/debian/hwraid.le-vert.net.gpg.key | apt-key add -
apt-get install megactl

Maybe we want to learn a bit how to use it?
man megasasctl
Well..we are in a hurry, so we ask the program for the current status.
Result Example:
a0 LSI MegaRAID SAS 9260-4i encl:1 ldrv:1 batt:FAULT, module missing, pack missing, charge failed
a0d0 3725GiB RAID 1 1x2 optimal
a0e252s0 3726GiB a0d0 online
a0e252s1 3726GiB a0d0 online

Now we do a health check without battery check this time.
megasasctl -HB
The result should be empty!

Version 2

wget http://www.ipfusions.com/setup/MegaCli-8.07.07-1.noarch.rpm
aptitude install alien
alien MegaCli-8.07.07-1.noarch.rpm
dpkg -i megacli_8.07.07-2_all.deb
dpkg -L megacli

Now we ask for the status:
/opt/MegaRAID/MegaCli/MegaCli64 -LDInfo -LALL -aALL
Result example:
Adapter 0 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name :
RAID Level : Primary-1, Secondary-0, RAID Level Qualifier-0
Size : 3.637 TB
Sector Size : 512
Is VD emulated : Yes
Mirror Data : 3.637 TB
State : Optimal
Strip Size : 256 KB
Number Of Drives : 2
Span Depth : 1
Default Cache Policy: WriteBack, ReadAhead, Direct, Write Cache OK if Bad BBU
Current Cache Policy: WriteBack, ReadAhead, Direct, Write Cache OK if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy : Disk's Default
Encryption Type : None
Bad Blocks Exist: No
Is VD Cached: No
Exit Code: 0x00

State: should be Optimal !


  • Hi,
    I have a RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 3108 [Invader] [1000:005d]

    I was trying to mount it but failed.
    megacli -LDInfo -LALL -aALL

    Exit Code: 0x00

    My module is:
    “[zillur@genomics megamap]$ modinfo megaraid_sas
    filename: /lib/modules/3.10.0-862.11.6.el7.x86_64/kernel/drivers/scsi/megaraid/megaraid_sas.ko.xz
    description: Avago MegaRAID SAS Driver
    author: megaraidlinux.pdl@avagotech.com
    version: 07.702.06.00-rh2
    license: GPL
    retpoline: Y
    rhelversion: 7.5
    srcversion: A19DC3530FA946F3FE5CCAD
    alias: pci:v00001000d00000411sv*sd*bc*sc*i*
    intree: Y
    vermagic: 3.10.0-862.11.6.el7.x86_64 SMP mod_unload modversions
    signer: CentOS Linux kernel signing key
    sig_key: D4:11:5F:11:00:55:DB:56:C8:D6:05:AB:75:21:73:CF:B1:AC:54:D8
    sig_hashalgo: sha256
    parm: lb_pending_cmds:Change raid-1 load balancing outstanding threshold. Valid Values are 1-128. Default: 4 (int)
    parm: max_sectors:Maximum number of sectors per IO command (int)
    parm: msix_disable:Disable MSI-X interrupt handling. Default: 0 (int)
    parm: msix_vectors:MSI-X max vector count. Default: Set by FW (int)
    parm: allow_vf_ioctls:Allow ioctls in SR-IOV VF mode. Default: 0 (int)
    parm: throttlequeuedepth:Adapter queue depth when throttled due to I/O timeout. Default: 16 (int)
    parm: resetwaittime:Wait time in seconds after I/O timeout before resetting adapter. Default: 180 (int)
    parm: smp_affinity_enable:SMP affinity feature enable/disbale Default: enable(1) (int)
    parm: rdpq_enable: Allocate reply queue in chunks for large queue depth enable/disable Default: disable(0) (int)
    parm: dual_qdepth_disable:Disable dual queue depth feature. Default: 0 (int)
    parm: scmd_timeout:scsi command timeout (10-90s), default 90s. See megasas_reset_timer. (int)”

    dmesg report:
    “02:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02)
    [zillur@genomics megamap]$ dmesg | grep -i raid
    [ 2.164013] megaraid_sas 0000:02:00.0: Waiting for FW to come to ready state
    [ 2.164017] megaraid_sas 0000:02:00.0: FW in FAULT state!!
    [ 106.261587] megaraid_sas 0000:02:00.0: Diag reset adapter never cleared megasas_adp_reset_fusion 3552
    [ 106.261593] megaraid_sas 0000:02:00.0: FW restarted successfully from megasas_init_fw!
    [ 136.261751] megaraid_sas 0000:02:00.0: Waiting for FW to come to ready state
    [ 136.261757] megaraid_sas 0000:02:00.0: FW in FAULT state!!
    [ 136.261772] megaraid_sas 0000:02:00.0: Failed from megasas_init_fw 5543

    Any Help?
    Best Regards

    1. Hi Zillur,
      I have put the significant messages in Bold in your comment.
      Unfortunately, this means that the FirmWare(FW) in the Raid controller didn’t respond to the initialization of the kernel module,
      therefore the software megacli can’t talk to the controller and the kernel won’t be able to talk to it either for mounting disks.
      It looks like either the controller is faulty, or its firmware was not loaded properly or something else went wrong.
      Unfortunately I’m not an expert in the SAS Contoller troubleshooting.
      I would suggest to either temporarily try to get yourself a new controller of the same type just to see if the first controller is faulty,
      or maybe look for a new firmware for this controller and search in Google on how to load the new firmware in the controller.
      I wish you good luck šŸ™‚

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: