[GH-ISSUE #122] /var/log/messages spam

kerem commented

2026-03-07 19:12:11 +03:00

Owner

Originally created by @NewFolk on GitHub (Sep 28, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/122

Originally assigned to: @007revad on GitHub.

Hi and thank you for this perfect project.

I am not sure in the reasons, but looks these messages appeared after this script.
Be honest I don't check messages very often.

Synology_enable_M2_volume v1.0.10
DS918+ DSM 7.2-64570-3

root@Server:~# tail -f /var/log/messages
2023-09-28T08:36:20+03:00 Server synostgd-disk[29430]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:37:20+03:00 Server synostgd-disk[29608]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:39:20+03:00 Server synostgd-disk[30025]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:40:20+03:00 Server synostgd-disk[30203]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:42:20+03:00 Server synostgd-disk[31038]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:43:20+03:00 Server synostgd-disk[31267]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:44:20+03:00 Server synostgd-disk[31641]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:45:20+03:00 Server synostgd-disk[32206]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:46:20+03:00 Server synostgd-disk[318]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:47:20+03:00 Server synostgd-disk[908]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:48:20+03:00 Server synostgd-disk[1486]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:49:20+03:00 Server synostgd-disk[2047]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:50:20+03:00 Server synostgd-disk[2630]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:51:20+03:00 Server synostgd-disk[3199]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:52:20+03:00 Server synostgd-disk[3770]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:53:20+03:00 Server disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:54:20+03:00 Server synostgd-disk[4947]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)
2023-09-28T08:55:20+03:00 Server synostgd-disk[5519]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273)

I would be very grateful if you could advise me with the reason of this spam and how it could be fixed

Originally created by @NewFolk on GitHub (Sep 28, 2023). Original GitHub issue: https://github.com/007revad/Synology_enable_M2_volume/issues/122 Originally assigned to: @007revad on GitHub. Hi and thank you for this perfect project. I am not sure in the reasons, but looks these messages appeared after this script. Be honest I don't check messages very often. Synology_enable_M2_volume v1.0.10 DS918+ DSM 7.2-64570-3 ``` root@Server:~# tail -f /var/log/messages 2023-09-28T08:36:20+03:00 Server synostgd-disk[29430]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:37:20+03:00 Server synostgd-disk[29608]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:39:20+03:00 Server synostgd-disk[30025]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:40:20+03:00 Server synostgd-disk[30203]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:42:20+03:00 Server synostgd-disk[31038]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:43:20+03:00 Server synostgd-disk[31267]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:44:20+03:00 Server synostgd-disk[31641]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:45:20+03:00 Server synostgd-disk[32206]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:46:20+03:00 Server synostgd-disk[318]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:47:20+03:00 Server synostgd-disk[908]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:48:20+03:00 Server synostgd-disk[1486]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:49:20+03:00 Server synostgd-disk[2047]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:50:20+03:00 Server synostgd-disk[2630]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:51:20+03:00 Server synostgd-disk[3199]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:52:20+03:00 Server synostgd-disk[3770]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:53:20+03:00 Server disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:54:20+03:00 Server synostgd-disk[4947]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) 2023-09-28T08:55:20+03:00 Server synostgd-disk[5519]: disk_monitor.c:289 The temperature[23] of /dev/nvme0n1 >= T2. (T1: -273, T2: -273) ``` I would be very grateful if you could advise me with the reason of this spam and how it could be fixed

kerem commented

2026-03-07 19:12:12 +03:00

Author

Owner

@007revad commented on GitHub (Sep 28, 2023):

I've never seen that before. But I've never looked for it before either.

I just checked /var/log/messages for my DS1821+ DSM 7.2-64570-2 and it doesn't have nvme temperature related log entries.

I also checked /var/log/messages for my DS720+ DSM 7.2.1-69057 and it doesn't have any disk_monitor log entries.

Plenty of people with a DS918+ just use the syno_hdd_db script and not the syno_enable_m2_volume script.

Do you want to:

Run syno_enable_m2_volume --restore
Reboot and run syno_hdd_db -n
Check your volume is still shown in storage manager.
Wait a couple of minutes and then check the log.

@007revad commented on GitHub (Sep 28, 2023): I've never seen that before. But I've never looked for it before either. I just checked /var/log/messages for my DS1821+ DSM 7.2-64570-2 and it doesn't have nvme temperature related log entries. I also checked /var/log/messages for my DS720+ DSM 7.2.1-69057 and it doesn't have any disk_monitor log entries. Plenty of people with a DS918+ just use the syno_hdd_db script and not the syno_enable_m2_volume script. Do you want to: 1. Run `syno_enable_m2_volume --restore` 2. Reboot and run `syno_hdd_db -n` 3. Check your volume is still shown in storage manager. 4. Wait a couple of minutes and then check the log.

kerem commented

2026-03-07 19:12:12 +03:00

Author

Owner

@NewFolk commented on GitHub (Oct 1, 2023):

Thank you for the replay. I've updated to 7.2.1 and while updating system have lost my nvme disk. Re-run syno_enable_m2_volume.sh helped me.
I have some critical services runs on SSD, so I'm sorry, but I'm not ready to experiments.

For now on 7.2.1 spam stays.

I guess something wrong could be with SSD. Or SMART Information.

root@Server:~# nvme list
Node             SN                   Model                                    Namespace Usage                      Format           FW Rev  
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1     S5H7NS0N841301H      Samsung SSD 970 EVO 500GB                1          90.79  GB / 500.11  GB    512   B +  0 B   2B2QEXE7
/dev/nvme0n1p1   S5H7NS0N841301H      Samsung SSD 970 EVO 500GB                1          90.79  GB / 500.11  GB    512   B +  0 B   2B2QEXE7
/dev/nvme0n1p2   S5H7NS0N841301H      Samsung SSD 970 EVO 500GB                1          90.79  GB / 500.11  GB    512   B +  0 B   2B2QEXE7
/dev/nvme0n1p3   S5H7NS0N841301H      Samsung SSD 970 EVO 500GB                1          90.79  GB / 500.11  GB    512   B +  0 B   2B2QEXE7
root@Server:~# smartctl --info /dev/nvme0n1
smartctl 6.5 (build date Sep 26 2022) [x86_64-linux-4.4.302+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: NVMe Status 0x200b
root@Server:~# sudo smartctl -a -d nvme -T permissive /dev/nvme0n1
smartctl 6.5 (build date Sep 26 2022) [x86_64-linux-4.4.302+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: NVMe Status 0x200b

@NewFolk commented on GitHub (Oct 1, 2023): Thank you for the replay. I've updated to 7.2.1 and while updating system have lost my nvme disk. Re-run syno_enable_m2_volume.sh helped me. I have some critical services runs on SSD, so I'm sorry, but I'm not ready to experiments. For now on 7.2.1 spam stays. I guess something wrong could be with SSD. Or SMART Information. ``` root@Server:~# nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 S5H7NS0N841301H Samsung SSD 970 EVO 500GB 1 90.79 GB / 500.11 GB 512 B + 0 B 2B2QEXE7 /dev/nvme0n1p1 S5H7NS0N841301H Samsung SSD 970 EVO 500GB 1 90.79 GB / 500.11 GB 512 B + 0 B 2B2QEXE7 /dev/nvme0n1p2 S5H7NS0N841301H Samsung SSD 970 EVO 500GB 1 90.79 GB / 500.11 GB 512 B + 0 B 2B2QEXE7 /dev/nvme0n1p3 S5H7NS0N841301H Samsung SSD 970 EVO 500GB 1 90.79 GB / 500.11 GB 512 B + 0 B 2B2QEXE7 root@Server:~# smartctl --info /dev/nvme0n1 smartctl 6.5 (build date Sep 26 2022) [x86_64-linux-4.4.302+] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read NVMe Identify Controller failed: NVMe Status 0x200b root@Server:~# sudo smartctl -a -d nvme -T permissive /dev/nvme0n1 smartctl 6.5 (build date Sep 26 2022) [x86_64-linux-4.4.302+] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read NVMe Identify Controller failed: NVMe Status 0x200b ```

kerem commented

2026-03-07 19:12:12 +03:00

Author

Owner

@007revad commented on GitHub (Oct 1, 2023):

Christian Franke, the co-creator of smartctrl, says for smartctrl v6.6 to try lease retry smartctrl --info /dev/nvme0 but DSM has smartctrl v6.5

I've never been able to get smartctrl --info to work DSM for an NVMe drive. I believe the smartctrl version in DSM is too old.

@007revad commented on GitHub (Oct 1, 2023): Christian Franke, the co-creator of smartctrl, says for smartctrl v6.6 to try lease retry `smartctrl --info /dev/nvme0` but DSM has smartctrl v6.5 I've never been able to get `smartctrl --info` to work DSM for an NVMe drive. I believe the smartctrl version in DSM is too old.