Talk:Serial Attached SCSI

From Wikipedia, the free encyclopedia
  (Redirected from Talk:Serial attached SCSI)
Jump to: navigation, search
WikiProject Computing / Hardware (Rated Start-class, Mid-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.
Taskforce icon
This article is supported by Computer hardware task force (marked as Mid-importance).

Q + A[edit]

Q: It would be interesting to see even a short list of points about how SAS compares to SATA - what limitations each one has the the other doesn't?

A: As noted in the article, SATA is limited to direct-attached connection of ATA drives only and does not support SAS drives. SAS supports SATA drives (in fact, it uses the same internal narrow cables), a complex topology, a SCSI command set, and for SAS-native drives, a globally unique drive identifier. 02:46, 6 October 2006 (UTC) A: Sata does actually support port multipliers but only one level of them and only one initiator and relatively few ports. SAS allows for multiple initiators and networks of expanders. 21:46, 13 April 2008 (UTC)

Q: I'd like to see something about performance of SAS relative to SCSI or SATA or IDE. Probably best as a link out than directly here. Leodirac 23:46, 5 January 2007 (UTC)

Q: It would be nice if SAS Expanders/Fanouts were explained more thoroughly. IE What the devices look like and how they interact with the controller. More of a broad explanation and implementation rather then ultra technical. Diagram, pictures, etc.

Q: The article says that SAS is backward compatible with SATA. What does that mean exactly? A: Sata drives can be connected to a SAS system but not vice-versa. Plugwash (talk) 21:46, 13 April 2008 (UTC)

Q: I would like to see a brief History of SAS in the document -- when was it introduced to general public? Harry Pehkonen (talk) 15:21, 26 October 2011 (UTC)

SAS vs parallel SCSI[edit]

Since parallel SCSI also support hot swap. I've remove the following line

--Sltan 05:48, 23 January 2007 (UTC)

Parallel SCSI does not really support hot swapping..You an attach / unattach devices without powering down the computer, but you need to manually do a bus-rescan every single time the bus is changed. If you do not do a bus rescan, the changes will not show.

With SAS, this is automatic because it is a point to point serial link, not a bus. (talk) 21:19, 8 December 2008 (UTC)surge

-- comments by ard >: Hotswap with parallel scsi comes from the enclose controller. That one knows when a new disk is inserted, and hence a bus scan can be targeted to one id, and initiated automatically. Sata/Sas practice the same thing except that the hot-swap is speced as part of the bus, and hence is supported in the controller, and hence the *driver* knows when to scan instead of some enclosure daemon that polls the enclosure on events. Furthermore: currently it says that parallel scsi is multidrop, but it's just a bus which can host multiple initiators and targets. Initiators can be targets as well (that has been supported in some of the better operating systems). —Preceding unsigned comment added by (talk) 11:34, 27 August 2010 (UTC)


There are references for this article but they do not follow Wikipedia's guideline for citing sources at WP:CITE. Ceros 04:15, 5 December 2006 (UTC)

SATA 1 and SATA 2?[edit]

In the article about SATA it can be read that SATA II shouldn't be confused with SATA/300. Which is said on (the ones who make the standard). So the comparsion between SATA and SAS maybe should be changed. Like NCQ is an "additional capability" as they say, nothing about that it should be in SATA/300. Aqualize 22:55, 5 February 2007 (UTC)


A Hershey's kiss for size comparison?

but they "are one of the most popular candies in the world". Yep, never heard of those before :)

Any chance someone could make a new photo and include a ruler in the picture to show the size/scale? One with metric and imperial would be nice :) It would be a little more useful than using a chocolate as the reference object. —Preceding unsigned comment added by (talk) 05:18, 20 November 2007 (UTC)

is it ok?[edit]

List of SAS & SAS RAID controllers - in fact it is a commercial ad with prices, "buy" button etc., not a list. Is it ok in —Preceding unsigned comment added by (talk) 12:33, 25 November 2007 (UTC)

drive identification[edit]

"SATA devices are uniquely identified by their port number connected to the Host bus adapter while SAS devices are uniquely identified by their World Wide Name (WWN)." so how are SATA drives within a SAS system identified? Plugwash (talk) 18:18, 12 April 2008 (UTC)

error in SAS layers diagram?[edit]

In the frame definition layer, I think "SPP transport layer" is a typo; it should be "SSP transport layer". At least I can't find a reasonable definition for SPP, whereas SSP is "Serial SCSI Protocol" :-). --klode (talk) 16:20, 20 May 2008 (UTC)

I would agree, this seems to be a mistake. (Qualle14 (talk) 22:57, 14 March 2012 (UTC))

Usage / deployment?[edit]

I'd like to know what the common usage for SAS drives would be (mission-critical servers, mid-range servers, low-demand servers, etc.) I'd also like to see some numbers as to how many are out there, how many will be out there, etc. Will this technology eventually dominate all server applications? ---Ransom (-- (talk) 15:56, 3 June 2008 (UTC))

Please read WP:FORUM, but the short answer is that SAS already has taken over all of the above. -- KelleyCook (talk) 16:22, 3 June 2008 (UTC)
Could you please cite a reference? It seems to me that, if anything, SATA has taken over all but very high-end servers. Quanstro (talk) 20:27, 19 December 2008 (UTC)

Is it compatible with SATA 6.0 Gbit/s?[edit]

Is SAS compatible with SATA 6.0 Gbit/s? Urvabara (talk) 14:56, 27 August 2008 (UTC)

Yes, they are all (and will be) backwards compatible. Even 6 gig devices when plugged into a 3 gig hba should work... SAS/SATA regardless. It's kind of like PCIexpress (1 & 2) where as either card will work in either slot. (talk) 21:15, 8 December 2008 (UTC) surge

Slower than Parallel SCSI?[edit]

In the first paragraph... "At present it is slightly slower than the final parallel SCSI implementation, but in 2009 it will double its present speed to 6 Gbit/s"

I don't think you's 3 Gb/sec PER LANE...most SAS HBAs have 2 ports, 4 lanes per port (8 total) -- That's 2400 MB/sec half duplex, 4800 MB/sec full duplex...

Compare that to a Parallel SCSI HBA which has two independent U320 Parallel SCSI Busses (Not full duplex)...640 MB / sec.

I don't see how anyone can say it is slower under any circumstance. (talk) 21:15, 8 December 2008 (UTC)surge

Number of devices[edit]

Within the SAS domain section it is stated that a SAS domain can have up to 16,256 devices, while under the comparison to parallel scsi it is stated that sas supports up to 16,384 devices (the latter being 2^14, and thus sounding more correct to me, though I don't know). Are these numbers correct? If so it might be clearer if a note stating this were added. Peter Law (talk) 17:45, 13 January 2009 (UTC)

port identifiers[edit]

The article compares sas, scsi and FC port identifiers. It states that the "port identifier" in FC is the WWPN. This seems slightly confusing as the word "Port-ID" is usually referring to the identifier assigned in a fabric or loop to communicate with the port. The WWPN is not used for the communication itself. I think the comparison is fair as long as the "port identifier" is removed. Instead one could say something like HW address.. — Preceding unsigned comment added by Qualle14 (talkcontribs) 22:53, 14 March 2012 (UTC)

SAS signal pins relative to connectors used in marketplace[edit]

1. i read that SAS, being differential, and having 4 signals per channel, uses eight signal lines per drive. i read on this wiki page how the sff-8086 (26 pin) connector may be used to transmit four channels. if each drive requires 8 lines, and if four drives are to be supported: 8 * 4 = 32 lines. how is it physically possible to send signals to four drives using only 26 pins? an explanation here would be welcome

2. similarly at the actual drive, the sff-8482 connector is used. the wiki article mentions how on the 'underside' or 'backside' of the connector, additional pins are to be found - without any information as to the pin counts and/or mapping of pin to SAS signal.

3. finally, i realize this page is focused to speak towards the 'standards' side of SAS. however in practice, the market place sometimes offers implementations that might not be fully standards compliant. this is of course then confusing for a consumer. 'sideband' signalling found on many SAS implementations would be one topic that should be included here, so that it is at least discussed. which SAS signal pins are to be used for 'sideband' signal? and how does this need for extra signal relate to the pinouts of the standard connectors sff-8086,8087,8088?

any explanations here would certainly help to remove some of the confusion i now have. thanks. — Preceding unsigned comment added by (talk) 18:20, 27 September 2012 (UTC)

1.+2. SAS uses one pair of contacts for each direction, so 4 electrical lines per channel. Check for details.
3. Sideband signalling is present to allow for application specific signals without having to use additional cabling (e.g. SGPIO). Sideband pins are present on internal connectors only. Zac67 (talk) 18:51, 27 September 2012 (UTC)

SAS vs. SSA[edit]

SAS is reinventing the wheel. All the perks praised in this article were available 20 years ago in IBM's Serial Storage Architecture (SSA):

  • point-to-point links
  • loop topology
  • dual-ported drives
  • simultaneous multi-link transfers
  • multiple initiators (up to 2 in RAID and up to 8 in JBOD configurations)
  • "target mode SSA" communication between initiators

It even had optical extenders which allowed to extend the SSA loop between datacentres at distances up to 10 km.

The only difference being the electronic circuitry at the time was capable of 20 MB/s per link, upgraded in late 90s to 40 MB/s per link. 15 years later the only improvement is frequency increase mere 15-fold. SSA adapters allowed port 1 on adapter A to participate in a loop with port 2 on adapter B with the remaining two ports not sharing a loop. SAS adapters I've seen so far demand port 1 to be joined with port 1 which makes the implementation more error prone.

It seems the WP article on SSA is written by a newbie who knows nothing about it. — Preceding unsigned comment added by (talk) 22:20, 4 January 2014 (UTC)

SFF-8470 connector pin count[edit]

I believe the SFF-8470 connector has 34 pins, not 32. I have already changed the article.

Unfortunately, I couldn't find this clearly mentioned in the SFF-8470 standard. It references figure 9, but the references to this figure in the PDF are not links or they do not work. And the figure 9 seems to describe a particular connector variant, not the pin numbering as referenced. But the values (m and n) in the tables correspond as do other verification methods I tried (none of them significantly authoritative though).

The pin counts should be as follows:

  • 16 signal pins,
  • 18 ground pins.

The ground pins are actually 9 dual-sided pairs and could therefore be counted as two per pair, giving 18 pins altogether. Together with the signal pins we get the total count of 34 pins. This is also close to the original number of 32, so the original author might have used the same counting method.

Anyone knowing better is welcome to correct me (and, if possible, leave an explanation comment here). :-) — Preceding unsigned comment added by JITR (talkcontribs) 09:01, 8 October 2015 (UTC)

Requested move 09 April 2016[edit]

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: Moved. I'm not really WP:involved here, as my only action was to query it when it was at WP:RMT, in case someone thought it was contorversial. Hopefully therefore it's fine for me to close this. There is unanimous support to move, so it was indeed uncontroversial.  — Amakuru (talk) 17:18, 19 April 2016 (UTC)

Serial attached SCSISerial Attached SCSI – It's a proper name, and it's used as such throughout the article. – — Dsimic (talk | contribs) 14:27, 9 April 2016 (UTC)

@Dsimic, Amakuru, and Dicklyon: This is a contested technical request (permalink). Anthony Appleyard (talk) 22:42, 9 April 2016 (UTC)
  • Contesting - I think this should go through full RM. I don't have a definite opinion now, but capitalisation/title issues are rarely straightforward, and there are definitely sources that use the current capitalisation.  — Amakuru (talk) 18:13, 9 April 2016 (UTC)
  • Since it's essentially always capitalized in sources, it's hard to imagine this one drawing any opposition. Just because caps are involved doesn't mean it's potentially controversial. Dicklyon (talk) 21:26, 9 April 2016 (UTC)
    • Indeed. If some admins are getting worn out sorting controversial from non-controversial upper/lower case conversions, maybe they need to take a break from it, and let others pick that slack up. We seem to have enough admins around for this sort of thing. What we don't want is the entire editorial community bogged down in pointless full-RM discussions that should have been speedied. This would consume far more editorial productivity than a few turned-out-to-be controversial case changes that slip through, especially since WP:RM#Requests to revert undiscussed moves can be used to do those without discussion, and if someone wants to insist on the move, it's up to them to list it for discussion. Treating them as "auto-contested" opens a discussion whether one is needed or not.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:32, 17 April 2016 (UTC)
  • The second and sixth sources in the article itself use lower case for "access", but like I say, I don't really oppose this, I was just querying it. Move it back to uncontroversial if you like, Dicklyon I have no objection to that.  — Amakuru (talk) 22:21, 9 April 2016 (UTC)
  • Supporting the move: it's a proper name, T10 drafts – probably the most RS – also capitalize the A. --Zac67 (talk) 17:18, 10 April 2016 (UTC)
  • Supporting the renaming as the one who requested it. — Dsimic (talk | contribs) 21:21, 11 April 2016 (UTC)
    • Please don't do that. Your nomination is your support. Double-!voting like this gives the impression that a proposal has more support than it really does.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:27, 17 April 2016 (UTC)
  • Support, since it's the proper name of a specification. If it were not, it would be serial-attached SCSI. We should actually check the sources. If the reliable ones sometimes properly hyphenate the compound modifier, WP should as well, since we always default to proper English, and only make exception for ungrammatical constructions when the incorrect usage is uniform in virtually all RS. If it's variable, we use the proper variant, not the improper one.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:27, 17 April 2016 (UTC)

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.