QNAP TS-453 Pro Hard Drives does not sleep

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
KimmoFin
New here
Posts: 5
Joined: Fri Nov 06, 2015 7:10 pm

QNAP TS-453 Pro Hard Drives does not sleep

Post by KimmoFin » Fri Nov 06, 2015 7:19 pm

Hi,

I just bought TS-453 Pro week back and tried to get HDs to spin down (WD Red 3TB).

I think I should have put off all other services than MyQnapCloud CloudLink (all other apps are put off). I have set also HDs to go sleep after 5 minutes.

They they keep staying up.

My Firmware is: 4.2.0 Build 20151023

Here is also some log info which it just keeps continuing to do:
<7>[45607.911018] kworker/u8:2(23921): WRITE block 8 on md9 (8 sectors)
<7>[45607.911050] md9_raid1(308): WRITE block 1060216 on sdb1 (1 sectors)
<7>[45607.911084] md9_raid1(308): WRITE block 1060216 on sdd1 (1 sectors)
<7>[45607.911099] md9_raid1(308): WRITE block 1060216 on sdc1 (1 sectors)
<7>[45607.911112] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45607.932043] md9_raid1(308): WRITE block 1060232 on sdb1 (1 sectors)
<7>[45607.932062] md9_raid1(308): WRITE block 1060232 on sdd1 (1 sectors)
<7>[45607.932073] md9_raid1(308): WRITE block 1060232 on sdc1 (1 sectors)
<7>[45607.932084] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45607.954330] kworker/u8:2(23921): WRITE block 262416 on md9 (8 sectors)
<7>[45607.954347] kworker/u8:2(23921): WRITE block 262424 on md9 (8 sectors)
<7>[45607.954366] kworker/u8:2(23921): WRITE block 262432 on md9 (8 sectors)
<7>[45607.954380] kworker/u8:2(23921): WRITE block 262568 on md9 (8 sectors)
<7>[45607.954393] kworker/u8:2(23921): WRITE block 262584 on md9 (8 sectors)
<7>[45607.954406] kworker/u8:2(23921): WRITE block 294912 on md9 (8 sectors)
<7>[45607.954421] kworker/u8:2(23921): WRITE block 0 on md9 (8 sectors)
<7>[45608.155004] md9_raid1(308): WRITE block 1060216 on sdb1 (1 sectors)
<7>[45608.155026] md9_raid1(308): WRITE block 1060216 on sdd1 (1 sectors)
<7>[45608.155040] md9_raid1(308): WRITE block 1060216 on sdc1 (1 sectors)
<7>[45608.155052] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45608.176487] md9_raid1(308): WRITE block 1060232 on sdb1 (1 sectors)
<7>[45608.176503] md9_raid1(308): WRITE block 1060232 on sdd1 (1 sectors)
<7>[45608.176513] md9_raid1(308): WRITE block 1060232 on sdc1 (1 sectors)
<7>[45608.176523] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45616.231008] kjournald(318): WRITE block 278552 on md9 (8 sectors)
<7>[45616.231044] md9_raid1(308): WRITE block 1060216 on sdb1 (1 sectors)
<7>[45616.231075] md9_raid1(308): WRITE block 1060216 on sdd1 (1 sectors)
<7>[45616.231093] md9_raid1(308): WRITE block 1060216 on sdc1 (1 sectors)
<7>[45616.231106] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45616.265395] md9_raid1(308): WRITE block 1060232 on sdb1 (1 sectors)
<7>[45616.265408] md9_raid1(308): WRITE block 1060232 on sdd1 (1 sectors)
<7>[45616.265419] md9_raid1(308): WRITE block 1060232 on sdc1 (1 sectors)
<7>[45616.265429] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45616.287868] kjournald(318): WRITE block 536144 on md9 (8 sectors)
<7>[45616.287882] kjournald(318): WRITE block 536152 on md9 (8 sectors)
<7>[45616.287893] kjournald(318): WRITE block 536160 on md9 (8 sectors)
<7>[45616.287904] kjournald(318): WRITE block 536168 on md9 (8 sectors)
<7>[45616.287915] kjournald(318): WRITE block 536176 on md9 (8 sectors)
<7>[45616.287925] kjournald(318): WRITE block 536184 on md9 (8 sectors)
<7>[45616.287939] kjournald(318): WRITE block 536192 on md9 (8 sectors)
<7>[45616.287951] kjournald(318): WRITE block 536200 on md9 (8 sectors)
<7>[45616.287961] kjournald(318): WRITE block 536208 on md9 (8 sectors)
<7>[45616.288364] kjournald(318): WRITE block 536216 on md9 (8 sectors)
<7>[45586.511079] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45586.532000] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45587.831120] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45587.854239] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45588.078053] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)

Could you please help, what could be the issue?

Cheers,
Kimmo

bnova
Starting out
Posts: 13
Joined: Fri Oct 09, 2015 6:25 am

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by bnova » Fri Nov 06, 2015 11:21 pm

Hi Kimmo
Also write to the support, I think it's better
https://helpdesk.qnap.com/

User avatar
pwilson
Guru
Posts: 22568
Joined: Fri Mar 06, 2009 11:20 am
Location: Victoria, BC, Canada (UTC-08:00)

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by pwilson » Fri Nov 06, 2015 11:50 pm

KimmoFin wrote:Hi,

I just bought TS-453 Pro week back and tried to get HDs to spin down (WD Red 3TB).

I think I should have put off all other services than MyQnapCloud CloudLink (all other apps are put off). I have set also HDs to go sleep after 5 minutes.

They they keep staying up.

My Firmware is: 4.2.0 Build 20151023

Here is also some log info which it just keeps continuing to do:

Code: Select all

<7>[45607.911018] kworker/u8:2(23921): WRITE block 8 on md9 (8 sectors)
<7>[45607.911050] md9_raid1(308): WRITE block 1060216 on sdb1 (1 sectors)
<7>[45607.911084] md9_raid1(308): WRITE block 1060216 on sdd1 (1 sectors)
<7>[45607.911099] md9_raid1(308): WRITE block 1060216 on sdc1 (1 sectors)
<7>[45607.911112] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45607.932043] md9_raid1(308): WRITE block 1060232 on sdb1 (1 sectors)
<7>[45607.932062] md9_raid1(308): WRITE block 1060232 on sdd1 (1 sectors)
<7>[45607.932073] md9_raid1(308): WRITE block 1060232 on sdc1 (1 sectors)
<7>[45607.932084] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45607.954330] kworker/u8:2(23921): WRITE block 262416 on md9 (8 sectors)
<7>[45607.954347] kworker/u8:2(23921): WRITE block 262424 on md9 (8 sectors)
<7>[45607.954366] kworker/u8:2(23921): WRITE block 262432 on md9 (8 sectors)
<7>[45607.954380] kworker/u8:2(23921): WRITE block 262568 on md9 (8 sectors)
<7>[45607.954393] kworker/u8:2(23921): WRITE block 262584 on md9 (8 sectors)
<7>[45607.954406] kworker/u8:2(23921): WRITE block 294912 on md9 (8 sectors)
<7>[45607.954421] kworker/u8:2(23921): WRITE block 0 on md9 (8 sectors)
<7>[45608.155004] md9_raid1(308): WRITE block 1060216 on sdb1 (1 sectors)
<7>[45608.155026] md9_raid1(308): WRITE block 1060216 on sdd1 (1 sectors)
<7>[45608.155040] md9_raid1(308): WRITE block 1060216 on sdc1 (1 sectors)
<7>[45608.155052] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45608.176487] md9_raid1(308): WRITE block 1060232 on sdb1 (1 sectors)
<7>[45608.176503] md9_raid1(308): WRITE block 1060232 on sdd1 (1 sectors)
<7>[45608.176513] md9_raid1(308): WRITE block 1060232 on sdc1 (1 sectors)
<7>[45608.176523] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45616.231008] kjournald(318): WRITE block 278552 on md9 (8 sectors)
<7>[45616.231044] md9_raid1(308): WRITE block 1060216 on sdb1 (1 sectors)
<7>[45616.231075] md9_raid1(308): WRITE block 1060216 on sdd1 (1 sectors)
<7>[45616.231093] md9_raid1(308): WRITE block 1060216 on sdc1 (1 sectors)
<7>[45616.231106] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45616.265395] md9_raid1(308): WRITE block 1060232 on sdb1 (1 sectors)
<7>[45616.265408] md9_raid1(308): WRITE block 1060232 on sdd1 (1 sectors)
<7>[45616.265419] md9_raid1(308): WRITE block 1060232 on sdc1 (1 sectors)
<7>[45616.265429] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45616.287868] kjournald(318): WRITE block 536144 on md9 (8 sectors)
<7>[45616.287882] kjournald(318): WRITE block 536152 on md9 (8 sectors)
<7>[45616.287893] kjournald(318): WRITE block 536160 on md9 (8 sectors)
<7>[45616.287904] kjournald(318): WRITE block 536168 on md9 (8 sectors)
<7>[45616.287915] kjournald(318): WRITE block 536176 on md9 (8 sectors)
<7>[45616.287925] kjournald(318): WRITE block 536184 on md9 (8 sectors)
<7>[45616.287939] kjournald(318): WRITE block 536192 on md9 (8 sectors)
<7>[45616.287951] kjournald(318): WRITE block 536200 on md9 (8 sectors)
<7>[45616.287961] kjournald(318): WRITE block 536208 on md9 (8 sectors)
<7>[45616.288364] kjournald(318): WRITE block 536216 on md9 (8 sectors)
<7>[45586.511079] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45586.532000] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45587.831120] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)
<7>[45587.854239] md9_raid1(308): WRITE block 1060232 on sda1 (1 sectors)
<7>[45588.078053] md9_raid1(308): WRITE block 1060216 on sda1 (1 sectors)


Could you please help, what could be the issue?

Cheers,
Kimmo


The output of blkdevMonitor.sh can easily create 60,000 lines of output. Your "excerpt" doesn't show anything useful.

Perhaps you could paste the output of your blkdevMonitor.sh script (all 100 iterations) to PasteBin.com, and then provide us with the URL to access it.

All your output provided shows it that something is still writing to: /mnt/HDA_ROOT.
You should be running that script from either /tmp or /root, or it will not provide valid information in the first place.

Personally I don't have any desire for Firmware initiated Spindown in the first place. I'm quite comfortable letting the drives themselves use their own power management. I too am running WD Reds on my machine, and I honesty don't care if they ever spindown.

Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs

Please review: When you're asking a question, please include the following.

User avatar
schumaku
Guru
Posts: 43664
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by schumaku » Sat Nov 07, 2015 12:09 am

Hello Kimmo,

Don't waste to much time on the HDD spin-down: If the HDD are not accessed, they will spin down - permitting there are no other processes waking them up again, or some firmware builds prohibiting the spin-down sometimes. In other words: Can't get rid of the impression 4.2.0 Build 20151023 will never spin down. On earlier 4.2 build, we clearly heard the spin-up some times from a bunch of NAS near here, but none since the very recent builds.

Regards,
-Kurt.

....a famous name here -> https://www.youtube.com/watch?v=24bq7Ailzpw

KimmoFin
New here
Posts: 5
Joined: Fri Nov 06, 2015 7:10 pm

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by KimmoFin » Sat Nov 07, 2015 5:42 pm

Thanks,

I am running the script currently as admin from /root. I will take the whole 100 runs and sent as you informed (I will let you know the link once done).

Based on rows I followed yesterday till 45 runs, it keeps only doing exactly same rows as I have already sent yesterday. There is no other items than kworker, kjournalid ja raid writes. Those just keeps continuing and continuing.

I'll let you know when I have sent the data.

Cheers,
Kimmo

KimmoFin
New here
Posts: 5
Joined: Fri Nov 06, 2015 7:10 pm

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by KimmoFin » Sun Nov 08, 2015 10:03 pm

pwilson wrote:
The output of blkdevMonitor.sh can easily create 60,000 lines of output. Your "excerpt" doesn't show anything useful.

Perhaps you could paste the output of your blkdevMonitor.sh script (all 100 iterations) to PasteBin.com, and then provide us with the URL to access it.

All your output provided shows it that something is still writing to: /mnt/HDA_ROOT.
You should be running that script from either /tmp or /root, or it will not provide valid information in the first place.

Personally I don't have any desire for Firmware initiated Spindown in the first place. I'm quite comfortable letting the drives themselves use their own power management. I too am running WD Reds on my machine, and I honesty don't care if they ever spindown.


Hi,

Process is going to output.txt file as I am writing, but found from screen something I did not see before:

<7>[47721.739320] sed(5216): dirtied inode 6914 (crontabbi08Ed) on md9
<7>[47731.745726] sed(5225): dirtied inode 6847 (crontabOZUdMb) on md9
<7>[47741.752089] sed(5232): dirtied inode 6914 (crontabPO1Jrc) on md9
<7>[47751.758499] sed(5235): dirtied inode 6847 (crontabOKBikc) on md9
<7>[47761.764966] sed(5243): dirtied inode 6914 (crontabCXEI3e) on md9

KimmoFin
New here
Posts: 5
Joined: Fri Nov 06, 2015 7:10 pm

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by KimmoFin » Sun Nov 08, 2015 11:00 pm

pwilson wrote:
The output of blkdevMonitor.sh can easily create 60,000 lines of output. Your "excerpt" doesn't show anything useful.

Perhaps you could paste the output of your blkdevMonitor.sh script (all 100 iterations) to PasteBin.com, and then provide us with the URL to access it.

All your output provided shows it that something is still writing to: /mnt/HDA_ROOT.
You should be running that script from either /tmp or /root, or it will not provide valid information in the first place.

Personally I don't have any desire for Firmware initiated Spindown in the first place. I'm quite comfortable letting the drives themselves use their own power management. I too am running WD Reds on my machine, and I honesty don't care if they ever spindown.


Here is the link http://pastebin.com/KCvts3C4 to pastebin

KimmoFin
New here
Posts: 5
Joined: Fri Nov 06, 2015 7:10 pm

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by KimmoFin » Mon Nov 09, 2015 2:14 am

Got disks to sleep when enabled time from internet :) I thought I had tried that before as mentioned in some forum already. No idea why that does the magic :)

Cheers,
Kimmo

User avatar
schumaku
Guru
Posts: 43664
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by schumaku » Mon Nov 09, 2015 5:10 am

KimmoFin wrote:Got disks to sleep when enabled time from internet :) I thought I had tried that before as mentioned in some forum already. No idea why that does the magic :)
Unless you have another local reliable NTP server (ideally an ntpd) the hourly check to an Internet source is almost mandatory for two-factor authentication.

qwerty6000
Starting out
Posts: 25
Joined: Thu Jun 09, 2016 4:38 pm

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by qwerty6000 » Fri Jul 29, 2016 3:25 pm

KimmoFin wrote:Got disks to sleep when enabled time from internet :) I thought I had tried that before as mentioned in some forum already. No idea why that does the magic :)

Cheers,
Kimmo



I had read that having the time settings do a sync from the internet caused the disks to never sleep, but you seem to be stating the dead opposite?

I have exact same problem with TS453PRO ... very little is being reported as to "what" is causing it, just something occasionally causes some read/write activity every few minutes.

qwerty6000
Starting out
Posts: 25
Joined: Thu Jun 09, 2016 4:38 pm

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by qwerty6000 » Fri Jul 29, 2016 3:30 pm

KimmoFin wrote:Got disks to sleep when enabled time from internet :) I thought I had tried that before as mentioned in some forum already. No idea why that does the magic :)

Cheers,
Kimmo



I had read that having the time settings do a sync from the internet caused the disks to never sleep, but you seem to be stating the dead opposite?

I have exact same problem with TS453PRO ... very little is being reported as to "what" is causing it, just something occasionally causes some read/write activity every few minutes.

User avatar
schumaku
Guru
Posts: 43664
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: QNAP TS-453 Pro Hard Drives does not sleep

Post by schumaku » Sat Aug 06, 2016 9:07 pm

qwerty6000 wrote:I had read that having the time settings do a sync from the internet caused the disks to never sleep, but you seem to be stating the dead opposite?
Lack of a reference, I guess you talk of a historical issue.

Post Reply

Return to “HDD Spin Down (HDD Standby)”