It was a figurative "we" but you're right. I still have the
truss log file and the Toshiba drive which I can install into the HP system - I already said that I have tested it in the HP system and
pkg behaved the same, it was slow - and "we" can give this another try if you're interested.
Talking about problems, it seems I have another one. I said that in the current system I have 4 HDDs and one of those (the Toshiba drive) was replaced with a Hitachi drive with FreeBSD on it.
Well, this Hitachi drive is identical to a drive from those 4 - another Hitachi which has a Windows installation on it.
And when I say "identical", they really are - down to brand, model and firmware revision.
Here is the Hitachi drive with Windows (
ada2):
Code:
# camcontrol identify ada2
pass2: <HUA723020ALA640> ATA8-ACS SATA 3.x device
pass2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
protocol ATA8-ACS SATA 3.x
device model HUA723020ALA640
firmware revision
serial number
additional product id
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported 3907029168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200
Zoned-Device Commands no
Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
Native Command Queuing (NCQ) yes 32 tags
NCQ Priority Information yes
NCQ Non-Data Command no
NCQ Streaming no
Receive & Send FPDMA Queued no
NCQ Autosense no
SMART yes yes
security yes no
power management yes yes
microcode download yes yes
advanced power management yes no 0/0x00
automatic acoustic management no no
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload no no
general purpose logging yes yes
free-fall no no
sense data reporting no no
extended power conditions yes yes
device statistics notification no no
Data Set Management (DSM/TRIM) no
Trusted Computing no
encrypts all user data no
Sanitize no
Host Protected Area (HPA) yes no 3907029168/3907029167
HPA - Security yes no
Accessible Max Address Config no
And here is the Hitachi drive with FreeBSD (
ada3):
Code:
# camcontrol identify ada3
pass3: <HUA723020ALA640> ATA8-ACS SATA 2.x device
pass3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
protocol ATA8-ACS SATA 2.x
device model HUA723020ALA640
firmware revision
serial number
additional product id
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported 3907029168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200
Zoned-Device Commands no
Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
Native Command Queuing (NCQ) yes 32 tags
NCQ Priority Information yes
NCQ Non-Data Command no
NCQ Streaming no
Receive & Send FPDMA Queued no
NCQ Autosense no
SMART yes yes
security yes no
power management yes yes
microcode download yes yes
advanced power management yes no 0/0x00
automatic acoustic management no no
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload no no
general purpose logging yes yes
free-fall no no
sense data reporting no no
extended power conditions yes yes
device statistics notification no no
Data Set Management (DSM/TRIM) no
Trusted Computing no
encrypts all user data no
Sanitize no
Host Protected Area (HPA) yes no 3907029168/3907029167
HPA - Security yes no
Accessible Max Address Config no
Do you spot the problem? Despite of these drives being identical, down to the firmware revision, one of them (with Windows) is seen as being a SATA 3 (600 MB/s) device while the other (with FreeBSD on it) is seen as if it's a SATA 2 device (300 MB/s).
I have swapped physical SATA ports but no change, there is still this difference. I also changed the SATA cables, no dice.
My motherboard is a Gigabyte GA-970A-DS3P and according to its specs, all of its SATA ports are SATA 3, not a mix of SATA2/SATA3.
I really don't understand why is this difference.