Intel Communities: Message List - S2600GZ drive numbering issue

Re: S2600GZ drive numbering issue

webadmin@intel.com — Fri, 08 Jun 2012 16:09:36 GMT

JFFulcrum,

Editing the ServiceGroupOrder reg key, adding an SCIS first entry, is visible in the online WinPE but it has no effect. The same can be said for changing the Tag REG_DWORD property of the iaStorA driver reg key. I used a valid value for the Tag value based on another driver which is also installed so as to avoid messing up by using an invalid Tag.

The site you linked kinda says, even though all this is true, it still may not work. So I don't know if it's a case of information being too old to be applicable, or there's some deeper interaction.

The only way I see of futher exploiting this technique is to actually edit the .ini file. I don't want to do this because I don't want to break Driver Signing. I think I have enough to go back to the stake holder and say, this isn't possible.

Thanks JFFulcrum, Philip and Edward for your assistance, even if it didn't get to the solution I hoped for, it was very much appreciated. It helped reinforce what I was finding independently. If anyone has any last tricks I'm all ears, but I think if nothing changes by Monday, I'll call this done.

Jason

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 20:52:07 GMT

Philip,

Interesting theory, but SATA is at Bus 0, Device 31, Function 2 while SAS SCU is at Bus 3, Device 0, Function 0.

Jason

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 17:11:57 GMT

Jason,

While I have not looked at the electrical layout for the board as far as controller positioning on the PCI-E bus yet I suspect that despite what the BIOS says (essentially software says) that WinPE is seeing the physical bus position of each controller.

The one showing first is higher (closer to position 0 iirc) than the other.

There may be no way to change this.

We run into this situation to some degree when we are setting up multiple RoC Hardware RAID controllers along side a number of SAS HBAs. Pecking order can become an issue.

Philip

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 16:57:15 GMT

Philip,

Optional boot order is configured with the AHCI / 240GB SSD first, but this does not carry through to WinPE.

Jason

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 16:38:42 GMT

Jason,

What does Boot Order and then the submenu Hard Drive order look like?

The customer is only as right as the solution will allow. One cannot ask for something that cannot be had as much as it may be desired.

Philip

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 16:29:35 GMT

Philip,

I verified the build and it seems that when I said the SCU was in ESRT2 mode I was incorrect, it is in fact in RSTe mode. This is due to the fact that I am testing on a reference system that was not configured per the build instructions. I should point out that the build instructions are essentially, from the customer. So any argument you have for changing the build are invalid since, in all cases, the customer is always right. I have no idea what the customer wants to achieve by this build, and it's not in my purview to spec the systems, I merely support the process and find answers.

That being said, I will show you the mass storage controller configuration which is in play.

Notice the SATA controller is in AHCI.

Jason

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 16:10:41 GMT

Jason,

There are two modes for the chipset software RAID setup. Shown above is the LSI* setting. The other is Intel's Matrix Storage. We _always_ use the LSI version. We can then later plug in an Intel or LSI RoC Hardware RAID controller and pick up the arrays without issue.

Why are you splitting the drives across controllers anyway?

The setup being done is not quite what we would do for workstation and server setups.

Plug the drives into the same controller define RAID 1 for the pair and either JBOD (leave it) or RAID 0 the standalone.

Make sure the standalone is on cable port 0 while the others are on 1 and 2. This will place the standalone at the top of the list.

If the image above is not clear a better one is on our blog here:

http://blog.mpecsinc.ca/2012/05/thoughts-on-intel-server-system.html

Philip

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 15:12:41 GMT

Philip,

Let me clarify, I am using two onboard controllers, one is the SCU and the other is the SATA controller. SATA is set to AHCI and the SCU is using ESRT2 RAID with a RAID 1 array. No RIAD key is in use / necessary. AFAIK, LSI makes expansion cards, not onboard controllers; the onboard controllers are all Intel made.

Re: S2600GZ drive numbering issue

webadmin@intel.com — Thu, 07 Jun 2012 15:18:38 GMT

JFFulcrum,

This is an interesting idea, I am trying this out as we "speak".

I have a few blockers/ concerns - just for your inquisitive mind to mull over.

USB detection is pretty poor on this board and my keyfob that works on good old smack over wont boot this board. I've reformatted the keyfob several times and now I'm down to using the internal USB port in hopes that the detection is better there.
editing the registry might work, there are some rumblings from colleagues that this wont matter since the reg keys get instantiated when WinPE loads. I've edited the WinPE registry offline before with good results so I'm skeptical this is an issue.
changing the .ini file will break driver signing so if I can't achieve a positive result via reg hack, this may be the way to go - but it will introduce a nice little wrinkle that should really annoy me later.

Welp, that's my feedback on your suggestions for now. I'll get to coaxing this board to boot with a keyfob now and hope for the best.

Jason

Re: S2600GZ drive numbering issue

webadmin@intel.com — Wed, 06 Jun 2012 22:34:19 GMT

Are you using the LSI* setting for both SATA controllers?

Which RAID Key are you using please?

Philip