PINE64
NVME SSD Samsung 960 EVO Works! - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Pinebook Pro Hardware and Accessories (https://forum.pine64.org/forumdisplay.php?fid=116)
+--- Thread: NVME SSD Samsung 960 EVO Works! (/showthread.php?tid=9274)



NVME SSD Samsung 960 EVO Works! - Tekchip - 02-24-2020

Just wanted to report that I've recently installed the Samsung 960 EVO 500GB MZ-V6E500 2280. Running Manjaro ARM as primary drive. I wasn't sure it would work since the wiki shows the 970s don't work. I haven't noticed any heat from the drive but then I haven't done any particularly large read/writes. Seems stable thus far. Been using it about a week at this point.

What tests should I run before updating the wiki to note this thing is good to go?

Is there any other information anyone else would like about this?

Is there a standard for testing or verifying drives before we add them to the wiki? Perhaps I missed this somewhere if it already exists. Maybe worth noting at the top of the page or linking to those type of instructions here if/when they exist. https://wiki.pine64.org/index.php/Pinebook_Pro_Hardware_Accessory_Compatibility

Code:
smartctl 7.1 2019-12-30 r5022 [aarch64-linux-5.5.0-3.1-MANJARO-ARM] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 960 EVO 500GB
Serial Number:                      S3X4NB0K501841X
Firmware Version:                   3B7QCXE7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 500,107,862,016 [500 GB]
Unallocated NVM Capacity:           0
Controller ID:                      2
Number of Namespaces:               1
Namespace 1 Size/Capacity:          500,107,862,016 [500 GB]
Namespace 1 Utilization:            285,444,767,744 [285 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 5581b4b31f
Local Time is:                      Mon Feb 24 23:24:31 2020 CST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0007):   Security Format Frmw_DL
Optional NVM Commands (0x001f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     83 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     6.04W       -        -    0  0  0  0        0       0
1 +     5.09W       -        -    1  1  1  1        0       0
2 +     4.08W       -        -    2  2  2  2        0       0
3 -   0.0400W       -        -    3  3  3  3      210    1500
4 -   0.0050W       -        -    4  4  4  4     2200    6000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        34 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    8,699,295 [4.45 TB]
Data Units Written:                 9,937,895 [5.08 TB]
Host Read Commands:                 86,990,454
Host Write Commands:                60,449,849
Controller Busy Time:               357
Power Cycles:                       195
Power On Hours:                     243
Unsafe Shutdowns:                   44
Media and Data Integrity Errors:    0
Error Information Log Entries:      83
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               34 Celsius
Temperature Sensor 2:               39 Celsius

Error Information (NVMe Log 0x01, max 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
 0         83     0  0x00b0  0x4212  0x028            0     -     -
 1         82     0  0x0016  0x4212  0x028            0     1     -
 2         81     0  0x0011  0x4212  0x028            0     1     -
 3         80     0  0x000a  0x4212  0x028            0     1     -
 4         79     0  0x0056  0x4212  0x028            0     -     -
 5         78     0  0x0046  0x4212  0x028            0     -     -
 6         77     0  0x007c  0x4212  0x028            0     -     -
 7         76     0  0x0078  0x4212  0x028            0     -     -
 8         75     0  0x00c6  0x4212  0x028            0     -     -
 9         74     0  0x00da  0x4212  0x028            0     -     -
10         73     0  0x0054  0x4212  0x028            0     -     -
11         72     0  0x00fe  0x4212  0x028            0     -     -
12         71     0  0x00c8  0x4212  0x028            0     -     -
13         70     0  0x00f6  0x4212  0x028            0     -     -
14         69     0  0x003f  0x4212  0x028            0     -     -
15         68     0  0x006c  0x4212  0x028            0     -     -
... (48 entries not shown)
Code:
Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning : 0
temperature : 32 C
available_spare : 100%
available_spare_threshold : 10%
percentage_used : 1%
endurance group critical warning summary: 0
data_units_read : 8,699,271
data_units_written : 9,937,359
host_read_commands : 86,989,736
host_write_commands : 60,440,491
controller_busy_time : 357
power_cycles : 195
power_on_hours : 243
unsafe_shutdowns : 44
media_errors : 0
num_err_log_entries : 83
Warning Temperature Time : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1           : 32 C
Temperature Sensor 2           : 38 C
Thermal Management T1 Trans Count : 0
Thermal Management T2 Trans Count : 0
Thermal Management T1 Total Time : 0
Thermal Management T2 Total Time : 0
Code:
test: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=64
fio-3.18
Starting 1 process

test: (groupid=0, jobs=1): err= 0: pid=4794: Mon Feb 24 23:33:25 2020
 read: IOPS=44.3k, BW=173MiB/s (182MB/s)(3070MiB/17736msec)
  bw (  KiB/s): min=148798, max=205644, per=100.00%, avg=177361.71, stdev=13880.86, samples=35
  iops        : min=37199, max=51411, avg=44340.17, stdev=3470.22, samples=35
 write: IOPS=14.8k, BW=57.8MiB/s (60.7MB/s)(1026MiB/17736msec); 0 zone resets
  bw (  KiB/s): min=50307, max=68894, per=100.00%, avg=59279.29, stdev=4794.75, samples=35
  iops        : min=12576, max=17223, avg=14819.37, stdev=1198.76, samples=35
 cpu          : usr=17.72%, sys=52.03%, ctx=273652, majf=0, minf=17
 IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
    submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
    complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
    issued rwts: total=785920,262656,0,0 short=0,0,0,0 dropped=0,0,0,0
    latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
  READ: bw=173MiB/s (182MB/s), 173MiB/s-173MiB/s (182MB/s-182MB/s), io=3070MiB (3219MB), run=17736-17736msec
 WRITE: bw=57.8MiB/s (60.7MB/s), 57.8MiB/s-57.8MiB/s (60.7MB/s-60.7MB/s), io=1026MiB (1076MB), run=17736-17736msec

Disk stats (read/write):
 nvme0n1: ios=783951/262028, merge=0/17, ticks=589056/5627, in_queue=190, util=99.89%



RE: NVME SSD Samsung 960 EVO Works! - xmixahlx - 02-24-2020

sweet.

useful info:
drive power reported information
power usage
battery impact
anything not working, like suspend
any configurations you have made


RE: NVME SSD Samsung 960 EVO Works! - Tekchip - 02-24-2020

(02-24-2020, 05:18 PM)xmixahlx Wrote: sweet.

useful info:
drive power reported information
power usage
battery impact
anything not working, like suspend
any configurations you have made

I'm not a linux noob per say but I've not worked with power or battery stuff within linux much. Only recently started using Linux on my personal laptops. Are there specific commands to run for each of these items?

This feeds in to my secondary questions about building a sort of testing suite(list of items and commands) for this testing so others who might give this a go can just use those and provide this information up front and in a uniform way.

Thanks for clarifying your request with needed commands so I can capture this info and then we can put together a testing doc of sorts.