LSI HBA Questions

Status
Not open for further replies.

NASbox

Guru
Joined
May 8, 2012
Messages
644
I've read though the FreeNAS Community Hardware Guide 2016-10 Edition (Revision 1e) and if I understand what
I've read, to support SATA3 (6G) Hard drives I need an LSI SAS2008 based HBA, and whatever I buy must be
crossflashed.

In the guide it mentions the LSI SAS 9211, SAS 9240, SAS 9207 series, the IBM/Lenovo M1015/M1115 and the Dell H200 and H310.

Question #1 - Are these all equivalent, or should I select one over another?

A quick list of the different variants I found on EBay ranging from about $50US - $100US:

Dell PERC H200 SAS 2008 9210-8i 047MCV
Fujitsu 9211-8i D2607-A11 LSI SAS2008 - $50 US
Intel SAS 2008-8i(9211-8i)
IBM ServeRaid M1015 46M0861 LSI SAS9220-8i - $90US+-
LSI 9240-8i 8-port SAS SATA LSI00200 Server RAID Controller Card
LSI 9240-8i IBM M1015 8-port SAS SATA LSI00200

If paying $100 rather that $50 gets me worth while better specs/performance, I'm OK with paying the extra money.

Obviously EBay and used carries a risk, but other than looking for an established seller with a good reputation
is there anything I should be looking for?

Question #2 - Firmware, I've seen references that say I should be flashing to V16 (a year or so old), and that newer versions will cause problems/don't match the FreeNAS drivers.
I've also seen references that talk about v20 and that the newer releases of the v20 are the way to go. Can someone offer some guidance?

Given that someone may see this who has just bought/flashed/installed one of these cards, it would be much appreciated if they could give me a reference for where they bought it.

ALSO: If anyone has seen decent connectors on EBay at a good price, I'd love to know. From what I've read there is a lot of junk, and likely the only way to know is to buy it.

Thanks in advance for any assistance.
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,367
They are all mostly equivalent. The IBM cards require an extra step to flash the first time (need to erase their IBMness). The dell cards require an extra step again.

I have an M1015 and M1115. Flashing with @Spearfoot's flash set was trivial. As far as I can tell the cards are identical.

Don't order LSI cards that come from China, unless you want a counterfeit.

Yes, run the latest firmware. Currently 20.0.7.0 iirc

Follow the most recent instructions on this forum. If in doubt, ask. There are instructions on the net that will destroy your card.

Regarding connectors on eBay, I bought some... they just looked like SAS cables, but in reality we're just a collection of bits designed to look like a SAS cable, not actually function as one.
 

Sakuru

Guru
Joined
Nov 20, 2015
Messages
527

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478

NASbox

Guru
Joined
May 8, 2012
Messages
644
Thanks everyone for the input - it's all much appreciated.

I really appreciate the Monoprice link - I bought all the cables with shipping for less than half the price of what I would have to spend locally.

Did some looking around for a card and found this supplier... seems to be selling lots of them and has a decent reputation.

http://www.ebay.com/itm/New-IT-Mode...0?hash=item43e72c3fd2:g:hboAAOSwOgdYxx1I#rwid
http://www.ebay.com/itm/New-IT-Mode...0?hash=item43e72c3fd2:g:hboAAOSwOgdYxx1I#rwid
Obviously EBay has it's risks, but I was wondering if this looks good or am I missing something?

Again, any input is much appreciated.
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478
Thanks everyone for the input - it's all much appreciated.

I really appreciate the Monoprice link - I bought all the cables with shipping for less than half the price of what I would have to spend locally.

Did some looking around for a card and found this supplier... seems to be selling lots of them and has a decent reputation.

http://www.ebay.com/itm/New-IT-Mode...0?hash=item43e72c3fd2:g:hboAAOSwOgdYxx1I#rwid
Obviously EBay has it's risks, but I was wondering if this looks good or am I missing something?

Again, any input is much appreciated.
That eBay seller has 100% positive feedback on 10,251 reviews, so I would feel confident in purchasing from them/him/her. The board itself looks like a good deal, too - in fact, I coincidentally happen to have that very listing in my 'watch' list.
 

NASbox

Guru
Joined
May 8, 2012
Messages
644
Thanks @Spearfoot just wanted to make sure that I wasn't overlooking anything obvious and that I had selected a suitable card.

I'm going to be moving my FreeNAS box from a compact case to a full tower, adding a hot swap cartridge bay for backups, and maybe a couple of more pools.

I'm still on FreeNAS-8.3.1-RELEASE-x64 (r13452) so I guess I have to upgrade before installing?

As you can see from my current release I value stability over latest and greatest - and also to what release?
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478
Thanks @Spearfoot just wanted to make sure that I wasn't overlooking anything obvious and that I had selected a suitable card.

I'm going to be moving my FreeNAS box from a compact case to a full tower, adding a hot swap cartridge bay for backups, and maybe a couple of more pools.

I'm still on FreeNAS-8.3.1-RELEASE-x64 (r13452) so I guess I have to upgrade before installing?

As you can see from my current release I value stability over latest and greatest - and also to what release?
Yikes! That's a really old version! I don't have any experience with it, so I can't offer any advice as to whether or not it will work with your new HBA. My guess is that it should work -- LSI cards are well-supported by FreeBSD, and have been for a long time -- so you can stay on that older release if you so desire. You may actually have to flash an older version of the LSI firmware to match up with whatever firmware FreeNAS 8.x expects...

FreeNAS 11.0 has just been released... but if you value stability, you might consider using 9.10.2-U5, which is what I'm currently running and which has worked well for me.
 

NASbox

Guru
Joined
May 8, 2012
Messages
644
FreeNAS 11.0 has just been released... but if you value stability, you might consider using 9.10.2-U5, which is what I'm currently running and which has worked well for me.

Thanks @Spearfoot ... I stayed with 8.3 because I was using UFS USB for backup... and it was working so I didn't have a great need to touch it. But my backups have outgrown USB, so I've decided to fork out some money for hot swap disk drives so I can mirror pools to disk and then take them off the system.

I've now got to project plan the upgrade, but that should be a different thread. Once I get the card and get things going I'll report back - hopefully it will save somebody else some time.
 

NASbox

Guru
Joined
May 8, 2012
Messages
644
As promised I'm reporting back on the HBA mentioned above:

http://www.ebay.com/itm/New-IT-Mode...-PCI-E-Card-Bulk-pack-US-Seller-/291641245650

I'm hoping that the info will be useful to others, and also to get some guidance on how to move forward with this device.

Since it will be a few weeks before I will have the time to rebuild my FreeNAS, and I can't afford to have extended downtime, I decided to do initial testing of the device on my Linux Mint box. I installed the card and have been successfully running badblocks on a new drive for approximately a week - so the card clearly works. I'll include the information about the card that I have obtained from the linux system.

Questions:
  1. From the information provided does it look as if this card is ready to use as is, or will I need to flash new firmware?
  2. Is there a way I can test this card for compatibility with FreeNAS (likely with 9.10.2-U5) with some sort of bootable USB? So that I don't have to dismantle my current system, I'd like to be able to just boot the current test system (if possible without disconnecting the linux disks that are connected to the motherboard, but if necessary I can pull the cables) and just run a few quick tests to know if things will work?
  3. Any advice/comments about this piece of hardware? I've built several PCs over the last 20 years, but I'm a complete noob with this type of commercial grade hardware and have very limited BSD experience, so if someone can point me in the right direction it would be a big help and would be appreciated!

BIOS BOOT SCREEN
index.php


SETUP UTILITY AVAILABLE DURING BOOT
index.php


The information dumped from the card follows:
Code:
lspci
03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

Code:
sudo modinfo mpt3sas
filename:  /lib/modules/4.4.0-81-generic/kernel/drivers/scsi/mpt3sas/mpt3sas.ko
alias:  mpt2sas
version:  12.100.00.00
license:  GPL
description:  LSI MPT Fusion SAS 3.0 Device Driver
author:  Avago Technologies <MPT-FusionLinux.pdl@avagotech.com>
srcversion:  613283D7C839632EB9649EA
alias:  pci:v00001000d000000C3sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C2sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C1sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C0sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C8sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C7sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C6sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C5sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C4sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C9sv*sd*bc*sc*i*
alias:  pci:v00001000d00000095sv*sd*bc*sc*i*
alias:  pci:v00001000d00000094sv*sd*bc*sc*i*
alias:  pci:v00001000d00000091sv*sd*bc*sc*i*
alias:  pci:v00001000d00000090sv*sd*bc*sc*i*
alias:  pci:v00001000d00000097sv*sd*bc*sc*i*
alias:  pci:v00001000d00000096sv*sd*bc*sc*i*
alias:  pci:v00001000d0000007Esv*sd*bc*sc*i*
alias:  pci:v00001000d0000006Esv*sd*bc*sc*i*
alias:  pci:v00001000d00000087sv*sd*bc*sc*i*
alias:  pci:v00001000d00000086sv*sd*bc*sc*i*
alias:  pci:v00001000d00000085sv*sd*bc*sc*i*
alias:  pci:v00001000d00000084sv*sd*bc*sc*i*
alias:  pci:v00001000d00000083sv*sd*bc*sc*i*
alias:  pci:v00001000d00000082sv*sd*bc*sc*i*
alias:  pci:v00001000d00000081sv*sd*bc*sc*i*
alias:  pci:v00001000d00000080sv*sd*bc*sc*i*
alias:  pci:v00001000d00000065sv*sd*bc*sc*i*
alias:  pci:v00001000d00000064sv*sd*bc*sc*i*
alias:  pci:v00001000d00000077sv*sd*bc*sc*i*
alias:  pci:v00001000d00000076sv*sd*bc*sc*i*
alias:  pci:v00001000d00000074sv*sd*bc*sc*i*
alias:  pci:v00001000d00000072sv*sd*bc*sc*i*
alias:  pci:v00001000d00000070sv*sd*bc*sc*i*
depends:  scsi_transport_sas,raid_class
intree:  Y
vermagic:  4.4.0-81-generic SMP mod_unload modversions
parm:  logging_level: bits for enabling additional logging info (default=0)
parm:  max_sectors:max sectors, range 64 to 32767  default=32767 (ushort)
parm:  missing_delay: device missing delay , io missing delay (array of int)
parm:  max_lun: max lun, default=16895  (ullong)
parm:  hbas_to_enumerate: 0 - enumerates both SAS 2.0 & SAS 3.0 generation HBAs
  1 - enumerates only SAS 2.0 generation HBAs
  2 - enumerates only SAS 3.0 generation HBAs (default=0) (ushort)
parm:  diag_buffer_enable: post diag buffers (TRACE=1/SNAPSHOT=2/EXTENDED=4/default=0) (int)
parm:  disable_discovery: disable discovery  (int)
parm:  prot_mask: host protection capabilities mask, def=7  (int)
parm:  max_queue_depth: max controller queue depth  (int)
parm:  max_sgl_entries: max sg entries  (int)
parm:  msix_disable: disable msix routed interrupts (default=0) (int)
parm:  smp_affinity_enable:SMP affinity feature enable/disbale Default: enable(1) (int)
parm:  max_msix_vectors: max msix vectors (int)
parm:  mpt3sas_fwfault_debug: enable detection of firmware fault and halt firmware - (default=0)




Code:
udo lspci -s 03:00 -vv
03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
  Subsystem: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
  Latency: 0
  Interrupt: pin A routed to IRQ 16
  Region 0: I/O ports at e000
  Region 1: Memory at 908c0000 (64-bit, non-prefetchable) [size=16K]
  Region 3: Memory at 90480000 (64-bit, non-prefetchable) [size=256K]
  Expansion ROM at 90400000 [disabled] [size=512K]
  Capabilities: [50] Power Management version 3
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
  Capabilities: [68] Express (v2) Endpoint, MSI 00
  DevCap: MaxPayload 4096 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
  ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
  DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
  RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
  MaxPayload 256 bytes, MaxReadReq 512 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
  LnkCap: Port #0, Speed 5GT/s, Width x8, ASPM L0s, Exit Latency L0s <64ns, L1 <1us
  ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 5GT/s, Width x2, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
  DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF Not Supported
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
  LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
  Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
  Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
  EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
  Capabilities: [d0] Vital Product Data
  Unknown small resource type 00, will not decode more.
  Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
  Address: 0000000000000000  Data: 0000
  Capabilities: [c0] MSI-X: Enable+ Count=15 Masked-
  Vector table: BAR=1 offset=00002000
  PBA: BAR=1 offset=00003800
  Capabilities: [100 v1] Advanced Error Reporting
  UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
  CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
  Capabilities: [138 v1] Power Budgeting <?>
  Capabilities: [150 v1] Single Root I/O Virtualization (SR-IOV)
  IOVCap: Migration-, Interrupt Message Number: 000
  IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy+
  IOVSta: Migration-
  Initial VFs: 16, Total VFs: 16, Number of VFs: 0, Function Dependency Link: 00
  VF offset: 1, stride: 1, Device ID: 0072
  Supported Page Size: 00000553, System Page Size: 00000001
  Region 0: Memory at 00000000908c4000 (64-bit, non-prefetchable)
  Region 2: Memory at 00000000904c0000 (64-bit, non-prefetchable)
  VF Migration: offset: 00000000, BIR: 0
  Capabilities: [190 v1] Alternative Routing-ID Interpretation (ARI)
  ARICap: MFVC- ACS-, Next Function: 0
  ARICtl: MFVC- ACS-, Function Group: 0
  Kernel driver in use: mpt3sas
  Kernel modules: mpt3sas

------------------------------------------------------------------------------------------

sudo modinfo mpt3sas
filename:  /lib/modules/4.4.0-81-generic/kernel/drivers/scsi/mpt3sas/mpt3sas.ko
alias:  mpt2sas
version:  12.100.00.00
license:  GPL
description:  LSI MPT Fusion SAS 3.0 Device Driver
author:  Avago Technologies <MPT-FusionLinux.pdl@avagotech.com>
srcversion:  613283D7C839632EB9649EA
alias:  pci:v00001000d000000C3sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C2sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C1sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C0sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C8sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C7sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C6sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C5sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C4sv*sd*bc*sc*i*
alias:  pci:v00001000d000000C9sv*sd*bc*sc*i*
alias:  pci:v00001000d00000095sv*sd*bc*sc*i*
alias:  pci:v00001000d00000094sv*sd*bc*sc*i*
alias:  pci:v00001000d00000091sv*sd*bc*sc*i*
alias:  pci:v00001000d00000090sv*sd*bc*sc*i*
alias:  pci:v00001000d00000097sv*sd*bc*sc*i*
alias:  pci:v00001000d00000096sv*sd*bc*sc*i*
alias:  pci:v00001000d0000007Esv*sd*bc*sc*i*
alias:  pci:v00001000d0000006Esv*sd*bc*sc*i*
alias:  pci:v00001000d00000087sv*sd*bc*sc*i*
alias:  pci:v00001000d00000086sv*sd*bc*sc*i*
alias:  pci:v00001000d00000085sv*sd*bc*sc*i*
alias:  pci:v00001000d00000084sv*sd*bc*sc*i*
alias:  pci:v00001000d00000083sv*sd*bc*sc*i*
alias:  pci:v00001000d00000082sv*sd*bc*sc*i*
alias:  pci:v00001000d00000081sv*sd*bc*sc*i*
alias:  pci:v00001000d00000080sv*sd*bc*sc*i*
alias:  pci:v00001000d00000065sv*sd*bc*sc*i*
alias:  pci:v00001000d00000064sv*sd*bc*sc*i*
alias:  pci:v00001000d00000077sv*sd*bc*sc*i*
alias:  pci:v00001000d00000076sv*sd*bc*sc*i*
alias:  pci:v00001000d00000074sv*sd*bc*sc*i*
alias:  pci:v00001000d00000072sv*sd*bc*sc*i*
alias:  pci:v00001000d00000070sv*sd*bc*sc*i*
depends:  scsi_transport_sas,raid_class
intree:  Y
vermagic:  4.4.0-81-generic SMP mod_unload modversions
parm:  logging_level: bits for enabling additional logging info (default=0)
parm:  max_sectors:max sectors, range 64 to 32767  default=32767 (ushort)
parm:  missing_delay: device missing delay , io missing delay (array of int)
parm:  max_lun: max lun, default=16895  (ullong)
parm:  hbas_to_enumerate: 0 - enumerates both SAS 2.0 & SAS 3.0 generation HBAs
  1 - enumerates only SAS 2.0 generation HBAs
  2 - enumerates only SAS 3.0 generation HBAs (default=0) (ushort)
parm:  diag_buffer_enable: post diag buffers (TRACE=1/SNAPSHOT=2/EXTENDED=4/default=0) (int)
parm:  disable_discovery: disable discovery  (int)
parm:  prot_mask: host protection capabilities mask, def=7  (int)
parm:  max_queue_depth: max controller queue depth  (int)
parm:  max_sgl_entries: max sg entries  (int)
parm:  msix_disable: disable msix routed interrupts (default=0) (int)
parm:  smp_affinity_enable:SMP affinity feature enable/disbale Default: enable(1) (int)
parm:  max_msix_vectors: max msix vectors (int)
parm:  mpt3sas_fwfault_debug: enable detection of firmware fault and halt firmware - (default=0)
 

Attachments

  • LSIHBA_1.jpg
    LSIHBA_1.jpg
    131.7 KB · Views: 3,292
  • LSIHBA_2.jpg
    LSIHBA_2.jpg
    183.4 KB · Views: 3,085
Last edited:

Stux

MVP
Joined
Jun 2, 2016
Messages
4,367
Its running 20.0.7 IT firmware. Seems right.
 

NASbox

Guru
Joined
May 8, 2012
Messages
644
Thanks @Stux.

The vendor said he had a P20, and that's what I asked for... nice to know that's what I got and that I can hopefully skip the flashing step(s).

I never heard of Avago Technologies, is that the normal BIOS for this card? Or is this some sort of clone?
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
I never heard of Avago Technologies, is that the normal BIOS for this card? Or is this some sort of clone?
The three companies are now one. (LSI, Avago, Broadcom)
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176

NASbox

Guru
Joined
May 8, 2012
Messages
644
Thanks for clearing that one up... so now the last part of the question... any quick easy way to test this card with a bootable FreeBSD CD?

If so exactly which version and how do I know I have the right drivers?
I'd like to be able to do some quick comparability testing before I dismantle everything.
I'm transplanting my system to a new case, doing a version upgrade, and adding new hardware, so I'd like to test the pieces individually if I can.

Any help is much appreciated... and much thanks to the awesome community here (and of course the devs who work so hard on FreeNAS)!
 

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
If so exactly which version and how do I know I have the right drivers?
I would just test it with FreeNAS 11.0 (latest version). Keep your data safe by taking
out the drives of your current pool, or disconnect the cables to them for now.
FreeNAS is fully functional without a pool mounted for testing the HBA, you
just need some old hard drive you have laying about to test connectivity/cables.

If I read the above posts correctly your new HBA has come with the proper
IT mode and the proper firmware (20.00.07.00), so you are good to go with
either FreeNAS 9.10.2 U5 or 11.0

In my mind, testing this way (with FreeNAS) you will familiarize yourself
with the GUI at the same time.
 

Evi Vanoost

Explorer
Joined
Aug 4, 2016
Messages
91
Obviously most cards have the same chipset will work, as said, the IBM/Dell/HP may require an extra step if used in a non-branded box. I even got an Apple-branded LSI card working with FreeNAS.

As far as the cables, I've been burned by some as well. I buy good-brand names (LSI, Adaptec) because the cheaper ones can be really crap. Some come without latches, I have one set of cables where the latches broke off, the latch had a plastic tab that was glued to the mechanism so they're perpetually locked and didn't come out of the card anymore, given it was in a 1U server between some other things, I couldn't access the mechanism. I had to unrack the server, take out the card and the cable by bending the frame and then use a tiny screw driver to move the pin backwards.
 

NASbox

Guru
Joined
May 8, 2012
Messages
644
@BigDave, thanks for suggestion... During the installation process FreeNAS write to any hard disks that are attached to the motherboard? I plan on installing the test system to a USB drive. The system I am using is a linux machine with disks formatted EXT4. As long as I'm very careful which disk I select do I need to unplug everything to avoid damage to the other disks while I'm testing the system. It's just a short test run, so I don't really want to subject everything to the wear/tear of unplugging/plugging. Any input would be appreciated.

@EV I appreciate the comment. I have easy access in a very large case, and from what I can see the MonoPrice cables are fine In my application. I wouldn't want to use them on a test bench where they were being installed and removed frequently, or if sharp bends were required.
 
Status
Not open for further replies.
Top