[GH-ISSUE #135] NAS shutdown due to high temperature on NVME disk #767

Closed
opened 2026-03-12 16:35:47 +03:00 by kerem · 4 comments
Owner

Originally created by @aferende on GitHub (Aug 16, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/135

Hi everyone,
I open this thread because I had a high temperature problem on my NVME drives used in a RAID Pool on my NAS DS1821+.
The disks are 2 WD Red SN700 2 TB (these are the technical specifications: https://www.westerndigital.com/it-it/products/internal-drives/wd-red-sn700-nvme-ssd#WDS200T1R0C)
Especially the 2nd NVME (only the 2th strangely) reached 71 degrees and the NAS shut down for protection.

Searching the internet I found this post:
https://www.reddit.com/r/synology/comments/12aci2n/disk_overheat_disk_m2_drive_1had_reached_70c/
where some NAS system files are indicated where it is possible to change the operating limit temperature.

I use these disks on a Pool dedicated to VMM and the temperature peak was reached when I went to delete some old snapshots. At that point the system started recovering the unoccupied space and made the temperature of the 2nd disk rise from 41 degrees to 71 degrees in a few seconds.
(I haven't activated LTRIM, Do you suggest to activate it? Could improve this phase?)

Given that in the meantime I ordered 2 heat synks for NVME https://www.amazon.it/gp/product/B09NRKT3GW/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 (hoping they improve the situation),

I would like to understand from you if you have encountered the same problem, if there is a way to insert in the script some option that modifies the temperature limit in NAS system config file (always if it is the case to do so) maybe as optional.

Thank you all

Originally created by @aferende on GitHub (Aug 16, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/135 Hi everyone, I open this thread because I had a **high temperature problem on my NVME drives** used in a RAID Pool on my NAS DS1821+. The disks are 2 WD Red SN700 2 TB (these are the technical specifications: https://www.westerndigital.com/it-it/products/internal-drives/wd-red-sn700-nvme-ssd#WDS200T1R0C) Especially the 2nd NVME (only the 2th strangely) **reached 71 degrees and the NAS shut down for protection**. Searching the internet I found this post: https://www.reddit.com/r/synology/comments/12aci2n/disk_overheat_disk_m2_drive_1had_reached_70c/ where some NAS system files are indicated where it is possible to change the operating limit temperature. I use these disks on a Pool dedicated to VMM and **the temperature peak was reached when I went to delete some old snapshots. At that point the system started recovering the unoccupied space and made the temperature of the 2nd disk rise from 41 degrees to 71 degrees in a few seconds.** (I haven't activated LTRIM, Do you suggest to activate it? Could improve this phase?) Given that in the meantime I ordered 2 heat synks for NVME https://www.amazon.it/gp/product/B09NRKT3GW/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 (hoping they improve the situation), I would like to understand from you if you have encountered the same problem, if there is a way to insert in the script some option that modifies the temperature limit in NAS system config file (always if it is the case to do so) maybe as optional. Thank you all
kerem closed this issue 2026-03-12 16:35:52 +03:00
Author
Owner

@007revad commented on GitHub (Aug 17, 2023):

You could try enabling TRIM. But I suspect the process that deletes old snapshots and then recovers the now unused space would still cause your overheating issue.

I think getting some heatsinks is the best option.

You could set the fan speed to Full before doing any snapshot deletions then set it back to your preferred setting after - but that would become annoying to have to do regularly. If the NVMe drive(s) still overheat with the fan set to full then nothing you can change in the fan's config file will help - part from changing the shutdown temperature.

Your NVMe drives have a Operating temp of 0°C to 70°C so I would not increase the shutdown temperature about the current 70°C. The M.2 shutdown temp in DSM 7.2 on the DS1821+ is set to 71°C

There are a few settings that could help:

  • Change the fan speeds so the fans increase their speed to full speed sooner.
  • Change the 2nd and 3rd temperatures to lower values so the fans increase their at a lower temperature.
  • Change the shutdown temperature to a higher temperature (not something I'd do unless I had checked the maximum temperature for my specific brand/model of NVMe drive(s). Your NVMe drives have a Operating temp of 0°C to 70°C so I would not increase the shutdown temperature about the current 70°C.
  • The skip_check_temp="10" looks like it tells DSM how long to wait between temperature checks.
  • The period="30" looks like how long DSM will run the fans at that speed before reverting back to checking the temperature.

With the M.2 drives located where they are I suspect it would take some time for them to benefit from an increase in fan speed.

The DS1821+ schemd.xml file is different to a Synology with an Intel CPU.

<adt_fan_config skip_check_temp="10" type="DUAL_MODE_LOW" hibernation_speed="UNKNOWN">
	<alert_config threshold="2" period="30" alert_temp="68" shutdown_temp="71" name="m2"/>

	<manual_config name="m2_temperature" threshold="2" period="30" temp="0" fan_speed="70"/>
	<manual_config name="m2_temperature" threshold="2" period="30" temp="48" fan_speed="130"/>
	<manual_config name="m2_temperature" threshold="2" period="30" temp="59" fan_speed="170"/>
	<manual_config name="m2_temperature" threshold="2" period="30" temp="64" fan_speed="255"/>
<!-- gh-comment-id:1682307457 --> @007revad commented on GitHub (Aug 17, 2023): You could try enabling TRIM. But I suspect the process that deletes old snapshots and then recovers the now unused space would still cause your overheating issue. I think getting some heatsinks is the best option. You could set the fan speed to Full before doing any snapshot deletions then set it back to your preferred setting after - but that would become annoying to have to do regularly. If the NVMe drive(s) still overheat with the fan set to full then nothing you can change in the fan's config file will help - part from changing the shutdown temperature. Your NVMe drives have a Operating temp of 0°C to 70°C so I would not increase the shutdown temperature about the current 70°C. The M.2 shutdown temp in DSM 7.2 on the DS1821+ is set to 71°C There are a few settings that could help: - Change the fan speeds so the fans increase their speed to full speed sooner. - Change the 2nd and 3rd temperatures to lower values so the fans increase their at a lower temperature. - Change the shutdown temperature to a higher temperature (not something I'd do unless I had checked the maximum temperature for my specific brand/model of NVMe drive(s). Your NVMe drives have a Operating temp of 0°C to 70°C so I would not increase the shutdown temperature about the current 70°C. - The skip_check_temp="10" **looks** like it tells DSM how long to wait between temperature checks. - The period="30" **looks** like how long DSM will run the fans at that speed before reverting back to checking the temperature. With the M.2 drives located where they are I suspect it would take some time for them to benefit from an increase in fan speed. The DS1821+ schemd.xml file is different to a Synology with an Intel CPU. ``` <adt_fan_config skip_check_temp="10" type="DUAL_MODE_LOW" hibernation_speed="UNKNOWN"> <alert_config threshold="2" period="30" alert_temp="68" shutdown_temp="71" name="m2"/> <manual_config name="m2_temperature" threshold="2" period="30" temp="0" fan_speed="70"/> <manual_config name="m2_temperature" threshold="2" period="30" temp="48" fan_speed="130"/> <manual_config name="m2_temperature" threshold="2" period="30" temp="59" fan_speed="170"/> <manual_config name="m2_temperature" threshold="2" period="30" temp="64" fan_speed="255"/> ```
Author
Owner

@aferende commented on GitHub (Aug 18, 2023):

Hi Dave and thanks for the reply.
I would say that the heatsink and LTRIM combination make the difference.
I retried the same operations from the past days and this time the NVME disk temperature never went above 58 degrees.
I agree that the NVME location doesn't help with cooling (and perhaps this is also why Synology doesn't support NVME storage pools); I also have a few millimeters from the NVME (on the left) a 10gbe ethernet card that heats like a water heater (I forgot to mention it in the first post :-) )

For everyone's convenience, here are some photos of the disks with the heatsink mounted.
I'd say there's enough room to mount the heatsink without it touching the drive in the first bay:

photo_2023-08-18_16-58-53
photo_2023-08-18_16-59-05
photo_2023-08-18_16-59-08
photo_2023-08-18_16-59-12

Thanks Andrea.

<!-- gh-comment-id:1684049234 --> @aferende commented on GitHub (Aug 18, 2023): Hi Dave and thanks for the reply. I would say that the **heatsink and LTRIM combination make the difference**. I retried the same operations from the past days and this time the NVME disk temperature never went above 58 degrees. I agree that the NVME location doesn't help with cooling (and perhaps this is also why Synology doesn't support NVME storage pools); I also have a few millimeters from the NVME (on the left) a 10gbe ethernet card that heats like a water heater (I forgot to mention it in the first post :-) ) For everyone's convenience, here are some photos of the disks with the heatsink mounted. I'd say there's enough room to mount the heatsink without it touching the drive in the first bay: ![photo_2023-08-18_16-58-53](https://github.com/007revad/Synology_HDD_db/assets/13355101/f281294a-9891-43c2-8d38-b2a05af4ae24) ![photo_2023-08-18_16-59-05](https://github.com/007revad/Synology_HDD_db/assets/13355101/7c7d0e7e-ab21-4a3a-92a6-ae3d3326bd11) ![photo_2023-08-18_16-59-08](https://github.com/007revad/Synology_HDD_db/assets/13355101/3ec014e2-4b78-41e1-b351-307930594a21) ![photo_2023-08-18_16-59-12](https://github.com/007revad/Synology_HDD_db/assets/13355101/63293b13-79cd-41de-a591-c9b3a380f037) Thanks Andrea.
Author
Owner

@007revad commented on GitHub (Aug 21, 2023):

Thanks for pictures. I forgot that the NVMe slots are beside drive 1 in a DS1821+.

I'm not sure how effective that heatsink would be at cooling with the fins running the length of the drive. maybe something like this https://www.ebay.com.au/itm/124977791664 would cool better since the airflow. Though the mass of the heatsink should prevent the NVMe drive from rapidly increasing in temperature.

It looks like it's a perfect fit. Do you know how think it is?

<!-- gh-comment-id:1685462087 --> @007revad commented on GitHub (Aug 21, 2023): Thanks for pictures. I forgot that the NVMe slots are beside drive 1 in a DS1821+. I'm not sure how effective that heatsink would be at cooling with the fins running the length of the drive. maybe something like this https://www.ebay.com.au/itm/124977791664 would cool better since the airflow. Though the mass of the heatsink should prevent the NVMe drive from rapidly increasing in temperature. It looks like it's a perfect fit. Do you know how think it is?
Author
Owner

@aferende commented on GitHub (Aug 21, 2023):

6mm should still be acceptable.
The ones I got (Amazon link) are 3mm thick.
Not knowing if they were too tall, I didn't want to overdo it

<!-- gh-comment-id:1686098511 --> @aferende commented on GitHub (Aug 21, 2023): 6mm should still be acceptable. The ones I got (Amazon link) are 3mm thick. Not knowing if they were too tall, I didn't want to overdo it
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_HDD_db#767
No description provided.