mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #366] Drive temperature broken #628
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#628
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 @Ubsefor on GitHub (Oct 15, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/366
The script somehow breaks synology drive temperature reporting, it gets stuck at 29C constantly, while smartmontools report correct temperature
@007revad commented on GitHub (Oct 15, 2024):
Do you mean smartctl?
Which Synology model and DSM version?
@Ubsefor commented on GitHub (Oct 15, 2024):
Yes, smartctl -a /dev/block | grep "Temp" shows correct temperature, its also shown correctly in "scrutiny"
Right now I’m patching synodrivedb.db by hand, we'll see if that will help
UPD: It did not, I believe this is due to model.dtb edits; drive info also contains firmware version, which it did not have before the patch
SA6400, 7.2.2-72806
@007revad commented on GitHub (Oct 15, 2024):
syno_hdd_db only edits model.dtb if the script detects a E10M20-T1, M2D20, M2D18 or M2D17 connected to a NAS model that does not officially support them and the E10M20-T1, M2D20, M2D18 or M2D17 is not already in model.dtb.
So the script would not touch model.dtb on a SA6400