Other Wear and tear of ssd`s and nvme`s

Checking my hard drives and trying to understand RAW_VALUE.
What it should be ?
I have 1 ssd with 466 ( 177 Wear Leveling Count ) 1355 ( 233 Media Wearout Indicator ) 1169 ( 241 Host Writes GiB ) and anotrher SSD is half of it - give a take.
Also i have 5 nvme`1s would be great to know which command to use to check health.

Im using smartmontools
 
Also i have 5 nvme`1s would be great to know which command to use to check health.

Im using smartmontools
I am using a command like smartctl -d nvme -a /dev/nvme0 ... if this is what you mean. This should output everything a drive is capable. Drives may be different.

Code:
# smartctl -d nvme -x /dev/nvme0|tail -n 30

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

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        37 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    4,766,423 [2.44 TB]
Data Units Written:                 5,069,708 [2.59 TB]
Host Read Commands:                 80,616,715
Host Write Commands:                56,112,653
Controller Busy Time:               6,665
Power Cycles:                       104
Power On Hours:                     111
Unsafe Shutdowns:                   24
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 8 of 8 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged
 
This is just my wild guess, but perhaps emulators/wine can help. It probably needs nvme pass-though. Let us know if you have any success.
I might be able to pass 1 nvme as other 4 are in raid card and runs FreeBSD OS.
For NVMe, probably. For SATA you would have to pass in the whole controller with all ports.
This is a bit complicated to my task. I might just use one disk for windows and do it that way.
 
For NVMe, probably.
NVMe passthrough works great on my end:
Code:
ppt0@pci0:7:0:0:    class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 device=0x5013 subvendor=0x2646 subdevice=0x5013
    vendor     = 'Kingston Technology Company, Inc.'
    device     = 'KC3000/FURY Renegade NVMe SSD [E18]'
    class      = mass storage
    subclass   = NVM
 
Back
Top