Skip to main content

Fantec SRC-2080x7 connect backplane from SAS to Sata




I've read this topic: How exactly does a SAS SFF-8087 breakout cable work? + RAID/connection questions



Which basically explains that you can go from sata to SAS, but not vice versa.



However, from the store page of the Fantec SRC-2080x7 chassis I've seen a few reviews where people seem to use a breakout cable to connect the sata ports from the motherboard to the Mini SAS port (SFF-8087) on the backplane (where sata HDD's are connected).



Is there an exception to this backplane regarding this cable?



Because the SFF-8087 breakout cable doesn't seem to be working for me. Which would be consistent with the topic I linked above, though I'd be suprised if the people in the reviews haven't tested it before posting their review.




Note: The store page is in german and I've been translating everything to english by using Google Translate



This is the page of the chassis by the manufacturer, but also in german (even the english language at the top-right doesn't help).



EDIT: My backplane model is DH-6GMSAS-03A


Answer



SFF-8087 connectors are frequently used for SATA multi-port connections as well - on backplanes or sometimes even on RAID controllers. In reverse, you can use a SFF-8087-to-4xSATA fanout cable to connect standard on-board SATA ports to a (passive) SAS cage or the Fantec case you've linked to, where you plug the SATA drives (obviously, SAS drives would fit but won't work).



That said, I've seen some really low-quality fanout cables that were hard to correctly plug into the SFF-8087 receptacle - and in one case extremely hard to remove again. Make sure everything is plugged correctly, the 8087 is latched, and the drives are powered before or together with system power.


Comments

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...