Intel JBOD2224S2DP - Troubleshooting Redundant Path Fail

We have an Intel JBOD2224S2DP that has seemingly dropped one of its expanders as we are seeing a MPIO path error on both nodes in a Hyper-V/Storage Spaces cluster (2x nodes + 2x JBODs).

First step is to get the SAS IDs for the expanders by pulling the cover:

With IDs in-hand the next step is to figure out which one has failed.

We do this by downloading the latest firmware for the JBOD and copying the contents to a \TMP folder on the server or server node.

Open an elevated CMD on the server/node and:

C:
CD \TMP\Windows [ENTER]
cmdtool2_64 -adpsetprop ExposeEnclDevicesEnbl 1 -aall [ENTER]
xflash -I get avail [ENTER]

And, voila! We have our culprit:

The problematic expander is the one on the right.

The final step to run on the server/node:
cmdtool2_64 -adpsetprop ExposeEnclDevicesEnbl 0 -aall [ENTER]

Now, off to call Intel to see about a warranty replacement or to find one out there somewhere. ;)

UPDATE 2017-08-16: As it turns out, we replaced the seemingly problematic expander and still had the error. After swapping the RS25GB008 HBA pair between nodes the problem followed the HBAs. After a bit more testing we found that one of the RS25GB008 HBAs had a bad port.

Since Intel no longer supports them and distribution didn't have any in the channel we had to go out and find some via the regular channels. They just arrived the other day and we now have MPIO on both systems without an error.

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service
Twitter: @MPECSInc

2 Node 1 JBOD Hyper-V Cluster Connectivity Guide

Okay, so just how do we wire up that cluster?

We connect two SAS cables from each HBA on each node to one expander on the JBOD.

We then connect two SAS cables from each HBA on each node to one expander on the JBOD. Note the left/right split between the cable sets to keep things simple and clean.

This gives us two redundant paths between the Hyper-V hosts if setting up an asymmetric cluster (2 nodes 1 JBOD) or redundant paths between SOFS nodes and the JBOD.

The following shows the setup for an Intel Server System R1208JP4OC 1U single socket server:

We always try to keep the cables plugged in identically on each node. So, in this case the bottom HBA is plugged into Expander 0 and the top HBA is plugged into Expander 1.

In a Scale-Out File Server cluster where we have three nodes and three JBODs we would be utilizing an LSI SAS HBA with 4 external ports (-16e). In that case we would cable up each node just as we did here between each JBOD giving us the left/right split.

Given the Intel JBOD2224S2DP’s three external ports per expander we would be limited to the three node setup unless we utilized our LSI SAS6160 SAS Switches to scale beyond three nodes and JBODs.

Philip Elder
Microsoft Cluster MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen ASP Project
Find out more at
Third Tier: Enterprise Solutions for Small Business

MANDATORY: Intel JBOD2224S2DP Firmware Update for Same Enclosure ID Storage Spaces Problem

Intel has released a new firmware for the Intel JBOD2224S2DP storage enclosure that deals with the enclosure delivering the same Enclosure ID to Windows Server 2012 R2 Storage Spaces.

•   Intel Download Center: Intel Storage System JBOD2000 Family Expander Firmware

Why is this firmware mandatory?

Because up until now when two or more Intel JBOD2224S2DP units were connected to Scale-Out File Server nodes and one ran the Get-StorageEnclosure PowerShell command one would get the same ID back for every one.

The firmware problem killed Storage Spaces enclosure resilience. What is that you ask?

In Storage Spaces, with a Two-Way or Three-Way mirror one can have three enclosures set up to allow one to drop out completely and things keep going.

If one has configured five enclosures with a Three-Way Mirror then the Storage Spaces setup can tolerate two enclosures dropping out.

• Storage Spaces FAQ: Enclosure Awareness Support – Tolerating an Entire Enclosure Failing

If the Intel JBOD unit is already in a production setting with plans to add more enclosures at a later date then it is important to note that this firmware update would be required prior to adding the new units.

For new setups, this firmware update should be a part of the preparation steps for the JBOD prior to implementation or baseline testing.

Philip Elder
Microsoft Cluster MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Chef de partie in the SMBKitchen ASP Project
Find out more at
Third Tier: Enterprise Solutions for Small Business