TS251A making writing noises all the time

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
mke21
New here
Posts: 8
Joined: Wed Apr 16, 2014 4:55 pm

TS251A making writing noises all the time

Post by mke21 »

Without much hope for a solution after looking at the threads here, I still try to ask what to do.

My brand new TS251A is not only not going into standby, but seem to actually write to the hard-disk literally all the time, making quite a bit of noise. It just never stops or take a pause, not even for a minute. Apart from the fact that the noise is irritating, I cannot help thinking of the writing cycles on my disks and my electricity bill.

I've tried to turn off all the services that I could find, just to see if I could make it go away, but didn't help. I'm wondering what makes it do this.

The QNAP support asked me to run a program called Disk_Standby_Debug, but it doesn't seem to run, saying that " cannot execute binary file".

I tried running blkdevMonitor_20151225.sh, which I read somewhere is obsolete and should not be used, but anyway, I posted part of the outcome below.:

Code: Select all

============= 0/100 test, Wed Mar 17 22:23:39 CET 2021 ===============
<7>[181445.082733] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,16) (1 sectors)<7>[181445.193421] md9_raid1(2427): WRITE block 1060232 on unknown-block(<<<7>[181445.311441] hal_enc_temp(2615):<<<<7>[181446.318653] hal_enc_temp(2615): dirtied inode 7350187 (em_0.info) on tmpfs
<<7>[181445.082710] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,0) (1 sectors)
<7>[181445.082733] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,16) (1 sectors)<7>[181445.193421] md9_raid1(2427): WRITE block 1060232 on unknown-block(<<<7>[181445.311441] hal_enc_temp(2615):<<<<7>[181446.318653] hal_enc_temp(2615): dirtied inode 7350187 (em_0.info) on tmpfs

============= 1/100 test, Wed Mar 17 22:23:52 CET 2021 ===============
<<<7>[181457.560727<7>[181458.568520] hal_enc_temp(2615): dirtied inode 7354<<<<7>[181460.585711] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,0) (1 sectors)
<<<7>[181457.560727<7>[181458.568520] hal_enc_temp(2615): dirtied inode 7354<<<<7>[181460.585711] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,0) (1 sectors)
<7>[181460.585732] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,16) (1 sectors)

============= 2/100 test, Wed Mar 17 22:24:02 CET 2021 ===============
<<<7>[181501.936847] jbd2/md9-8(2440): WRITE block 20624 on unknown-block(9,9) (8 sectors)

============= 3/100 test, Wed Mar 17 22:24:42 CET 2021 ===============
<<<7>[181516.<7>[181517.059839] jbd2/md9-8(2440): WRITE block 261944 on unknown-block(9,9) (8 sectors)

============= 4/100 test, Wed Mar 17 22:24:58 CET 2021 ===============
<<<7>[181528.724574] drbdadm-84(1954): dirtied inode 6702 (ha) on md9
<7>[181528.724609] drbdadm-84(1954): dirtied inode 7157 (r1.res) on md9
<<<7>[181528.724574] drbdadm-84(1954): dirtied inode 6702 (ha) on md9
<7>[181528.724609] drbdadm-84(1954): dirtied inode 7157 (r1.res) on md9
<<<7>[181528.724574] drbdadm-84(1954): dirtied inode 6702 (ha) on md9
<7>[181528.724609] drbdadm-84(1954): dirtied inode 7157 (r1.res) on md9

============= 5/100 test, Wed Mar 17 22:25:11 CET 2021 ===============
<<7>[181557.412820] jb<<<7>[181557.474676] jbd2/md9-8(2440): WRITE block 21184 on unknown-block(9,9) (8 sectors)

============= 6/100 test, Wed Mar 17 22:25:39 CET 2021 ===============
<<<7><<7>[181577.606753] rsyslogd(31232): dirtied inode 13286 (kmsg) on md9

============= 7/100 test, Wed Mar 17 22:25:58 CET 2021 ===============
<7>[181622.969834] jbd2/md9-8(2440): WRITE block 21768 on unknown-block(9,9) (8 sectors)

============= 8/100 test, Wed Mar 17 22:26:44 CET 2021 ===============
<<<7>[181659.269691] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,0) (1 sectors)
<7>[181659.269712] md9_raid1(2427): WRITE block 1060216 on unknown-block(8,16) (1 sectors)

============= 9/100 test, Wed Mar 17 22:27:21 CET 2021 ===============
<7>[181664.375600] jbd2/md9-8(2440): WRITE block 375720 on unknown-block(9,9) (8 sectors)
<7>[181664.375666] jbd2/md9-8(2440): WRITE block 22248 on unknown-block(9,9) (8 sectors)
<7>[181664.375672] jbd2/md9-8(2440): WRITE block 22256 on unknown-block(9,9) (8 sectors)
<7>[181664.375677] jbd2/md9-8(2440): WRITE block 22264 on unknown-block(9,9) (8 sectors)
<7>[181664.375693] jbd2/md9-8(2440): WRITE block 22272 on unknown-block(9,9) (8 sectors)

============= 10/100 test, Wed Mar 17 22:27:30 CET 2021 ===============
tim@onozcafe.com
Starting out
Posts: 28
Joined: Thu Mar 17, 2016 10:08 am

Re: TS251A making writing noises all the time

Post by tim@onozcafe.com »

I have a TVS-1282 with the same issue my drives never go on standby and are continuously running, the heat of my NAS is always dangerously high. My NAS has shut down due to overheating, but even this the NAS waits till it is overheated and then shuts down, it doesn't shut down when it is getting close to overheating. I have resorted to always tuning off my NAS and only turning it on when needed, which can be a pain in the **. Is there no help for this issue.

mke21 has had this thread going for almost a week with no reply, where are the moderators.

Thanks
Tim N
Note: My user name is an old email that is not in use

Qnap:
TVS-1282 i3 6100, 4-20TB HDD's, drive bays 5 - 8 are not functioning, assuming backplane since drives work in another device without issue.
Added - 2 Noctua 80mm fans (internal), 2 Noctua 120mm fans (external) & Noctua NH-L9x65 CPU Cooler
Used as a Jellyfin Server

Computer:
Processor Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor
User avatar
OneCD
Guru
Posts: 12037
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

Re: TS251A making writing noises all the time

Post by OneCD »

tim@onozcafe.com wrote: Mon Mar 22, 2021 6:48 am mke21 has had this thread going for almost a week with no reply, where are the moderators.
The moderators need something to moderate first. They are not required to respond to every call for help. :'

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
User avatar
Toxic17
Ask me anything
Posts: 6469
Joined: Tue Jan 25, 2011 11:41 pm
Location: Planet Earth
Contact:

Re: TS251A making writing noises all the time

Post by Toxic17 »

tim@onozcafe.com wrote: Mon Mar 22, 2021 6:48 am mke21 has had this thread going for almost a week with no reply, where are the moderators.

Moderators are here, what would you like me to do with this thread?
Regards Simon

Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following


NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
User avatar
Toxic17
Ask me anything
Posts: 6469
Joined: Tue Jan 25, 2011 11:41 pm
Location: Planet Earth
Contact:

Re: TS251A making writing noises all the time

Post by Toxic17 »

mke21 wrote: Thu Mar 18, 2021 6:13 am Without much hope for a solution after looking at the threads here, I still try to ask what to do.
not sure if QNAP support asked you to read and check all apps but this is the usual port of call to start with.

https://www.qnap.com/en/how-to/faq/arti ... andby-mode
Regards Simon

Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following


NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
Steve62
Starting out
Posts: 18
Joined: Sun Nov 15, 2020 1:01 am

Re: TS251A making writing noises all the time

Post by Steve62 »

mke21 wrote: Thu Mar 18, 2021 6:13 am Without much hope for a solution after looking at the threads here, I still try to ask what to do.

My brand new TS251A is not only not going into standby, but seem to actually write to the hard-disk literally all the time, making quite a bit of noise. It just never stops or take a pause, not even for a minute. Apart from the fact that the noise is irritating, I cannot help thinking of the writing cycles on my disks and my electricity bill.

I've tried to turn off all the services that I could find, just to see if I could make it go away, but didn't help. I'm wondering what makes it do this.
Don't know whether you found a solution, but I was having the same issue with my TS-251D. I'm not that tech savvy, but read through loads of posts on this board suggesting all kinds of fixes, none of which have worked. Then I came across this post from 2017:
ChuckDavis666 wrote: Fri Apr 07, 2017 1:04 pm I have identified three factors that will keep drives from spinning down after a period of inactivity. (I was also investigating what seemed to be the related issue of constant disk activity, and was able to identify what is probably causing the constant activity on certain drives. See viewtopic.php?f=55&t=131537.)

To identify these factors I lobotomized my QNAP NAS to the level of a slug to make sure it wasn't an application or service that was causing (what I thought was) the constant disk activity. For testing I set the inactivity timer to 5 minutes.

** Using a Windows mapped drive causes enough disk activity to keep the disks from spinning down. (A separate admin user for the mapped drive actually appears in the QTS Dashboard.) Disconnecting the drive mapping in Windows does not appear to be sufficient to stop the disk activity; the PC has to be rebooted. Solution: Use //w.x.y.z/ (IP address) or //NASName/ instead.

** Being logged into QTS using the web browser interface also causes enough disk activity to keep the disks from spinning down. Solution: Logout when not actively working in QTS. Especially important to logout when testing disk drive behavior.

** Note - Running Qfinder Pro on a PC does not impact disk drive activity.

With no Windows mapped drives, being logged out of QTS and with a 5 minute inactivity timer my disk drives will spin down. With the inactivity timer changed to 10 minutes the drives would still spin down.

When the inactivity timer was changed to 15 minutes, however, the drives would not spin down. I determined that it is QNAP Cloud that activates every 10-15 minutes and keeps the drives from being spun down by QTS.

On my (de-lobotomized) system, at least, I believe that any failure of the drives to spin down will be a normal consequence of whatever applications and services happen to be running. I am not too concerned about this, since as has been pointed out in other postings the spin down/spin up is harder on the drives than a (normal) amount of reading, writing and spinning at idle. In addition, some drives with constant disk activity are, in fact, doing an almost constant surface scan which has been accounted for in the MTBF of the drives. (This surface scan is being performed by the drive firmware, and is not visible to QTS, so does not keep QTS from spinning down the drives.)
I had already tried stopping all the applications and services I could without the NAS stopping functioning as I needed it. However, I had not disconnected the drive I had mapped in Windows 10. So I disconnected that, changed the inactivity timer to 5 minutes, and now the constant reading has ceased. I have to emphasise that I use my NAS in a quite limited fashion as I am just a home user with the NAS working as a basic file server and personal cloud for the family. Everything I need it do to is still operating smoothly.
Qnap TS-251D-2G, 2 x 2GB drives in RAID1 on Windows 10.
Post Reply

Return to “HDD Spin Down (HDD Standby)”