Blade hangs on boot and "FW/BIOS, firmware progress (ABR Status) FW/BIOS ROM corruption" message in AMM

http://linuxtoolkit.blogspot.com/2011/04/blade-hangs-on-boot-and-fwbios-firmware.htmlIf you see and encounter error

Blade hangs on boot and "FW/BIOS, firmware progress (ABR Status) FW/BIOS ROM corruption" message in AMM - IBM BladeCenter HS22, HS22V

Symptoms
When booting BladeCenter HS22 or HS22V with Integrated Management Module (IMM) build yuoo84c installed, the blade may hang at the "UEFI Platform Initializing" screen. The hang will be accompanied by the following event in the chassis Advanced Management Module (AMM) log:

FW/BIOS, firmware progress (ABR Status) FW/BIOS ROM corruption

Affected Systems:
The system may be any of the following IBM servers:

• BladeCenter HS22, type 1936, any model
• BladeCenter HS22, type 7870, any model
• BladeCenter HS22V, type 1949, any model
• BladeCenter HS22V, type 7871, any model 

Workaround
This failure may be reduced by disabling Internet Protocol Version 6 (IPv6) support for the IMM. This can be done via the following steps:

1. Boot the blade to the F1 Unified Extensible Firmware Interface (UEFI) setup screen.
2. Select "System Settings" and press Enter
3. Select "Integrated Management Module" and press Enter
4. Select "Network Configuration" and press Enter
5. Change "IP6" setting to "Disable"

Occasionally, the failure can be recovered by restarting the IMM. If this is not successful, then it is necessary to reseat the blade in the chassis to recover. After a reseat, the blade will boot normally.

Additional Information
This error only occurs at boot time so production servers that are up and running are not at risk.


https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014477272

BNT L2/3 Ethernet Module flash

http://emmanuel.iffly.free.fr/doku.php?id=hardware:blade_center

INIT failed status and Problem communicating with BSMP on IBM Blade Chassis

I have a fully loaded Blade Chassis H (ie 14 Blades). I have the following symptoms similar to what was written in IBM Site INIT failed status - IBM BladeCenter HS22, HS22V

   

0X0021600 / Symptom:

BladeCenter HS22 or HS22V status is reported as Init Failed and the following error is posted in the Advanced Management Module (AMM) event log:

0x00216000 Problem communicating with BSMP

The chassis has 14 blades installed.

Workaround:

Remove one blade from the chassis.

Solution:
Install AMM firmware v3.54L (BPET54L) or later.

The file is available by selecting the appropriate machine type on the 'Software and device drivers - IBM BladeCenter' web page, at the following URL:

IBM  Blade Chassis Product View

Patching

Select the correct Blade Chassis Product. Since I am using Blade Chassis H, my fixes were

ibm_fw_amm_bpet62o_anyos_noarch
(IBM BladeCenter Advanced Management Module Firmware Update)

The patching will require restart of the AMM. Restarting the Advanced Management Module will disconnect your current session.


http://linuxtoolkit.blogspot.com/2012/03/init-failed-status-and-problem.html 

Производительность mdadm raid 5,6,10 и ZFS zraid, zraid2, ZFS striped mirror

https://habr.com/ru/post/344204/

о дисковой производительности Windows VM в Proxmox VE

https://habr.com/ru/post/315334/

Калькулятор
https://efsol.ru/articles/raid-performance.html

BladeCenter S SAS Raid: add capacity with low battery

Mar 17, 2016 | Tags: bbu, bladecenters, raid, sas

This question has not been answered yet.

When i try to add my new disk to an existing Pool with the CLI command "add capacity" the result is:

<CLI> add capacity -pool StoragePoolA -drivelist 1:5 1:6

Working ...

Current Machine Local Time: 03/17/2016  09:27:05 AM
Error : add capacity command failed
Reason: Low battery

I know there is a "low battery" status but i'm stuck with "Reset BladeCenter S BBU expiration date" .

Is it possible to force the operation?  

My SAS swversion is:<CLI> swversion
Current Machine Local Time: 03/17/2016  09:22:15 AM

Software version      : H-3.1.1.2
UBoot version         : H-1.1.4.6
OS  version           : H-2.4.20.12
SES version           : 0107
BMC version           : S0BT10A    0121 02/08/2010
FPGA version          : 01.07
CPLD version          : S0CP00A    C00A 01/01/2000
SAS switch version    : S0SW01D    R109 10/09/2014
BBU FirmwareRev       : 58.0
Package Build No      : 1.3.4.012
     

Замена батареек IBM BladeCenter RAID Battery Backup replacement

IBM BladeCenter RAID Battery Backup replacement

 

Does anybody know if is possible to replace the battery inside of a "IBM BladeCenter RAID Battery Backup Module" (p/n 22R6649) ?
The battery is a double 4.8V 3500mAh (P/N 17P8979) and is easy to find a replacement by many sellers over internet.
CLI output is:

CLI> battery -ctlr 0 -get

Controller 0
Current Machine Local Time: 02/23/2016  02:28:45 PM

  BBU State                                         : 3  (Faulted)
  BBU Fault Code                                    : 10  (Expired)
  BBU Part Number                                   : 22R6649
  BBU Serial Number                                 : xxxxxxx
  BBU FRU Number                                    : 22R6833
  BBU Firmware Revision                             : 58.0
  BBU Expiration Date                               : Sun Jan 27 12:00:00 2013
  Charging state information        
  BBU Charging                                      : False 
  BBU Capacity (Hours)                              : 0 

EDIT: I found a possible solution here: https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014928197
They suggest to place the batteries in service status with CLI
mountstate -setobject -dismount -bbu 0
mountstate -setobject -dismount -bbu 1
Then change the batteries and reinstall the first one, wait about two minutes, and check if battery is recognized. The BBU Expiration Date should be reset.
I followed all the procedure suggested (I also powered off the entire Bladecenter) but my BBU is still Faulty and Expired, with the same Expiration Date:
BBU Expiration Date : Sun Jan 27 12:00:00 2013

 

Сброс пароля SAS Raid controller Ibm bladecenter

https://www-01.ibm.com/support/docview.wss?uid=ibm1MIGR-5079527

How to reset the SAS RAID module CLI password - IBM BladeCenter S

Troubleshooting

Problem

This explains how to reset the SAS RAID Module CLI password back to the default password.

Resolving The Problem

Source

RETAIN tip: H194812

Symptom

This explains how to reset the SAS RAID Module CLI password back to the default password.

Affected configurations

The system is configured with one or more of the following IBM Options:

• IBM BladeCenter S SAS RAID Controller Module, Option 43W3584

This tip is not hardware specific.
This tip is not software specific.

Workaround

High-Level Workaround Process:

1. Shutdown both controllers using the AMM.
   
   
   
2. Reset Defaults on Bay 3 controller only.
   - Wait for Bay 3 controller to reset/post using the AMM.
   
   
   
3. Shutdown Bay 3 controllers using the AMM.
   - Wait for Bay 3 controller to turn off.
   
   
   
4. Reset Defaults on Bay 4 controller only using the AMM.
   - Wait for Bay 4 controller to reset/post.
   
   
   
5. Power on Bay 3 controller using the AMM
   

Additional information

Detailed Workaround Process:

1. Shutdown both controllers down using the AMM
   
   1. Log into the Advanced Management Module.
      
      
      
   2. Click on I/O Module Task --> Admin/Power/Restart.
      
      
      
   3. Click the box next to Bay 3 and Bay 4.
      
      
      
   4. Under Available actions select Power Off Module(s).
      
      
      
   5. Click on Perform action.
      
      
      
   6. Click on OK.
      
      
      
   7. Verify the power state message is Off under the Pwr column.
      
   
   
2. Perform Reset to Defaults on Bay 3 using the AMM
   
   1. Log into the Advanced Management Module.
      
      
      
   2. Click on I/O Module Task --> Configuration.
      
      
      
   3. Click on Advanced Configuration under the Bay 3 (SAS RAID Ctrl Mod) section
      
      
      
   4. Verify Advanced Setup setting are Enabled
      
      

      - Enable: 'External management over all ports' - Enable: 'Preserve new IP configuration on all resets'

      
      
   5. Click on Restore Defaults Button
      
      
      
   6. Click on OK.
      
      
      
   7. Click on I/O Module Task --> Admin/Power/Restart.
      
      

      - Wait For Bay 3 to POST Successfully: POST results available: Module completed POST successfully.

• Shutdown controller in Bay 3 using the AMM
  

1. Log into the Advanced Management Module.
   
   
   
2. Click on I/O Module Task --> Admin/Power/Restart.
   
   
   
3. Click the box next to Bay 3.
   
   
   
4. Under Available actions select Power Off Module(s).
   
   
   
5. Click on Perform action.
   
   
   
6. Click on OK.
   
   
   
7. Verify the power state message is Off under the Pwr column.
   

• Perform Reset to Defaults on Bay 4 using the AMM
  

1. Log into the Advanced Management Module.
   
   
   
2. Click on I/O Module Task --> Configuration.
   
   
   
3. Click on Advanced Configuration under the Bay 4 (SAS RAID Ctrl Mod) section
   
   
   
4. Verify Advanced Setup setting are Enabled
   
   

   - Enable: 'External management over all ports' - Enable: 'Preserve new IP configuration on all resets'

   
   
5. Click on Restore Defaults Button
   
   
   
6. Click on OK.
   
   
   
7. Click on I/O Module Task --> Admin/Power/Restart.
   
   

   - Wait For Bay 4 to POST Successfully: POST results available: Module completed POST successfully.

• Power On Bay Bay 3 using the AMM
  

1. Log into the Advanced Management Module Application.
   
   
   
2. Click on I/O Module Task --> Admin/Power/Restart.
   
   
   
3. Click the box next to Bay 3.
   
   
   
4. Under Available actions select Power On Module(s).
   
   
   
5. Click on Perform action.
   
   
   
6. Click on OK.
   
   
   
7. Verify the power state message is On under the Pwr column.
   
   

   - Wait For Bay 3 to POST Successfully: POST results available: Module completed POST successfully.