On Friday, 30 May 2025 02:25:03 British Summer Time Dale wrote:
> Howdy,
>
> Same thing just a new drive. I got a new 20TB drive in, same as last
> one in this thread. This is what I get from it.
>
>
> May 29 19:06:52 Gentoo-1 kernel: ata4: found unknown device (class 0)
> May 29 19:07:02 Gentoo-1 kernel: ata4: softreset failed (1st FIS failed)
> May 29 19:07:02 Gentoo-1 kernel: ata4: found unknown device (class 0)
> May 29 19:07:12 Gentoo-1 kernel: ata4: softreset failed (1st FIS failed)
> May 29 19:07:12 Gentoo-1 kernel: ata4: found unknown device (class 0)
> May 29 19:07:17 Gentoo-1 kernel: ata4: found unknown device (class 0)
> May 29 19:07:17 Gentoo-1 kernel: ata4: SATA link up 1.5 Gbps (SStatus
> 113 SControl 330)
> May 29 19:07:17 Gentoo-1 kernel: ata4: link online but 1 devices
> misclassified, retrying
> May 29 19:07:17 Gentoo-1 kernel: ata4: reset failed (errno=-11),
> retrying in 30 secs
> May 29 19:07:47 Gentoo-1 kernel: ata4: SATA link up 1.5 Gbps (SStatus
> 113 SControl 330)
> May 29 19:07:48 Gentoo-1 kernel: ata4.00: ATA-11: ST20000NM007D-3DJ103,
> SN05, max UDMA/133
> May 29 19:07:48 Gentoo-1 kernel: ata4.00: 39063650304 sectors, multi 16:
> LBA48 NCQ (depth 32), AA
> May 29 19:07:48 Gentoo-1 kernel: ata4.00: Features: NCQ-sndrcv
> May 29 19:07:48 Gentoo-1 kernel: ata4.00: configured for UDMA/133
> May 29 19:07:48 Gentoo-1 kernel: scsi 3:0:0:0: Direct-Access
> ATA ST20000NM007D-3D SN05 PQ: 0 ANSI: 5
> May 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: Attached scsi generic sg9
> type 0
> May 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: [sdi] 39063650304 512-byte
> logical blocks: (20.0 TB/18.2 TiB)
> May 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: [sdi] 4096-byte physical blocks
> May 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: [sdi] Write Protect is off May
> 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: [sdi] Mode Sense: 00 3a 00 00 May
> 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: [sdi] Write cache: enabled, read
> cache: enabled, doesn't support DPO or FUA
> May 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: [sdi] Preferred minimum I/O
> size 4096 bytes
> May 29 19:07:48 Gentoo-1 kernel: sd 3:0:0:0: [sdi] Attached SCSI
> removable disk
>
>
> And hdparm -I shows this.
>
>
> root@Gentoo-1 / # hdparm -I dev/sdi
>
> dev/sdi:
>
> ATA device, with non-removable media
> Model Number: ST20000NM007D-3DJ103
> Serial Number: ZVT3ANGK
> Firmware Revision: SN05
> Transport: Serial, ATA8-AST, SATA 1.0a, SATA II
> Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
> Standards:
> Used: unknown (minor revision code 0xffff)
> Supported: 11 10 9 8 7 6 5
> Likely used: 11
> Configuration:
> Logical max current
> cylinders 16383 16383
> heads 16 16
> sectors/track 63 63
> --
> CHS current addressable sectors: 16514064
> LBA user addressable sectors: 268435455
> LBA48 user addressable sectors: 39063650304
> Logical Sector size: 512 bytes [ Supported:
> 512 4096 ]
> Physical Sector size: 4096 bytes
> Logical Sector-0 offset: 0 bytes
> device size with M = 1024*1024: 19074048 MBytes
> device size with M = 1000*1000: 20000588 MBytes (20000 GB)
> cache/buffer size = unknown
> Form Factor: 3.5 inch
> Nominal Media Rotation Rate: 7200
> Capabilities:
> LBA, IORDY(can be disabled)
> Queue depth: 32
> Standby timer values: spec'd by Standard, no device specific minimum
> R/W multiple sector transfer: Max = 16 Current = 16
> Recommended acoustic management value: 254, current value: 0
> DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> Cycle time: min=120ns recommended=120ns
> PIO: pio0 pio1 pio2 pio3 pio4
> Cycle time: no flow control=120ns IORDY flow control=120ns
> Commands/features:
> Enabled Supported:
> * SMART feature set
> Security Mode feature set
> * Power Management feature set
> * Write cache
> * Look-ahead
> * WRITE_BUFFER command
> * READ_BUFFER command
> * DOWNLOAD_MICROCODE
> Power-Up In Standby feature set
> * SET_FEATURES required to spinup after power up
> SET_MAX security extension
> * 48-bit Address feature set
> * Mandatory FLUSH_CACHE
> * FLUSH_CACHE_EXT
> * SMART error logging
> * SMART self-test
> * Media Card Pass-Through
> * General Purpose Logging feature set
> * WRITE_{DMA|MULTIPLE}_FUA_EXT
> * 64-bit World wide name
> * IDLE_IMMEDIATE with UNLOAD
> Write-Read-Verify feature set
> * WRITE_UNCORRECTABLE_EXT command
> * {READ,WRITE}_DMA_EXT_GPL commands
> * Segmented DOWNLOAD_MICROCODE
> * unknown 119[6]
> * unknown 119[7]
> unknown 119[8]
> unknown 119[9]
> * Gen1 signaling speed (1.5Gb/s)
> * Gen2 signaling speed (3.0Gb/s)
> * Gen3 signaling speed (6.0Gb/s)
> * Native Command Queueing (NCQ)
> * Phy event counters
> * Idle-Unload when NCQ is active
> * READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
> * DMA Setup Auto-Activate optimization
> Device-initiated interface power management
> * Software settings preservation
> unknown 78[7]
> * SMART Command Transport (SCT) feature set
> * SCT Write Same (AC2)
> * SCT Error Recovery Control (AC3)
> * SCT Features Control (AC4)
> * SCT Data Tables (AC5)
> unknown 206[7]
> unknown 206[12] (vendor specific)
> unknown 206[13] (vendor specific)
> unknown 206[14] (vendor specific)
> * SANITIZE_ANTIFREEZE_LOCK_EXT command
> * SANITIZE feature set
> * OVERWRITE_EXT command
> * All write cache is non-volatile
> * Extended number of user addressable sectors
> <<< SNIP >>>
> Checksum: correct
> root@Gentoo-1 / #
>
>
> According to that, it is connected at udma6 which is the fastest. So
> that is good, I guess. Since both drives is slow to connect, it seems
> this is a trend and may just be normal for these drives. Given I use
> these for data that is only put in use a few minutes after booting,
> which gives it plenty of time to connect properly, then it isn't a
> problem for me. I just wouldn't want to try to put a OS on the thing
> and boot from it.
>
> Any one else have different thoughts? See a problem that is a trend, in
> a bad way? Given two different drives has the same slow connect time,
> maybe it is normal.
>
> By the way, I have data on the first 20TB drive and it has worked fine
> so far. I've had to reboot a couple times and by the time the system
> comes up, I login, KDE comes up and I get to a Konsole to unlock the
> encrypted drives, they are ready. I'd guess it takes at least three
> minutes from power up until I unlock the drives. This is likely shorter
> if I put one of these drives on the NAS box, no GUI on it. Still, I
> give it plenty of time to come up before even ssh'ing into the box much
> less unlocking it.
>
> Dale
>
> :-) :-) You can transfer some data from a tmpfs and measure the speed. If it gets anywhere near 4.8 Gbit/s (600 MB/s) its a SATA 3. The delay in the kernel picking it up at boot may be related to its size, but I have no experience of such large drives to be able to confirm this.
signature.asc
Description: This is a digitally signed message part.
