Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

Datacenter SystemsSystem x - X6, M5, M4
All Forum Topics
Options

60 Posts

09-16-2015

New Zealand

59 Signins

957 Page Views

  • Posts: 60
  • Registered: ‎09-16-2015
  • Location: New Zealand
  • Views: 957
  • Message 1 of 4

IMM and MSM disagree

2019-12-31, 2:36 AM

a final post for 2019 :)

I have a x3630M4 (7158) with M5110 raid controller, where the IMM and MSM/Raid card disagree about the drive status.

 

IMM shows Disk 0 as being disabled due to detected fault.

It was over a month ago, and was replaced, and now is all good according to MSM.

 

IMM firmware was updated, which rebooted it.

MSM was upgraded.

I haven't tried a server reboot yet, it will happen during the next maintenance window, along with the raid and EFI firmware to see if that sorts it.

 

Strange issue, and I have another one, same model, which is doing the same thing.

Given I have at least 20 of this model in operation, and haven't encountered it before, still trying to sort out a cause.

 

Might be a new puzzle for 2020.

 

 

 

Reply
Options

87 Posts

08-13-2015

China

140 Signins

1284 Page Views

  • Posts: 87
  • Registered: ‎08-13-2015
  • Location: China
  • Views: 1284
  • Message 2 of 4

Re: IMM and MSM disagree

2019-12-31, 6:14 AM

pls check the vpd info of disk0 from GUI -Storage -disk  , was the disk0 info (s/n, sas address ) show the correct info with MSM ?

 

This could be false alert  / or the status didn't syne up from controller after drive replacement. below steps can be use to isolate this issue.

 

1. Udate Imm to latest version and reboot IMM.

2. ./storcli64 /c0  restart   ( try to restart the controller ,during restart ,IO will be blcok by os driver, pls check this when server was idle /less io there.

 

3. AC cycle the server.

 

4. backup imm config, restore IMM to factory, and check whether it fix, if fixed, reconfigure IMM.

Reply
Options

60 Posts

09-16-2015

New Zealand

59 Signins

957 Page Views

  • Posts: 60
  • Registered: ‎09-16-2015
  • Location: New Zealand
  • Views: 957
  • Message 3 of 4

Re: IMM and MSM disagree

2020-02-13, 20:58 PM
I have finally resolved this after much trial and error. Upgrading the raid controller to 23.34.0-0023 with ibm_fw_sraidmr_6gb-23.34.0-0023_windows_32-64.exe fixes it. Many links for this controller on the IBM site are broken, inluding the latest windows driver. I have used the MR_WINDOWS_DRIVER_6.14-6.714.18.00-WHQL.zip from Broadcom instead, which is the correct one confirmed by the MegaSAS2.inf having IBMM5110.DeviceDesc = "IBM ServeRAID M5110 SAS/SATA Controller" It is found on the downloads for the MegaRAID SAS 9266-8i controller.
Reply
Options

11 Posts

02-25-2020

United States of America

6 Signins

20 Page Views

  • Posts: 11
  • Registered: ‎02-25-2020
  • Location: United States of America
  • Views: 20
  • Message 4 of 4

Re:IMM and MSM disagree

2020-02-27, 22:59 PM
Hi! How You manage this issue? Rebuild the whole array? Change the drive on new? Based on total storage volume and each drive size on pictures a You provide, suggest You to install simply adapter that work with disks as simply host, and use ZFS, for example in FreeNAS implementation. Better than all LSI/Qlogic that should may find now for Systemx. Of course, if You not so stick to IMM. But anyway, I hope a Your data are more important to You than so-so usability with IMM. :)
Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms