Recognizing SMR HDDs

[Gary Jennejohn]

Now that ken@ has checked in the SMR code I'm wondering how I can see
whether it's having any effect.

I have a 8TB SMR disk in a USB3 enclosure. Does the kernel emit any
sort of trace to indicate that it sees the drive as SMR and takes
that into account?

I have the probe trace enabled in my kernel config, but I don't see
anything special pop out when I turn the drive on.

Does the fact that the drive appears as a /dev/daX play any role?

BTW the disk returns an error when multiple LUNs are probed.

--
Gary Jennejohn
_______________________________________________
freebsd...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

[Peter Jeremy]

On 2016-May-26 08:42:53 +0200, Gary Jennejohn <gljen...@gmail.com> wrote:
>Now that ken@ has checked in the SMR code I'm wondering how I can see
>whether it's having any effect.

camcontrol(8) has been enhanced with SMR options and there's a new
zonectl(8) command - these should be able to report whether the drive
is recognized as a host-aware or host-managed SMR drive. I believe
that drive-managed SMR drives don't admit to anything.

>Does the fact that the drive appears as a /dev/daX play any role?

USB drives are handled via the SCSI CAM layer rather than as SATA
drives. It's possible that either the umass(4) driver or your USB
to SATA adapter are not correctly handling the relevant commands.

--
Peter Jeremy

[Kenneth D. Merry]

On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> Now that ken@ has checked in the SMR code I'm wondering how I can see
> whether it's having any effect.
>
> I have a 8TB SMR disk in a USB3 enclosure. Does the kernel emit any
> sort of trace to indicate that it sees the drive as SMR and takes
> that into account?

There is nothing extra emitted in the dmesg to tell you it is an SMR drive,
you have to look.

> I have the probe trace enabled in my kernel config, but I don't see
> anything special pop out when I turn the drive on.

You'll see extra states in the probe compared to a standard drive if it
is Host Aware or Host Managed. You won't see those states if it is Drive
Managed.

> Does the fact that the drive appears as a /dev/daX play any role?

It shouldn't matter. I put changes in both the da(4) and ada(4) drivers to
support SMR drives. And the changes should work even when you have an ATA
protocol drive attached via a SCSI transport. Which is likely the case
with your drive. What kind of drive is it?

Here are some things you can do on any disk to see what it is:

diskinfo -v /dev/daX

For example:

# diskinfo -v /dev/da18
/dev/da18
512 # sectorsize
8001563222016 # mediasize in bytes (7.3T)
15628053168 # mediasize in sectors
4096 # stripesize
0 # stripeoffset
972801 # Cylinders according to firmware.
255 # Heads according to firmware.
63 # Sectors according to firmware.
Z84003SK # Disk ident.
id1,enc@n5003048001f311fd/type@0/slot@13/elmdesc@Slot_19 #
Physical path
Host_Aware # Zone Mode

So this is a Host Aware drive.

zonectl -c params -d /dev/daX

# zonectl -c params -d /dev/da18
Zone Mode: Host Aware
Command support: Report Zones, Open, Close, Finish, Reset Write Pointer
Unrestricted Read in Sequential Write Required Zone (URSWRZ): No
Optimal Number of Open Sequential Write Preferred Zones: 128
Optimal Number of Non-Sequentially Written Sequential Write Preferred
Zones: 8
Maximum Number of Open Sequential Write Required Zones: Unlimited

If I issue the same command on a drive managed SMR drive:

# zonectl -c params -d /dev/da19
Zone Mode: Drive Managed
Command support: None
Unrestricted Read in Sequential Write Required Zone (URSWRZ): No
Optimal Number of Open Sequential Write Preferred Zones: Not Set
Optimal Number of Non-Sequentially Written Sequential Write Preferred Zones: Not Set
Maximum Number of Open Sequential Write Required Zones: Not Set

sysctl kern.cam.da.X

# sysctl kern.cam.da.18
kern.cam.da.18.sort_io_queue: -1
kern.cam.da.18.rotating: 1
kern.cam.da.18.unmapped_io: 1
kern.cam.da.18.error_inject: 0
[ begin SMR fields ]
kern.cam.da.18.max_seq_zones: 4294967295
kern.cam.da.18.optimal_nonseq_zones: 8
kern.cam.da.18.optimal_seq_zones: 128
kern.cam.da.18.zone_support: Report Zones, Open, Close, Finish, Reset Write
Pointer
kern.cam.da.18.zone_mode: Host Aware
[ end SMR fields ]
kern.cam.da.18.minimum_cmd_size: 6
kern.cam.da.18.delete_max: 262144
kern.cam.da.18.delete_method: NONE

# sysctl kern.cam.da.19
kern.cam.da.19.sort_io_queue: -1
kern.cam.da.19.rotating: 1
kern.cam.da.19.unmapped_io: 1
kern.cam.da.19.error_inject: 0
[ begin SMR fields ]
kern.cam.da.19.max_seq_zones: 0
kern.cam.da.19.optimal_nonseq_zones: 0
kern.cam.da.19.optimal_seq_zones: 0
kern.cam.da.19.zone_support: None
kern.cam.da.19.zone_mode: Drive Managed
[ begin SMR fields ]
kern.cam.da.19.minimum_cmd_size: 6
kern.cam.da.19.delete_max: 262144
kern.cam.da.19.delete_method: NONE

If you have a Host Aware or Host Managed drive, you can get the list of
zones and their status, reset the write pointer, etc.

Ask the drive (via camcontrol(8)) to list all zones on a Host Aware drive
(but truncate the output to 10 lines):

# camcontrol zone da18 -v -c rz |head -10
29809 zones, Maximum LBA 0x3a3812aaf (15628053167)
Zone lengths and types may vary
Start LBA Length WP LBA Zone Type Condition Sequential Reset
0, 524288, 0x80000, Conventional, NWP, Sequential, No Reset Needed
0x80000, 524288, 0x100000, Conventional, NWP, Sequential, No Reset Needed
0x100000, 524288, 0x180000, Conventional, NWP, Sequential, No Reset Needed
0x180000, 524288, 0x200000, Conventional, NWP, Sequential, No Reset Needed
0x200000, 524288, 0x280000, Conventional, NWP, Sequential, No Reset Needed
0x280000, 524288, 0x300000, Conventional, NWP, Sequential, No Reset Needed
0x300000, 524288, 0x380000, Conventional, NWP, Sequential, No Reset Needed

Ask the drive (via zonectl(8)) to report zones that are in the Full state:

# zonectl -d /dev/da18 -c rz -o full |head -10
192 zones, Maximum LBA 0x3a3812aaf (15628053167)
Zone lengths and types may vary
Start LBA Length WP LBA Zone Type Condition Sequential Reset
0x2000000, 524288, 0x2080000, Seq Preferred, Full, Sequential, No Reset Needed
0x2080000, 524288, 0x2100000, Seq Preferred, Full, Sequential, No Reset Needed
0x2100000, 524288, 0x2180000, Seq Preferred, Full, Sequential, No Reset Needed
0x2180000, 524288, 0x2200000, Seq Preferred, Full, Sequential, No Reset Needed
0x2200000, 524288, 0x2280000, Seq Preferred, Full, Sequential, No Reset Needed
0x2280000, 524288, 0x2300000, Seq Preferred, Full, Sequential, No Reset Needed
0x2300000, 524288, 0x2380000, Seq Preferred, Full, Sequential, No Reset Needed

Note that there are 192 zones in that state, versus 29809 zones total.

You can also reset write pointers. For example, reset the zone beginning
at LBA 0x2000000, which we see above is in the full state:

# zonectl -d /dev/da18 -c rwp -l 0x2000000

Now ask for the zone report beginning at LBA 0x2000000:

# zonectl -d /dev/da18 -c rz -l 0x2000000 |head -10
29745 zones, Maximum LBA 0x3a3812aaf (15628053167)
Zone lengths and types may vary
Start LBA Length WP LBA Zone Type Condition Sequential Reset
0x2000000, 524288, 0x2000000, Seq Preferred, Empty, Sequential, No Reset Needed
0x2080000, 524288, 0x2100000, Seq Preferred, Full, Sequential, No Reset Needed
0x2100000, 524288, 0x2180000, Seq Preferred, Full, Sequential, No Reset Needed
0x2180000, 524288, 0x2200000, Seq Preferred, Full, Sequential, No Reset Needed
0x2200000, 524288, 0x2280000, Seq Preferred, Full, Sequential, No Reset Needed
0x2280000, 524288, 0x2300000, Seq Preferred, Full, Sequential, No Reset Needed
0x2300000, 524288, 0x2380000, Seq Preferred, Full, Sequential, No Reset Needed

The zone is empty, and the write pointer is at the beginning of the zone
instead of the end.

You can only do that for Host Aware and Host Managed drives. Host Managed
drives aren't yet supported via the ada(4) driver. They should in theory
attach to the da(4) driver, but I haven't seen one yet.

> BTW the disk returns an error when multiple LUNs are probed.

That should just be because you've got the probe debugging turned on.

Ken
--
Kenneth Merry
k...@FreeBSD.ORG

[Gary Jennejohn]

On Thu, 26 May 2016 08:34:45 -0400
"Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:

> On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> What kind of drive is it?
>

ST8000AS 0002-1NA17Z 0X03

> Here are some things you can do on any disk to see what it is:
>
> diskinfo -v /dev/daX
>

I don't have the new versions of these utilities installed, so I can't
get any of this neat diskinfo/zonectl information.

> # sysctl kern.cam.da.19
> kern.cam.da.19.sort_io_queue: -1
> kern.cam.da.19.rotating: 1
> kern.cam.da.19.unmapped_io: 1
> kern.cam.da.19.error_inject: 0
> [ begin SMR fields ]
> kern.cam.da.19.max_seq_zones: 0
> kern.cam.da.19.optimal_nonseq_zones: 0
> kern.cam.da.19.optimal_seq_zones: 0
> kern.cam.da.19.zone_support: None
> kern.cam.da.19.zone_mode: Drive Managed
> [ begin SMR fields ]
> kern.cam.da.19.minimum_cmd_size: 6
> kern.cam.da.19.delete_max: 262144
> kern.cam.da.19.delete_method: NONE
>

My drive shows this;
sysctl kern.cam.da.0
kern.cam.da.0.sort_io_queue: -1
kern.cam.da.0.rotating: 1
kern.cam.da.0.unmapped_io: 0
kern.cam.da.0.error_inject: 0
kern.cam.da.0.max_seq_zones: 0
kern.cam.da.0.optimal_nonseq_zones: 0
kern.cam.da.0.optimal_seq_zones: 0
kern.cam.da.0.zone_support: None
kern.cam.da.0.zone_mode: Not Zoned <== I guess it can't be managed
kern.cam.da.0.minimum_cmd_size: 10
kern.cam.da.0.delete_max: 131072
kern.cam.da.0.delete_method: NONE

In fact, the ouput for every one of the 4 drives in the enclosure is
the same, even though the other three are non-SMR SATA drives.

--
Gary Jennejohn

[Kenneth D. Merry]

On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> On Thu, 26 May 2016 08:34:45 -0400
> "Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:
>
> > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > What kind of drive is it?
> >
>
> ST8000AS 0002-1NA17Z 0X03

Can you send the output of 'camcontrol inquiry daX -v' and
'camcontrol identify daX -v'?

There is a quirk for that particular drive to identify it as Drive Managed.
When attached behind a SAS controller it looks like this:

# camcontrol inquiry da12 -v
pass12: <ATA ST8000AS0002-1NA AR17> Fixed Direct Access SPC-4 SCSI device
pass12: Serial Number Z8407Y52
pass12: 600.000MB/s transfers, Command Queueing Enabled

Yes. There is something slightly odd about the Inquiry data you pasted
above. Seagate didn't set the bits in the ATA identify data to mark it as
a Drive Managed drive, so I put in a quirk entry to mark it as Drive
Managed.

Unfortunately with Drive Managed drives that is really all you know. You
don't know the zone boundaries or states. But, it is useful to know that
you really should write sequentially for good performance. (True of any
drive, but especially true with SMR drives.)

Ken
--
Kenneth Merry
k...@FreeBSD.ORG

[Gary Jennejohn]

On Thu, 26 May 2016 09:41:20 -0400

"Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:

> On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > On Thu, 26 May 2016 08:34:45 -0400
> > "Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:
> >
> > > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > > What kind of drive is it?
> > >
> >
> > ST8000AS 0002-1NA17Z 0X03
>
> Can you send the output of 'camcontrol inquiry daX -v' and
> 'camcontrol identify daX -v'?
>
> There is a quirk for that particular drive to identify it as Drive Managed.
> When attached behind a SAS controller it looks like this:
>
> # camcontrol inquiry da12 -v
> pass12: <ATA ST8000AS0002-1NA AR17> Fixed Direct Access SPC-4 SCSI device
> pass12: Serial Number Z8407Y52
> pass12: 600.000MB/s transfers, Command Queueing Enabled
>

Thanks for the info.

Here the requested output:

camcontrol inquiry da0 -v
pass5: <ST8000AS 0002-1NA17Z 0X03> Fixed Direct Access SPC-4 SCSI device
pass5: Serial Number 000000000000
pass5: 400.000MB/s transfers

camcontrol identify da0 -v
camcontrol: sending ATA ATA_IDENTIFY via pass_16 with timeout of 30000 msecs
pass5: Raw identify data:
0: 0c5a 3fff c837 0010 0000 0000 003f 0000
8: 0000 0000 2020 2020 2020 2020 2020 2020
16: 5a38 3430 3339 4738 0000 8000 0000 4152
24: 3133 2020 2020 5354 3830 3030 4153 3030
32: 3032 2d31 4e41 3137 5a20 2020 2020 2020
40: 2020 2020 2020 2020 2020 2020 2020 8010
48: 4000 2f00 4000 0200 0200 0007 3fff 0010
56: 003f fc10 00fb 5c10 ffff 0fff 0000 0007
64: 0003 0078 0078 0078 0078 0000 0000 0000
72: 0000 0000 0000 001f 8d0e 0004 00cc 0040
80: 03f0 001f 346b 7d61 6163 3469 bc41 6163
88: 407f 81e7 81e7 0000 fffe 0000 fe00 0000
96: 0000 0000 0000 0000 2ab0 a381 0003 0000
104: 0000 0000 6003 0000 5000 c500 7b0e 5cbe
112: 0000 0000 0000 0000 0000 0000 0000 40dc
120: 409c 0000 0000 0000 0000 0000 0000 0000
128: 0021 2ab0 a381 2ab0 a381 2020 0002 0140
136: 0108 5000 3c06 3c0a 0000 003c 0000 0008
144: 0000 0000 bdff 0280 0000 0000 0008 0000
152: 0000 0000 0000 8000 0000 0184 8b00 8008
160: 0000 0000 0000 0000 0000 0000 0000 0000
168: 0000 0000 0000 0000 0000 0000 0000 0000
176: 0000 0000 0000 0000 0000 0000 0000 0000
184: 0000 0000 0000 0000 0000 0000 0000 0000
192: 0000 0000 0000 0000 0000 0000 0000 0000
200: 0000 0000 0000 0000 0000 0000 30a5 0000
208: 0000 4000 0000 0000 0000 0000 0000 0000
216: 0000 175c 0000 0000 0000 0000 107f 0000
224: 0000 0000 0000 0000 0000 0000 0000 0000
232: 0000 0000 0000 0000 0000 0000 0000 0000
240: 0000 0000 0000 0000 0000 0000 0000 0000
248: 0000 0000 0000 0000 0000 0000 0000 6aa5

camcontrol: sending ATA READ_NATIVE_MAX_ADDRESS48 via pass_16 with timeout of 1000 msecs
pass5: Raw native max data:
0: 0000 0000 0000 0000 0000 0000
error = 0x00, sector_count = 0x0000, device = 0x00, status = 0x00
pass5: <ST8000AS0002-1NA17Z AR13> ACS-2 ATA SATA 3.x device
pass5: 400.000MB/s transfers

protocol ATA/ATAPI-9 SATA 3.x
device model ST8000AS0002-1NA17Z
firmware revision AR13
serial number Z84039G8
WWN 5000c5007b0e5cbe
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 4096, offset 0
LBA supported 268435455 sectors
LBA48 supported 15628053168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 5980

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 no no
automatic acoustic management no no
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload yes yes
general purpose logging yes yes
free-fall no no
Data Set Management (DSM/TRIM) no
Host Protected Area (HPA) yes no 15628053168/1
HPA - Security no

--
Gary Jennejohn

[Igor Mozolevsky]

On 26 May 2016 at 14:41, Kenneth D. Merry <k...@freebsd.org> wrote:

> On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > On Thu, 26 May 2016 08:34:45 -0400
> > "Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:
> >
> > > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > > What kind of drive is it?
> > >
> >
> > ST8000AS 0002-1NA17Z 0X03
>

[snip]

> Yes. There is something slightly odd about the Inquiry data you pasted
> above. Seagate didn't set the bits in the ATA identify data to mark it as
> a Drive Managed drive, so I put in a quirk entry to mark it as Drive
> Managed.
>
> Unfortunately with Drive Managed drives that is really all you know. You
> don't know the zone boundaries or states. But, it is useful to know that
> you really should write sequentially for good performance. (True of any
> drive, but especially true with SMR drives.)
>

The drive is supposed to have Word 69 set to 0x0001 and support ZAC MGMT
IN/OUT -
http://www.seagate.com/www-content/product-content/hdd-fam/seagate-archive-hdd/en-us/docs/100795782a.pdf
at pg. 24 and 28.

Incidentally AR17 firmware is a new batch, perhaps Seagate did what they
did with -DL003 drives where the early models reported 512n sector size (so
as not to confuse computers) and the later models properly reported 4kn
sector size?

--
Igor M.

[Kenneth D. Merry]

On Thu, May 26, 2016 at 16:00:41 +0200, Gary Jennejohn wrote:
> On Thu, 26 May 2016 09:41:20 -0400
> "Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:
>
> > On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > > On Thu, 26 May 2016 08:34:45 -0400
> > > "Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:
> > >
> > > > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > > > What kind of drive is it?
> > > >
> > >
> > > ST8000AS 0002-1NA17Z 0X03
> >
> > Can you send the output of 'camcontrol inquiry daX -v' and
> > 'camcontrol identify daX -v'?
> >
> > There is a quirk for that particular drive to identify it as Drive Managed.
> > When attached behind a SAS controller it looks like this:
> >
> > # camcontrol inquiry da12 -v
> > pass12: <ATA ST8000AS0002-1NA AR17> Fixed Direct Access SPC-4 SCSI device
> > pass12: Serial Number Z8407Y52
> > pass12: 600.000MB/s transfers, Command Queueing Enabled
> >
>
> Thanks for the info.
>
> Here the requested output:
>
> camcontrol inquiry da0 -v
> pass5: <ST8000AS 0002-1NA17Z 0X03> Fixed Direct Access SPC-4 SCSI device
> pass5: Serial Number 000000000000
> pass5: 400.000MB/s transfers

Okay. Looks like the USB to SATA chip is perhaps mangling the model
number. I'm guessing that is the "standard" way to do it, but it is
unfortunate.

The firmware is old, the current version is AR17. You should really ask
Seagate for updated firmware.

Ken
--
Kenneth Merry
k...@FreeBSD.ORG

[Kenneth D. Merry]

On Thu, May 26, 2016 at 15:02:24 +0100, Igor Mozolevsky wrote:
> On 26 May 2016 at 14:41, Kenneth D. Merry <k...@freebsd.org> wrote:
>
> > On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > > On Thu, 26 May 2016 08:34:45 -0400
> > > "Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:
> > >
> > > > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > > > What kind of drive is it?
> > > >
> > >
> > > ST8000AS 0002-1NA17Z 0X03
> >
>
> [snip]
>
>
> > Yes. There is something slightly odd about the Inquiry data you pasted
> > above. Seagate didn't set the bits in the ATA identify data to mark it as
> > a Drive Managed drive, so I put in a quirk entry to mark it as Drive
> > Managed.
> >
> > Unfortunately with Drive Managed drives that is really all you know. You
> > don't know the zone boundaries or states. But, it is useful to know that
> > you really should write sequentially for good performance. (True of any
> > drive, but especially true with SMR drives.)
> >
>
> The drive is supposed to have Word 69 set to 0x0001 and support ZAC MGMT
> IN/OUT -
> http://www.seagate.com/www-content/product-content/hdd-fam/seagate-archive-hdd/en-us/docs/100795782a.pdf
> at pg. 24 and 28.

That is a different drive. He has ST8000AS0002, which is a Drive Managed
drive. The doc above is for ST8000AS0022, which is a Host Aware drive.

> Incidentally AR17 firmware is a new batch, perhaps Seagate did what they
> did with -DL003 drives where the early models reported 512n sector size (so
> as not to confuse computers) and the later models properly reported 4kn
> sector size?

Yes, AR17 is the latest firmware. He really needs to upgrade, there are
bugs with older versions.

AR17 firmware reports the same thing in terms of sector size. For
instance, from one of mine:

rotocol ATA/ATAPI-9 SATA 3.x
device model ST8000AS0002-1NA17Z

firmware revision AR17
serial number Z8409926
WWN 5000c50086f84017

cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 4096, offset 0
LBA supported 268435455 sectors
LBA48 supported 15628053168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 5980

Ken
--
Kenneth Merry
k...@FreeBSD.ORG

[Gary Jennejohn]

On Thu, 26 May 2016 10:10:14 -0400
"Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:

> On Thu, May 26, 2016 at 16:00:41 +0200, Gary Jennejohn wrote:
> > protocol ATA/ATAPI-9 SATA 3.x
> > device model ST8000AS0002-1NA17Z
> > firmware revision AR13
>
> The firmware is old, the current version is AR17. You should really ask
> Seagate for updated firmware.
>

The Download Finder on the Seagate site claims that there is no newer
firmware.

So the question is, how to get the latest AR17 version from Seagate
as a simple consumer?

--
Gary Jennejohn

[Kenneth D. Merry]

On Thu, May 26, 2016 at 16:42:10 +0200, Gary Jennejohn wrote:
> On Thu, 26 May 2016 10:10:14 -0400
> "Kenneth D. Merry" <k...@FreeBSD.ORG> wrote:
>
> > On Thu, May 26, 2016 at 16:00:41 +0200, Gary Jennejohn wrote:
> > > protocol ATA/ATAPI-9 SATA 3.x
> > > device model ST8000AS0002-1NA17Z
> > > firmware revision AR13
> >
> > The firmware is old, the current version is AR17. You should really ask
> > Seagate for updated firmware.
> >
>
> The Download Finder on the Seagate site claims that there is no newer
> firmware.
>
> So the question is, how to get the latest AR17 version from Seagate
> as a simple consumer?

I would contact Seagate support and ask.

By the way, I've been able to download firmware for Seagate SATA drives via
camcontrol when they're attached via SATA and SAS controllers. I've never
tried it with USB.

I think camcontrol identify it as a SCSI protocol drive and as a result
may not let you download firmware because it doesn't recognize vendor
"ST8000AS".

So, assuming you get firmware from them, I would suggest upgrading it using
whatever Windows or Linux tool they give you. (I'll brick drives in my
lab at work, but I'd hate for you to brick your own drive.)

If you want to use camcontrol to do it, take it out of the USB enclosure
and hook it directly to a SATA or SAS controller.

Ken
--
Kenneth Merry
k...@FreeBSD.ORG