Other Testing speed of USB pen drives

balanga

Son of Beastie

Reaction score: 217
Messages: 4,024

How would I go about testing the speed of various USB pen drives?
 

ralphbsz

Son of Beastie

Reaction score: 2,189
Messages: 3,146

And note that like all flash storage, the write speed depends heavily on the internal layout of the data (flash data is not actually organized like disk data, more like a log-structured internal file system). And the read speed depends on how you have written the data, since it affects the layout.

Then there is the question of wearout: Cheap USB sticks use the crappiest flash that chip makes produce, so it doesn't have many write cycles. The manufacturers compensate by over-provisioning (more or less, depending on price point and design). But as the flash wears out, the performance will change.

So while bonnie++ is indeed the de-facto standard for simple testing, I would not believe the results to better than +- 25% or so.
 
OP
B

balanga

Son of Beastie

Reaction score: 217
Messages: 4,024

So how do I tell which flash chips are used in any particular stick and which would you recommend?

And can you tell how may 'write cycles' have taken place. I could do with going through all mine to see may be on their way out, if that's possible...
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 11,612
Messages: 37,946

The "problem" with USB sticks is that the controller firmware could lie to you. Just go watch some videos about people buying large memory sticks from Wish or AliBaba that are way too cheap compared to "real" sticks of that size. You plug it in, it tells you it's 8TB and there's 8TB free. It stops working once you write more than 64MB (or some other low number) to it though. Or it continues to appear to write but nothing actually ends up on the stick. The only way to really know how big it is is to open it up and look up the markings on the chips. But that's also not very reliable because those can be faked too, but they usually don't go that far.
 

covacat

Well-Known Member

Reaction score: 171
Messages: 365

you probably can't. some may have some proprietary way do that
but as a general rule
the write speed for all of the cheap ones SUCKS
the usb3.x more expensive ones from well known manufacturers are good/ok-ish
the higher end usb 2.0 may be decent
 

ralphbsz

Son of Beastie

Reaction score: 2,189
Messages: 3,146

So how do I tell which flash chips are used in any particular stick and which would you recommend?

And can you tell how may 'write cycles' have taken place. I could do with going through all mine to see may be on their way out, if that's possible...
You can't tell. The interface doesn't have any way to figure it out. They don't even support SMART.

I use them either of two ways. Either as a disposable way of transporting data: Write to them, read it immediately somewhere else; if the data doesn't arrive, throw the stick in the trash and use a different one. I have a small bin with a few dozen of them, usually free ones you get at conferences.

Or, if you want to use them to actually store things, buy name-brand ones of moderate capacity (Kingston, SanDisk). You pay quite a bit more, but those haven't broken often on me.
 

fcorbelli

Active Member

Reaction score: 54
Messages: 167

Personally I adopt my own methodology... which is to buy a large number of them and then try them out :)

Today I prefer the Sandisk Extreme Pro, until recently they were the Kingson HyperX (blue).

However, with regard to reliability, the very first thing I do is use my program (on Windows it is FILLAMI, for BSD is zpaqfranz) which does nothing but write 500MB pseudorandom files until it is almost filled, after which they are readed again to verify the correctness.

Of course it is not a foolproof method, but looking at the consistency of the writing and reading speed (which should be maintained, without major differences) I consider it essential for every stick, and the cheaper ones in particular.
Of course this is SEQUENTIAL write etc.etc.

I suppose many others similar tool exists
For ramdisk
Code:
zpaqfranz v51.28-experimental snapshot archiver, compiled May 28 2021
franz:VERBOSE list of files on (-verbose)
franz:KILL!

This is FILLAMI, reliability test for media.

Almost all free space will be filled by pseudorandom 512MB files,
then checked from the ztempdir-created folder.

These activities can reduce the media life,
especially for solid state drives and if repeated several times.

Normally used as stress test for newly devices/controllers
or (via NIC) for heavy network stress test.

Temporary files are NOT deleted by default (for zfs's scrub).

-kill    switch will clear (delete) temp files after execution
-verbose for extended output (check IO consistency speed)

More than 2GB of free disk space needed.

To EXIT press q, Q / anything else to continue
Free space 21.097.172.992 (19.65 GB) <<z:/ztempdir/>>
To write   20.886.201.262 (19.45 GB) 99 percent
37 chuks of (512.00 MB) will be written
000% ETA 0:00:00 todo (  18.50 GB) rnd (   2.89 GB/s) hash (  31.25 GB/s) W (   2.12 GB/s)
002% ETA 0:00:27 todo (  18.00 GB) rnd (   6.33 GB/s) hash (  29.41 GB/s) W (   1.99 GB/s)
(...)
097% ETA 0:00:00 todo ( 512.00 MB) rnd (   7.81 GB/s) hash (  29.41 GB/s) W (   1.99 GB/s)
Total time 12.016000  rnd 2.502000  hash 0.810000  write 8.688000
******* VERIFY
Loading chunk 00000  (1.58 GB/s) OK B95D42121C14AC3FAD3AB8207E9F309B
Loading chunk 00001  (1.58 GB/s) OK 044ADD8A789583BC5E56AFC015F91293
(...)
Loading chunk 00036  (1.98 GB/s) OK 737B64C0538D6087954C26945284BB51

Verify time 2.734000 (  18.50 GB) speed (   6.77 GB/s)
+OK all OK
Deleting tempfile 00000 / 00037
(...)
Deleting tempfile 00036 / 00037

For SanDISK Extreme Pro "real life" speed ~250MB/s

Code:
(...)
Free space 28.779.216.896 (26.80 GB) <<d:/ztempdir/>>
To write   28.491.424.727 (26.53 GB) 99 percent
52 chuks of (512.00 MB) will be written
000% ETA 0:00:00 todo (  26.00 GB) rnd (   2.89 GB/s) hash (  31.25 GB/s) W ( 287.16 MB/s)
001% ETA 0:03:43 todo (  25.50 GB) rnd (  10.64 GB/s) hash (  15.15 GB/s) W ( 219.84 MB/s)
003% ETA 0:02:51 todo (  25.00 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 214.05 MB/s)
005% ETA 0:02:32 todo (  24.50 GB) rnd (   7.94 GB/s) hash (  15.62 GB/s) W ( 215.49 MB/s)
007% ETA 0:02:17 todo (  24.00 GB) rnd (  10.42 GB/s) hash (  15.62 GB/s) W ( 248.06 MB/s)
009% ETA 0:02:09 todo (  23.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 227.45 MB/s)
011% ETA 0:02:03 todo (  23.00 GB) rnd (   6.33 GB/s) hash (  29.41 GB/s) W ( 222.80 MB/s)
013% ETA 0:01:59 todo (  22.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 221.36 MB/s)
015% ETA 0:01:54 todo (  22.00 GB) rnd (   7.81 GB/s) hash (  31.25 GB/s) W ( 240.83 MB/s)
017% ETA 0:01:49 todo (  21.50 GB) rnd (   7.81 GB/s) hash (  29.41 GB/s) W ( 250.12 MB/s)
019% ETA 0:01:45 todo (  21.00 GB) rnd (   6.25 GB/s) hash (  31.25 GB/s) W ( 253.84 MB/s)
021% ETA 0:01:41 todo (  20.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 237.37 MB/s)
023% ETA 0:01:38 todo (  20.00 GB) rnd (   7.81 GB/s) hash (  15.62 GB/s) W ( 234.00 MB/s)
025% ETA 0:01:34 todo (  19.50 GB) rnd (   7.81 GB/s) hash (  29.41 GB/s) W ( 255.87 MB/s)
026% ETA 0:01:32 todo (  19.00 GB) rnd (   7.94 GB/s) hash (  15.62 GB/s) W ( 228.98 MB/s)
028% ETA 0:01:29 todo (  18.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 216.95 MB/s)
030% ETA 0:01:26 todo (  18.00 GB) rnd (   7.81 GB/s) hash (  15.62 GB/s) W ( 266.25 MB/s)
032% ETA 0:01:22 todo (  17.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 297.67 MB/s)
034% ETA 0:01:19 todo (  17.00 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 289.92 MB/s)
036% ETA 0:01:16 todo (  16.50 GB) rnd (   6.25 GB/s) hash (  31.25 GB/s) W ( 272.92 MB/s)
038% ETA 0:01:13 todo (  16.00 GB) rnd (   6.33 GB/s) hash (  15.15 GB/s) W ( 266.39 MB/s)
040% ETA 0:01:11 todo (  15.50 GB) rnd (   7.81 GB/s) hash (  29.41 GB/s) W ( 193.87 MB/s)
042% ETA 0:01:10 todo (  15.00 GB) rnd (   7.81 GB/s) hash (  31.25 GB/s) W ( 194.97 MB/s)
044% ETA 0:01:08 todo (  14.50 GB) rnd (   7.81 GB/s) hash (  31.25 GB/s) W ( 207.29 MB/s)
046% ETA 0:01:06 todo (  14.00 GB) rnd (   7.81 GB/s) hash (  31.25 GB/s) W ( 185.04 MB/s)
048% ETA 0:01:03 todo (  13.50 GB) rnd (   7.94 GB/s) hash (  15.15 GB/s) W ( 221.36 MB/s)
050% ETA 0:01:01 todo (  13.00 GB) rnd (  10.42 GB/s) hash (  15.62 GB/s) W ( 224.27 MB/s)
051% ETA 0:00:59 todo (  12.50 GB) rnd (   7.94 GB/s) hash (  15.62 GB/s) W ( 191.54 MB/s)
053% ETA 0:00:57 todo (  12.00 GB) rnd (   7.81 GB/s) hash (  15.62 GB/s) W ( 215.49 MB/s)
055% ETA 0:00:54 todo (  11.50 GB) rnd (   6.33 GB/s) hash (  29.41 GB/s) W ( 244.51 MB/s)
057% ETA 0:00:52 todo (  11.00 GB) rnd (   7.81 GB/s) hash (  29.41 GB/s) W ( 215.49 MB/s)
059% ETA 0:00:49 todo (  10.50 GB) rnd (  10.64 GB/s) hash (  15.15 GB/s) W ( 289.92 MB/s)
061% ETA 0:00:47 todo (  10.00 GB) rnd (   7.81 GB/s) hash (  15.62 GB/s) W ( 244.39 MB/s)
063% ETA 0:00:44 todo (   9.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 270.61 MB/s)
065% ETA 0:00:42 todo (   9.00 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 272.92 MB/s)
067% ETA 0:00:39 todo (   8.50 GB) rnd (   6.33 GB/s) hash (  31.25 GB/s) W ( 287.16 MB/s)
069% ETA 0:00:36 todo (   8.00 GB) rnd (  10.42 GB/s) hash (  15.62 GB/s) W ( 284.76 MB/s)
071% ETA 0:00:34 todo (   7.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 279.93 MB/s)
073% ETA 0:00:32 todo (   7.00 GB) rnd (   6.33 GB/s) hash (  29.41 GB/s) W ( 292.40 MB/s)
075% ETA 0:00:29 todo (   6.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 266.25 MB/s)
076% ETA 0:00:27 todo (   6.00 GB) rnd (   7.94 GB/s) hash (  15.62 GB/s) W ( 289.76 MB/s)
078% ETA 0:00:24 todo (   5.50 GB) rnd (   7.81 GB/s) hash (  15.62 GB/s) W ( 277.51 MB/s)
080% ETA 0:00:22 todo (   5.00 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 282.40 MB/s)
082% ETA 0:00:20 todo (   4.50 GB) rnd (   6.33 GB/s) hash (  29.41 GB/s) W ( 272.92 MB/s)
084% ETA 0:00:17 todo (   4.00 GB) rnd (   7.94 GB/s) hash (  15.15 GB/s) W ( 268.48 MB/s)
086% ETA 0:00:15 todo (   3.50 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 268.48 MB/s)
088% ETA 0:00:13 todo (   3.00 GB) rnd (   7.81 GB/s) hash (  31.25 GB/s) W ( 287.16 MB/s)
090% ETA 0:00:11 todo (   2.50 GB) rnd (   6.33 GB/s) hash (  31.25 GB/s) W ( 275.12 MB/s)
092% ETA 0:00:08 todo (   2.00 GB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 282.40 MB/s)
094% ETA 0:00:06 todo (   1.50 GB) rnd (   7.81 GB/s) hash (  15.62 GB/s) W ( 287.32 MB/s)
096% ETA 0:00:04 todo (   1.00 GB) rnd (   7.81 GB/s) hash (  29.41 GB/s) W ( 272.92 MB/s)
098% ETA 0:00:02 todo ( 512.00 MB) rnd (   7.94 GB/s) hash (  29.41 GB/s) W ( 251.97 MB/s)
Total time 112.203000  rnd 3.419000  hash 1.097000  write 107.687000
 
OP
B

balanga

Son of Beastie

Reaction score: 217
Messages: 4,024

De facto standard tool to test disk performance is benchmarks/bonnie++.
root@T530:/# pkg install -y benchmarks/bonnie++
pkg: No packages available to install matching 'benchmarks/bonnie++' have been found in the repositories
root@T530:/# uname -a
FreeBSD T530 13.0-RELEASE FreeBSD 13.0-RELEASE #0 releng/13.0-n244733-ea31abc261f: Fri Apr 9 04:24:09 UTC 2021 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
What am I doing wrong?
 

grahamperrin

Daemon

Reaction score: 367
Messages: 1,221

What am I doing wrong?

Nothing, as far as I can tell.

<https://www.freshports.org/benchmarks/bonnie++/#packages> does show packages for FreeBSD:13:amd64 and FreeBSD:14:amd64 and I installed to FreeBSD-CURRENT a moment ago, so maybe it's simply not available for FreeBSD:13:amd64 at the moment.

Something linked from <https://pkg-status.freebsd.org/builds?jailname=130amd64> might hold a clue.

Coincidentally <https://old.reddit.com/r/freebsd/comments/nujgxe/-/h1f744p/?context=1> there's me wondering how to methodically discover explanations when a package is not in a repository.
 

grahamperrin

Daemon

Reaction score: 367
Messages: 1,221

maybe it's simply not available for FreeBSD:13:amd64 at the moment.

It's in latest:

1623432684232.png


– so balanga try pkg update -f
 

Phishfry

Beastie's Twin

Reaction score: 2,574
Messages: 5,458

Throw all that trash out and use the tools in base. dd files to it and monitor that with gstat or vmstat iostat.
That is true random sequential.
 

mer

Well-Known Member

Reaction score: 190
Messages: 329

Of course all you know is how that specific sample works. A fun fact about USB and other flash based things is Reading doesn't kill them, it's erasing that does. Writing often involves reading, modifying, erasing a block and writing (most devices can't write on an unerased device).
 
OP
B

balanga

Son of Beastie

Reaction score: 217
Messages: 4,024

Throw all that trash out and use the tools in base. dd files to it and monitor that with gstat or vmstat iostat.
That is true random sequential.
Basically I have a dodgy disk which is painfully slow and want to quantify just how painfully slow it is.

I just want a program which will create some output after a minute or so which confirm my perception of slowness.
 

Phishfry

Beastie's Twin

Reaction score: 2,574
Messages: 5,458

I found stressdisk useful on more than one occasion.
Ok 'trash' might have been an Oko like response.
Still couldn't you stress the disk with dd if=/dev/random of=/dev/da0 ?
Real world file usage statistics instead of synthetic benchmarks is why I say trashy tools.
 

grahamperrin

Daemon

Reaction score: 367
Messages: 1,221

… couldn't you stress the disk with dd if=/dev/random of=/dev/da0 ?

Yes, however the output from dd(1) is quite different.



With /dev/da3 (a low quality, giveaway device) currently mounted at /media/General_UDisk_, stressdisk cycle /media/General_UDisk_/ very soon yields an error (no surprise, given the low quality):

Code:
% stressdisk cycle /media/General_UDisk_/
2021/06/11 19:21:23 loaded statsfile "stressdisk_stats.json"
2021/06/11 19:21:23
Bytes read:         89576 MByte (  46.60 MByte/s)
Bytes written:      75302 MByte (   6.01 MByte/s)
Errors:                 0
Elapsed time:  116.763µs

2021/06/11 19:21:23 Removing 0 check files
2021/06/11 19:21:23 Starting round 1
2021/06/11 19:21:23 No check files - generating
2021/06/11 19:21:23 Writing file "/media/General_UDisk_/TST_0000" size 1000000000
2021/06/11 19:22:23
Bytes read:         89576 MByte (  46.60 MByte/s)
Bytes written:      75722 MByte (   6.01 MByte/s)
Errors:                 0
Elapsed time:  1m0.000911477s

2021/06/11 19:23:23
Bytes read:         89576 MByte (  46.60 MByte/s)
Bytes written:      76140 MByte (   6.02 MByte/s)
Errors:                 0
Elapsed time:  2m0.002454945s

2021/06/11 19:23:42 Writing file "/media/General_UDisk_/TST_0001" size 1000000000
2021/06/11 19:24:23
Bytes read:         89576 MByte (  46.60 MByte/s)
Bytes written:      76540 MByte (   6.02 MByte/s)
Errors:                 0
Elapsed time:  3m0.001253605s

2021/06/11 19:25:23
Bytes read:         89576 MByte (  46.60 MByte/s)
Bytes written:      76958 MByte (   6.03 MByte/s)
Errors:                 0
Elapsed time:  4m0.007112141s

2021/06/11 19:26:02 Writing file "/media/General_UDisk_/TST_0002" size 1000000000
2021/06/11 19:26:03 Error while writing "/media/General_UDisk_/TST_0002"
2021/06/11 19:26:03 Removing incomplete file "/media/General_UDisk_/TST_0002"
2021/06/11 19:26:03 Reading file "/media/General_UDisk_/TST_0001", "/media/General_UDisk_/TST_0000"
2021/06/11 19:26:03 Reading file "/media/General_UDisk_/TST_0000", "/media/General_UDisk_/TST_0001"
2021/06/11 19:26:04 Removing 2 check files
2021/06/11 19:26:04 Removing file "/media/General_UDisk_/TST_0000"
2021/06/11 19:26:04 Removing file "/media/General_UDisk_/TST_0001"
2021/06/11 19:26:04 Starting round 2
2021/06/11 19:26:04 No check files - generating
2021/06/11 19:26:04 Writing file "/media/General_UDisk_/TST_0000" size 1000000000
2021/06/11 19:26:04 Error while writing "/media/General_UDisk_/TST_0000"
2021/06/11 19:26:04 Removing incomplete file "/media/General_UDisk_/TST_0000"
2021/06/11 19:26:04 Removing 0 check files
2021/06/11 19:26:04 Only generated 0 files which isn't enough - reduce the size with -s
% mount | grep /media/General_UDisk_
/dev/da3 on /media/General_UDisk_ (msdosfs, local)
% df -h /media/General_UDisk_
Filesystem    Size    Used   Avail Capacity  Mounted on
/dev/da3      1.9G     64K    1.9G     0%    /media/General_UDisk_
% tail -n 8 /var/log/messages
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: ugen1.6: <General UDisk> at usbus1
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: umass4 on uhub5
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: umass4: <General UDisk, class 0/0, rev 2.00/1.00, addr 6> on usbus1
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: da3 at umass-sim4 bus 4 scbus9 target 0 lun 0
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: da3: <General UDisk 5.00> Removable Direct Access SCSI-2 device
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: da3: 40.000MB/s transfers
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: da3: 1911MB (3913728 512 byte sectors)
Jun 11 19:20:56 mowa219-gjp4-8570p kernel: da3: quirks=0x2<NO_6_BYTE>
%
 
OP
B

balanga

Son of Beastie

Reaction score: 217
Messages: 4,024

Can anyone make anything out of the output I get from smartctl ?

Code:
/dev/ada0
        512             # sectorsize
        500107862016    # mediasize in bytes (466G)
        976773168       # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        969021          # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        5195F2TYS       # Disk ident.
        Not_Zoned       # Zone Mode

Seek times:
        Full stroke:      250 iter in   6.294265 sec =   25.177 msec
        Half stroke:      250 iter in   4.592675 sec =   18.371 msec
        Quarter stroke:   500 iter in   7.738469 sec =   15.477 msec
        Short forward:    400 iter in   2.697010 sec =    6.743 msec
        Short backward:   400 iter in   2.700618 sec =    6.752 msec
        Seq outer:       2048 iter in   0.215103 sec =    0.105 msec
        Seq inner:       2048 iter in   0.289058 sec =    0.141 msec

Transfer rates:
        outside:       102400 kbytes in   0.997348 sec =   102672 kbytes/sec
        middle:        102400 kbytes in   1.261361 sec =    81182 kbytes/sec
        inside:        102400 kbytes in   1.953807 sec =    52410 kbytes/sec
 

Phishfry

Beastie's Twin

Reaction score: 2,574
Messages: 5,458

That is diskinfo -t not smartctl that you are showing.
102672 kbytes/sec
Transfer rate is what your looking for.
102672 kb/sec = 102.672 mb/sec roughly (12 Megabytes/sec). Just move the decimal point to the left.
Note this is the max the drive could produce.
The middle reading is more like an average.

The one thing I have deduced is that the Transfer Rate number is based on writes, not reads.
That is one tradeoff of this real basic tool. It does not separate read speed from write speeds.
 
OP
B

balanga

Son of Beastie

Reaction score: 217
Messages: 4,024

Oops!

Code:
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-RELEASE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

Warning: DEFAULT entry missing in drive database file(s)
=== START OF INFORMATION SECTION ===
Device Model:     TOSHIBA MK5061GSYN
Serial Number:    5195F2TYS
LU WWN Device Id: 5 000039 34698332c
Firmware Version: MH000C
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Jun 11 18:38:10 2021 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  120) seconds.
Offline data collection
capabilities:                    (0x51) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 112) minutes.
SCT capabilities:              (0x003f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0027   100   100   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   100   100   002    Pre-fail  Always       -       2314
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       5272
  5 Reallocated_Sector_Ct   0x0033   078   078   010    Pre-fail  Always       -       452
  7 Seek_Error_Rate         0x002f   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   074   074   000    Old_age   Always       -       10488
 10 Spin_Retry_Count        0x0033   205   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4860
183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       398
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       65535
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   095   000    Old_age   Always       -       224
189 High_Fly_Writes         0x003a   100   100   001    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   065   044   040    Old_age   Always       -       35 (Min/Max 33/35)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       47
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       10682531
193 Load_Cycle_Count        0x0032   092   092   000    Old_age   Always       -       83689
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       34
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 occurred at disk power-on lifetime: 4412 hours (183 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 c0 6a 6d 16 60  Error: ICRC, ABRT at LBA = 0x00166d6a = 1469802

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 0b c0 60 6d 16 40 00      00:24:40.209  WRITE FPDMA QUEUED
  61 70 b8 c0 11 12 40 00      00:24:30.508  WRITE FPDMA QUEUED
  61 20 b0 a0 a3 be 40 00      00:24:30.508  WRITE FPDMA QUEUED
  61 20 a8 c0 03 c9 40 00      00:24:30.507  WRITE FPDMA QUEUED
  61 08 a0 20 cf 61 40 00      00:24:30.504  WRITE FPDMA QUEUED

MART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     10074         -
# 2  Short offline       Completed without error       00%     10072         -
# 3  Short offline       Completed without error       00%     10072         -
# 4  Short offline       Completed without error       00%     10006         -
# 5  Short offline       Completed without error       00%     10005         -
# 6  Short offline       Completed without error       00%      9985         -
# 7  Extended offline    Aborted by host               90%      8602         -
# 8  Short offline       Completed without error       00%      8602         -
# 9  Extended offline    Completed without error       00%      6263         -
#10  Extended offline    Aborted by host               90%      6235         -
#11  Short offline       Completed without error       00%      1636         -
#12  Short offline       Completed without error       00%      1635         -
#13  Short offline       Completed without error       00%      1635         -
#14  Short offline       Completed without error       00%      1635         -
#15  Short offline       Completed without error       00%      1635         -
#16  Short offline       Completed without error       00%      1635         -
#17  Short offline       Completed without error       00%      1634         -
#18  Short offline       Completed without error       00%      1634         -
#19  Short offline       Completed without error       00%      1634         -
#20  Short offline       Completed without error       00%      1634         -
#21  Short offline       Completed without error       00%      1633         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 

Phishfry

Beastie's Twin

Reaction score: 2,574
Messages: 5,458

smartctl has nothing to do with disk speeds. It is about disk diagnosis. Providing an hourmeter and other disk statistics.
 
Top