Changes between Version 28 and Version 29 of LSIMegaRAIDSAS


Ignore:
Timestamp:
10/10/08 15:35:13 (17 years ago)
Author:
alexandre
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LSIMegaRAIDSAS

    v28 v29  
    6060{{{
    6161[root@server ~]# megasasctl
     62a0       PERC 5/i Integrated      encl:1 ldrv:2  batt:good
     63a0d0       67GiB RAID 1   1x2  optimal
     64a0d1      836GiB RAID 5   1x4  optimal
     65a0e8s0      68GiB  a0d0  online
     66a0e8s1      68GiB  a0d0  online
     67a0e8s2     279GiB  a0d1  online
     68a0e8s3     279GiB  a0d1  online
     69a0e8s4     279GiB  a0d1  online
     70a0e8s5     279GiB  a0d1  online
     71}}}
     72
     73There are several switches which are interresting:
     74  * '''-H''': Only print lines which are not ok.[[BR]]If nothing is printer, everything is fine
     75  * '''-B''': Ignore batttery problems when running -H.[[BR]]In fact megasasctl can't define if your controller has a battery or not.[[BR]]If you don't have one, use this parameter.
     76
     77=== 3.1.2. Periodic checks ===
     78
     79You can write your own script around megasasctl to check your adapter status health periodically.
     80However, I already did this for you. See megaraid-status below.
     81
     82== 3.2. megaraid-status ==
     83
     84=== 3.2.1. About megaraid-status ===
     85
     86'''megaraidsas-status''' is a wrapper script around megactl with periodics checks.
     87[[BR]]It is available in the packages repository too.
     88
     89[[BR]]The packages comes with a python wrapper around megasasctl and an initscript that '''periodic''' run this wrapper to '''check status'''.
     90[[BR]]It keeps a file with latest status and thus is able to detect RAID '''status changes and/or brokeness'''.
     91[[BR]]It will log a ligne to '''syslog''' when something failed and will send you a '''mail'''.
     92[[BR]]Until arrays are healthy again a '''reminder''' will be sent each 2 hours.
     93
     94=== 3.2.2. Wrapper output example ===
     95
     96{{{
     97server:~# megaraidsas-status
     98-- Arrays informations --
     99-- ID | Type | Size | Status
     100a0d0 | RAID 1 | 136GiB | optimal
     101
     102-- Disks informations
     103-- ID | Model | Status | Warnings
     104a0e8s0 | SEAGATE ST3146854SS 136GiB | online
     105a0e8s1 | SEAGATE ST3146854SS 136GiB | online
     106}}}
     107
     108{{{
     109[root@server ~]# megaraidsas-status
    62110-- Arrays informations --
    63111-- ID | Type | Size | Status
    … …  
    73121a0e8s4 | SEAGATE ST3300656SS 279GiB | online
    74122a0e8s5 | SEAGATE ST3300656SS 279GiB | online
    75 }}}
    76 
    77 There are several switches which are interresting:
    78   * '''-H''': Only print lines which are not ok.[[BR]]If nothing is printer, everything is fine
    79   * '''-B''': Ignore batttery problems when running -H.[[BR]]In fact megasasctl can't define if your controller has a battery or not.[[BR]]If you don't have one, use this parameter.
    80 
    81 === 3.1.2. Periodic checks ===
    82 
    83 You can write your own script around megasasctl to check your adapter status health periodically.
    84 However, I already did this for you. See megaraid-status below.
    85 
    86 == 3.2. megaraid-status ==
    87 
    88 === 3.2.1. About megaraid-status ===
    89 
    90 '''megaraidsas-status''' is a wrapper script around megactl with periodics checks.
    91 [[BR]]It is available in the packages repository too.
    92 
    93 [[BR]]The packages comes with a python wrapper around megasasctl and an initscript that '''periodic''' run this wrapper to '''check status'''.
    94 [[BR]]It keeps a file with latest status and thus is able to detect RAID '''status changes and/or brokeness'''.
    95 [[BR]]It will log a ligne to '''syslog''' when something failed and will send you a '''mail'''.
    96 [[BR]]Until arrays are healthy again a '''reminder''' will be sent each 2 hours.
    97 
    98 === 3.2.2. Wrapper output example ===
    99 
    100 {{{
    101 server:~# megaraidsas-status
    102 -- Arrays informations --
    103 -- ID | Type | Size | Status
    104 a0d0 | RAID 1 | 136GiB | optimal
    105 
    106 -- Disks informations
    107 -- ID | Model | Status | Warnings
    108 a0e8s0 | SEAGATE ST3146854SS 136GiB | online
    109 a0e8s1 | SEAGATE ST3146854SS 136GiB | online
    110 }}}
    111 
    112 {{{
    113 [root@server ~]# megaraidsas-status
    114 -- Arrays informations --
    115 -- ID   Type    Size    Status
    116 a0d0    RAID 1  67GiB   optimal
    117 a0d1    RAID 5  836GiB  optimal
    118 
    119 -- Disks informations
    120 -- ID   Model                   Status
    121 a0e8s0  FUJITSU MBA3073RC       online
    122 a0e8s1  FUJITSU MBA3073RC       online
    123 a0e8s2  SEAGATE ST3300656SS     online
    124 a0e8s3  SEAGATE ST3300656SS     online
    125 a0e8s4  SEAGATE ST3300656SS     online
    126 a0e8s5  SEAGATE ST3300656SS     online
    127123}}}
    128124