Menu

#3 megasasctl doesn't provide good battery state

open
nobody
None
5
2020-03-22
2009-12-28
Anonymous
No

Running on a gentoo x86_64 2.6.28-r9.

box ~ # megasasctl
a0 IBM ServeRAID-MR10i SAS/SATA Controller encl:1 ldrv:1 batt:FAULT, unknown charge state
a0d0 134GiB RAID 5 1x3 optimal
hot spares : a0e0s3
a0e0s0 68GiB a0d0 online
a0e0s1 68GiB a0d0 online
a0e0s2 68GiB a0d0 online
a0e0s3 68GiB hotspare

But using megacli 4.0.11 :
box ~ # MegaCli -AdpBbuCmd -GetBbuStatus -a0

BBU status for Adapter: 0

BatteryType: iBBU
Voltage: 4077 mV
Current: 0 mA
Temperature: 39 C

BBU Firmware Status:

Charging Status : None
Voltage : OK
Temperature : OK
Learn Cycle Requested : No
Learn Cycle Active : No
Learn Cycle Status : OK
Learn Cycle Timeout : No
I2c Errors Detected : No
Battery Pack Missing : No
Battery Replacement required : No
Remaining Capacity Low : No
Periodic Learn Required : No

Battery state:

GasGuageStatus:
Fully Discharged : No
Fully Charged : Yes
Discharging : Yes
Initialized : Yes
Remaining Time Alarm : No
Remaining Capacity Alarm: No
Discharge Terminated : No
Over Temperature : No
Charging Terminated : No
Over Charged : No

Relative State of Charge: 96 %
Charger System State: 49168
Charger System Ctrl: 0
Charging current: 0 mA
Absolute state of charge: 99 %
Max Error: 2 %

Exit Code: 0x00

The card is an IBM ServeRAID-MR10i with a LSI SAS 1078 :
08:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04)
Subsystem: IBM SystemX MegaRAID SAS 8808E
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e8240000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 2000 [size=256]
Memory at e8200000 (64-bit, non-prefetchable) [size=256K]
[virtual] Expansion ROM at e8800000 [disabled] [size=64K]
Capabilities: [b0] Express Endpoint, MSI 00
Capabilities: [c4] Message Signalled Interrupts: Mask- 64bit+ Count=1/4 Enable-
Capabilities: [d4] MSI-X: Enable- Mask- TabSize=4
Capabilities: [e0] Power Management version 2
Capabilities: [ec] Vital Product Data <?>
Capabilities: [100] Power Budgeting <?>
Kernel driver in use: megaraid_sas

Discussion

  • Jason Klein

    Jason Klein - 2011-06-22

    Same battery fault false alarm here. MegaCli shows no BBU errors, while megactl shows battery FAULT.

    CentOS 5.6 x86_64
    megactl 0.4.1
    MegaCli 8.00.23-1

    $ sudo /opt/megactl/megactl-0.4.1/megasasctl
    a0 LSI MegaRAID SAS 9260-4i encl:1 ldrv:1 batt:FAULT, unknown charge state
    a0d0 1TiB RAID 10 2x2 DEGRADED
    a0e252s0 558GiB a0d0 rebuild
    a0e252s1 558GiB a0d0 online
    a0e252s2 558GiB a0d0 online
    a0e252s3 558GiB a0d0 online

    $ sudo /opt/MegaRAID/MegaCli/MegaCli64 -AdpBbuCmd -GetBbuStatus -a0

    BBU status for Adapter: 0

    BatteryType: iBBU
    Voltage: 4082 mV
    Current: 0 mA
    Temperature: 28 C

    BBU Firmware Status:

    Charging Status : None
    Voltage : OK
    Temperature : OK
    Learn Cycle Requested : No
    Learn Cycle Active : No
    Learn Cycle Status : OK
    Learn Cycle Timeout : No
    I2c Errors Detected : No
    Battery Pack Missing : No
    Battery Replacement required : No
    Remaining Capacity Low : No
    Periodic Learn Required : No
    Transparent Learn : No

    Battery state:

    GasGuageStatus:
    Fully Discharged : No
    Fully Charged : Yes
    Discharging : Yes
    Initialized : Yes
    Remaining Time Alarm : No
    Remaining Capacity Alarm: No
    Discharge Terminated : No
    Over Temperature : No
    Charging Terminated : No
    Over Charged : No

    Relative State of Charge: 100 %
    Charger System State: 49168
    Charger System Ctrl: 0
    Charging current: 0 mA
    Absolute state of charge: 101 %
    Max Error: 2 %

    Exit Code: 0x00

    Related data from dmesg...

    SCSI subsystem initialized
    megasas: 00.00.04.17-RH1 Wed. Nov. 25, 11:41:51 PST 2009
    megasas: 0x1000:0x0079:0x1000:0x9260: bus 2:slot 0:func 0
    ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 169
    PCI: Setting latency timer of device 0000:02:00.0 to 64
    megasas: FW now in Ready state
    scsi0 : LSI SAS based MegaRAID driver
    Vendor: SEAGATE Model: ST3600057SS Rev: 0006
    Type: Direct-Access ANSI SCSI revision: 05
    Vendor: SEAGATE Model: ST3600057SS Rev: 0006
    Type: Direct-Access ANSI SCSI revision: 05
    Vendor: SEAGATE Model: ST3600057SS Rev: 0006
    Type: Direct-Access ANSI SCSI revision: 05
    Vendor: SEAGATE Model: ST3600057SS Rev: 0006
    Type: Direct-Access ANSI SCSI revision: 05
    Vendor: LSI Model: MR9260-4i Rev: 2.70
    Type: Direct-Access ANSI SCSI revision: 05
    SCSI device sda: 2342125568 512-byte hdwr sectors (1199168 MB)
    sda: Write Protect is off
    sda: Mode Sense: 1f 00 00 08
    SCSI device sda: drive cache: write back
    SCSI device sda: 2342125568 512-byte hdwr sectors (1199168 MB)
    sda: Write Protect is off
    sda: Mode Sense: 1f 00 00 08
    SCSI device sda: drive cache: write back
    sda: sda1 sda2
    sd 0:2:0:0: Attached scsi disk sda

    Let me know if I can provide any other information.

     
  • Detlef Paschke

    Detlef Paschke - 2020-03-22

    Hi there,
    this problem still seems to exist. Megactl shows a faulty BBU although everything is OK.

    root@Proxmox:~# megasasctl
    a0       LSI 2108 MegaRAID        encl:1 ldrv:1  batt:FAULT, low voltage
    a0d0      7446GiB RAID 5   1x5  optimal
    a0e252s0   1863GiB  a0d0  online
    a0e252s1   1863GiB  a0d0  online
    a0e252s2   1863GiB  a0d0  online
    a0e252s3   1863GiB  a0d0  online
    a0e252s4   1863GiB  a0d0  online
    
    root@Proxmox:~# megaclisas-status
    -- Controller information --
    -- ID | H/W Model         | RAM    | Temp | BBU    | Firmware
    c0    | LSI 2108 MegaRAID | 512MB  | N/A  | Good   | FW: 12.15.0-0239
    
    -- Array information --
    -- ID | Type   |    Size |  Strpsz | Flags | DskCache |   Status |  OS Path | CacheCade |InProgress
    c0u0  | RAID-5 |   7271G |   64 KB | RA,WB |  Default |  Optimal | /dev/sdf | None      |Background Initialization : Completed 23%, Taken 52 min.
    
    -- Disk information --
    -- ID  | Type | Drive Model                                  | Size     | Status          | Speed    | Temp | Slot ID  | LSI ID
    c0u0p0 | HDD  | WD-WMC300643544WDC WD20EFRX-68AX9N0 80.00A80 | 1.817 TB | Online, Spun Up | 6.0Gb/s  | 28C  | [252:0]  | 13
    c0u0p1 | HDD  | WD-WCC4M1ZJ9X98WDC WD20EFRX-68EUZN0 82.00A82 | 1.817 TB | Online, Spun Up | 6.0Gb/s  | 29C  | [252:1]  | 15
    c0u0p2 | HDD  | WD-WCC4M0CV40Y2WDC WD20EFRX-68EUZN0 82.00A82 | 1.817 TB | Online, Spun Up | 6.0Gb/s  | 28C  | [252:2]  | 14
    c0u0p3 | HDD  | WD-WMC301253572WDC WD20EFRX-68AX9N0 80.00A80 | 1.817 TB | Online, Spun Up | 6.0Gb/s  | 28C  | [252:3]  | 16
    c0u0p4 | HDD  | WD-WCC4M2660527WDC WD20EFRX-68EUZN0 82.00A82 | 1.817 TB | Online, Spun Up | 6.0Gb/s  | 28C  | [252:4]  | 17
    
    root@Proxmox:~# megacli -AdpBbuCmd -GetBbuStatus  -aALL
    
    BBU status for Adapter: 0
    
    BatteryType: iBBU08
    Voltage: 4063 mV
    Current: 0 mA
    Temperature: 38 C
    Battery State: Optimal
    Design Mode  : 48+ Hrs retention with a non-transparent learn cycle and moderate service life.
    
    BBU Firmware Status:
    
      Charging Status              : None
      Voltage                                 : OK
      Temperature                             : OK
      Learn Cycle Requested                   : Yes
      Learn Cycle Active                      : No
      Learn Cycle Status                      : OK
      Learn Cycle Timeout                     : No
      I2c Errors Detected                     : No
      Battery Pack Missing                    : No
      Battery Replacement required            : No
      Remaining Capacity Low                  : No
      Periodic Learn Required                 : No
      Transparent Learn                       : No
      No space to cache offload               : No
      Pack is about to fail & should be replaced : No
      Cache Offload premium feature required  : No
      Module microcode update required        : No
    
    BBU GasGauge Status: 0x0280
      Relative State of Charge: 100 %
      Charger System State: 1
      Charger System Ctrl: 0
      Charging current: 0 mA
      Absolute state of charge: 79 %
      Max Error: 0 %
    
    Exit Code: 0x00
    

    Best wishes

     

Log in to post a comment.