Hi CRZ,

Installing this upgrade now on 5220 running 2.5.1b. I will let all know how it goes.

K.

I installed it (with a little help from Symantec) on 2.5.1GA because of a couple failed EEB installs they had to do some script editing to get the install.

Since then I have been getting High Disk IO error alerts  even while nothing is going on. I have contacted our RPS about this.

Hi Wolfsbane,

Ouch on the high disk IO error alerts. Installed no problem for me on 2.5.1b (appliance release). It solved my Linux clients BMR issue. I had issue where no BMR backups would not run for linux clients. This upgrade solved it.

K.

We're getting these alerts as well. They are caused by the RAID Controller cache battery tests that seems to have kicked off by the v2.5.2 software.

If you check with

/opt/MegaRAID/MegaCli/MegaCli64 -AdpBbuCmd -GetBbuStatus -aALL

you'll see that the battery status is either discharging or charging due to Learn Cycle Requested.
Due to the fact that the battery status is not 'healthy' the RAID controller disables the write cache, which causes the heavy disk I/O (Every write is being performed physically to the disks, causing some write performance decrease and fairly heavy utilized disks).

Just sit tide for 24 hours. After this time everything should be fine.

Marco V.

I have been getting them for five days

BBU status for Adapter: 0

BatteryType: iBBU
Voltage: 4029 mV
Current: 0 mA
Temperature: 29 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: 99 %
Charger System State: 49168
Charger System Ctrl: 0
Charging current: 0 mA
Absolute state of charge: 82 %
Max Error: 2 %
Adapter 1: Get BBU Status Failed.

Exit Code: 0x01

Everything looks OK

Well,

We have 6 appliances running and since this morning the appliances stopped screaming.
I also double checked the current controller cache settings and everything went back to normal.
And NO, we haven't overruled that cache settings manually!!!

To conclude, for our 6 appliances it took approx. 41 hours to settle back to normal behavior.
Find below the current status of the Raid Controllers Cache settings;

All,

Sorry for my 'not-so-complete' analysis.
I've tackled the problem now completely. After the update to v2.5.2 Symantec decided to disable
the controller cache for Adapter 2, the internal disks Raid Controller.

This definitely solved it. Due to the fact that since this morning the intensity of those mail really dropped from once every 15 minutes to intermitted once or twice every two hours, I reacted a bit too premature..

One might expect Symantec releasing a Technote for this... ;-)

Also do not forget to Acknowledge the existing Alert (Settings -> Alert AcknowledgeErrors)... ;-)

Best regards,

        Marco

Our alerts have stopped as well. You appear to have a 24TB 5220 and therefore have different controllers. Mine is a 4TB unit and we look like this:

/opt/MegaRAID/MegaCli/MegaCli64 -LDInfo -L0 -aALL
                                    

Adapter 0 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name                :
RAID Level          : Primary-6, Secondary-0, RAID Level Qualifier-3
Size                : 4.541 TB
State               : Optimal
Strip Size          : 64 KB
Number Of Drives    : 7
Span Depth          : 1
Default Cache Policy: WriteBack, ReadAdaptive, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAdaptive, Direct, No Write Cache if Bad BBU
Access Policy       : Read/Write
Disk Cache Policy   : Disabled
Encryption Type     : None

Adapter 1 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name                :
RAID Level          : Primary-1, Secondary-0, RAID Level Qualifier-0
Size                : 930.390 GB
State               : Optimal
Strip Size          : 64 KB
Number Of Drives    : 2
Span Depth          : 1
Default Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if Bad BBU
Access Policy       : Read/Write
Disk Cache Policy   : Enabled
Encryption Type     : None

Exit Code: 0x00

This is from the only machine I upgraded. The others show this:

/opt/MegaRAID/MegaCli/MegaCli64 -LDInfo -L0 -aALL
                                    

Adapter 0 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name                :
RAID Level          : Primary-6, Secondary-0, RAID Level Qualifier-3
Size                : 4.541 TB
State               : Optimal
Strip Size          : 64 KB
Number Of Drives    : 7
Span Depth          : 1
Default Cache Policy: WriteBack, ReadAdaptive, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteThrough, ReadAdaptive, Direct, No Write Cache if Bad BBU
Access Policy       : Read/Write
Disk Cache Policy   : Disabled
Encryption Type     : None

Adapter 1 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name                :
RAID Level          : Primary-1, Secondary-0, RAID Level Qualifier-0
Size                : 930.390 GB
State               : Optimal
Strip Size          : 64 KB
Number Of Drives    : 2
Span Depth          : 1
Default Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if Bad BBU
Access Policy       : Read/Write
Disk Cache Policy   : Enabled
Encryption Type     : None

Exit Code: 0x00

Which is essentially the same. I do not believe the data drive array is supposed to have the write cache enabled. I have put that to Symantec to validate.