From owner-freebsd-questions@freebsd.org Wed Nov 9 22:20:14 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53EE0C381BC for ; Wed, 9 Nov 2016 22:20:14 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from avasout07.plus.net (avasout07.plus.net [84.93.230.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E8D97145 for ; Wed, 9 Nov 2016 22:20:13 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk ([80.229.31.82]) by avasout07 with smtp id 5yL41u0031mJoLY01yL5KL; Wed, 09 Nov 2016 22:20:05 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.2 cv=TLMHcBta c=1 sm=1 tr=0 a=cd0K7rcWwnZFf6xQxRobyA==:117 a=cd0K7rcWwnZFf6xQxRobyA==:17 a=kj9zAlcOel0A:10 a=MKtGQD3n3ToA:10 a=L24OOQBejmoA:10 a=dik7HMQjudEA:10 a=ZZnuYtJkoWoA:10 a=OclBzrJlUodnP0v0DAwA:9 a=xy0um9MfbNtPLTsu:21 a=WbOuXFrl7zPjsaKA:21 a=CjuIK1q_8ugA:10 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.87) (envelope-from ) id 1c4bDv-00015n-3w for freebsd-questions@freebsd.org; Wed, 09 Nov 2016 22:20:04 +0000 Date: Wed, 9 Nov 2016 22:20:02 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Message-ID: <20161109222002.7995b1c9@curlew.lan> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: SSD drive appears to have been "downgraded" from SATA 2 to SATA 1 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 22:20:14 -0000 I have two allegedly identical SanDisk SATA 3 SSD drives connected to my SATA 2 motherboard as a ZFS mirror. One of these drives (ada2) is reported as running as SATA 2 as expected but the other (ada0) is only reported as SATA 1. I've swapped the drive connections and cables between the 2 SATA ports but the same drive still shows up as SATA 1 so I'm assuming the discrepancy lies with the drives and not the motherboard or drivers. Could there be any way that the system could at some time have forced the drive down to SATA 1, in which case how do I revert it? Or is it more likely that I have a faulty SSD drive? I'm including some relevant sections from dmesg and results from camcontrol identify below. atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xfe02c000-0xfe02cfff irq 21 at device 8.0 on pci0 ata2: at channel 0 on atapci1 ata3: at channel 1 on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xfe02b000-0xfe02bfff irq 22 at device 8.1 on pci0 ata4: at channel 0 on atapci2 ata5: at channel 1 on atapci2 ada0 at ata2 bus 0 scbus3 target 0 lun 0 ada0: ATA8-ACS SATA 3.x device ada0: Serial Number 133641400083 ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 512bytes) ada0: 122104MB (250069680 512 byte sectors) ada1 at ata3 bus 0 scbus4 target 0 lun 0 ada1: ATA8-ACS SATA 2.x device ada1: Serial Number 9VMA33V1 ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes) ada1: 476940MB (976773168 512 byte sectors) ada2 at ata4 bus 0 scbus5 target 0 lun 0 ada2: ATA8-ACS SATA 3.x device ada2: Serial Number 133641400601 ada2: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 512bytes) ada2: 122104MB (250069680 512 byte sectors) ada3 at ata5 bus 0 scbus6 target 0 lun 0 ada3: ATA8-ACS SATA 2.x device ada3: Serial Number 9VMA33C8 ada3: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes) ada3: 476940MB (976773168 512 byte sectors) curlew:/tmp# camcontrol identify ada0 pass1: ATA8-ACS SATA 3.x device pass1: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 512bytes) protocol ATA/ATAPI-8 SATA 3.x device model SanDisk SD6SB2M128G1022I firmware revision X210400 serial number 133641400083 WWN 5001b44a293aeb13 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 250069680 sectors LBA48 supported 250069680 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM non-rotating Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags NCQ Queue Management no NCQ Streaming no Receive & Send FPDMA Queued no SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 128/0x80 automatic acoustic management no no media status notification no no power-up in Standby no no write-read-verify no no unload no no general purpose logging yes yes free-fall no no Data Set Management (DSM/TRIM) yes DSM - max 512byte blocks yes 16 DSM - deterministic read yes zeroed Host Protected Area (HPA) yes no 250069680/250069680 HPA - Security no curlew:/tmp# camcontrol identify ada2 pass3: ATA8-ACS SATA 3.x device pass3: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 512bytes) protocol ATA/ATAPI-8 SATA 3.x device model SanDisk SD6SB2M128G1022I firmware revision X210400 serial number 133641400601 WWN 5001b44a293aed19 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 250069680 sectors LBA48 supported 250069680 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM non-rotating Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags NCQ Queue Management no NCQ Streaming no Receive & Send FPDMA Queued no SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 128/0x80 automatic acoustic management no no media status notification no no power-up in Standby no no write-read-verify no no unload no no general purpose logging yes yes free-fall no no Data Set Management (DSM/TRIM) yes DSM - max 512byte blocks yes 16 DSM - deterministic read yes zeroed Host Protected Area (HPA) yes no 250069680/250069680 HPA - Security no -- Mike Clarke