mirror of
https://github.com/007revad/Synology_SMART_info.git
synced 2026-04-25 16:15:48 +03:00
[GH-ISSUE #64] output from NVMe drives is messed up #12
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_SMART_info#12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bertoalbert on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/007revad/Synology_SMART_info/issues/64
Hi Dave,
I'm running your script and the HDD-drives work quiet fine. But the nvme-drives are a little bit scrambled. Is there anything I can do?
Best,
bertoal
`
Der Aufgabenplaner hat eine ausgelöste Aufgabe abgeschlossen.
Aufgabe: smart-007revad
Start: Tue, 24 Feb 2026 21:12:50 GMT
Ende: Tue, 24 Feb 2026 21:13:06 GMT
Aktueller Status: 1 (Unterbrochen)
Standardausgabe/Fehler:
Synology_SMART_info v1.4.37 - by 007revad
ds423plus DS423+ DSM 7.3.2-86009-1
Using smartctl 7.5
Using options: --email
Drive 1 MG07ACA14TE ZXXXXXXXXXX /dev/sata3
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 0
9 Power_On_Hours 12720
10 Spin_Retry_Count 0
194 Temperature_Celsius 29
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
Drive 2 MG07ACA14TE ZxxxxxxxxxG /dev/sata4
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 0
9 Power_On_Hours 12728
10 Spin_Retry_Count 0
194 Temperature_Celsius 31
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
Drive 3 ST4000VN006-3CW104 ZxxxxxxxL /dev/sata1
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 1
9 Power_On_Hours 23360
10 Spin_Retry_Count 0
187 Reported_Uncorrect 0
188 Command_Timeout 0
194 Temperature_Celsius 32
195 Hardware_ECC_Recovered 0
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
Drive 4 ST4000VN006-3CW104 WxxxxxxD /dev/sata2
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 0
9 Power_On_Hours 19922
10 Spin_Retry_Count 0
187 Reported_Uncorrect 0
188 Command_Timeout 0
194 Temperature_Celsius 32
195 Hardware_ECC_Recovered 0
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
M.2 Drive 1 Samsung SSD 970 EVO Plus 1TB Sxxxxxxxx7A /dev/nvme0n1
SMART overall-health self-assessment test result: PASSED
/volume1/scripts/Synology_SMART_info/syno_smart_info.sh: line 1010: [[: 76
75
74
0: syntax error in expression (error token is "75
74
0")
SMART Error Counter Log: No Errors Logged
/volume1/scripts/Synology_SMART_info/syno_smart_info.sh: line 1517: [[: 76
75
74
0: syntax error in expression (error token is "75
74
0")
/volume1/scripts/Synology_SMART_info/syno_smart_info.sh: line 1522: [[: 76
75
74
0: syntax error in expression (error token is "75
74
0")
1 Critical_Warning 0
2 Temperature 41 C
5 Percentage_Used 0%
12 Power_On_Hours 21986
13 Unsafe_Shutdowns 2
14 Media_Errors 0
M.2 Drive 2 Samsung SSD 970 EVO Plus 1TB SxxxxxxxF /dev/nvme1n1
SMART overall-health self-assessment test result: PASSED
/volume1/scripts/Synology_SMART_info/syno_smart_info.sh: line 1010: [[: 59
58
57
0: syntax error in expression (error token is "58
57
0")
SMART Error Counter Log: No Errors Logged
/volume1/scripts/Synology_SMART_info/syno_smart_info.sh: line 1517: [[: 59
58
57
0: syntax error in expression (error token is "58
57
0")
/volume1/scripts/Synology_SMART_info/syno_smart_info.sh: line 1522: [[: 59
58
57
0: syntax error in expression (error token is "58
57
0")
1 Critical_Warning 0
2 Temperature 39 C
5 Percentage_Used 0%
12 Power_On_Hours 21986
13 Unsafe_Shutdowns 2
14 Media_Errors 0
Von ds423plus
`
@007revad commented on GitHub (Feb 24, 2026):
I can see what's gone wrong.
What do the following commands return?
@bertoalbert commented on GitHub (Feb 24, 2026):
thanks for your response:
``
akXXXg@ds423plus:~$ sudo nvme error-log /dev/nvme0 | grep error_count
error_count : 76
error_count : 75
error_count : 74
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
and
aXXXXXg@ds423plus:~$ sudo nvme error-log /dev/nvme1 | grep error_count
error_count : 59
error_count : 58
error_count : 57
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
error_count : 0
@007revad commented on GitHub (Feb 24, 2026):
Try this version: https://github.com/007revad/Synology_SMART_info/releases/tag/v1.4.38
@bertoalbert commented on GitHub (Feb 24, 2026):
wow - fast, faster, Dave
It look better! Is this the way it should looks like?
``
Der Aufgabenplaner hat eine ausgelöste Aufgabe abgeschlossen.
Aufgabe: smart-007revad
Start: Tue, 24 Feb 2026 23:08:11 GMT
Ende: Tue, 24 Feb 2026 23:08:23 GMT
Aktueller Status: 15 (Unterbrochen)
Standardausgabe/Fehler:
Synology_SMART_info v1.4.38 - by 007revad
ds423plus DS423+ DSM 7.3.2-86009-1
Using smartctl 7.5
Using options: --email
Drive 1 MG07ACA14TE XXXXXXXX /dev/sata3
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 0
9 Power_On_Hours 12722
10 Spin_Retry_Count 0
194 Temperature_Celsius 28
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
Drive 2 MG07ACA14TE XXXXXXX /dev/sata4
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 0
9 Power_On_Hours 12730
10 Spin_Retry_Count 0
194 Temperature_Celsius 30
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
Drive 3 ST4000VN006-3CW104 XXXXXXXXXXXXXXXXX /dev/sata1
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 1
9 Power_On_Hours 23362
10 Spin_Retry_Count 0
187 Reported_Uncorrect 0
188 Command_Timeout 0
194 Temperature_Celsius 31
195 Hardware_ECC_Recovered 0
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
Drive 4 ST4000VN006-3CW104 XXXXXXXXXXXXXXXX /dev/sata2
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: No Errors Logged
1 Raw_Read_Error_Rate 0
5 Reallocated_Sector_Ct 0
7 Seek_Error_Rate 0
9 Power_On_Hours 19924
10 Spin_Retry_Count 0
187 Reported_Uncorrect 0
188 Command_Timeout 0
194 Temperature_Celsius 30
195 Hardware_ECC_Recovered 0
197 Current_Pending_Sector 0
198 Offline_Uncorrectable 0
199 UDMA_CRC_Error_Count 0
M.2 Drive 1 Samsung SSD 970 EVO Plus 1TB XXXXXXXX /dev/nvme0n1
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: 76
Critical Warning: 0x00
Temperature: 54 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 46,167,813 [23.6 TB]
Data Units Written: 98,545,540 [50.4 TB]
Host Read Commands: 322,259,345
Host Write Commands: 2,680,716,885
Controller Busy Time: 12,404
Power Cycles: 7
Power On Hours: 21,988
Unsafe Shutdowns: 2
Media and Data Integrity Errors: 0
Error Information Log Entries: 76
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 54 Celsius
Temperature Sensor 2: 65 Celsius
M.2 Drive 2 Samsung SSD 970 EVO Plus 1TB XXXXX /dev/nvme1n1
SMART overall-health self-assessment test result: PASSED
SMART Error Counter Log: 59
Critical Warning: 0x00
Temperature: 50 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 8,130,264 [4.16 TB]
Data Units Written: 98,545,732 [50.4 TB]
Host Read Commands: 73,783,180
Host Write Commands: 2,680,821,803
Controller Busy Time: 11,612
Power Cycles: 7
Power On Hours: 21,988
Unsafe Shutdowns: 2
Media and Data Integrity Errors: 0
Error Information Log Entries: 59
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 50 Celsius
Temperature Sensor 2: 65 Celsius
@007revad commented on GitHub (Feb 24, 2026):
Normally the output for NVMe drives would look similar to the HDDs (with just the important SMART attributes, neatly formatted), but because your NVMe drives have an error log count greater than 0 it's showing the full SMART output.
I should update the
-ior--incrementaloptions to also log and monitor each drives' error count. That way if you schedule the script to run as root with the--email --incrementaloptions you would get an email anytime the error log count increases for any drive. Like this:@bertoalbert commented on GitHub (Feb 25, 2026):
Hi Dave, thanks for your support. I updated "--incremental" and got:
`Aufgabe: smart-007revad
Start: Wed, 25 Feb 2026 19:50:36 GMT
Ende: Wed, 25 Feb 2026 19:50:36 GMT
Aktueller Status: 1 (Unterbrochen)
Standardausgabe/Fehler:
getopt: unrecognized option '--incremental'
Synology_SMART_info v1.4.38 - by 007revad
Usage: syno_smart_info.sh [options]
Options:
-a, --all Show all SMART attributes
-e, --email Disable colored text in output scheduler emails
-i, --increased Only show important attributes that have increased
-u, --update Update the script to the latest version
-h, --help Show this help message
-v, --version Show the script version
I will check for some days and maybe I return just to "--e" to get a better overview.
Best, bertoalbert
`
@007revad commented on GitHub (Feb 25, 2026):
Sorry. It's
--increased(not --incremental)@bertoalbert commented on GitHub (Feb 25, 2026):
now I don't get any mails - in this case, it is a good sign ;-)
@007revad commented on GitHub (Feb 25, 2026):
You can edit smart.log (in the same folder as syno_smart_info.sh) to test it.
Change
Unsafe_Shutdowns=2toUnsafe_Shutdowns=1then run the scheduled task and you should get an email showing that Unsafe_Shutdowns has increased from 1 to 2.@bertoalbert commented on GitHub (Feb 25, 2026):
unfortunately it doesn't work, but it doesn't matter by now - I'm happy to get an email with all the data - maybe I will check tomorrow
@007revad commented on GitHub (Feb 25, 2026):
When using --incremental make sure you set the schedule to email when the script terminates abnormally.
@bertoalbert commented on GitHub (Feb 26, 2026):
when I change the value and run the script, the values remain "1" in the smart.log
after starting a new task (weekly and not at "system start") the value changed again to "2"
I'll keep an eye on it. Thanks for your support