jgreco
Resident Grinch
- Joined
- May 29, 2011
- Messages
- 18,680
I agree with what you're saying about breakout cables. The issue is that in the first post in this thread, it states they can be used to connect directly to drives.
I don't see such a statement. However, it's definitely possible to connect SAS drives to a single-SAS breakout cable.
Sata Adapter 22 Pin 7+15 Pin Male To Female Serial ATA Power Sync Data convertor | eBay
Find great deals for Sata Adapter 22 Pin 7+15 Pin Male To Female Serial ATA Power Sync Data convertor. Shop with confidence on eBay!
www.ebay.com

SAS 22 Pin to 7 Pin + 15 Pin SATA Hard Disk Drive Raid Adapter with 15 Pin Power Port - Newegg.com
Buy SAS 22 Pin to 7 Pin + 15 Pin SATA Hard Disk Drive Raid Adapter with 15 Pin Power Port with fast shipping and top-rated customer service. Once you know, you Newegg!
So the eBay one is $2.37 per drive.
The Primer also says
SAS and SATA use different connectors on the drive. The SATA drive connector has a gap between the signal and power sections, which allows separate power and data cables to be easily connected.
So there's clearly a warning about this if you read the correct section.
What is pictured is the latter (SATA connectors) but the text calls it the former (SAS).
"SATA" and "SAS" refer to signalling, not connectors. It's the signalling that's important. To flip this around, there are plenty of examples to be had of SATA (only) signalling being run on top of connectors typically used for SAS, and this imposes issues such as length limitations and the inability to attach an SAS expander.
For anyone who has worked with either even in passing, it's no big deal. But in a topic that is calling itself a primer for people not familiar with SAS, it can be a problem. A new person, following what's currently posted, buying those cables and trying to connect them to SAS drives- which is what the text tells them they're for- is going to break hardware (if they force it) and/or have a non-functional setup (from a half-plugged-in connector).
Why is it a point of contention? I don't know why it should be. It seemed like a minor mistake, either in image choice or in the descriptions.
I guess I expect that people reading a primer actually read the primer in its entirety, and not just pick and choose a sentence here and an image there. Because the SAS/SATA interoperability thing is such a potential for trainwreck, and there are so many potential gotchas and caveats, I don't really think the primer is intended to cover stuff like the esoteric errata in SATP-via-expander differences between SAS1 and SAS2, and rather is intended to help the average FreeNAS user who has no idea what SAS is to get up to speed. I do not want to get into a situation where I am having to spell out every caveat and proviso at every possible point of misunderstanding; that would be terribly awful for a newbie to read and even worse to write.
So if I really wanted to be thorough, yes, I could go open up the bins in the shop here and I could write a SAS/SATA primer that includes all sorts of obscure and arcane bits of trivia that either zero or maybe one reader on the forum would ever need to know. I don't really care to do that and it would create a total TL : DR situation. It's a primer. It isn't everything you might ever need to know, and unfortunately due to design choices made by the designers of SAS and SATA to make these somewhat-interoperable on both the signalling and connector levels, there's quite a bit of arcana that you might possibly need to know that I do NOT cover.
See, I just don't really see a good fix here. I'm not willing to call them "SATA connectors" because they aren't SATA connectors (evidenced by SAS running over them). SATA has other similar boggles such as eSATA (which is yet another interesting divergence) and has been shown to opportunistically go over a variety of connectors. "SAS" is more-correct because a SAS lane can drive a SATA target, but a SATA channel cannot drive a SAS target. Because it's a SAS Primer, the possibility of a SATA-only controller and target setup is out of scope, so anytime something is downgraded to "SATA" when being discussed, it should be because it is "SATA-only." So both technically and contextually it is more appropriate to refer to the lane as a SAS lane, and because there are single lane SAS connectors on devices such as backplanes to accept them, it feels like it would be wrong to call them "SATA" as this would be an additional point for confusion.
It seemed like a minor mistake, either in image choice or in the descriptions.
I deem this to be a minor mistake in user interpretation, not in image choice or description. As an apparent victim of the circumstances here, can you tell me if it would have been clearer had there been a description of a 22-to-7-plus-15 adapter? When I wrote the text
SAS and SATA use different connectors on the drive. The SATA drive connector has a gap between the signal and power sections, which allows separate power and data cables to be easily connected.
I specifically picked the phrase "separate power and data cables to be easily" to indicate this type of issue. I concede that people sometimes miss the things I try hard to imply, but I also feel like what I wrote after it should be sufficient explanation, and that a reader just totally missed it, so further explanation is not meaningful. If you wish to argue that I should explicitly mention an adapter is necessary for dual-ported SAS HDD's to be able to accept a single-lane SAS cable, perhaps there's a point there, but it's implied by what I said. You could probably sell me on this argument though.
My goal with the Primer isn't to fill in every possible detail and bit of knowledge. It's to make sure that newcomers, hobbyists, and non-IT-pros who have no idea what all this "SAS" stuff is can get the clear idea that this is very usable technology.
Last edited: