hard-drive – Can You Run SAS Drive from SAS Backplane to SATA on Motherboard?

Yes. It's definitely not ideal, but yes, you can.

Scenarios...

• Shared backplane behind a SAS expander. Not good.
• Shared backplane with dedicated 4-lane SAS connectors (e.g. a Dell or HP server's internal drive bays with 1:1 port controller port to disk bay mapping). Okay.

I tell people to just use nearline SAS instead of SATA these days, just to avoid any issues. Expanders tend to cause more problems in these mixed scenarios.

Technical explanation in detail.

It's when you add SAS expanders (and SATA Tunneling Protocol) to the mix that you start encountering weird errors with misbehaving SATA disks. SATA simply isn't designed with a switching fabric in mind, and it looks like firmwares still aren't robust enough to deal with command tunneling reliably in the presence of errors.

SATA/SAS are not like hubs, rather they work much like a network switch. This means that a single SATA/SAS port provides the entire advertised bandwidth, independently from the other ports.

In other words, a chipset providing 4x SATA 3.0 ports (6 Gb/s each) has a "SATA backplane" switching capability of 4x6 Gb/s = 24 Gb/s. For a 4x SAS 3.0 ports (12 Gb/s each), the "SAS backplane" switching capability is 4x12 Gb/s = 48 Gb/s

Does this means that all the available raw bandwidth really is usable? Well, no. Problem is that these SATA/SAS ports must be connected by some other upstream bus, which will likely affect (reduce) the real available bandwidth.

Take, for example, the previous-gen Z97 Intel chipset: it has 6x SATA 3.0 ports, for a total of 36 Gb/s or 4.5 GB/s. This is a very respectable I/O transfer rate for a consumer product. However, the disk controller (integrated into the chipset) connects to the CPU using a much narrow (albeit full-duplex) 2 GB/s link. In other words, you will never reach the theoretical 4.5 GB/s peak of the SATA links.

Another complication is represented by SATA port multiplier or SAS port expander. What are these things? Well, they are what they claim to be: port multipliers/expanders to connect more drive to a single SATA/SAS port. You can think them as "mini-controller" which use a single SATA/SAS port as upstream bus and provide multiple ports to downstream devices.

This means that disks connected after a SATA port multiplier / SAS expander are limited by the bandwidth provided by the single upstream port - 1x SATA 6 Gb/s or SAS 3.0 12 Gb/s port. You can combine multiple upstream port to provide added performance, but the basic problem remains: you share multiple downstream port connected by few upstream links.

Let use your 4x SAS 3.0 controller as an example: using SAS expander you can link multiple drives to every single upstream SAS port - say 16x downstream SAS 3.0 links for each 1x SAS upstream link, for a grand total of 64x available SAS 3.0 ports / devices. Even if you populate all 64 SAS ports with lightning fast SSD, your total transfer rate will be limited by the 4x SAS links used to connect the downstream expander. So, from a theoretical 64x12 Gb/s (768 Gb/s or 96 GB/s), your real peak transfer rate will be 4x12 Gb/s (48 Gb/s or 6 GB/s).

Things are not so bad, though. After all, it is very difficult to hit all the disks at the same time. This is the reason behind multiplier/expander existance: to privilege disk capacity (and easy trace routing) vs raw performance.