Sign in to follow this  
Slowdive

Supermicro SuperStorage 6047R-E1R72L / Expander Card with LSI 9271-8i

Recommended Posts

Hi,

i need to Configure the Storage server (first 24 SATA Seagate SV35) with a LSI MegaRAID 9271-8i in RAID 6. I connected both mini-SAS SFF-8087 x4 from the LSI to the first HBA on the expander Card so that the Controller manages 24 SATA HDDs. The problem is that the LSI WebBIOS only shows Connector Ports 0-3 active (so only the first mini-SAS Cable / Connector).

I tried cross-connecting the LSI with one mini-SAS on the first HBA1 and second to the HBA2, and the result was unexpected, now both Connector ports were active, but all the Drives were "unconfigured, BAD" and i couldn't add them to drive groups.

LSI Support can't help me because they don't know much about the Expander, Backplane etc. And Supermicro suggested that the problem lies with the SATA Drives, and I should use SAS Drives instead. But i cannot believe that is the case.

I want to use a non-cascading Architecture with 2 HW RAID-Controllers + Onboard RAID-Controller for a combined of 72 SATA HDDs. As seen in this Documentation :

http://www.superxpert.com/assets/product/datasheet/6047R-E1R72L/6047R-E1R72L.pdf

This is the Server : http://www.supermicro.com.tw/products/system/4U/6047/SSG-6047R-E1R72L.cfm?parts=SHOW

Edited by Slowdive

Share this post


Link to post
Share on other sites

basically, you're trying to form a "wide" connection (with x8 bandwidth) between your controller and the ports served by the first expander. is there any setting on the controller related to "wide" negotiation? does it behave the same if you connect both x4 links to the expander for the top 24 ports? (ie, the "HBA2" connectors)

connecting the controller to one x4 connector for HBA1 and HBA2 would logically cause the controller to negotiate two narrow links (to the two expanders). (but that's how you'd use that one controller to connect to all 48 front bays.) I speculate that the renegotiation made the controller firmware think the disk setup had changed as well - so it doesn't want to treat the disks as already-configured.

I'm assuming you have the "non-cascading" expander architecture.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this