Strange noise coming from 10TB drives (WD100EFAX)


#41

Unfortunately no Videos are allowed to be posted here……
could you give me your E-Mail please?

Otherwise, with What Android app can I take an Audio file and post it in here?
( I believe Audio Files aren´t allowed as well here), Maybe I Need to upload it somewhere?
Otherwise, I try to upload it on YouTube and post the link…


#42


That’s what I used in the first post :slight_smile:

This android app should work just fine. Most android phones have some kind of audio recorder apps already installed.


#43

#44

https://youtu.be/U7b1aK6GIxk


#45

You won´t believe…the last Video was when I disconnected the 2nd HDD and removed virtually the first one, so there was no Volume in the NAS System at all…still having electrical power, the left HDD continued to make those sounds….that´s why I wonder why it depends on the torrent in your Situation, which means the drives are ok?!

What you say?

Could please have a WD staff have a look at These Videos and tell us, What the reason for the beeping is PLEASE?!


#46

It sounds very similar, the whole thing is confusing. In my case the noise seems to be connected to the activity of the drives. Like random read/writes in the case of torrents and the noise being absent if the drives are under heavy use like a re-build or data scrubbing.
In your case the drives seems to be making this sound regardless, just idling doing nothing brings out the noise. I don’t know what to make of this. Is the noise coming and going or is it always present?
It’s so ■■■■ frustrating!


#47

It is Always present, once having started and as you wrote it is Independent on running apps, working on the NAS Surface or just doing Nothing. And the NAS is in the LIVING ROOM which is not acceptable.

QNAP recommended using WD Red drives for the SilentNAS though because they have only 5400rpm and so are more silent and have less temperature….


#48

That’s my experience with WD’s Red drives, until I got the 10 TB’s. In my case the noise levels are good most of the time, not as quiet as smaller drives of course but compared to the competition the drives are quiet and cool.
Only during these episodes the noise level becomes a problem. Have you tried to connect the drives to a desktop computer and see if the noise is still present?


#49

when I have time (maybe holidays or so) I will try…which means that setting up my personalized NAS has to wait for a longer time…too bad that NO EXPERT can help us!!!


#50

right now I try to take the first system drive as the 2nd data drive and vice versa and use obly one drive at once…

Maybe that helps…if not, this could mean that maybe BOTH DRIVES ARE DEFECT ??? Would be very unlikely or?

Or we maybe have to deal with a HIGHLY SOPHISTICATED Media Scan for whatever reason…


#51

Is everyone hearing this noise running a BTRFS filesystem? Or does it occur on EXT4 as well?


#52

I’m using BTRFS on my Synology NAS. Interesting to hear if that’s the case for the rest of the guys in this thread.


#53

QNAP uses EXT4, I had no choice.

This noise came up just again after I again initialised my NAS, started with one HDD first, then one day later I connected the 2nd HDD to my NAS this evening, copied 80GB data on the 2nd drive and it must have been midnight…hoooray then I had these sounds again…I will send the DumpFiles now to QNAP, hopefully they can help me to figure out what´s the problem here…

Again WD, could you please try to help us further, too?
You should be knowing these sounds, don´t you?


#54

Inmy QNAP dumpfiles, I have seen this error message…

2019-03-02 00:03:53,676 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:04:04,193 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:04:14,708 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:04:25,214 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:04:35,733 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:04:46,251 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:04:56,762 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:05:07,277 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:05:17,784 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:05:28,297 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:05:38,801 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:05:49,314 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:05:59,827 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:06:10,333 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:06:20,845 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:06:31,358 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:06:41,871 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:06:52,386 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:07:02,896 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:07:13,404 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:07:23,920 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:07:34,433 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:07:44,942 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:07:55,459 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:08:05,970 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:08:16,483 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:08:26,989 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:08:37,501 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:08:48,017 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:08:58,522 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:09:09,036 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:09:19,546 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:09:30,051 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:09:40,557 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:09:51,071 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:10:01,584 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:10:12,091 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:10:22,598 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:10:33,113 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>> Don’t have the interface: eth0
2019-03-02 00:10:43,624 slaacrrd[24508] ERROR [slaacrrd.py:343] _stat >>>

This could be the reasons for the beeping!!! What is it?


#55

Hopefully QNAP can help us getting to the bottom of this, at least be able to rule some things out.

I’m not holding my breath, there haven’t been any sign of them(WD) acknowledge there is a problem.
That is baffling to me, you would think the engineers at WD would have intimate knowledge of the inner workings of the drives.


#56

That has something to do with the networking, possibly be related ipv6 and shouldn’t have anything to do with the storage.

Edit: looks like the NAS can’t find one of the network ports. So not related to anything that could cause the drive to make a noise, unfortunately.


#57

but it correlates in time with the starting of the beeping, and it is my only error message…I am not running any apps but the diagnostic tool


#58

maybe these sounds don´t come from the HDDs at all???
(I know you checked it, but maybe…)


#59

I’m not sure we have the same problem. The sound is similar but the conditions are different.

In my case I’m 100% certain that the noise is coming from the drives, none of the NAS hardware is capable of producing sounds like that, and by using the “hose technique” I can pinpoint the noise pretty well.
I would suggest you use the a hose as well, and see if you can pinpoint the source of the sound.
I used a vacuum hose.


#60

I also believe that my sounds are coming from the HDDs and
I agree that I can´t imagine that a fix part of the NAS can make this sound, but maybe this is not a sound of something moving…could it be a controller or something connected to the HDDs?

Again,it would be very helpful if WD could tell us if this sound is or is not known to be a WD Red HDD sound…