01-17-2021, 11:58 AM
Thanks for all the feedback! I likely won't try all of your suggestions, simply because I don't have the free time I'd like to. But I did try the overnight restic restore again, with two changes: 1) set the max latency to 0 (disabling APST), and 2) used my 5v/3a USB-C charger instead of the barrel charger (think the barrel was only getting 5v/2.4a max with the outlet). The result was no missing NVMe drive overnight, seeing evidence of continued operation, and still nearly full power (whereas before it would have shut off around 4am). So it appears to either be the lowest power state (as you surmise), or APST itself.
I did actually! I had already previously decompiled, changed the max link speed, and recompiled the device tree, and had no change in issues. I might try reverting this to Gen2 speeds to rule it out as a possible red herring (i.e. maybe APST is the only problem and Gen2 speeds are fine). For what it's worth, here's my SMART report. Notice that temp has reached nowhere near critical conditions. 37 Celsius was the highest I've seen, and reports no count (I presume that's what that is) of critical warnings, so temp doesn't appear to be an issue here.
(01-17-2021, 01:04 AM)dsimic Wrote: Edit: According to the Linux kernel NVMe driver source, only a single Toshiba NVMe SSD has confirmed APST-related issues. However, we clearly see that more drives are affected on certain systems. By the way, please make sure that the PCIe link in your PineBook Pro runs at Gen1 speed, as described here.
I did actually! I had already previously decompiled, changed the max link speed, and recompiled the device tree, and had no change in issues. I might try reverting this to Gen2 speeds to rule it out as a possible red herring (i.e. maybe APST is the only problem and Gen2 speeds are fine). For what it's worth, here's my SMART report. Notice that temp has reached nowhere near critical conditions. 37 Celsius was the highest I've seen, and reports no count (I presume that's what that is) of critical warnings, so temp doesn't appear to be an issue here.
Code:
smartctl 7.1 2019-12-30 r5022 [aarch64-linux-5.7.19-1-MANJARO-ARM] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: INTEL SSDPEKNW020T8
Serial Number: <redacted>
Firmware Version: 004C
PCI Vendor/Subsystem ID: 0x8086
IEEE OUI Identifier: <redacted>
Controller ID: 1
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2,048,408,248,320 [2.04 TB]
Namespace 1 Formatted LBA Size: 512
Local Time is: Sun Jan 17 12:42:27 2021 EST
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 77 Celsius
Critical Comp. Temp. Threshold: 80 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 5.50W - - 0 0 0 0 0 0
1 + 3.60W - - 1 1 1 1 0 0
2 + 2.60W - - 2 2 2 2 0 0
3 - 0.0300W - - 3 3 3 3 5000 5000
4 - 0.0040W - - 4 4 4 4 5000 9000
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: 36 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 6,929 [3.54 GB]
Data Units Written: 3,842,148 [1.96 TB]
Host Read Commands: 245,426
Host Write Commands: 15,698,447
Controller Busy Time: 1,535
Power Cycles: 22
Power On Hours: 79
Unsafe Shutdowns: 4
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Thermal Temp. 1 Transition Count: 4
Thermal Temp. 1 Total Time: 79
Error Information (NVMe Log 0x01, max 256 entries)
No Errors Logged
