Can PCI Express 2.0 handle 12GB SAS?

Discussion in 'RAID Controllers and Host Bus Adapters' started by Churchill, Apr 30, 2017.

  1. Churchill

    Churchill Admiral

    Joined:
    Jan 6, 2016
    Messages:
    756
    Likes Received:
    169
    I have a sever with PCI Express 2.0 x8. The backplane in my SAS expanders support 12GBps SAS. Is it possible to get a M1215 (or comparable) SAS card and get 12GBps speeds with PCI express 2.0?
     
    #1
  2. Jeggs101

    Jeggs101 Well-Known Member

    Joined:
    Dec 29, 2010
    Messages:
    1,466
    Likes Received:
    216
    For a drive or two or many drives?
     
    #2
  3. Churchill

    Churchill Admiral

    Joined:
    Jan 6, 2016
    Messages:
    756
    Likes Received:
    169
    For 26 drives. 24 on one channel to the SAS expander and 2 to a SAS->SATA breakout.

    Handle is 'bad' word. What kind of speed am I looking at? Will I even get close to topping the 6GB/s speed ?
     
    #3
  4. i386

    i386 Well-Known Member

    Joined:
    Mar 18, 2016
    Messages:
    1,664
    Likes Received:
    400
    26 * 150mb/s = ~3900mb/s
    pcie 2.0 x8 = 4000mb/s
     
    #4
    Churchill likes this.
  5. Churchill

    Churchill Admiral

    Joined:
    Jan 6, 2016
    Messages:
    756
    Likes Received:
    169
    Curse the MATHS!

    Thanks for the answer @i386 looks like I don't have to spend the money after all.
     
    #5
Similar Threads: Express handle
Forum Title Date
RAID Controllers and Host Bus Adapters How do you use these? LSI SAS9200-16E 16-Port 6Gb/s PCI Express SATA+SAS HBA Controller H3-25140-02 Apr 3, 2019
RAID Controllers and Host Bus Adapters Any experience with ATTO ExpressSAS H608? Oct 30, 2015
RAID Controllers and Host Bus Adapters SAS RAID card/HBA with Solaris Express Support Sep 19, 2013
RAID Controllers and Host Bus Adapters Maximum # harddisk a motherboard can handle with 2 SAS expanders Oct 7, 2016
RAID Controllers and Host Bus Adapters Issues with LSI2008 on OmniOS? (mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31110d00) Oct 30, 2014

Share This Page