MSA 1500 problem I2C error

[Osama Odeh_1]

After new installation new for MSA 1500 with 2 msa100 controller " 30 I2C READ FAILURE " message appear,
we try to isolate the problem by use each cortoller alone but still we have the same error
we also try to use
fiber module one by one and still problem exist.

then we upgrade the firmware to the latest version 5.10.b414 and it's cloned to the another controller and the storage work fine ,

but after about 20 days and
the message appear again
then we just power off the storage and power on and it's work.
did we need to replace the box may it's a bus problem.


** note where can we retreive all history message appear on lcd
in command line in event log acommand nothing appear there

Thanks in advance

[John Kufrovich]

O.Odeh,

Can you please post the
MSA cli >show tech_support

Regards,
jk

[Matthew P Simms]

We had I2c errors on our MSA1500 for a year and a half. After replacing the backplane, msa1000 controllers, SCSI cables, and SCSI IO Modules, we unpluged our 2 MSA20 SATA shelves and the error disappeared.

We've dumped our MSA20 SATA shelves and now only run all MSA30 with no problems at all, both MSA20 shevles seemed to be causing all the errors.

That's my MSA1500cs experience with the I2c errors.

[Osama Odeh_1]

dear john and mathew

thanks for yoor response

sorry there is amistake when i post this thread because the error i2c didn't appear after the upgrade because the it admin told me the it appear but when i double check on his site i found MSA 1500 is hang and the error is 513 uncoorectable ecc message
on right controller when this happend the left controller also hang
this problem i see it two times


after restart the MSa 1500 it's work fine thent after 14 hours the 513 message appeaer again

we decide to replace the right contoller with new one
but also after hours the same problem appear on the left controller

** now we are testing MSA1500 with only the new controller with 256mb cache

to see if this problem appear

thanks again

but the current

[Osama Odeh_1]

john you can find attached file on previous reply for >show tech_support

thanks

[John Kufrovich]

O. Odeh
These first steps may not solve your initial problem but they are important.

1). Please set an ACL (aka SSP), this will eliminate servers taking LUNs and any future mistakes.
2). While configuring the ACL, Please set the host profile to the appropriate OS.

Once completed can you post a new tech_support.

Regards,

[Osama Odeh_1]

** after last error appear on the left controller we tested the following and error message ecc 513 not appear again:

1- test with only one controller with 256mb cache
2- test with two controller each 256mb cache
3- test with only onecontroller with 512mb cache
4- test with two controller each 512mb cache

any suugestion please
for this issue

thanks

[Chris V.]

Hello,

I got similar issue lately (2/1, then 16/1) and the MSA 1500 enclosure itself had to be replaced.
Initially, one of the disk enclosure was triggreing a "zombie" Fan alert that triggered the I2C bus error driving to the whole 4 disks enclosures system to go down.

After replacement of the MAS1500, the disk enclosure (replaced later on :)) still generated the Fan error, but this time, the MSA reported the error and kept running.

To summarize, I'm afraid you'll have to replace the box.

Chris

[John Kufrovich]

Chris,
It is not the box. Please provide a MSA cli >show tech_support

What model of servers?
single port HBA or dual ported?

[John Kufrovich]

0.0deh,

Making sure you and I are on the same page.

In your last msg, you performed some testing. Is the 513 ecc error still occurring.

Did you make the ACL changes?

[Osama Odeh_1]

Hi john,
about SSP we didn't configure it because we have only 2 dl380 server connected to SAN switch to this MSA (( pls confirm did this related to our problem an we must to configure ssp))

our 2 servers work as ms cluster ( exchange 2003).

** till now after last diagnostic and using two controller and 512mb memory on each one
the ecc error not appear( we don't know why not appear again )

we afraid it's occured randomly

we planing to replacle the MSA 1500 cs 361263-001 box

any suggestion pls
thanks

[PJJ De Mol]

John, why are you so sure it is not the box? Could you explain?

Background for my question. Today we had a 10 hour downtime due to MSA controllers giving errors. It started out with a (bogus?) fan controller message. And after restart we got 30/31 error I2C read/write errors.

Got support involved, swapping controllers etc etc did not help in the end the chassis was swapped (and al our original stuff was put in there) and guess what system was back up and running.

My fear now is that we might get into this again later one (lost a good deal of confidence today).

BTW: I will try to run the tech_support command tomorrow.

[John Kufrovich]

O.Oden,

Setting SSP isn't related to the ECC problem I was being proactive. I would hate for you to add another server and mistakenly use a LUN. Windows has a nasty habit of claiming all LUNs for itself. Plus you should set the Host Profile mode.

If I create a FTP site can you run this data collection tool against either node. It is similiar to Microsoft MPS reports.

[John Kufrovich]

PJJ,

Did you get the show tech_support