Cross-flashing an IBM M5014 to LSI 9260
- Thread starter sijones
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Hi Patrick,
That would great if you get the chance.
I received my M5014 today and found that it has IBM firmware version 12.12.0-0098 installed on it. Looking at the firmware revision history, in version 12.12.0-0085 it appears that the following change "Prevent non IBM firmware from being flashed on IBM ServeRAID branded controllers" was implemented. Do you know if this is a showstopper?
Kind regards,
Steve
The M5014 is practically identical to the M5015 (excepting Cache size) same FW will flash to both cards
The procedure is the same, I would think the SBR is the same too.
As for 12.12.0-0098 it means MSM when flashing a different FW will fails as will Megarec.
BUT you clear the Firmware first then reboot and flash the FW of choice, then set the SBR then reboot again.
The M5014 is now I think the king of cheap bargains, taken over from the M1015 which are hard to find now for what they used to go for.
The procedure is the same, I would think the SBR is the same too.
As for 12.12.0-0098 it means MSM when flashing a different FW will fails as will Megarec.
BUT you clear the Firmware first then reboot and flash the FW of choice, then set the SBR then reboot again.
The M5014 is now I think the king of cheap bargains, taken over from the M1015 which are hard to find now for what they used to go for.
Yes with the IBM SBR you can make a cup of tea, bake the scones, grow the Raspberries to make jam.
The very fist boot after flash takes the longest (about 3min), this is no matter which SBR you have
Change the SBR to anything but SBR and it will no take 1/2 as long in subsequent boots.
Firmware 12.12.0-0047 (IBM) and 12.12.0-0048 (Intel or SUN/Oracle) have Active drive spindown (full power save features)
These are the only FW with this that I know of.
The very fist boot after flash takes the longest (about 3min), this is no matter which SBR you have
Change the SBR to anything but SBR and it will no take 1/2 as long in subsequent boots.
Firmware 12.12.0-0047 (IBM) and 12.12.0-0048 (Intel or SUN/Oracle) have Active drive spindown (full power save features)
These are the only FW with this that I know of.
Card came with 12.12.0-0039
X9SCM-F posts fine with the card but I am getting a blinking cursor even when setting the SSD connected to the motherboard as boot device 1. Have even tried disabling the option ROM, card BIOS, battery pull and etc.
Fun stuff.
X9SCM-F posts fine with the card but I am getting a blinking cursor even when setting the SSD connected to the motherboard as boot device 1. Have even tried disabling the option ROM, card BIOS, battery pull and etc.
Fun stuff.
Hi,
I would like to crossflash mine too but need a guide on how to do this?
any help would be appreciated
Thanks
I would like to crossflash mine too but need a guide on how to do this?
any help would be appreciated
Thanks
Why are these cards causing so many issues with Mobo's.
You'd think with a Supermicro it would just work.
See the thread "My M5015 experiences' it will lead you to salvation
The M1015 has been out for a long time, it must be in 1000's of Supermicro server worldwide, surely this would have been addressed ages ago.
Even Supermicro making the BIOS must know the issues with LSI and have a workaround from previous motherboards
It all seems so strange, the OEMs seem not to learn from anything previous, just put something out and hope for the best attitude seems more and more prevalent.
I may need to do some testing of my own.
I have the P8Z77 WS where the card works but sas2flash refuses to work, but Megarec does (so I can't cross flash to IR or IT mode, but can to MegaRAID mode.
The ASROck is a stable mobo where everything works as it should.
In need to get me a LGA1155 Xeon to put in the WS board, so I can get the ASRock Fatal1ty working and do more testing on that
Even Supermicro making the BIOS must know the issues with LSI and have a workaround from previous motherboards
It all seems so strange, the OEMs seem not to learn from anything previous, just put something out and hope for the best attitude seems more and more prevalent.
I may need to do some testing of my own.
I have the P8Z77 WS where the card works but sas2flash refuses to work, but Megarec does (so I can't cross flash to IR or IT mode, but can to MegaRAID mode.
The ASROck is a stable mobo where everything works as it should.
In need to get me a LGA1155 Xeon to put in the WS board, so I can get the ASRock Fatal1ty working and do more testing on that
So the way I think of it, technically ServeRAID is an IBM product, in theory are only meant to work in IBM servers. Supermicro probably does not have a huge base putting IBM rebrands of LSI cards into their servers. That being said, at least we have found out that we can work around the issue.
What motherboard have you got the M5014 in ?
In older PCIe Gen1 boards this may happen as the controller to system speed is not high enough to cope with 6Gbps
In older PCIe Gen1 boards this may happen as the controller to system speed is not high enough to cope with 6Gbps
It's in a Fujitsu Primergy TX100 S3. This uses a Fujitsu D3009 motherboard. The raid controller states two speeds for the drive; Drive Speed and Negotiated Link Speed. Both of these are 3Gbps. If it was a limitation of the motherboard wouldn't it still show that the drive is capable of 6Gbps and then negotiate down to 3Gbps?
This is the manual for the motherboard: http://manuals.ts.fujitsu.com/file/10327/tx100s3-d3009-tm-en.pdf
Many thanks for you assistance.
Kind regards,
Steve
Last edited:
OK it's fairly new then.
Have a look in the BIOS that the PCIe setting is not set to PCIe Gen1, my ASUS mobo can force PCIe Gen1
This might be the issue, I can test this once I'm back home.
What version FW is the M5014 running, as originally SATA3 was not out when the M5015/4 were released.
Latest version currently is 12.12.0-0111 (or was it 0-0101)
And yes you'd think the controller would say the drives are 6Gbps and slow down to 3Gbps but you never know these days.
Have a look in the BIOS that the PCIe setting is not set to PCIe Gen1, my ASUS mobo can force PCIe Gen1
This might be the issue, I can test this once I'm back home.
What version FW is the M5014 running, as originally SATA3 was not out when the M5015/4 were released.
Latest version currently is 12.12.0-0111 (or was it 0-0101)
And yes you'd think the controller would say the drives are 6Gbps and slow down to 3Gbps but you never know these days.
I couldn't see anything in the BIOS to change the PCIe settings. It's running FW 12.12.0-0111.
Kind regards,
Steve
Hey Pieter,
Was getting the PAL issue on the X9SCM-F with sas2flsh. Decided to try megarec and I think it just worked.
How does this sound...
Was getting the PAL issue on the X9SCM-F with sas2flsh. Decided to try megarec and I think it just worked.
How does this sound...
It now shows up as a LSI MegaRAID SAS 9260-8i during the firmware initialization which is what I would expect using the above. Been a long time since I did a non- sas2flash
I flashed with 12.15.0.189 firmware and the card is showing on bios post that is LSI9260-8i and working.
But I don't have the Advance Software Options menu in bios or MSM application in Windows.
I found on internet one pdf that show some difference between MR controller and IR controller and IR controller is missing Advance Software Option.
Any suggestion?
But I don't have the Advance Software Options menu in bios or MSM application in Windows.
I found on internet one pdf that show some difference between MR controller and IR controller and IR controller is missing Advance Software Option.
Any suggestion?