3TB drives only showing as 2.2TB on Intel M1015 Card

[Hippo]

Hi,

Just upgraded the server. Running Freenas 9.1.1

I've added 8 new Seagate 3TB drives, and I am attempting to make a new RaidZ2 array. The computer sees the card, Freenas sees the drives, but they only appear at 2.2Tb in the web interface when creating the array. After doing a lot of research, I settled on the m1015 card. Found one on eBay, and the seller offered to flash it to IT mode for me.

Can somebody tell me if I'm missing something simple? Or if not, where should I look next.

Thanks,
Dan

 

[cyberjock]

Sounds like you might need to update the firmware? Maybe your version is so old it can't handle >2.2TB disks.

 

[Hippo]

That could be the case. Does anybody know which version was the first to support 3tb drives?

I believe I have 2.0.04-0771 from reading the output of dmesg.

Sent from my SAMSUNG-SGH-I747 using Tapatalk

 

[cyberjock]

Well, it's like this. Your firmware and driver should match. Sometimes if your firmware is newer than your driver you might be okay. But your firmware should NEVER be less than your driver. So you need to have the phase 14 or newer firmware.

 

[Hippo]

Okay, I guess that's reasonable. It's a bit counter intuitive. Normally you'd expect newer drivers to support older firmware.

Still, what's the best version for right now, and where do I get it? I saw a tutorial on flashing it somewhere, so I can go re-read that for the flashing info.

Thanks,
Dan

Sent from my SAMSUNG-SGH-I747 using Tapatalk

 

[gpsguy]

Information regarding flashing it to IT mode, can be found here. In the thread, is a link to the servethehome article. I let someone else suggest a version number.

 

[cyberjock]

I'm using v15 right now without problems. :)

 

[Hippo]

Cool thanks. I'll let you know what happens next.

This might be a little awkward as the card is in Seattle now, and I am not, but hopefully I can talk them through the procedure after I have collected all the files.

 

[cyberjock]

I just noticed something, your version number doesn't follow the typical version numbers. Can you post the output of dmesg?

 

[Hippo]

That is why I was confused by the simpler version numbers. I'll see what I can do when the west coast wakes up.

 

[Hippo]

Here's what I've got. The card shows up under mfi, and is listed along with "drake skinny" whatever that is. On boot is shows LSI, an the old firmware version I mentioned.

This is the whole thing. I hope it's meaningful...

Thanks again,
Dan

Code:

acpi0: reservation of fed40000, 5000 (3) failed
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, cfe00000 (3) failed
cpu0: <ACPI CPU> on acpi0
cpu1: <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 550
Event timer "HPET1" frequency 14318180 Hz quality 450
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
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> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xb000-0xb0ff mem 0xd0000000-0xdfffffff,0xfe8f0000-0xfe8fffff,0xfe700000-0xfe7fffff irq 18 at device 5.0 on pci1
pci1: <multimedia, HDA> at device 5.1 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> irq 18 at device 2.0 on pci0
pci2: <ACPI PCI bus> on pcib2
mfi0: <Drake Skinny> port 0xc000-0xc0ff mem 0xfe9fc000-0xfe9fffff,0xfe980000-0xfe9bffff irq 18 at device 0.0 on pci2
mfi0: Using MSI
mfi0: Megaraid SAS driver Ver 4.23
pcib3: <ACPI PCI-PCI bridge> irq 18 at device 10.0 on pci0
pci3: <ACPI PCI bus> on pcib3
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet> port 0xd800-0xd8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 18 at device 0.0 on pci3
re0: Using 1 MSI-X message
re0: Chip rev. 0x28000000
re0: MAC rev. 0x00000000
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: f4:6d:04:39:ba:28
ahci0: <ATI IXP700 AHCI SATA controller> port 0xa000-0xa007,0x9000-0x9003,0x8000-0x8007,0x7000-0x7003,0x6000-0x600f mem 0xfe6ffc00-0xfe6fffff irq 22 at device 17.0 on pci0
ahci0: AHCI v1.10 with 6 3Gbps 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 0xfe6fe000-0xfe6fefff irq 16 at device 18.0 on pci0
usbus0 on ohci0
ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fd000-0xfe6fdfff irq 16 at device 18.1 on pci0
usbus1 on ohci1
ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff800-0xfe6ff8ff irq 17 at device 18.2 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci0
ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fc000-0xfe6fcfff irq 18 at device 19.0 on pci0
usbus3 on ohci2
ohci3: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fb000-0xfe6fbfff irq 18 at device 19.1 on pci0
usbus4 on ohci3
ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff400-0xfe6ff4ff irq 19 at device 19.2 on pci0
usbus5: EHCI version 1.0
usbus5 on ehci1
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci0: <ATI IXP700/800 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0
ata0: <ATA channel> at channel 0 on atapci0
pci0: <multimedia, HDA> at device 20.2 (no driver attached)
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib4: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci4: <ACPI PCI bus> on pcib4
siis0: <SiI3124 SATA controller> port 0xec00-0xec0f mem 0xfebffc00-0xfebffc7f,0xfebf0000-0xfebf7fff irq 21 at device 6.0 on pci4
siisch0: <SIIS channel> at channel 0 on siis0
siisch1: <SIIS channel> at channel 1 on siis0
siisch2: <SIIS channel> at channel 2 on siis0
siisch3: <SIIS channel> at channel 3 on siis0
ohci4: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fa000-0xfe6fafff irq 18 at device 20.5 on pci0
usbus6 on ohci4
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb4
acpi_button0: <Power Button> on acpi0
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 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]
acpi_throttle0: <ACPI CPU Throttling> on cpu0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
(noperiph:siisch0:0:-1:-1): rescan already queued
(noperiph:siisch1:0:-1:-1): rescan already queued
(noperiph:siisch2:0:-1:-1): rescan already queued
(noperiph:siisch3:0:-1:-1): rescan already queued
mfi0: 426 (439433720s/0x0020/info) - Shutdown command received from host
mfi0: 427 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0073/1000/03b1/1014)
mfi0: 428 (boot + 3s/0x0020/info) - Firmware version 2.0.04-0771
mfi0: 429 (boot + 5s/0x0020/info) - Board Revision
mfi0: 430 (boot + 24s/0x0002/info) - Inserted: PD 0d(e0xff/s13)
mfi0: 431 (boot + 24s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=4433221100000000,0000000000000000
mfi0: 432 (boot + 24s/0x0002/info) - Inserted: PD 0e(e0xff/s14)
mfi0: 433 (boot + 24s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=4433221102000000,0000000000000000
mfi0: 434 (boot + 24s/0x0002/info) - Inserted: PD 0f(e0xff/s15)
mfi0: 435 (boot + 24s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=4433221101000000,0000000000000000
mfi0: 436 (boot + 24s/0x0002/info) - Inserted: PD 10(e0xff/s16)
mfi0: 437 (boot + 24s/0x0002/info) - Inserted: PD 10(e0xff/s16) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=4433221103000000,0000000000000000
mfi0: 438 (boot + 24s/0x0002/info) - Inserted: PD 11(e0xff/s17)
mfi0: 439 (boot + 24s/0x0002/info) - Inserted: PD 11(e0xff/s17) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=4433221104000000,0000000000000000
mfi0: 440 (boot + 24s/0x0002/info) - Inserted: PD 12(e0xff/s18)
mfi0: 441 (boot + 24s/0x0002/info) - Inserted: PD 12(e0xff/s18) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=4433221106000000,0000000000000000
mfi0: 442 (boot + 24s/0x0002/info) - Inserted: PD 13(e0xff/s19)
mfi0: 443 (boot + 24s/0x0002/info) - Inserted: PD 13(e0xff/s19) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=4433221105000000,0000000000000000
mfi0: 444 (boot + 24s/0x0002/info) - Inserted: PD 14(e0xff/s20)
mfi0: 445 (boot + 24s/0x0002/info) - Inserted: PD 14(e0xff/s20) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=4433221107000000,0000000000000000
mfi0: 446 (439433749s/0x0020/info) - Time established as 12/04/13  0:55:49; (25 seconds since power on)
mfi0: 447 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0073/1000/03b1/1014)
mfi0: 448 (boot + 3s/0x0020/info) - Firmware version 2.0.04-0771
mfi0: 449 (boot + 5s/0x0020/info) - Board Revision
mfi0: 450 (boot + 23s/0x0002/info) - Inserted: PD 0d(e0xff/s13)
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
DUMMYNET 0xfffffe0002f09500 with IPv6 initialized (100409)
load_dn_sched dn_sched WF2Q+ loaded
load_dn_sched dn_sched FIFO loaded
load_dn_sched dn_sched PRIO loaded
load_dn_sched dn_sched QFQ loaded
load_dn_sched dn_sched RR loaded
mfisyspd0 on mfi0
mfisyspd0: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 13)
mfisyspd0:  SYSPD volume attached
mfisyspd1 on mfi0
mfisyspd1: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 14)
mfisyspd1:  SYSPD volume attached
mfisyspd2 on mfi0
mfisyspd2: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 15)
mfisyspd2:  SYSPD volume attached
mfisyspd3 on mfi0
mfisyspd3: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 16)
mfisyspd3:  SYSPD volume attached
mfisyspd4 on mfi0
mfisyspd4: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 17)
mfisyspd4:  SYSPD volume attached
mfisyspd5 on mfi0
mfisyspd5: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 18)
mfisyspd5:  SYSPD volume attached
mfisyspd6 on mfi0
mfisyspd6: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 19)
mfisyspd6:  SYSPD volume attached
mfisyspd7 on mfi0
mfisyspd7: 2097151MB (4294967295 sectors) SYSPD volume (deviceid: 20)
mfisyspd7:  SYSPD volume attached
mfi0: 451 (boot + 23s/0x0002/info) - Inserted: PD 0d(e0xff/s13) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=4433221100000000,0000000000000000
mfi0: 452 (boot + 23s/0x0002/info) - Inserted: PD 0e(e0xff/s14)
mfi0: 453 (boot + 23s/0x0002/info) - Inserted: PD 0e(e0xff/s14) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=4433221102000000,0000000000000000
mfi0: 454 (boot + 23s/0x0002/info) - Inserted: PD 0f(e0xff/s15)
mfi0: 455 (boot + 23s/0x0002/info) - Inserted: PD 0f(e0xff/s15) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=4433221101000000,0000000000000000
mfi0: 456 (boot + 23s/0x0002/info) - Inserted: PD 10(e0xff/s16)
mfi0: 457 (boot + 23s/0x0002/info) - Inserted: PD 10(e0xff/s16) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=4433221103000000,0000000000000000
mfi0: 458 (boot + 23s/0x0002/info) - Inserted: PD 11(e0xff/s17)
mfi0: 459 (boot + 23s/0x0002/info) - Inserted: PD 11(e0xff/s17) Info: enclPd=ffff, scsiType=0, portMap=05, sasAddr=4433221104000000,0000000000000000
mfi0: 460 (boot + 23s/0x0002/info) - Inserted: PD 12(e0xff/s18)
mfi0: 461 (boot + 23s/0x0002/info) - Inserted: PD 12(e0xff/s18) Info: enclPd=ffff, scsiType=0, portMap=06, sasAddr=4433221106000000,0000000000000000
mfi0: 462 (boot + 23s/0x0002/info) - Inserted: PD 13(e0xff/s19)
mfi0: 463 (boot + 23s/0x0002/info) - Inserted: PD 13(e0xff/s19) Info: enclPd=ffff, scsiType=0, portMap=04, sasAddr=4433221105000000,0000000000000000
mfi0: 464 (boot + 23s/0x0002/info) - Inserted: PD 14(e0xff/s20)
mfi0: 465 (boot + 23s/0x0002/info) - Inserted: PD 14(e0xff/s20) Info: enclPd=ffff, scsiType=0, portMap=07, sasAddr=4433221107000000,0000000000000000
mfi0: 466 (439434353s/0x0020/info) - Time established as 12/04/13  1:05:53; (27 seconds since power on)
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 12Mbps Full Speed USB v1.0
usbus5: 480Mbps High Speed USB v2.0
usbus6: 12Mbps Full Speed USB v1.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 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <ATI> at usbus2
uhub2: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ugen3.1: <ATI> at usbus3
uhub3: <ATI OHCI root HUB, class 9/0, rev 1.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 EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5
ugen6.1: <ATI> at usbus6
uhub6: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada0: quirks=0x1<4K>
ada0: Previously was known as ad4
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad6
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada2: quirks=0x1<4K>
ada2: Previously was known as ad8
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada3: quirks=0x1<4K>
ada3: Previously was known as ad10
ada4 at ahcich4 bus 0 scbus4 target 0 lun 0
ada4: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada4: Command Queueing enabled
ada4: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada4: quirks=0x1<4K>
ada4: Previously was known as ad12
ada5 at ahcich5 bus 0 scbus5 target 0 lun 0
ada5: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada5: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada5: Command Queueing enabled
ada5: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada5: quirks=0x1<4K>
ada5: Previously was known as ad14
ada6 at ata0 bus 0 scbus6 target 0 lun 0
ada6: <SanDisk SDCFH-004G HDX 5.11> CFA-4 device
ada6: 66.700MB/s transfers (UDMA4, PIO 512bytes)
ada6: 3825MB (7835184 512 byte sectors: 16H 63S/T 7773C)
ada6: Previously was known as ad0
ada7 at siisch0 bus 0 scbus7 target 0 lun 0
ada7: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada7: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada7: Command Queueing enabled
ada7: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada7: quirks=0x1<4K>
ada7: Previously was known as ad16
ada8 at siisch1 bus 0 scbus8 target 0 lun 0
ada8: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada8: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada8: Command Queueing enabled
ada8: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada8: quirks=0x1<4K>
ada8: Previously was known as ad18
ada9 at siisch2 bus 0 scbus9 target 0 lun 0
ada9: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada9: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada9: Command Queueing enabled
ada9: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada9: quirks=0x1<4K>
ada9: Previously was known as ad20
ada10 at siisch3 bus 0 scbus10 target 0 lun 0
ada10: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada10: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada10: Command Queueing enabled
ada10: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada10: quirks=0x1<4K>
ada10: Previously was known as ad22
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1557020641 Hz quality 800
uhub6: 2 ports with 2 removable, self powered
uhub0: 3 ports with 3 removable, self powered
uhub1: 3 ports with 3 removable, self powered
uhub3: 3 ports with 3 removable, self powered
uhub4: 3 ports with 3 removable, self powered
uhub2: 6 ports with 6 removable, self powered
uhub5: 6 ports with 6 removable, self powered
Root mount waiting for: usbus2
Root mount waiting for: usbus2
Root mount waiting for: usbus2
Root mount waiting for: usbus2
ugen2.2: <Data Robotics Inc.> at usbus2
umass0: <Data Robotics Inc. Drobo3, class 0/0, rev 2.00/1.00, addr 2> on usbus2
da0 at umass-sim0 bus 0 scbus11 target 0 lun 0
da0: <Drobo Drobo3 3.00> Fixed Direct Access SCSI-5 device
da0: 40.000MB/s transfers
da0: 8388608MB (17179869184 512 byte sectors: 255H 63S/T 1069397C)
da0: quirks=0x2<NO_6_BYTE>
ugen1.2: <CPS> at usbus1
Trying to mount root from ufs:/dev/ufs/FreeNASs2a [ro]...
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
GEOM_RAID5: Module loaded, version 1.1.20110927.40 (rev 00ce00e5abb4)
GEOM_ELI: Device ada1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada2p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada7p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada8p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada9p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada10p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada3p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device ada5p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
GEOM_ELI: Device da0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:    Crypto: software
bridge0: Ethernet address: 02:ee:18:ca:18:00
bridge0: link state changed to UP
re0: promiscuous mode enabled
epair0a: Ethernet address: 02:ea:98:00:0c:0a
epair0b: Ethernet address: 02:ea:98:00:0d:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
re0: link state changed to DOWN
epair0a: promiscuous mode enabled
re0: link state changed to UP
epair1a: Ethernet address: 02:61:6c:00:0d:0a
epair1b: Ethernet address: 02:61:6c:00:0e:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair1a: promiscuous mode enabled
epair2a: Ethernet address: 02:57:87:00:0e:0a
epair2b: Ethernet address: 02:57:87:00:0f:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair2a: promiscuous mode enabled
epair3a: Ethernet address: 02:51:87:00:0f:0a
epair3b: Ethernet address: 02:51:87:00:10:0b
epair3a: link state changed to UP
epair3b: link state changed to UP
epair3a: promiscuous mode enabled
Local NSM refuses to monitor theon.broadstripe.com
ipfw: pullup failed
ipfw: pullup failed
ipfw: pullup failed
ipfw: pullup failed

 

[Red]

I'm the guy Dan is trying to help out with this. I just discovered mfiutil, and this might be useful:

~# mfiutil show adapter
mfi0 Adapter:
Product Name: ServeRAID M1015 SAS/SATA Controller
Serial Number: P465310710
Firmware: 20.1.1-0049
RAID Levels: JBOD, RAID0, RAID1, RAID10
Battery Backup: not present
NVRAM: 32K
Onboard Memory: 0M
Minimum Stripe: 8k
Maximum Stripe: 64k

~# mfiutil show drives
mfi0 Physical Drives:
13 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F30RCZ> SATA E1:S3
14 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F2ZRPG> SATA E1:S1
15 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F2VRK9> SATA E1:S2
16 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F31LV0> SATA E1:S0
17 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F2YXXE> SATA E1:S7
18 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F32DYE> SATA E1:S5
19 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F30154> SATA E1:S6

20 ( 2048G) JBOD <ST3000DM001-1CH1 CC27 serial=W1F2ZTLY> SATA E1:S4


~# mfiutil show firmware
mfi0 Firmware Package Version: 20.1.1-0049
mfi0 Firmware Images:
Name Version Date Time Status
BIOS 4.11.00 active
PCLI 03.00-009:#%00008 Sep 20 2009 14:05:00 active
BCON 4.0-14-e_6-Rel Nov 20 2009 16:38:05 active
NVDT 3.03.0039 Dec 08 2009 17:29:22 active
APP 2.0.04-0771 Dec 18 2009 12:57:31 active
BTBL 2.01.00.00-0019 May 14 2009 15:52:08 active
Note the reported sizes of the drives. Also, the firmware is all dated 2009, which is a bit old but I'd think would be plenty new enough to support 48-bit LBA. Help!

 

[Hippo]

Holy crap! 2009? That is really old.

Based on what had been said about newer drivers requiring newer firmware, I'm thinking an update is inevitable here.

 

[Red]

Next question: can I use mfiutil flash rather than go through all this rigmarole of creating a DOS-formatted (!!) USB boot stick?

 

[cyberjock]

Something is not right here. I'm really not sure what the heck is going on... Here's what my card says:

mps0: <LSI SAS2008> port 0x4000-0x40ff mem 0xd2400000-0xd2403fff,0xd2440000-0xd247ffff irq 18 at device 0.0 on pci3
mps0: Firmware: 15.00.00.00, Driver: 14.00.00.01-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>

Notice the Firmware and Driver version. You have no such entry. I have to assume you don't have an M1015 installed at all. In fact:

mfi0: <Drake Skinny> port 0xc000-0xc0ff mem 0xfe9fc000-0xfe9fffff,0xfe980000-0xfe9bffff irq 18 at device 0.0 on pci2
mfi0: Using MSI
mfi0: Megaraid SAS driver Ver 4.23

That is NOT an M1015. Notice the mps driver instead of mfi driver. That's a MegaRAID controller(not sure the exact model, but its a "skinny"). Far from a controller we'd recommend for ZFS unless I'm really confused. You even list v20 firmware, but latest for the LSI-2008 cards is phase 17.

Additionally, you are planning to use Realtek(again, not recommended hardware). Works for some not for many. That's your choice though.

To be completely honest, something is very wrong here and I don't know if I feel comfortable giving continued advice because I can't even conceive of this being a good reliable server long-term with that hardware. I'm not even sure what advice to give since I can't even validate your controller. You say that you have an M1015, but I see no evidence of an M1015 anywhere in the system.

Additionally, mfiutil doesn't work with the M1015. When I try to run it it says:

mfiutil: mfi_open: No such file or directory

Well, duh. M1015s aren't mfi devices. It's an mps device.

I'm quite confused at the moment. Someone needs to explain what is really going on because somewhere either I'm totally off my rocker or someone else is very confused about the hardware they think they own.

 

[Hippo]

But it's clearly listed as an m1015 in the output. There's always the possibility that the eBay seller mislead us...

Product Name: ServeRAID M1015 SAS/SATA Controller
Serial Number: P465310710
Firmware: 20.1.1-0049
RAID Levels: JBOD, RAID0, RAID1, RAID10

 

[cyberjock]

But it's clearly listed as an m1015 in the output. There's always the possibility that the eBay seller mislead us...

To be honest, that's what I was thinking but I wasn't going to say it. Can you take a picture of the card and post it? Front and back?

 

[Hippo]

I'll try have them do it.

There are also two syba sata cards in there. They're the megaraid devices I believe.

 

[Red]

Success! Oy, what a pain in the ass that was.

As cyberjock pointed out, the card seemed to have come with some weird mutant firmware so I decided to flash it with firmware downloaded from servethehome.com. After figuring out how to make a DOS boot USB stick, I then spent way too much time trying to coax my server into booting from the stick before giving it up. I managed to get DOS to boot on two different motherboards I tried the card in, but both of them refused to run sas2flsh.exe, complaining of a failed PAL initialization. Off to the Internet I go, eventually finding a UEFI shell which I put on my memory stick and booted on the one machine whose BIOS offered a "boot to UEFI shell from filesystem" option. Flashed the card, and it recognized the drives as 3TB, finally. Volume size from 8x3TB RAIDZ2 was 15.2 TiB, less than I would have hoped for but I'll take it.

dmesg output:
mps0: <LSI SAS2008> port 0xc000-0xc0ff mem 0xfe9fc000-0xfe9fffff,0xfe980000-0xfe9bffff irq 18 at device 0.0 on pci2
mps0: Firmware: 15.00.00.00, Driver: 14.00.00.01-fbsd

 

[cyberjock]

MUCH MUCH better! I like that dmesg output!

I don't know what the other guy did(we'll call him "Red" for now) but he doesn't know how to flash SAS controllers and should be replaced immediately.

(just kidding)

Glad that's all worked out. You got lucky in that the card actually let you reflash the firmware. I was a little woried that the reflash tool wouldn't recognize it as an M1015 and tell you there are no cards to reflash.