If you move to newer generation NVMe-based flash storage, smartctl won\u2019t work anymore. It looks like support for NVMe in Smartmontools<\/strong> is coming<\/a>, and it would be great to get a single tool that supports both SATA and NVMe flash storage.<\/p>\n\n\n\n In the meantime, you can use the nvme tool available from the nvme-cli package. It provides some basic information for NVMe devices.<\/p>\n\n\n\n To get information about the NVMe devices installed:<\/p>\n\n\n\n To get SMART information:<\/p>\n\n\n\n Available Spare<\/strong>. Contains a normalized percentage (0 to 100%) of the remaining spare capacity that is available.<\/p>\n\n\n\n Available Spare Threshold<\/strong>. When the Available Spare capacity falls below the threshold indicated in this field, an asynchronous event completion can occur. The value is indicated as a normalized percentage (0 to 100%).<\/p>\n\n\n\n Percentage Used<\/strong>. Contains a vendor specific estimate of the percentage of the NVM subsystem life used, based on actual usage and the manufacturer\u2019s prediction of NVM life.<\/p>\n\n\n\n (Note: the number can be more than 100% if you\u2019re using storage for longer than its planned life.)<\/p>\n\n\n\n Data Units Read\/Data Units Written<\/strong>. This is the number of 512-byte data units that are read\/written, but it is measured in an unusual way. The first value corresponds to 1000 of the 512-byte units. So you can multiply this value by 512000 to get value in bytes. It does not include meta-data accesses.<\/p>\n\n\n\n Host Read\/Write Commands<\/strong>. The number of commands of the appropriate type issued. Using this value, as well as one below, you can compute the average IO size for \u201cphysical\u201d reads and writes.<\/p>\n\n\n\n Controller Busy Time<\/strong>. Time in minutes that the controller was busy servicing commands. This can be used to gauge long-term storage load trends.<\/p>\n\n\n\n Unsafe Shutdowns<\/strong>. The number of times a power loss happened without a shutdown notification being sent. Depending on the NVMe device you\u2019re using, an unsafe shutdown might corrupt user data.<\/p>\n\n\n\n Warning Temperature Time\/Critical Temperature Time<\/strong>. The time in minutes a device operated above a warning or critical temperature. It should be zeroes.<\/p>\n\n\n\n Wear_Leveling<\/strong>. This shows how much of the rated cell life was used, as well as the min\/max\/avg write count for different cells. In this case, it looks like the cells are rated for 1800 writes and about 1100 on average were used<\/p>\n\n\n\n Timed Workload Media Wear<\/strong>. The media wear by the current \u201cworkload.\u201d This device allows you to measure some statistics from the time you reset them (called the \u201cworkload\u201d) in addition to showing the device lifetime values.<\/p>\n\n\n\n Timed Workload Host Reads<\/strong>. The percentage of IO operations that were reads (since the workload timer was reset).<\/p>\n\n\n\n Thermal Throttle Status<\/strong>. This shows if the device is throttled due to overheating, and when there were throttling events in the past.<\/p>\n\n\n\n Nand Bytes Written<\/strong>. The bytes written to NAND cells. For this device, the measured unit seems to be in 32MB values<\/a>. It might be different for other devices.<\/p>\n\n\n\n Host Bytes Written<\/strong>. The bytes written to the NVMe storage from the system. This unit also is in 32MB values. The scale of these values is not very important, as they are the most helpful for finding the write amplification of your workload. This ratio is measured in writes to NAND and writes to HOST. For this example, the Write Amplification Factor (WAF) is 16185227 \/ 6405605 = 2.53<\/strong> <\/p>\n","protected":false},"excerpt":{"rendered":" Checking NVMe Flash Health If you move to newer generation NVMe-based flash storage, smartctl won\u2019t work anymore. It looks like support for NVMe in Smartmontools is coming, and it would be great to get a single tool that supports both SATA and NVMe flash storage. In the meantime, you can use the nvme tool available from the nvme-cli package. It provides … Continue reading NVME Stats<\/span> #nvme list
Node SN Model Namespace Usage Format FW Rev \n---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------\n\/dev\/nvme0n1 S4EWNG0M116212J Samsung SSD 970 EVO Plus 1TB 1 713.05 GB \/ 1.00 TB 512 B + 0 B 1B2QEXM7\n<\/pre>
<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n#nvme smart-log \/dev\/nvme0
Smart Log for NVME device:nvme0 namespace-id:ffffffff
critical_warning : 0
temperature : 37 C
available_spare : 100%
available_spare_threshold : 10%
percentage_used : 0%
data_units_read : 13,820,831
data_units_written : 20,647,263
host_read_commands : 197,831,770
host_write_commands : 499,344,371
controller_busy_time : 1,663
power_cycles : 36
power_on_hours : 8,091
unsafe_shutdowns : 18
media_errors : 0
num_err_log_entries : 0
Warning Temperature Time : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1 : 37 C
Temperature Sensor 2 : 34 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<\/pre><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n