- Joined
- Jul 12, 2022
- Messages
- 3,222
I believe that disks shouldn't make that kind of noise. Make sure they are not spinning up and down every 5 seconds.and because the disks makes a "clunk" noise every 5 seconds which can drive anybody crazy.
I believe that disks shouldn't make that kind of noise. Make sure they are not spinning up and down every 5 seconds.and because the disks makes a "clunk" noise every 5 seconds which can drive anybody crazy.
They only do the clunk noise every 5 seconds when i have them spinning 24x7, so it might be their PWL "feature". They don't do it when they are set to spin down but that is a conversation for another thread (which I'm about to start).I believe that disks shouldn't make that kind of noise. Make sure they are not spinning up and down every 5 seconds.
WD disks doing WD things...They only do the clunk noise every 5 seconds when i have them spinning 24x7, so it might be their PWL "feature".
Great to hear! Did the fan sound level increase?In the end I used the noctua NA-FC1 pwm fan controller as suggested by @Davvo . The Fans now stay in the low 40C even when they are under heavy use which is perfect for me because they experience very little temperature change and they are more than 20C below their max spec limit.
I would recommend against that. You only have two drives which consume 4.1 watts each at idle, .4 watts each when sleeping (3.7 watts diff) so a total of 7.4 watts saved if you sleep them. Now compare that to the possibility of the spindle motor electronics dying. The NAS itself consumes 8.1 watts of power alone, which is actually pretty darn good, call me impressed. So I'd recommend leaving the drives running if power consumption/price is your concern. If you do sleep them, periodically check the startup count, make sure they are not waking up too often. Computers on the network can poll the network and get the NAS to spin the drives back up, just for a status only.Now that my disks don't go above 42C under heavy use, i may consider putting them to sleep as well. This time to save energy (because somebody else will pay for the electricity of this system) and because the disks makes a "clunk" noise every 5 seconds which can drive anybody crazy.
Check the Load_Cycle_Count on the drives. See if that value is incrementing. Fast incrementing is cause for notice and to find out if it's too much, slow incrementing (maybe 5 to 24 in a 24 hour period) is good. Mine never increment unless the drive is powered off, the way I like it.hey only do the clunk noise every 5 seconds when i have them spinning 24x7
smartctl -A /dev/ada1
reports the followingID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 3 Spin_Up_Time 0x0007 083 083 001 Pre-fail Always - 342 (Avera 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 23 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 547 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 15 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 43
smartctl -A /dev/ada0
shows the followingID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 3 Spin_Up_Time 0x0007 083 083 001 Pre-fail Always - 340 (Average 352) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 22 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 547 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 42
Yes, some drives are noisier than others and I do understand, which is why my server use to be in the basement, then I moved and now it's in the Loft. The only thing I can hear is when I have a power outage, the UPS beeps, well all of my UPS's beep. Drives me crazy when the power outage lasts for a few hours because I have to run around and manually turn them off even though the NAS powered down already.BTW, the idea to put the drives to sleep was not necesarily to save power, it was more to eliminate this noise.
Shouldn't it be the capabilities of the Linux box that's sending the files?I'm just hoping this low transfer speeds are inherent to Rsync and not a reflection of the general capabilities of this system.
Well there are several things that could be a factor.These results are extremely disappointing.
This is during RSync? Could be a lot of small files, if you could check the hard drive activity, bet there are a lot of seek operations slowing it down. Also, I'm not an RSync person but my limited experience was that it was run more as a background priority, not foreground high or normal priority. So that could be part of the issue, but my first guess is drive activity slowing it down. But as you said, it could be something with the network.So, my issue must be somewhere in my network settings.
scp
tool for this and I achieved a throughput of 85MB/s consistently (or 680Mb/s according to my napkin math). That was while copying a multitude of video files ranging from 400MB to 34GB in size. This is a good thing. There are going to be people who want to build a small server at a less expensive price. I agree, the throughput is great and I'm actually pleased to be surprised by it. Be warned that you may be asked a few questions by new builders looking for an option like yours.All in all, except for the clunking noise of the disks, I am very happy with this Qnap running TrueNAS. It is affordable (i couldn't have built anything less expensive with two 3.5" drives), it is small, quiet, the power consumption is negligible and its performance can easily saturate my internet connection. I think its the perfect target machine for remote replication tasks (at least for my use).