QNAP TS-877 Truenas Journal

That could be the cause.

Your disk was 56C when you ran the smartctl -a command.

TrueNAS monitors the disk temperature, and alerts you if it exceeds a threshold

If you look at System Settings → Services, then configure the SMART service you’ll see the global temp critical temp (mine is 44C)

Then on each disk you can overrride if you want, say if its an NVMe that you don’t mind reaching a toasty 60C.

1 Like

They really do look like sweet cases/systems if you can get TrueNAS running well on it… and its not a drive cooker :wink:

No ECC though right?

yeah no ecc. thats my only qualm with it. so unfortunately i have to make do without. also it didn’t originally come with this cpu, i downgraded because i want to use less power (used it for many years didn’t find issue with it, and from my usage i barely utilize more than 10-25% of the cpu most of the time anyway), and use the cpu for a different project :sweat_smile:

I think ryzen 2600 works on this system?
https://www.reddit.com/r/qnap/comments/rubrr2/cpu_upgrade_on_ts877/

also this nas isnt bad for zfs and they were going to add quts hero to it via a license sale, but never happened. then they flagged it for EOL…

so taking things into my own hands i had to go truenas just to get zfs :smirk: unraid was another route, but i went for truenas. neither is a bad choice

i made the change, ty.

yeah 60c is fine with me.

hm login and ui slightly slow not sure why.

i have a rsync from ts-253d ongoing :X

This slow-mode happens sometimes then goes away on it’s own hm…

I think there might be an active issue…

(edit: find it annoying that Discourse censors my quote.)

1 Like

after i set the temp alert limit to 60 i got this new alert

New alerts:

  • Device: /dev/sdb [SAT], Temperature 60 Celsius reached critical limit of 60 Celsius (Min/Max ??/60).

Uhuh.

How hot is your drive now? 60C?

Plus, you’ve been running an rsync for a few days… so the drives are working pretty hard… building up quite a bit of heat.

If the case cover is on, and all the fans are spinning at 100%, then unfortunately the cooling is not quite good enough, but that’s really QNAP’s fault.

Is it possible that the QNAP software normally controls the fans and now its not?

root@xxxxxxx[~]# smartctl -a /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.16-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate IronWolf Pro
Device Model: ST4000NE001-3CR101
Serial Number: xxxxxxxxxxxxxxxxxx
LU WWN Device Id: xxxxxxxxxxxxxxxxxxxxx
Firmware Version: EN01
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-4 (minor revision not indicated)
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Apr 21 23:59:03 2024 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 559) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 348) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x50bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 080 064 044 Pre-fail Always - 93776682
3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 56
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 080 060 045 Pre-fail Always - 111484283
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6436
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 56
18 Head_Health 0x000b 100 100 050 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 040 031 000 Old_age Always - 60 (Min/Max 53/69)
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 41
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 690
194 Temperature_Celsius 0x0022 060 069 000 Old_age Always - 60 (0 30 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 6408h+42m+22.385s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 8362735949
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 109492560310

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Extended offline Completed without error 00% 6065 -

2 Extended offline Completed without error 00% 5321 -

3 Extended offline Completed without error 00% 4625 -

4 Extended offline Completed without error 00% 3897 -

5 Extended offline Completed without error 00% 3756 -

6 Extended offline Completed without error 00% 3155 -

7 Extended offline Completed without error 00% 2435 -

8 Extended offline Completed without error 00% 1691 -

9 Extended offline Completed without error 00% 971 -

#10 Extended offline Completed without error 00% 227 -
#11 Extended offline Completed without error 00% 15 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try ‘smartctl -x’ for more

root@xxxxxxxxx[~]#

This drive was sent to be as a recertified drive for my rma replacement under warranty :thinking: i did the smart tests it showed nothing wrong with it.

Seagate Ironwolf Pro 4TB 256MB HDD ST4000NE001 Hard Disk Drive Seagate Hard Drive Seagate Internal

it’s the ugly duckling in my flock of 3.5’’ hard drives. the other 3 is the same as the first i posted. this one is the only different model (which is a pro, an upgrade i suppose)

earlier in this thread i said my drives were 128mb cache, but i think that is for the OLD wd reds i had, which i had sinced moved to the TL-D400S. So the drives on my ts-877 are using 256mb cache :sweat_smile:

Its not really the test results you are interested in, but rather then SMART attributes section.

You can see that in the “Temperature_Celsius” row your drive (sdb, different to sdc previously) has now reached 60C.

ie 60 celsius.

Hence the alert.

1 Like

i see the problem.

the fans stopped working :open_mouth:

how to fix this?

all the fans died as far as i can see. do i need to add a script or something to get the fans working again?

1 Like

Dunno.

If your system is cooking, and the fans aren’t spinning you need to resolve this… asap.

Either by stopping your rsync… and possibly shutting down, or getting the fans to spin etc.

If they are standard PC fans then they can be run via any 12V power supply.

Were they ever spinning under TrueNAS?

honestly, i don’t know because i wasn’t really looking. only when the hdd smart alerts popped up did i take note of a possible temp issue.

at that point i went to check and to my shock the exhaust fans weren’t spinning.

i think all the fans affected. 2 exhaust, 1 power supply, and the other 2 fans facing the hard drive cage. so none seem to be working.

But yeah, this is serious. You’re running a non-oem operating system on an appliance, and its not cooling.

You must do something before you destroy hardware.

well i found this but not sure if it will work or not

honestly i dont know what to do here x-x;

roll back to qts i guess?

← Mr Stux.

Cancel your rsync. Its rsync right… so you can restart it later.

Shutdown. Let things cooldown.

Then try to figure it out.

i have some external fans i am using now. problem solved so i can keep it running.

I don’t really have a long term solution for this. hopefully an expert comes along and has some advice :smiling_face_with_tear:

if i had to guess, this requires some scripts to activate the fans to tell it to run, if not it doesn’t. otherwise i can’t explain this. I will later go bios check if i can force fans to just run or not.

That’s a good idea.

How are the fans connected to the motherboard?

Regular PC fans?

Possibly sort of fan-controller hub could be used.

But, you basically need to work out if your fan has died (unlikely), or if there is some way to control it… and if not… then perhaps just power it… somehow.

This is possibly something to take to a QNAP dedicated forum.

cpu and hard drive temperature


the solution fixed the issue in the short term.

long term no idea. at this rate either keep it like this (mad max configuration :smiling_face_with_tear: ) or something else (maybe some sort of fan script for this model?)