SOLVED Disks: No Entry has been found on Gigabyte 990FX-UD5

[zeroluck]

Hi, I've done some searching and can't find any similar issues so I'm first time posting here.

I've installed the most recent version of FreeNAS onto a DIY iSCSI SAN I'm building from a Norco 4224 case with a Gigabyte GA-990fx-UD5 for work. Initially I set it up with some SuperMicro AOC-SAS2LP-MV8 cards and used LIO and CentOS 7 but I'm getting bad iSCSI performance with that setup so right now I'm trying to do a ZFS performance proof-of-concept just using the onboard SB950 AHCI card since the SAS2LP cards aren't supported.

I've connected 4 1TB disks to the top backplane and used a SFF-8087 --> quad SATA connector to the onboard controller, and I can see all 4 disks in the BIOS. The MB is set to AHCI. The SSD I have FreeNAS installed onto boots up fine and is on the same controller as the 4 1TB disks, but when I go to View Disks under Storage in the FreeNAS web interface it says "No entry has been found". I got into the console and ran some commands to verify that the OS is not seeing my disks:

Code:

[root@freenas ~]# sysctl kern.disks                                            
kern.disks: ada0

Here is my dmesg:

Code:

[root@freenas] ~# dmesg
Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.3-RELEASE-p8 #2 r275790+6365d9c: Sat Jan 24 09:16:18 PST 2015
    root@build3.ixsystems.com:/tank/home/jkh/build/93/FN/objs/os-base/amd64/fusion/jkh/93/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: AMD FX(tm)-8350 Eight-Core Processor            (4018.43-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x600f20  Family = 0x15  Model = 0x2  Stepping = 0
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x3e98320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD Features2=0x1ebbfff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,XOP,SKINIT,WDT,LWP,FMA4,TCE,NodeId,TBM,Topology,PCXC,PNXC>
  Standard Extended Features=0x8
  TSC: P-state invariant, performance statistics
real memory  = 18236833792 (17392 MB)
avail memory = 16469741568 (15706 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <ALASKA A M I>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 8 core(s)
cpu0 (BSP): APIC ID: 16
cpu1 (AP): APIC ID: 17
cpu2 (AP): APIC ID: 18
cpu3 (AP): APIC ID: 19
cpu4 (AP): APIC ID: 20
cpu5 (AP): APIC ID: 21
cpu6 (AP): APIC ID: 22
cpu7 (AP): APIC ID: 23
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20111123/tbfadt-606)
ioapic0 <Version 2.1> irqs 0-23 on motherboard
ioapic1 <Version 2.1> irqs 24-55 on motherboard
ispfw: registered firmware <isp_1040>
ispfw: registered firmware <isp_1040_it>
ispfw: registered firmware <isp_1080>
ispfw: registered firmware <isp_1080_it>
ispfw: registered firmware <isp_12160>
ispfw: registered firmware <isp_12160_it>
ispfw: registered firmware <isp_2100>
ispfw: registered firmware <isp_2200>
ispfw: registered firmware <isp_2300>
ispfw: registered firmware <isp_2322>
ispfw: registered firmware <isp_2400>
ispfw: registered firmware <isp_2400_multi>
ispfw: registered firmware <isp_2500>
ispfw: registered firmware <isp_2500_multi>
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: <AES-CBC,AES-XTS> on motherboard
padlock0: No ACE support.
acpi0: <ALASKA A M I> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 450
Event timer "HPET2" frequency 14318180 Hz quality 450
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 52 at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <mass storage, RAID> at device 0.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> irq 52 at device 4.0 on pci0
pci2: <ACPI PCI bus> on pcib2
vgapci0: <VGA-compatible display> port 0xe000-0xe07f mem 0xfd000000-0xfdffffff,0xc0000000-0xcfffffff,0xd0000000-0xd1ffffff irq 44 at device 0.0 on pci2
vgapci0: Boot video device
pci2: <multimedia, HDA> at device 0.1 (no driver attached)
pcib3: <ACPI PCI-PCI bridge> irq 53 at device 9.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pci3: <serial bus, USB> at device 0.0 (no driver attached)
pcib4: <ACPI PCI-PCI bridge> irq 54 at device 11.0 on pci0
pci4: <ACPI PCI bus> on pcib4
pci4: <mass storage, RAID> at device 0.0 (no driver attached)
pcib5: <ACPI PCI-PCI bridge> irq 54 at device 12.0 on pci0
pci5: <ACPI PCI bus> on pcib5
pci5: <mass storage, RAID> at device 0.0 (no driver attached)
pcib6: <ACPI PCI-PCI bridge> irq 54 at device 13.0 on pci0
pci6: <ACPI PCI bus> on pcib6
em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xd020-0xd03f mem 0xfe380000-0xfe39ffff,0xfe360000-0xfe37ffff irq 40 at device 0.0 on pci6
em0: Using an MSI interrupt
em0: Ethernet address: 00:15:17:fd:0d:2a
em1: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xd000-0xd01f mem 0xfe320000-0xfe33ffff,0xfe300000-0xfe31ffff irq 41 at device 0.1 on pci6
em1: Using an MSI interrupt
em1: Ethernet address: 00:15:17:fd:0d:2b
ahci0: <AMD SB7x0/SB8x0/SB9x0 AHCI SATA controller> port 0xf040-0xf047,0xf030-0xf033,0xf020-0xf027,0xf010-0xf013,0xf000-0xf00f mem 0xfe807000-0xfe8073ff irq 19 at device 17.0 on pci0
ahci0: AHCI v1.20 with 6 6Gbps ports, Port Multiplier supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe806000-0xfe806fff irq 18 at device 18.0 on pci0
usbus0 on ohci0
ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe805000-0xfe8050ff irq 17 at device 18.2 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe804000-0xfe804fff irq 18 at device 19.0 on pci0
usbus2 on ohci1
ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe803000-0xfe8030ff irq 17 at device 19.2 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci1
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib7: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci7: <ACPI PCI bus> on pcib7
ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe802000-0xfe802fff irq 18 at device 20.5 on pci0
usbus4 on ohci2
pcib8: <ACPI PCI-PCI bridge> at device 21.0 on pci0
pci8: <ACPI PCI bus> on pcib8
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xc000-0xc0ff mem 0xd2104000-0xd2104fff,0xd2100000-0xd2103fff irq 16 at device 0.0 on pci8
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00100000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Ethernet address: 74:d4:35:85:a6:27
pcib9: <ACPI PCI-PCI bridge> at device 21.1 on pci0
pci9: <ACPI PCI bus> on pcib9
pci9: <serial bus, USB> at device 0.0 (no driver attached)
pcib10: <ACPI PCI-PCI bridge> at device 21.2 on pci0
pci10: <ACPI PCI bus> on pcib10
ahci1: <Marvell 88SE9172 AHCI SATA controller> port 0xb040-0xb047,0xb030-0xb033,0xb020-0xb027,0xb010-0xb013,0xb000-0xb00f mem 0xfe110000-0xfe1101ff irq 18 at device 0.0 on pci10
ahci1: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS
ahcich6: <AHCI channel> at channel 0 on ahci1
ahcich7: <AHCI channel> at channel 1 on ahci1
ohci3: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe801000-0xfe801fff irq 18 at device 22.0 on pci0
usbus5 on ohci3
ehci2: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe800000-0xfe8000ff irq 17 at device 22.2 on pci0
usbus6: EHCI version 1.0
usbus6 on ehci2
acpi_button0: <Power Button> on acpi0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
wbwd0: HEFRAS and EFER do not align: EFER 0x2e DevID 0xff DevRev 0xff CR26 0xff
acpi_throttle0: <ACPI CPU Throttling> on cpu0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
acpi_throttle2: <ACPI CPU Throttling> on cpu2
acpi_throttle2: failed to attach P_CNT
device_attach: acpi_throttle2 attach returned 6
acpi_throttle3: <ACPI CPU Throttling> on cpu3
acpi_throttle3: failed to attach P_CNT
device_attach: acpi_throttle3 attach returned 6
acpi_throttle4: <ACPI CPU Throttling> on cpu4
acpi_throttle4: failed to attach P_CNT
device_attach: acpi_throttle4 attach returned 6
acpi_throttle5: <ACPI CPU Throttling> on cpu5
acpi_throttle5: failed to attach P_CNT
device_attach: acpi_throttle5 attach returned 6
acpi_throttle6: <ACPI CPU Throttling> on cpu6
acpi_throttle6: failed to attach P_CNT
device_attach: acpi_throttle6 attach returned 6
acpi_throttle7: <ACPI CPU Throttling> on cpu7
acpi_throttle7: failed to attach P_CNT
device_attach: acpi_throttle7 attach returned 6
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 480Mbps High Speed USB v2.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 480Mbps High Speed USB v2.0
usbus4: 12Mbps Full Speed USB v1.0
usbus5: 12Mbps Full Speed USB v1.0
usbus6: 480Mbps High Speed USB v2.0
ugen0.1: <ATI> at usbus0
uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <ATI> at usbus1
uhub1: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
ugen2.1: <ATI> at usbus2
uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen3.1: <ATI> at usbus3
uhub3: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3
ugen4.1: <ATI> at usbus4
uhub4: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ugen5.1: <ATI> at usbus5
uhub5: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
ugen6.1: <ATI> at usbus6
uhub6: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
uhub4: 2 ports with 2 removable, self powered
uhub5: 4 ports with 4 removable, self powered
uhub0: 5 ports with 5 removable, self powered
uhub2: 5 ports with 5 removable, self powered
uhub6: 4 ports with 4 removable, self powered
uhub1: 5 ports with 5 removable, self powered
uhub3: 5 ports with 5 removable, self powered
ugen2.2: <Rextron> at usbus2
ukbd0: <USB> on usbus2
kbd2 at ukbd0
ums0: <USB> on usbus2
ums0: 5 buttons and [XYZ] coordinates ID=1
ada0 at ahcich1 bus 0 scbus1 target 0 lun 0
ada0: <Samsung SSD 840 EVO 120GB EXT0BB6Q> ATA-9 SATA 3.x device
ada0: Serial Number S1D5NSBF542024N
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 114473MB (234441648 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad6
SMP: AP CPU #1 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #4 Launched!
Timecounter "TSC-low" frequency 2009213176 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-9.3-STABLE-201501241715 []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
wbwd0: HEFRAS and EFER do not align: EFER 0x2e DevID 0xff DevRev 0xff CR26 0xff
vboxdrv: fAsync=0 offMin=0x995 offMax=0x7520[\code}

Any ideas of where I should start? Obviously the SB950 chip is supported and dmesg shows FreeBSD loading the driver for it up, but why aren't my disks showing up?

These disks were previously in an ETI iSCSI array, is it possible that they need to be formatted before BSD can see them? I would think it could still see the block device and let me wipe it...

 

[zeroluck]

I just tried the Marvell onboard controller and wiping the disks with parted magic, I still can't get any disks to show up in the GUI. I've tried

Code:

camcontrol rescan all

also to no avail.

 

[gpsguy]

At a minimum the disks will need some amount of wiping if they were used with another OS. Sometimes you might be able to run some dd commands on the beginning and end of the drives. You might find the commands with a search of the forum. DBAN with the quick option should work, but it will take longer.

Be prepared for a barrage of comments regarding the use of a desktop CPU (esp AMD) in your system.


Sent from my phone

 

[zeroluck]

I already wiped the disks several different ways with gparted and they don't show up on the controller I am booted from. I put one of the 1TB Seagate ES.1000 disks I'm trying to get working into a USB 2.0 drive sled/dock and it shows up as da0 right away. It's definitely not the disks. I also took a brand new, empty Seagate ES.2000 off the spare shelf and it works in the sled and not on the onboard SATA controller.

Is it normal to be able to boot off a SATA controller but not be able to see disks on it?

gpsguy, Surely what processor I have in the computer has no bearing on whether FreeNAS can see disks on the onboard SATA controller that I am successfully booting on? I'm not here to start an argument about AMD vs Intel... I just want to see if FreeNAS is going to work for us.

 

[zeroluck]

I'm just going to test multipathing and throughput by connecting the USB sled-ed disk to my VMWare environment. If I can get reasonable speeds for a USB 2.0 disk I think I'll buy some IBM controllers so I can get this show on the road.

I tried the USB3 port on this motherboard and it also didn't work. If only this software had been written on Linux you could have a slick interface AND hardware compatibility.... I guess I've always been a dreamer...

 

[cyberjock]

I tried the USB3 port on this motherboard and it also didn't work. If only this software had been written on Linux you could have a slick interface AND hardware compatibility.... I guess I've always been a dreamer...

Yeah, except when FreeNAS was in early development the only ZFS that existed for Linux was complete and utterly useless sh*t. There was no "zfs on linux" project, so the project you love would be some obscure thing like all the other linux variants and probably would have died long before zfs on linux hit "stable" status.

Also notice that nobody seems to be working on a FreeNAS equivalent that is based on Linux. I don't think that's a coincidence. ;)

 

[zeroluck]

Sometimes there's only demand/developers/market for one solution in a niche like this, right? OpenFiler is dead and everything else is sketchy.

Anyway, do you have any ideas as to why I can't see my disks on the onboard controller? I've read your hardware guide, I know what I have isn't recommended but I didn't originally build this box to do FreeNAS :( If I can make it perform satisfactorily, I'll definitely buy some supported cards and potentially even replace the motherboard.

 

[cyberjock]

If the disks don't show up in camcontrol devlist, then it's almost certainly the SATA controller on your board isn't supported.

I love Gigabyte (all my desktops are made of them). But as a server they're not my first or second choice. AMD is just bad because generally AMD boards are made as cheap as possible, so you often end up with controllers that aren't supported except in Windows and sometimes Linux.

 

[zeroluck]

If that's the case how am I booting off the controller? And what is this in dmesg?

Code:

ahci0: <AMD SB7x0/SB8x0/SB9x0 AHCI SATA controller> port 0xf040-0xf047,0xf030-0xf033,0xf020-0xf027,0xf010-0xf013,0xf000-0xf00f mem 0xfe807000-0xfe8073ff irq 19 at device 17.0 on pci0
ahci0: AHCI v1.20 with 6 6Gbps ports, Port Multiplier supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0

and this?

Code:

ahci1: <Marvell 88SE9172 AHCI SATA controller> port 0xb040-0xb047,0xb030-0xb033,0xb020-0xb027,0xb010-0xb013,0xb000-0xb00f mem 0xfe110000-0xfe1101ff irq 18 at device 0.0 on pci10
ahci1: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS
ahcich6: <AHCI channel> at channel 0 on ahci1
ahcich7: <AHCI channel> at channel 1 on ahci1

I did originally spec out Xeon and Opteron server boards but we had to cut it because they wanted this cheap.

 

[cyberjock]

So, few things (and you'll probably think I'm full of shit.. don't kill the messenger).

Onboard stuff is often customized, so despite the fact that it might have a driver, and the OS might load the driver, that's no indication that "it will work". A great example of customization is the LSI controllers on Supermicro motherboards. You have to use the one from Supermicro, or you have to be forceful with the reflashing. I don't even know if you can use the firmware from LSI because I'm not stupid enough to risk ruining a motherboard with the firmware from LSI instead of Supermicro. ;) When you buy stuff that is on-board you aren't always buying the reference design, so you can't always use the reference driver.

AMDs, they're a mess. Period. The CPU isn't particularly well supported by AMD itself on FreeBSD, and often the AMD boards are built as cheap as possible. This creates plenty of obstacles to getting a good working system. I don't recommend them because when you weigh the statistical chances of getting a working system with AMD against a non-working system that then requires you go buy a whole second system that is Intel based, I prefer to give you the "easy button". Buy the Intel stuff as it should work.

If you look at your first post I see:

1. ada0 at ahcich1 bus 0 scbus1 target 0 lun 0
2. ada0: <Samsung SSD 840 EVO 120GB EXT0BB6Q> ATA-9 SATA 3.x device
3. ada0: Serial Number S1D5NSBF542024N
4. ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
5. ada0: Command Queueing enabled
6. ada0: 114473MB (234441648 512 byte sectors: 16H 63S/T 16383C)
7. ada0: Previously was known as ad6

I don't see any other disks listed, so I think it's a foregone conclusion that you ran a camcontrol devlist and saw none of your missing drives. That's because the system didn't detect them. Your guess is as good as mine for the precise technical reason. But at the end of the day the problem is going to be the same. Gotta use supported hardware and it looks like yours isn't. By comparison, I've got 15 disks in my system and they all list themselves right at the same place as your single disk.

Yes, I realize you may have a boot device hooked up directly to the motherboard, and it could be that the driver is able to detect the boot device and use it because of something obscure in the BIOS that handles the boot routine well enough to make the drive work. It could be that the port happens to be port 0 and the driver has some fatal exit call after port 0 because the hardware isn't truely compatible. Who cares why one works and the others don't. The problem is that the others don't.

Unfortunately, nobody here is really going to spend a stupendous amount of time to help you troubleshoot the problem because at the end of the day the answer is very very likely to be "its not supported, get other hardware". As a community we don't have the resources to let every person that wants to use <insert random hardware here> get one-on-one support with identifying every little problem with their hardware. We provide a list that we know works well, and you can choose to buy from that list, or not. If you choose no, you are likely buying yourself hardware that keeps a little more coin in your pocket, but you're going to be on your own if there's a problem.

And being on an island by yourself is very lonely.

 

[zeroluck]

I just got the disks recognized on my onboard controller by plugging the disk directly in and bypassing my Norco 4224 backplane/ SFF-8087 spider cable, probably a bad cable. Thanks for being so helpful.

I was sort of suspicious because I have loaded PF Sense (also based off FreeBSD 9.x) onto many diverse hardwares, coincidentally this exact board and it had 0 problems loading multiple disks. Also... it sees the controllers in the OS and even boots off a disk that is connected...

For other people out there that end up here the Marvell 88SE9172 and the AMD SB7x0/SB8x0/SB9x0 both DO work. I haven't figured out what's up with my Norco backplane yet.

 

[zeroluck]

For the sake of competion I wanted to post an update. The array works well. I recently upgraded the system to newer motherboard because I needed more RAM and that system could only do 32GB ECC. This is my new system:

• Supermicro ATX DDR4 LGA 2011 Motherboards X10SRH-CLN4F-O
  
• Intel Xeon E5-1620 v3 Haswell-EP 3.5GHz 4 x 256KB L2 Cache 10MB L3 Cache LGA 2011-3 140W BX80644E51620V3 Server Processor
  
• Crucial 64GB Kit (16GBx4) DDR4 2133 (PC4-2133) DR x4 ECC Registered 288-Pin Server Memory CT4K16G4RFD4213 / CT4C16G4RFD4213
  
• 2x Samsung 850 Pro 128GB 2.5-Inch SATA III Internal SSD BOOT
  
• 2x Samsung 850 Pro 256GB 2.5-Inch SATA III Internal SSD L2ARC

System has been online for months now with no issues and better performance than some of our EqualLogic SANs!