[Solved] HDD spin down with Samba enabled

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
DarkSchneider
Starting out
Posts: 14
Joined: Mon Oct 01, 2018 5:06 pm

[Solved] HDD spin down with Samba enabled

Post by DarkSchneider » Mon Oct 01, 2018 5:18 pm

Hello, I'd like to share how I achieved my TS-431P with firmware 4.3.4 to finally spin down HDDs (4 in RAID5) with Samba enabled.

Well, in my case, I detected that having a Linux system with a fixed Samba mount point (mount or fstab) holds the HDDs on, with regular smbd process (using the QNAP method to detect). At the moment that Linux system (a Raspberry Pi) was shutdown, the HDDs spin down.
To solve this situation (I need that mount in the system), I used autofs with options "--timeout 300 --ghost", and works like a charm. When needed (accessed) it is mounted fine, and the HDDs spin down.
Seems that for fixed mounts, the timeout is infinite, and this NAS tries to hold the connection established with HDDs enabled, so they can be accessed immediately. And I say "this NAS", because I have another one, a WD MyBookLive (with HDD integrated in the case), that goes to standby even with fixed mounts in the Linux system.

I have to say that all services but "multimedia manager" (enabling the media library option) are disabled. Then I'll try one by one and check if it goes to standby.

And about Windows, if you don't have network mapped drives to the NAS, and close the Explorer windows accessing the NAS, then it goes to standby with no problem. Windows does not hold an unlimited connection.

DarkSchneider
Starting out
Posts: 14
Joined: Mon Oct 01, 2018 5:06 pm

Re: [Solved] HDD spin down with Samba enabled

Post by DarkSchneider » Sat Oct 13, 2018 1:32 am

Updated to QTS 4.3.5.0713 and now seems to wake up more often by its own. Looked and is smbXserver related, usually with session control and lock files. As the lock folder is placed in the HDDs, then they spin up. Tried to change it to USB drive, but when reboot it "repairs" the smb.conf file by its own setting it again on the HDDs.

User avatar
serbanhs
New here
Posts: 6
Joined: Fri Oct 19, 2018 7:09 pm

Re: [Solved] HDD spin down with Samba enabled

Post by serbanhs » Fri Oct 19, 2018 7:49 pm

I have a QNAP TS 253 A, and everything worked just fine 'til QTS 4.3.5 update!
Since then, the HDDs never turned in stand by mode. Setting is to 10 minutes. I tried everything I knew, but nothing has changed!
Any suggestion to solve it? :S Please! :cry:
Thanks!

User avatar
serbanhs
New here
Posts: 6
Joined: Fri Oct 19, 2018 7:09 pm

Re: [Solved] HDD spin down with Samba enabled

Post by serbanhs » Sat Oct 20, 2018 4:48 pm

After I ran blkdevMonitor_20151225.sh, this is the result:
login as: admin
admin@192.168.1.5's password:
[~] # /root/blkdevMonitor_20151225.sh
===== Welcome to use blkdevMonitor_v2 on Sat Oct 20 10:56:09 EEST 2018 =====
Stop klogd.sh daemon... Done
Turn off/on VM block_dump & Clean dmesg
Countdown: 3 2 1
Start...
============= 0/100 test, Sat Oct 20 10:56:15 EEST 2018 ===============
<7>[ 3590.754297] disk_manage.cgi(23030): dirtied inode 2121 (ihm_status.conf) on md9
<7>[ 3595.893379] kjournald(2183): WRITE block 535360 on md9 (8 sectors)
<7>[ 3595.893415] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3595.893452] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3595.932486] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3595.932498] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3596.029582] kjournald(2183): WRITE block 535368 on md9 (8 sectors)
<7>[ 3596.030052] kjournald(2183): WRITE block 535376 on md9 (8 sectors)
<7>[ 3596.269331] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3596.269369] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3596.307451] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3596.307466] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3595.893415] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3595.932486] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3596.269331] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3596.307451] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3595.893452] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3595.932498] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3596.269369] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3596.307466] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)

============= 1/100 test, Sat Oct 20 10:56:17 EEST 2018 ===============
<7>[ 3610.752872] kworker/u8:0(25876): WRITE block 262656 on md9 (8 sectors)
<7>[ 3610.752909] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3610.752947] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3610.785841] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3610.785860] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3611.003860] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3611.003896] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3611.072571] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3611.072599] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3610.752909] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3610.785841] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3611.003860] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3611.072571] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3610.752947] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3610.785860] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3611.003896] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3611.072599] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)

============= 2/100 test, Sat Oct 20 10:56:19 EEST 2018 ===============
<7>[ 3639.184425] sshd(23591): dirtied inode 5636098 (admin) on dm-0
<7>[ 3639.220934] sshd(23591): dirtied inode 11665409 (admin) on dm-0
<7>[ 3644.883794] jbd2/dm-0-8(2923): WRITE block 13958913656 on dm-0 (8 sectors)
<7>[ 3644.883890] jbd2/dm-0-8(2923): WRITE block 13958913664 on dm-0 (8 sectors)
<7>[ 3644.883918] jbd2/dm-0-8(2923): WRITE block 13958913672 on dm-0 (8 sectors)
<7>[ 3644.884371] jbd2/dm-0-8(2923): WRITE block 13958913680 on dm-0 (8 sectors)

============= 3/100 test, Sat Oct 20 10:56:20 EEST 2018 ===============
<7>[ 3659.183315] kworker/u8:0(25876): WRITE block 360710400 on dm-0 (8 sectors)
<7>[ 3659.183407] kworker/u8:0(25876): WRITE block 746586368 on dm-0 (8 sectors)
<7>[ 3661.962205] md13_raid1(2200): WRITE block 1060256 on sda4 (1 sectors)
<7>[ 3661.962244] md13_raid1(2200): WRITE block 1060256 on sdb4 (1 sectors)
<7>[ 3661.996713] md13_raid1(2200): WRITE block 1060272 on sda4 (1 sectors)
<7>[ 3661.996728] md13_raid1(2200): WRITE block 1060272 on sdb4 (1 sectors)
<7>[ 3661.962205] md13_raid1(2200): WRITE block 1060256 on sda4 (1 sectors)
<7>[ 3661.962244] md13_raid1(2200): WRITE block 1060256 on sdb4 (1 sectors)
<7>[ 3661.996713] md13_raid1(2200): WRITE block 1060272 on sda4 (1 sectors)
<7>[ 3661.996728] md13_raid1(2200): WRITE block 1060272 on sdb4 (1 sectors)
<7>[ 3661.962205] md13_raid1(2200): WRITE block 1060256 on sda4 (1 sectors)
<7>[ 3661.996713] md13_raid1(2200): WRITE block 1060272 on sda4 (1 sectors)
<7>[ 3661.962244] md13_raid1(2200): WRITE block 1060256 on sdb4 (1 sectors)
<7>[ 3661.996728] md13_raid1(2200): WRITE block 1060272 on sdb4 (1 sectors)

============= 4/100 test, Sat Oct 20 10:56:26 EEST 2018 ===============
<7>[ 3839.974154] qanalytic_tool(6930): dirtied inode 111542274 (flush.lock) on dm-0
<7>[ 3839.990612] qanalytic_tool(6930): dirtied inode 111542275 (analytic.lock) on dm-0
<7>[ 3840.007029] qanalytic_tool(6930): dirtied inode 111542273 (.@analytic) on dm-0
<7>[ 3840.023159] qanalytic_tool(6930): dirtied inode 111542279 (analyyCQUBM.pos) on dm-0
<7>[ 3840.023263] qanalytic_tool(6930): dirtied inode 111542277 (analyyCQUBM) on dm-0

============= 5/100 test, Sat Oct 20 10:59:14 EEST 2018 ===============
<7>[ 3845.885264] jbd2/dm-0-8(2923): WRITE block 13958913688 on dm-0 (8 sectors)
<7>[ 3845.885353] jbd2/dm-0-8(2923): WRITE block 13958913696 on dm-0 (8 sectors)
<7>[ 3845.885380] jbd2/dm-0-8(2923): WRITE block 13958913704 on dm-0 (8 sectors)
<7>[ 3845.885403] jbd2/dm-0-8(2923): WRITE block 13958913712 on dm-0 (8 sectors)
<7>[ 3845.885424] jbd2/dm-0-8(2923): WRITE block 13958913720 on dm-0 (8 sectors)
<7>[ 3845.885445] jbd2/dm-0-8(2923): WRITE block 13958913728 on dm-0 (8 sectors)
<7>[ 3845.885888] jbd2/dm-0-8(2923): WRITE block 13958913736 on dm-0 (8 sectors)
<7>[ 3859.972770] kworker/u8:0(25876): WRITE block 0 on dm-0 (8 sectors)
<7>[ 3859.972859] kworker/u8:0(25876): WRITE block 3408 on dm-0 (8 sectors)
<7>[ 3859.972890] kworker/u8:0(25876): WRITE block 7138705536 on dm-0 (8 sectors)
<7>[ 3859.972922] kworker/u8:0(25876): WRITE block 7138705664 on dm-0 (8 sectors)
<7>[ 3859.972949] kworker/u8:0(25876): WRITE block 7138738432 on dm-0 (8 sectors)

============= 6/100 test, Sat Oct 20 10:59:46 EEST 2018 ===============
<7>[ 3889.529397] setcfg(10881): dirtied inode 2070 (CACHEDEV1_DATA.log) on md9
<7>[ 3889.529470] setcfg(10881): dirtied inode 2070 (CACHEDEV1_DATA.log) on md9
<7>[ 3889.547392] setcfg(10885): dirtied inode 2297 (CACHEDEV1_DATA.lo~) on md9
<7>[ 3889.555484] sed(10888): dirtied inode 2070 (CACHEDEV1_DATA.log2VC0uI) on md9
<7>[ 3889.575405] setcfg(10895): dirtied inode 2297 (CACHEDEV1_DATA.lo~) on md9
<7>[ 3889.717085] setcfg(10926): dirtied inode 2070 (CACHEDEV1_DATA.lo~) on md9
<7>[ 3889.960037] setcfg(10976): dirtied inode 2297 (CACHEDEV1_DATA.lo~) on md9
<7>[ 3890.381782] setcfg(11116): dirtied inode 2105 (vg1.log) on md9
<7>[ 3890.382013] setcfg(11116): dirtied inode 2070 (vg1.lo~) on md9
<7>[ 3890.390404] sed(11119): dirtied inode 2105 (vg1.logewUWay) on md9
<7>[ 3890.408953] setcfg(11122): dirtied inode 2070 (vg1.lo~) on md9
<7>[ 3890.543790] setcfg(11153): dirtied inode 2105 (vg1.lo~) on md9
<7>[ 3890.784371] setcfg(11203): dirtied inode 2070 (vg1.lo~) on md9
<7>[ 3890.975271] setcfg(11259): dirtied inode 2141 (vg1_snapshot_usage.log) on md9
<7>[ 3890.975494] setcfg(11259): dirtied inode 2105 (vg1_snapshot_usage.lo~) on md9
<7>[ 3890.983662] sed(11262): dirtied inode 2141 (vg1_snapshot_usage.logOgJWm9) on md9
<7>[ 3891.002033] setcfg(11265): dirtied inode 2105 (vg1_snapshot_usage.lo~) on md9
<7>[ 3891.393007] setcfg(11349): dirtied inode 1959 (vg1_snapshot_reservation.log) on md9
<7>[ 3891.393228] setcfg(11349): dirtied inode 2141 (vg1_snapshot_reservation.lo~) on md9
<7>[ 3891.401475] sed(11352): dirtied inode 1959 (vg1_snapshot_reservation.logGFniZD) on md9
<7>[ 3891.420033] setcfg(11355): dirtied inode 2141 (vg1_snapshot_reservation.lo~) on md9

============= 7/100 test, Sat Oct 20 11:00:04 EEST 2018 ===============
<7>[ 3891.880428] getcfg(11545): dirtied inode 2090 (vg1_snapshot_recycle.log) on md9
<7>[ 3891.902568] setcfg(11564): dirtied inode 1959 (vg1_snapshot_recycle.lo~) on md9
<7>[ 3891.914571] sed(11583): dirtied inode 2090 (vg1_snapshot_recycle.log3TTHlc) on md9
<7>[ 3891.965494] disk_manage.cgi(11381): dirtied inode 2121 (ihm_status.conf) on md9
<7>[ 3894.891625] kjournald(2183): WRITE block 263368 on md9 (8 sectors)
<7>[ 3894.891660] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3894.891697] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3894.923863] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3894.923899] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3894.940508] kjournald(2183): WRITE block 263432 on md9 (8 sectors)
<7>[ 3894.940523] kjournald(2183): WRITE block 263440 on md9 (8 sectors)
<7>[ 3894.940533] kjournald(2183): WRITE block 311304 on md9 (8 sectors)
<7>[ 3894.940542] kjournald(2183): WRITE block 312272 on md9 (8 sectors)
<7>[ 3894.940552] kjournald(2183): WRITE block 312280 on md9 (8 sectors)
<7>[ 3894.940561] kjournald(2183): WRITE block 278592 on md9 (8 sectors)
<7>[ 3894.940571] kjournald(2183): WRITE block 278608 on md9 (8 sectors)
<7>[ 3894.940602] kjournald(2183): WRITE block 445208 on md9 (8 sectors)
<7>[ 3894.940613] kjournald(2183): WRITE block 445216 on md9 (8 sectors)
<7>[ 3894.940623] kjournald(2183): WRITE block 508040 on md9 (8 sectors)
<7>[ 3894.940635] kjournald(2183): WRITE block 508048 on md9 (8 sectors)
<7>[ 3894.942760] kjournald(2183): WRITE block 535384 on md9 (8 sectors)
<7>[ 3894.942776] kjournald(2183): WRITE block 535392 on md9 (8 sectors)
<7>[ 3894.942788] kjournald(2183): WRITE block 535400 on md9 (8 sectors)
<7>[ 3894.942798] kjournald(2183): WRITE block 535408 on md9 (8 sectors)
<7>[ 3894.942808] kjournald(2183): WRITE block 535416 on md9 (8 sectors)
<7>[ 3894.942819] kjournald(2183): WRITE block 535424 on md9 (8 sectors)
<7>[ 3894.942829] kjournald(2183): WRITE block 535432 on md9 (8 sectors)
<7>[ 3894.942839] kjournald(2183): WRITE block 535440 on md9 (8 sectors)
<7>[ 3894.942849] kjournald(2183): WRITE block 535448 on md9 (8 sectors)
<7>[ 3894.942861] kjournald(2183): WRITE block 535456 on md9 (8 sectors)
<7>[ 3894.942872] kjournald(2183): WRITE block 535464 on md9 (8 sectors)
<7>[ 3894.942882] kjournald(2183): WRITE block 535472 on md9 (8 sectors)
<7>[ 3894.942892] kjournald(2183): WRITE block 535480 on md9 (8 sectors)
<7>[ 3894.942904] kjournald(2183): WRITE block 535488 on md9 (8 sectors)
<7>[ 3894.943303] kjournald(2183): WRITE block 535496 on md9 (8 sectors)
<7>[ 3895.188617] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3895.188655] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3895.207134] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3895.207148] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3909.528162] kworker/u8:2(13992): WRITE block 0 on md9 (8 sectors)
<7>[ 3909.528198] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3909.528237] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3894.891660] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3894.923863] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3895.188617] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3895.207134] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3909.528198] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3894.891697] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3894.923899] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3895.188655] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3895.207148] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3909.528237] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)

============= 8/100 test, Sat Oct 20 11:00:22 EEST 2018 ===============
<7>[ 3909.563509] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3909.563549] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3909.580218] kworker/u8:2(13992): WRITE block 8 on md9 (8 sectors)
<7>[ 3909.580241] kworker/u8:2(13992): WRITE block 262416 on md9 (8 sectors)
<7>[ 3909.580254] kworker/u8:2(13992): WRITE block 262424 on md9 (8 sectors)
<7>[ 3909.580266] kworker/u8:2(13992): WRITE block 262520 on md9 (8 sectors)
<7>[ 3909.580279] kworker/u8:2(13992): WRITE block 262576 on md9 (8 sectors)
<7>[ 3909.580291] kworker/u8:2(13992): WRITE block 262632 on md9 (8 sectors)
<7>[ 3909.580303] kworker/u8:2(13992): WRITE block 262640 on md9 (8 sectors)
<7>[ 3909.580314] kworker/u8:2(13992): WRITE block 262648 on md9 (8 sectors)
<7>[ 3909.580326] kworker/u8:2(13992): WRITE block 262656 on md9 (8 sectors)
<7>[ 3909.580338] kworker/u8:2(13992): WRITE block 262664 on md9 (8 sectors)
<7>[ 3909.580351] kworker/u8:2(13992): WRITE block 262744 on md9 (8 sectors)
<7>[ 3909.580363] kworker/u8:2(13992): WRITE block 311296 on md9 (8 sectors)
<7>[ 3909.783194] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3909.783236] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3909.801703] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3909.801738] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3909.563509] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3909.783194] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 3909.801703] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 3909.563549] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 3909.783236] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 3909.801738] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)

============= 9/100 test, Sat Oct 20 11:00:47 EEST 2018 ===============
<7>[ 4142.269258] qanalytic_tool(29804): dirtied inode 111542274 (flush.lock) on dm-0
<7>[ 4142.285401] qanalytic_tool(29804): dirtied inode 111542275 (analytic.lock) on dm-0
<7>[ 4142.301513] qanalytic_tool(29804): dirtied inode 111542273 (.@analytic) on dm-0

============= 10/100 test, Sat Oct 20 11:04:14 EEST 2018 ===============
<7>[ 4142.318007] qanalytic_tool(29804): dirtied inode 111542278 (analyhzdFHv) on dm-0
<7>[ 4147.875467] jbd2/dm-0-8(2923): WRITE block 13958913744 on dm-0 (8 sectors)
<7>[ 4147.875569] jbd2/dm-0-8(2923): WRITE block 13958913752 on dm-0 (8 sectors)
<7>[ 4147.875597] jbd2/dm-0-8(2923): WRITE block 13958913760 on dm-0 (8 sectors)
<7>[ 4147.875615] jbd2/dm-0-8(2923): WRITE block 13958913768 on dm-0 (8 sectors)
<7>[ 4147.875632] jbd2/dm-0-8(2923): WRITE block 13958913776 on dm-0 (8 sectors)
<7>[ 4147.875649] jbd2/dm-0-8(2923): WRITE block 13958913784 on dm-0 (8 sectors)
<7>[ 4147.876123] jbd2/dm-0-8(2923): WRITE block 13958913792 on dm-0 (8 sectors)
<7>[ 4162.267933] kworker/u8:2(13992): WRITE block 7138738432 on dm-0 (8 sectors)
<7>[ 4162.268041] kworker/u8:2(13992): WRITE block 0 on dm-0 (8 sectors)
<7>[ 4162.268074] kworker/u8:2(13992): WRITE block 3408 on dm-0 (8 sectors)
<7>[ 4162.268106] kworker/u8:2(13992): WRITE block 7138705536 on dm-0 (8 sectors)
<7>[ 4162.268133] kworker/u8:2(13992): WRITE block 7138705664 on dm-0 (8 sectors)

============= 11/100 test, Sat Oct 20 11:04:50 EEST 2018 ===============
<7>[ 4192.804073] disk_manage.cgi(1203): dirtied inode 2121 (ihm_status.conf) on md9
<7>[ 4197.873815] kjournald(2183): WRITE block 535504 on md9 (8 sectors)
<7>[ 4197.873855] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4197.873893] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4197.908559] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4197.908583] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4197.925253] kjournald(2183): WRITE block 535512 on md9 (8 sectors)
<7>[ 4197.925663] kjournald(2183): WRITE block 535520 on md9 (8 sectors)
<7>[ 4198.143753] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4198.143792] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4198.173016] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4198.173043] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4197.873855] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4197.908559] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4198.143753] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4198.173016] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4197.873893] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4197.908583] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4198.143792] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4198.173043] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)

============= 12/100 test, Sat Oct 20 11:05:14 EEST 2018 ===============
<7>[ 4202.942619] kworker/u8:2(13992): WRITE block 262656 on md9 (8 sectors)
<7>[ 4202.942656] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4202.942695] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4202.980869] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4202.980901] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4203.198605] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4203.198642] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4203.216169] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4203.216181] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4202.942656] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4202.980869] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4203.198605] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4203.216169] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4202.942695] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4202.980901] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4203.198642] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4203.216181] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)

============= 13/100 test, Sat Oct 20 11:05:47 EEST 2018 ===============
<7>[ 4351.020055] redis-server(11480): dirtied inode 1959 (temp-11480.rdb) on md9
<7>[ 4351.020128] redis-server(11480): WRITE block 393216 on md9 (8 sectors)
<7>[ 4351.020173] md9_raid1(2170): WRITE block 1060216 o

============= 14/100 test, Sat Oct 20 11:07:43 EEST 2018 ===============
<7>[ 4351.093922] redis-server(11480): dirtied inode 2294 (?) on md9
<7>[ 4351.020217] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4351.056623] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4351.056663] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4351.073785] kjournald(2183): WRITE block 535528 on md9 (8 sectors)
<7>[ 4351.073810] kjournald(2183): WRITE block 535536 on md9 (8 sectors)
<7>[ 4351.073821] kjournald(2183): WRITE block 535544 on md9 (8 sectors)
<7>[ 4351.073830] kjournald(2183): WRITE block 535552 on md9 (8 sectors)
<7>[ 4351.073840] kjournald(2183): WRITE block 535560 on md9 (8 sectors)
<7>[ 4351.073849] kjournald(2183): WRITE block 535568 on md9 (8 sectors)
<7>[ 4351.073858] kjournald(2183): WRITE block 535576 on md9 (8 sectors)
<7>[ 4351.074507] kjournald(2183): WRITE block 535584 on md9 (8 sectors)
<7>[ 4351.293795] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4351.293832] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4351.306605] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4351.306638] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4356.860638] kjournald(2183): WRITE block 535592 on md9 (8 sectors)
<7>[ 4356.860675] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4356.860711] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4356.897630] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4356.897643] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4356.914289] kjournald(2183): WRITE block 535600 on md9 (8 sectors)
<7>[ 4356.914301] kjournald(2183): WRITE block 535608 on md9 (8 sectors)
<7>[ 4356.914311] kjournald(2183): WRITE block 535616 on md9 (8 sectors)
<7>[ 4356.914320] kjournald(2183): WRITE block 535624 on md9 (8 sectors)
<7>[ 4356.914329] kjournald(2183): WRITE block 535632 on md9 (8 sectors)
<7>[ 4356.914337] kjournald(2183): WRITE block 535640 on md9 (8 sectors)
<7>[ 4356.914346] kjournald(2183): WRITE block 535648 on md9 (8 sectors)
<7>[ 4356.914355] kjournald(2183): WRITE block 535656 on md9 (8 sectors)
<7>[ 4356.914364] kjournald(2183): WRITE block 535664 on md9 (8 sectors)
<7>[ 4356.914844] kjournald(2183): WRITE block 535672 on md9 (8 sectors)
<7>[ 4357.126597] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4357.126634] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4357.139295] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4357.139322] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4361.925444] kworker/u8:1(31543): WRITE block 262576 on md9 (8 sectors)
<7>[ 4361.925482] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4361.925514] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4361.955442] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4361.955465] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4361.972108] kworker/u8:1(31543): WRITE block 262744 on md9 (8 sectors)
<7>[ 4361.972129] kworker/u8:1(31543): WRITE block 263264 on md9 (8 sectors)
<7>[ 4361.972142] kworker/u8:1(31543): WRITE block 263344 on md9 (8 sectors)
<7>[ 4361.972160] kworker/u8:1(31543): WRITE block 0 on md9 (8 sectors)
<7>[ 4361.972171] kworker/u8:1(31543): WRITE block 8 on md9 (8 sectors)
<7>[ 4361.972182] kworker/u8:1(31543): WRITE block 262416 on md9 (8 sectors)
<7>[ 4361.972194] kworker/u8:1(31543): WRITE block 262424 on md9 (8 sectors)
<7>[ 4361.972205] kworker/u8:1(31543): WRITE block 262432 on md9 (8 sectors)
<7>[ 4362.174428] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4362.174465] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4362.188742] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4362.188756] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4351.056623] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4351.293795] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4351.306605] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4356.860675] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4356.897630] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4357.126597] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4357.139295] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4361.925482] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4361.955442] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4362.174428] md9_raid1(2170): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 4362.188742] md9_raid1(2170): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 4351.020217] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4351.056663] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4351.293832] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4351.306638] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4356.860711] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4356.897643] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4357.126634] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4357.139322] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4361.925514] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4361.955465] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)
<7>[ 4362.174465] md9_raid1(2170): WRITE block 1060216 on sdb1 (1 sectors)
<7>[ 4362.188756] md9_raid1(2170): WRITE block 1060232 on sdb1 (1 sectors)

============= 15/100 test, Sat Oct 20 11:08:02 EEST 2018 ===============

Is there anybody to "translate" this in English for me :?:

User avatar
Don
Guru
Posts: 12007
Joined: Thu Jan 03, 2008 4:56 am
Location: Long Island, New York

Re: [Solved] HDD spin down with Samba enabled

Post by Don » Sat Oct 20, 2018 5:54 pm

Learn the use code brackets when pasting long amounts of data. It makes it easier to read.
Read the Online Manuals and use the forum search feature before posting.

It is a recommended to use RAID and have external backups. RAID will protect you from disk failure, keep your system running, and data accessible while the disk is replaced and the RAID rebuilt. Backups will allow you to recover data that is lost or corrupted, or from system failure. One does not replace the other.

Submit bugs and feature requests to QNAP via their Helpdesk app.

NAS: TVS-882BR | F/W: 4.3.6.0895 | 40GB | 2 x M.2 SATA RAID 1 (System/VMs) | 4 x M.2 NMVe QM2-4P-384A RAID 5 (Cache) | 5 x 4TB HDD RAID 6 (Data) | 1 x Blu-ray
NAS: TVS-663 | F/W: 4.4.2.1320 | 16GB | 2 x M.2 NMVe QM2-2P RAID 1 (Cache) | 4 x 4TB RAID 5
Apps: Boinc, Squid, DNSMasq, PLEX, iDrive, QVPN, QLMS, MP3fs, HBS, Entware, DLstation, +others

_robocop_
First post
Posts: 1
Joined: Thu Oct 18, 2018 9:11 pm

Re: [Solved] HDD spin down with Samba enabled

Post by _robocop_ » Sat Oct 20, 2018 8:39 pm

I have a QNAP TS 228 (latest FW), same problem... I noticed it´s happening when CloudLink is installed. When I remove (uninstall) CloudLink, then harddisk normally spindowns.

User avatar
serbanhs
New here
Posts: 6
Joined: Fri Oct 19, 2018 7:09 pm

Re: [Solved] HDD spin down with Samba enabled

Post by serbanhs » Sat Oct 20, 2018 11:44 pm

Hi Don, thanks for your reply!
I read the manuals, but I found nothing there. However, thank you for your suggestion to submit bugs and feature requests to QNAP via their Helpdesk app, I just did it and I'm waiting for a response.

User avatar
serbanhs
New here
Posts: 6
Joined: Fri Oct 19, 2018 7:09 pm

Re: [Solved] HDD spin down with Samba enabled

Post by serbanhs » Sun Oct 21, 2018 3:22 pm

Hy _robocop_,

It seems you were right about CloudLink app, after I disabled it everything went back to normal. Still, before QNAP 4.3.5 Update, everything was working fine. Anyway, I need this app enabled for remote access, so I asked for help from Qnap Team, via HelpDesk app. Do the same!

Best regards. :D

User avatar
serbanhs
New here
Posts: 6
Joined: Fri Oct 19, 2018 7:09 pm

Re: [Solved] HDD spin down with Samba enabled

Post by serbanhs » Tue Oct 30, 2018 1:28 pm

Problem is solved by CloudLink 2.2.4.

Post Reply

Return to “HDD Spin Down (HDD Standby)”