Greetings Proxmox community!
I recently bought a Samsung pm1725a U.2 SSD, updated the firmware, and put it into service in my Proxmox server. It's working great, and `smartctl -a` in the console shows happy things.
While all that looks good, Proxmox is displeased:
When I press "Show S.M.A.R.T. Values", Proxmox is even further displeased:
I saw somebody having the same problem below, but they said they are not experiencing it in PVE, only PVB. I, however, am experiencing this in PVE.
https://forum.proxmox.com/threads/s-m-a-r-t-status-unknown.95417/post-421877
I'd be OK excluding this drive from smartmontools, but I'd prefer for everything to work according to plan. Tips would be appreciated here.
John
I recently bought a Samsung pm1725a U.2 SSD, updated the firmware, and put it into service in my Proxmox server. It's working great, and `smartctl -a` in the console shows happy things.
Code:
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.39-3-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
NVMe device successfully opened
Use 'smartctl -a' (or '-x') to print SMART (and more) information
root@lsnhg:/srv/scripts# nano /etc/smartd.conf
root@lsnhg:/srv/scripts# smartctl -a /dev/nvme0
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.39-3-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZWLL3T2HMJP-00003
Serial Number: **********
Firmware Version: GPNABB3Q
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 3,200,631,791,616 [3.20 TB]
Unallocated NVM Capacity: 0
Controller ID: 33
NVMe Version: 1.2
Number of Namespaces: 32
Local Time is: Sun Aug 21 17:55:11 2022 MST
Firmware Updates (0x17): 3 Slots, Slot 1 R/O, no Reset required
Optional Admin Commands (0x000e): Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x003e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Resv
Log Page Attributes (0x02): Cmd_Eff_Lg
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 78 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 25.00W - - 0 0 0 0 100 100
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 53 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 12%
Data Units Read: 31,794,435,155 [16.2 PB]
Data Units Written: 19,603,213,942 [10.0 PB]
Host Read Commands: 1,205,231,359,969
Host Write Commands: 724,927,251,939
Controller Busy Time: 229,284
Power Cycles: 149
Power On Hours: 20,291
Unsafe Shutdowns: 145
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 53 Celsius
Temperature Sensor 2: 53 Celsius
Temperature Sensor 3: 50 Celsius
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors LoggedWhile all that looks good, Proxmox is displeased:
When I press "Show S.M.A.R.T. Values", Proxmox is even further displeased:
I saw somebody having the same problem below, but they said they are not experiencing it in PVE, only PVB. I, however, am experiencing this in PVE.
https://forum.proxmox.com/threads/s-m-a-r-t-status-unknown.95417/post-421877
I'd be OK excluding this drive from smartmontools, but I'd prefer for everything to work according to plan. Tips would be appreciated here.
John
