On 2018-11-01 13:45, spaml...@mail-on.us wrote:
On 2018-11-01 03:59, Frank Leonhardt (M) wrote:
On 1 November 2018 05:14:35 GMT+00:00, spaml...@mail-on.us wrote:
Hi all,
I picked out, and put together some hardware for a new FreeBSD
powered box. I chose a WD blue drive I knew was pretty zippy.
But I was quite disappointed to discover that FreeBSD wouldn't
support it @6Gb.
The following output from dmesg(8):
GEOM: new disk ada0
ada0: <WDC WD10EZEX-75WN4A0 01.01A01> ACS-3 ATA SATA 3.x device
ada0: Serial Number WD-WCC6Y3CJCTDC
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 953869MB (1953525168 512 byte sectors)
My hardware supports it; both drive, and controller. Yet for
some reason FreeBSD will only *acknowledge* the capabilities.
Do I need to impose some quirk, or something.
Thanks!
That is saying it will do transfers at 300 Megabytes/second on the
interface. You'll be lucky to get that from a WD desktop drive due to
mechanical limitations. WD blues at 1Tb tend to do 125-150MBps tops,
and the range released a couple of years back (2015?) seem slower than
the previous generation, although the spindle speeds vary.
6G vs. 3G is only interesting talking to silicone drives or a SATA
expander.
But an interesting question - why does it say SATA2 instead of SATA3?
Thanks for your reply, Frank!
Be that as it may. As platters go. I bought this 1Tb WD blue, because
all
the stats for it indicated it was faster that all the major
competitors,
and interestingly, faster than their "high-end" Black counterpart. I
also
bought it, because it was quieter than all the others.
That said; given that the port it runs off of, and the drive is truly
a Sata 3 (3.1). Why won't FreeBSD treat it as such. Why does it
penalize
the drive?
I have another Sata 3 drive on the second Sata 3 port, that FreeBSD
actually treats as what it is:
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <ST3000DM001-1CH166 CC47> ACS-2 ATA SATA 3.x device
ada1: Serial Number W1F55VT9
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 2861588MB (5860533168 512 byte sectors)
ada1: quirks=0x1<4K>
Another point comes to mind. As Erich pointed out, changing cables about
randomly is a known trouble-shooting method, but the cables are
theoretically identical, and all good for 1m in length. *theoretically*.
But, SATA 3 is backwards compatible with SATA 2. This works by the
controller and the drive deciding whether both sides are SATA 3, and if
one disagrees they'll fall back to SATA 2 (or SATA 1). This could easily
be an incompatibility at the hardware level.
Have you checked that ALL the sockets on your motherboard are SATA 3?
It's quite possible there are some slower ones for attaching optical
drives etc. Is it restricted in the motherboard hardware settings?
(sometimes called BIOS settings).
Regards, Frank.
_______________________________________________
freebsd-hardware@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscr...@freebsd.org"
