FreeNAS 9.3 to 9.10 upgrade breaks ASUS P5Q (Marvell AHCI SATA controller)

Status
Not open for further replies.

Purkki

Dabbler
Joined
Apr 13, 2016
Messages
10
Hi

I upgraded from FreeNAS-9.3-STABLE-201604041648
to 9.10 (e9dd2aa0c143ea7cdbe91aaee021959e) and it breaks ASUS P5Q (Marvell 88SX6121 AHCI SATA controller (Marvell 88SE6111).

The Marvell SATA controller shows only 1 disc instead of 2 connected to it.
Change: Port Multiplier supported -> Port Multiplier not supported

Bios is set "Normal mode"
From bios you can set the 2 SATA-ports work in a:
Super Mode (stripe)
EZ Backup (mirror)
Normal Mode ("normal" SATA-ports, Note: Windows only supports the first port. Freenas 9.3 showed both ports fine.)

Both Marvell ports have been working fine since FreeNAS 8.3.0
There is 8 SATA hard drives connected to the motherboard and they are all in the same pool (Raid-z2).

camcontrol devlist (Freenas 9.3)
Code:
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus0 target 1 lun 0 (pass1,ada1)
<Port Multiplier 57231095 2106>    at scbus0 target 15 lun 0 (pass2,pmp0)
<ST2000DL001-9VT156 CC43>          at scbus3 target 0 lun 0 (pass3,ada2)
<ST2000DL001-9VT156 CC43>          at scbus4 target 0 lun 0 (pass4,ada3)
<ST2000DL001-9VT156 CC43>          at scbus5 target 0 lun 0 (pass5,ada4)
<WDC WD20EFRX-68EUZN0 80.00A80>    at scbus6 target 0 lun 0 (pass6,ada5)
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus7 target 0 lun 0 (pass7,ada6)
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus8 target 0 lun 0 (pass8,ada7)
<Kingston DataTraveler 3.0 PMAP>   at scbus10 target 0 lun 0 (pass9,da0)
<Kingston DataTraveler 3.0 PMAP>   at scbus11 target 0 lun 0 (pass10,da1)


camcontrol devlist (Freenas 9.10)
Code:
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus0 target 0 lun 0 (ada0,pass0)
<ST2000DL001-9VT156 CC43>          at scbus3 target 0 lun 0 (ada1,pass1)
<ST2000DL001-9VT156 CC43>          at scbus4 target 0 lun 0 (ada2,pass2)
<ST2000DL001-9VT156 CC43>          at scbus5 target 0 lun 0 (ada3,pass3)
<WDC WD20EFRX-68EUZN0 80.00A80>    at scbus6 target 0 lun 0 (ada4,pass4)
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus7 target 0 lun 0 (ada5,pass5)
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus8 target 0 lun 0 (ada6,pass6)
<Kingston DataTraveler 3.0 PMAP>   at scbus10 target 0 lun 0 (da0,pass7)
<Kingston DataTraveler 3.0 PMAP>   at scbus11 target 0 lun 0 (da1,pass8)


Difference:
Code:
<WDC WD20EFRX-68AX9N0 80.00A80>    at scbus0 target 1 lun 0 (pass1,ada1)
<Port Multiplier 57231095 2106>    at scbus0 target 15 lun 0 (pass2,pmp0)

- Missing hard disc is connected to the Motherboards Marvell SATA-port.
- Also the Port Multiplier is missing.

Dmesg (Freenas 9.3)
Code:
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-p31 #0 r288272+ecf8c25: Mon Apr  4 09:55:51 PDT 2016
    root@build3.ixsystems.com:/tank/home/stable-builds/FN/objs/os-base/amd64/tank/home/stable-builds/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz (2933.50-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x1067a  Family = 0x6  Model = 0x17  Stepping = 10
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xc08e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,OSXSAVE>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant, performance statistics
real memory  = 10200547328 (9728 MB)
avail memory = 8206643200 (7826 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <A_M_I_ OEMAPIC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: No AESNI support.
padlock0: No ACE support.
acpi0: <A_M_I_ OEMXSDT> on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of fed08000, 1000 (3) failed
acpi0: reservation of fed1c000, 4000 (3) failed
acpi0: reservation of fed20000, 20000 (3) failed
acpi0: reservation of fed50000, 40000 (3) failed
acpi0: reservation of ffc00000, 300000 (3) failed
acpi0: reservation of fec00000, 1000 (3) failed
acpi0: reservation of fee00000, 1000 (3) failed
acpi0: reservation of e0000000, 10000000 (3) failed
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 9ff00000 (3) failed
cpu0: <ACPI CPU> on acpi0
ACPI Warning: Incorrect checksum in table [OEMB] - 0x02, should be 0x01 (20111123/tbutils-290)
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 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-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 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xc000-0xc0ff mem 0xa0000000-0xa7ffffff,0xc0000000-0xc000ffff irq 16 at device 0.0 on pci1
vgapci0: Boot video device
vgapci1: <VGA-compatible display> mem 0xdfff0000-0xdfffffff at device 0.1 on pci1
uhci0: <Intel 82801JI (ICH10) USB controller USB-D> port 0xb800-0xb81f irq 16 at device 26.0 on pci0
uhci0: LegSup = 0x2f00
usbus0 on uhci0
uhci1: <Intel 82801JI (ICH10) USB controller USB-E> port 0xb880-0xb89f irq 21 at device 26.1 on pci0
uhci1: LegSup = 0x2f00
usbus1 on uhci1
uhci2: <Intel 82801JI (ICH10) USB controller USB-F> port 0xbc00-0xbc1f irq 18 at device 26.2 on pci0
uhci2: LegSup = 0x2f00
usbus2 on uhci2
ehci0: <Intel 82801JI (ICH10) USB 2.0 controller USB-B> mem 0xbffffc00-0xbfffffff irq 18 at device 26.7 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci0
pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
pci4: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 17 at device 28.4 on pci0
pci3: <ACPI PCI bus> on pcib3
atapci0: <Marvell 88SE6121 UDMA133 controller> port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f mem 0xfebffc00-0xfebfffff irq 16 at device 0.0 on pci3
ahci0: <Marvell 88SE6121 AHCI SATA controller> at channel -1 on atapci0
ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported
ahci0: quirks=0x455<NOFORCE,NONCQ,2CH,EDGEIS,NOCOUNT>
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ata2: <ATA channel> at channel 0 on atapci0
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0
pci2: <ACPI PCI bus> on pcib4
ale0: <Atheros AR8121/AR8113/AR8114 PCIe Ethernet> port 0xdc00-0xdc7f mem 0xfeac0000-0xfeafffff irq 17 at device 0.0 on pci2
ale0: 960 Tx FIFO, 1024 Rx FIFO
ale0: Using 1 MSI messages.
miibus0: <MII bus> on ale0
atphy0: <Atheros F1 10/100/1000 PHY> PHY 0 on miibus0
atphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
ale0: Ethernet address: 00:22:15:3c:72:d9
uhci3: <Intel 82801JI (ICH10) USB controller USB-A> port 0xb080-0xb09f irq 23 at device 29.0 on pci0
uhci3: LegSup = 0x2f00
usbus4 on uhci3
uhci4: <Intel 82801JI (ICH10) USB controller USB-B> port 0xb400-0xb41f irq 19 at device 29.1 on pci0
uhci4: LegSup = 0x2f00
usbus5 on uhci4
uhci5: <Intel 82801JI (ICH10) USB controller USB-C> port 0xb480-0xb49f irq 18 at device 29.2 on pci0
uhci5: LegSup = 0x2f00
usbus6 on uhci5
ehci1: <Intel 82801JI (ICH10) USB 2.0 controller USB-A> mem 0xbffff800-0xbffffbff irq 23 at device 29.7 on pci0
usbus7: EHCI version 1.0
usbus7 on ehci1
pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci5: <ACPI PCI bus> on pcib5
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci1: <Intel ICH10 AHCI SATA controller> port 0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0xa400-0xa41f mem 0xbfffe800-0xbfffefff irq 19 at device 31.2 on pci0
ahci1: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported
ahcich2: <AHCI channel> at channel 0 on ahci1
ahcich3: <AHCI channel> at channel 1 on ahci1
ahcich4: <AHCI channel> at channel 2 on ahci1
ahcich5: <AHCI channel> at channel 3 on ahci1
ahcich6: <AHCI channel> at channel 4 on ahci1
ahcich7: <AHCI channel> at channel 5 on ahci1
acpi_button0: <Power Button> on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ichwd0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xccfff,0xcd000-0xcf7ff on isa0
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
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
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: 12Mbps Full Speed USB v1.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: 12Mbps Full Speed USB v1.0
usbus7: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen3.1: <Intel> at usbus3
uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3
ugen4.1: <Intel> at usbus4
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ugen5.1: <Intel> at usbus5
uhub5: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
ugen6.1: <Intel> at usbus6
uhub6: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6
ugen7.1: <Intel> at usbus7
uhub7: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus7
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub5: 2 ports with 2 removable, self powered
uhub6: 2 ports with 2 removable, self powered
uhub3: 6 ports with 6 removable, self powered
uhub7: 6 ports with 6 removable, self powered
ugen7.2: <vendor 0x0951> at usbus7
umass0: <vendor 0x0951 product 0x1666, class 0/0, rev 2.10/1.00, addr 2> on usbus7
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:10:0:-1: Attached to scbus10
ugen7.3: <Kingston> at usbus7
umass1: <Kingston DataTraveler 3.0, class 0/0, rev 2.10/1.00, addr 3> on usbus7
umass1:  SCSI over Bulk-Only; quirks = 0x8100
umass1:11:1:-1: Attached to scbus11
ahcich0: Timeout on slot 0 port 15
ahcich0: is 00000000 cs 00000001 ss 00000000 rs 00000001 tfd f10050 serr 00000000 cmd 10040017
(aprobe0:ahcich0:0:15:0): READ_BUFFER/PM. ACB: e4 01 00 00 00 0f 00 00 00 00 00 00
(aprobe0:ahcich0:0:15:0): CAM status: Command timeout
(aprobe0:ahcich0:0:15:0): Error 5, Retry was blocked
pmp0 at ahcich0 bus 0 scbus0 target 15 lun 0
pmp0: <Port Multiplier 57231095 2106> ATA-0 device
pmp0: 300.000MB/s transfers (SATA 2.x, NONE, PIO 8192bytes)
pmp0: 2 fan-out ports
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD20EFRX-68AX9N0 80.00A80> ATA-9 SATA 3.x device
ada0: Serial Number WD-WMC301092743
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada0: quirks=0x1<4K>
ada0: Previously was known as ad4
ada1 at ahcich0 bus 0 scbus0 target 1 lun 0
ada1: <WDC WD20EFRX-68AX9N0 80.00A80> ATA-9 SATA 3.x device
ada1: Serial Number WD-WMC300789297
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad5
ada2 at ahcich2 bus 0 scbus3 target 0 lun 0
ada2: <ST2000DL001-9VT156 CC43> ATA-8 SATA 2.x device
ada2: Serial Number 5YD55ASK
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 ad10
ada3 at ahcich3 bus 0 scbus4 target 0 lun 0
ada3: <ST2000DL001-9VT156 CC43> ATA-8 SATA 2.x device
ada3: Serial Number 6YD12GZ6
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 ad12
ada4 at ahcich4 bus 0 scbus5 target 0 lun 0
ada4: <ST2000DL001-9VT156 CC43> ATA-8 SATA 2.x device
ada4: Serial Number 5YD5GLSQ
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 ad14
ada5 at ahcich5 bus 0 scbus6 target 0 lun 0
ada5: <WDC WD20EFRX-68EUZN0 80.00A80> ATA-9 SATA 3.x device
ada5: Serial Number WD-WMC4M3237450
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 ad16
ada6 at ahcich6 bus 0 scbus7 target 0 lun 0
ada6: <WDC WD20EFRX-68AX9N0 80.00A80> ATA-9 SATA 3.x device
ada6: Serial Number WD-WMC301119833
ada6: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada6: Command Queueing enabled
ada6: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada6: quirks=0x1<4K>
ada6: Previously was known as ad18
ada7 at ahcich7 bus 0 scbus8 target 0 lun 0
ada7: <WDC WD20EFRX-68AX9N0 80.00A80> ATA-9 SATA 3.x device
ada7: Serial Number WD-WMC301119714
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 ad20
da0 at umass-sim0 bus 0 scbus10 target 0 lun 0
da0: <Kingston DataTraveler 3.0 PMAP> Removable Direct Access SCSI-6 device
da0: Serial Number 6B0DAB4049C9
da0: 40.000MB/s transfers
da0: 7640MB (15646720 512 byte sectors: 255H 63S/T 973C)
da0: quirks=0x2<NO_6_BYTE>
da1 at umass-sim1 bus 1 scbus11 target 0 lun 0
da1: <Kingston DataTraveler 3.0 PMAP> Removable Direct Access SCSI-6 device
da1: Serial Number 60A44C4138D8EE41097826AE
da1: 40.000MB/s transfers
da1: 14992MB (30703616 512 byte sectors: 255H 63S/T 1911C)
da1: quirks=0x2<NO_6_BYTE>
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1466750505 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-9.3-STABLE-201604041648 []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
vboxdrv: fAsync=0 offMin=0x294 offMax=0x932


Dmesg (Freenas 9.10)
Code:
Copyright (c) 1992-2016 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 10.3-RELEASE #0 1b72f49(freebsd10): Mon Apr 11 10:51:27 PDT 2016
    root@build.ixsystems.com:/tank/home/nightlies/build-

freenas9/_BE/objs/tank/home/nightlies/build-freenas9/_BE/trueos/sys/FreeNAS.amd64

amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz (2933.49-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x1067a  Family=0x6  Model=0x17  Stepping=10

Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,

PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>

Features2=0xc08e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1

,XSAVE,OSXSAVE>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  VT-x: HLT,PAUSE
  TSC: P-state invariant, performance statistics
real memory  = 10200547328 (9728 MB)
avail memory = 8244965376 (7863 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <A_M_I_ OEMAPIC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
random: <Software, Yarrow> initialized
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: No AESNI support.
padlock0: No ACE support.
acpi0: <A_M_I_ OEMXSDT> on motherboard
acpi0: Power Button (fixed)
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 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-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 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xc000-0xc0ff mem 0xa0000000-

0xa7ffffff,0xc0000000-0xc000ffff irq 16 at device 0.0 on pci1
vgapci0: Boot video device
vgapci1: <VGA-compatible display> mem 0xdfff0000-0xdfffffff at device 0.1 on pci1
uhci0: <Intel 82801JI (ICH10) USB controller USB-D> port 0xb800-0xb81f irq 16 at

device 26.0 on pci0
uhci0: LegSup = 0x2f00
usbus0 on uhci0
uhci1: <Intel 82801JI (ICH10) USB controller USB-E> port 0xb880-0xb89f irq 21 at

device 26.1 on pci0
uhci1: LegSup = 0x2f00
usbus1 on uhci1
uhci2: <Intel 82801JI (ICH10) USB controller USB-F> port 0xbc00-0xbc1f irq 18 at

device 26.2 on pci0
uhci2: LegSup = 0x2f00
usbus2 on uhci2
ehci0: <Intel 82801JI (ICH10) USB 2.0 controller USB-B> mem 0xbffffc00-0xbfffffff

irq 18 at device 26.7 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci0
pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
pci4: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 17 at device 28.4 on pci0
pci3: <ACPI PCI bus> on pcib3
atapci0: <Marvell 88SE6121 UDMA133 controller> port 0xec00-0xec07,0xe880-

0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f mem 0xfebffc00-0xfebfffff irq 16

at device 0.0 on pci3
ahci0: <Marvell 88SE6121 AHCI SATA controller> at channel -1 on atapci0
ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier not supported
ahci0: quirks=0x457<NOFORCE,NOPMP,NONCQ,2CH,EDGEIS,NOCOUNT>
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ata2: <ATA channel> at channel 0 on atapci0
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0
pci2: <ACPI PCI bus> on pcib4
ale0: <Atheros AR8121/AR8113/AR8114 PCIe Ethernet> port 0xdc00-0xdc7f mem

0xfeac0000-0xfeafffff irq 17 at device 0.0 on pci2
ale0: 960 Tx FIFO, 1024 Rx FIFO
ale0: Using 1 MSI messages.
miibus0: <MII bus> on ale0
atphy0: <Atheros F1 10/100/1000 PHY> PHY 0 on miibus0
atphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX,

1000baseT-FDX-master, auto, auto-flow
ale0: Using defaults for TSO: 65518/35/2048
ale0: Ethernet address: 00:22:15:3c:72:d9
uhci3: <Intel 82801JI (ICH10) USB controller USB-A> port 0xb080-0xb09f irq 23 at

device 29.0 on pci0
uhci3: LegSup = 0x2f00
usbus4 on uhci3
uhci4: <Intel 82801JI (ICH10) USB controller USB-B> port 0xb400-0xb41f irq 19 at

device 29.1 on pci0
uhci4: LegSup = 0x2f00
usbus5 on uhci4
uhci5: <Intel 82801JI (ICH10) USB controller USB-C> port 0xb480-0xb49f irq 18 at

device 29.2 on pci0
uhci5: LegSup = 0x2f00
usbus6 on uhci5
ehci1: <Intel 82801JI (ICH10) USB 2.0 controller USB-A> mem 0xbffff800-0xbffffbff

irq 23 at device 29.7 on pci0
usbus7: EHCI version 1.0
usbus7 on ehci1
pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci5: <ACPI PCI bus> on pcib5
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci1: <Intel ICH10 AHCI SATA controller> port 0xac00-0xac07,0xa880-0xa883,0xa800

-0xa807,0xa480-0xa483,0xa400-0xa41f mem 0xbfffe800-0xbfffefff irq 19 at device

31.2 on pci0
ahci1: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported
ahcich2: <AHCI channel> at channel 0 on ahci1
ahcich3: <AHCI channel> at channel 1 on ahci1
ahcich4: <AHCI channel> at channel 2 on ahci1
ahcich5: <AHCI channel> at channel 3 on ahci1
ahcich6: <AHCI channel> at channel 4 on ahci1
ahcich7: <AHCI channel> at channel 5 on ahci1
acpi_button0: <Power Button> on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ichwd0: <Intel ICH10R watchdog timer> on isa0
wbwd0: <Winbond 83667HG (0xa5/0x13) Watchdog Timer> at port 0x2e-0x2f on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xccfff,0xcd000-0xcf7ff on isa0
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]
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
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
random: unblocking device.
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.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: 12Mbps Full Speed USB v1.0
usbus7: 480Mbps High Speed USB v2.0
ugen5.1: <Intel> at usbus5
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
ugen4.1: <Intel> at usbus4
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ugen3.1: <Intel> at usbus3
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3
ugen2.1: <Intel> at usbus2
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen1.1: <Intel> at usbus1
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen0.1: <Intel> at usbus0
uhub5: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen7.1: <Intel> at usbus7
uhub6: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus7
ugen6.1: <Intel> at usbus6
uhub7: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6
uhub1: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
uhub5: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub7: 2 ports with 2 removable, self powered
uhub2: 6 ports with 6 removable, self powered
uhub6: 6 ports with 6 removable, self powered
ugen7.2: <Kingston> at usbus7
umass0: <Kingston DataTraveler 3.0, class 0/0, rev 2.10/1.00, addr 2> on usbus7
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:10:0:-1: Attached to scbus10
ugen7.3: <Kingston> at usbus7
umass1: <Kingston DataTraveler 3.0, class 0/0, rev 2.10/1.00, addr 3> on usbus7
umass1:  SCSI over Bulk-Only; quirks = 0x8100
umass1:11:1:-1: Attached to scbus11
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD20EFRX-68AX9N0 80.00A80> ACS-2 ATA SATA 3.x device
ada0: Serial Number WD-WMC301092743
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: 1907729MB (3907029168 512 byte sectors)
ada0: quirks=0x1<4K>
ada0: Previously was known as ad4
ada1 at ahcich2 bus 0 scbus3 target 0 lun 0
ada1: <ST2000DL001-9VT156 CC43> ATA8-ACS SATA 2.x device
ada1: Serial Number 5YD55ASK
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad10
ada2 at ahcich3 bus 0 scbus4 target 0 lun 0
ada2: <ST2000DL001-9VT156 CC43> ATA8-ACS SATA 2.x device
ada2: Serial Number 6YD12GZ6
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors)
ada2: quirks=0x1<4K>
ada2: Previously was known as ad12
ada3 at ahcich4 bus 0 scbus5 target 0 lun 0
ada3: <ST2000DL001-9VT156 CC43> ATA8-ACS SATA 2.x device
ada3: Serial Number 5YD5GLSQ
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 1907729MB (3907029168 512 byte sectors)
ada3: quirks=0x1<4K>
ada3: Previously was known as ad14
ada4 at ahcich5 bus 0 scbus6 target 0 lun 0
ada4: <WDC WD20EFRX-68EUZN0 80.00A80> ACS-2 ATA SATA 3.x device
ada4: Serial Number WD-WMC4M3237450
ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada4: Command Queueing enabled
ada4: 1907729MB (3907029168 512 byte sectors)
ada4: quirks=0x1<4K>
ada4: Previously was known as ad16
ada5 at ahcich6 bus 0 scbus7 target 0 lun 0
ada5: <WDC WD20EFRX-68AX9N0 80.00A80> ACS-2 ATA SATA 3.x device
ada5: Serial Number WD-WMC301119833
ada5: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada5: Command Queueing enabled
ada5: 1907729MB (3907029168 512 byte sectors)
ada5: quirks=0x1<4K>
ada5: Previously was known as ad18
ada6 at ahcich7 bus 0 scbus8 target 0 lun 0
ada6: <WDC WD20EFRX-68AX9N0 80.00A80> ACS-2 ATA SATA 3.x device
ada6: Serial Number WD-WMC301119714
ada6: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada6: Command Queueing enabled
ada6: 1907729MB (3907029168 512 byte sectors)
ada6: quirks=0x1<4K>
ada6: Previously was known as ad20
da0 at umass-sim0 bus 0 scbus10 target 0 lun 0
da0: <Kingston DataTraveler 3.0 PMAP> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 60A44C3FAC04BDB0997A0B6E
da0: 40.000MB/s transfers
da0: 7640MB (15646720 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
da1 at umass-sim1 bus 1 scbus11 target 0 lun 0
da1: <Kingston DataTraveler 3.0 PMAP> Removable Direct Access SPC-4 SCSI device
da1: Serial Number 60A44C4138D8EE41097826AE
da1: 40.000MB/s transfers
da1: 14992MB (30703616 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1466747023 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-

e9dd2aa0c143ea7cdbe91aaee021959e []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA>

IAP/2/40/0x3ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA,PRC>

IAF/3/40/0x67<INT,USR,SYS,REA,WRI>
ale0: link state changed to DOWN
ale0: link state changed to UP
vboxdrv: fAsync=0 offMin=0x294 offMax=0xb63


Difference:
Code:
ahci0: <Marvell 88SE6121 AHCI SATA controller> at channel -1 on atapci0
ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported
ahci0: quirks=0x455<NOFORCE,NONCQ,2CH,EDGEIS,NOCOUNT>
Changed to:
ahci0: <Marvell 88SE6121 AHCI SATA controller> at channel -1 on atapci0
ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier not supported
ahci0: quirks=0x457<NOFORCE,NOPMP,NONCQ,2CH,EDGEIS,NOCOUNT>

Port Multiplier supported -> Port Multiplier not supported

Is there something I can do?

Do you need more information to resolve the issue?

Currently the system works nicely with version 9.3 and running scrub (8h 11m to go) to get everything back to the state before the upgrade.

---
Update
Made ticket 14655
 
Last edited:
D

dlavigne

Guest
Note that this forum is for discussing (not reporting) possible bugs.

Please create the actual bug report at bugs.freenas.org and post the issue number here.
 

Purkki

Dabbler
Joined
Apr 13, 2016
Messages
10
Made ticket 14655


Code:
FreeBSD 10.3-RELEASE #0 1b72f49(freebsd10): Mon Apr 11 10:51:27 PDT 2016
    root@build.ixsystems.com:/tank/home/nightlies/build-

Also I started to wonder from the dmesg logs that did FreeNAS upgrade itself from 9.3 to 9.10 or somehow 10 nightlies...
 
Last edited by a moderator:

Purkki

Dabbler
Joined
Apr 13, 2016
Messages
10
I updated to Build FreeNAS-9.10-STABLE-201604181743 (74ef270)
Booted, the Freenas sees only 1 drive in the Marwell controller.

Changed:

Tunables -> Add Tunable:
Variable: hint.ahci.0.quirks
Value: 0x49
Type: Loader
Enabled: YES

After reboot Freenas does not see any hard drive on he Marwell controller.

ahci0: <Marvell 88SE6121 AHCI SATA controller> at channel -1 on atapci0
ahci0: AHCI v1.00 with 1 3Gbps ports, Port Multiplier supported
ahci0: quirks=0x49<NOFORCE,1CH,EDGEIS>
ahcich0: <AHCI channel> at channel 0 on ahci0

More info on: https://bugs.freenas.org/issues/14655

Is there something I am doing wrong or is there something wrong with the fix?
How do I reopen the ticket (if needed)?
 

pvanulden

Cadet
Joined
Nov 23, 2012
Messages
8
Purkki, did you ever get this resolved?
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
TBH, I am actually surprised that the devs even considered attempting to provide a solution for this board.
It is more of a desktop board that is not at all a good choice for FreeNAS:
  • Does not support ECC RAM
  • Has the janky old Marvell controller
  • Has FSB
 

pvanulden

Cadet
Joined
Nov 23, 2012
Messages
8
For the record, I upgraded from 9.2.1 to 9.10 over the weekend. I didn't have any issues with FreeNAS picking up my drives.
 

Purkki

Dabbler
Joined
Apr 13, 2016
Messages
10
Purkki, did you ever get this resolved?

Sorry no :( , but I would like to have the issue resolved.

TBH, I am actually surprised that the devs even considered attempting to provide a solution for this board.
It is more of a desktop board that is not at all a good choice for FreeNAS:
  • Does not support ECC RAM
  • Has the janky old Marvell controller
  • Has FSB

Its a home system, worked nicely for years and the board suits it purpose just fine.

I have been very happy with this system and it has inspired me to use Freenas/Truenas in corporate use as well, where the hardware is better, but if hardware problems occur and the support is like this my view with expanding corporate use is going to be changed.

There is another problem with Freenas https://forums.freenas.org/index.ph...9-10-worked-on-9-3-stable-201602031011.42491/ that affects specially corporate use and is not resolved as well.
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
TBH, I am actually surprised that the devs even considered attempting to provide a solution for this board.
It is more of a desktop board that is not at all a good choice for FreeNAS:
  • Does not support ECC RAM
  • Has the janky old Marvell controller
  • Has FSB
I agree. This hardware is much too old, and much too bad of a choice, really, for a FreeNAS, for anyone to lose sleep over it. I know the gentleman had a working system before on 9.3 et al, but, I mean, we're talking about a board so old it has DDR2 RAM, it is clearly a poor choice for a FreeNAS server, it has a front-side bus, we do not suggest anyone use "port multipliers" of any type. Can't run ECC RAM... I mean...? If you are running your FreeNAS on old deprecated hardware in order to save a few hundred euros, then I suppose you are rolling the dice. The devs are already much too busy with making sure everything is working on recommended hardware configurations...

My recommendation is that the devs not attempt to solve this, and that this gentleman revert to the last-known working condition, which was FreeNAS 9.3. My respects, however, to our Finnish friend Purkki.
 

Purkki

Dabbler
Joined
Apr 13, 2016
Messages
10
I agree. This hardware is much too old, and much too bad of a choice, really, for a FreeNAS, for anyone to lose sleep over it. I know the gentleman had a working system before on 9.3 et al, but, I mean, we're talking about a board so old it has DDR2 RAM, it is clearly a poor choice for a FreeNAS server, it has a front-side bus, we do not suggest anyone use "port multipliers" of any type. Can't run ECC RAM... I mean...? If you are running your FreeNAS on old deprecated hardware in order to save a few hundred euros, then I suppose you are rolling the dice. The devs are already much too busy with making sure everything is working on recommended hardware configurations...

My recommendation is that the devs not attempt to solve this, and that this gentleman revert to the last-known working condition, which was FreeNAS 9.3. My respects, however, to our Finnish friend Purkki.

This is probably my waste of time..

I do understand that not being ECC can cause problems, but whats problem with DDR2? Because newer memory techniques like DDR3 and DDR4 have shown problems as well like: https://en.wikipedia.org/wiki/Row_hammer

If the hardware has worked problem free since Freenas 8, I don't understand how it can be considered too old/bad.
Sure Marvell controllers have a bad reputation, but sadly those controllers are used also on many high end server hardware. And because of this I am really worried about the attitude of not fixing something that used to work well in the past.

And If I have understood the problem correctly the error was made in FreeBSD kernel development? If FreeNAS devs are unable to correct this, can the FreeBSD kernel devs handle it? Could you please forward the problem to them?
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
There is no problem with DDR2. My point was simply that anything with DDR2 in it is hardware from quite a long time ago, measured in computer time.

FreeNAS does not necessarily go out of its way to maintain compatibility with very old hardware, and it (or, FreeBSD) is notoriously finicky when it comes to HBA's, SATA port expanders, etc. This kind of thing. And especially Marvel. If you would like, you can fill out a bug report in bugs.freenas.org; maybe someone who had a similar problem might chime in with a solution.
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
There is no problem with DDR2. My point was simply that anything with DDR2 in it is hardware from quite a long time ago, measured in computer time.

FreeNAS does not necessarily go out of its way to maintain compatibility with very old hardware, and it (or, FreeBSD) is notoriously finicky when it comes to HBA's, SATA port expanders, etc. This kind of thing. And especially Marvel. If you would like, you can fill out a bug report in bugs.freenas.org; maybe someone who had a similar problem might chime in with a solution.
Also, FreeNAS 9.3.1 is wonderful. There is nothing wrong with staying on that. We have (lots of) users still on 9.2.x because their hardware was getting a bit old.
 

pirateghost

Unintelligible Geek
Joined
Feb 29, 2012
Messages
4,219
This is probably my waste of time..

I do understand that not being ECC can cause problems, but whats problem with DDR2? Because newer memory techniques like DDR3 and DDR4 have shown problems as well like: https://en.wikipedia.org/wiki/Row_hammer

If the hardware has worked problem free since Freenas 8, I don't understand how it can be considered too old/bad.
Sure Marvell controllers have a bad reputation, but sadly those controllers are used also on many high end server hardware. And because of this I am really worried about the attitude of not fixing something that used to work well in the past.

And If I have understood the problem correctly the error was made in FreeBSD kernel development? If FreeNAS devs are unable to correct this, can the FreeBSD kernel devs handle it? Could you please forward the problem to them?

If you want to alert FreeBSD devs of an issue, you should take the initiative to submit it yourself. Then you can follow the progress. Having someone else do it for you is just plain lazy.


And please tell me what high end server hardware uses Marvell controller? I want to make sure I don't give them any of my company's business.
 
Status
Not open for further replies.
Top