NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Spindown
Hello, I think there is something wrong with the Spindown Function of my ReadyNAS 204 (OS 6.5.0) cause it is alwas accessing the harddrives, even if there is nothing in use. I have no services runni...
Are you still seeing this problem?
I had the same problem on 6.5.0 and previous versions. The disk spun up after a short amount of time. I recently upgraded to 6.6.0 where in the changelog it says:
> Fixed disks always spinning up immediately with disk spindown enabled.
Sounded hopeful.
However, I now have a few "successful" spin downs (where the disks are spun down for a longer period of time. But often the disks spin up almost directly:
Oct 08 15:21:47 backup noflushd[3449]: Enabling spindown for disk 1 [sda,0:0:WDC_WD10EZEX-08M2NA0:WD-WCC3FEVR3SLZ:01.01A01:7200] Oct 08 15:21:47 backup noflushd[3449]: Enabling spindown for disk 2 [sdb,0:1:WDC_WD10EZEX-08M2NA0:WD-WCC3FPZ6VKF5:01.01A01:7200] Oct 08 15:21:47 backup noflushd[3449]: Error: Readahead /etc/resolv.conf failed. Oct 08 15:52:13 backup noflushd[3449]: Error: Readahead /etc/resolv.conf failed. Oct 08 15:52:13 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 08 15:52:15 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 08 15:52:23 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:08. Oct 08 15:52:23 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 08 16:22:44 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 08 16:22:56 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 08 16:42:47 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 08 16:43:00 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:10. Oct 08 16:53:30 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 08 16:53:42 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 08 17:13:33 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 08 17:13:46 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:10. Oct 08 17:24:16 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 08 17:24:28 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 08 17:44:19 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 08 17:44:32 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:10. Oct 08 17:55:02 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 08 17:55:14 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 08 18:15:05 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 08 18:15:18 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:10. Oct 08 18:25:48 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 08 18:26:01 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 08 19:06:17 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 08 19:06:30 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:11. Oct 08 19:10:00 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 08 19:36:30 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 00:00:10 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 4:50:08. Oct 09 00:00:10 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 4:23:37. Oct 09 00:55:38 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 00:55:40 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 00:55:47 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:07. Oct 09 00:55:47 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 09 01:27:54 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 01:27:56 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 01:28:03 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:07. Oct 09 01:28:03 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 09 01:58:25 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 01:58:27 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 01:58:34 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:07. Oct 09 01:58:34 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 09 02:28:56 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 02:28:58 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 02:29:05 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:07. Oct 09 02:29:05 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 09 02:59:26 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 02:59:29 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 02:59:36 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:07. Oct 09 02:59:36 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 09 03:29:57 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 03:30:00 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 03:30:07 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:07. Oct 09 03:30:07 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 09 04:00:28 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 04:00:31 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 04:00:38 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:00:07. Oct 09 04:00:38 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:05. Oct 09 04:50:50 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 04:50:52 backup noflushd[3449]: Spindown of disk 1 (/dev/sda) cancelled. Oct 09 05:28:14 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 05:28:26 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 09 05:58:47 backup noflushd[3449]: Spinning down disk 2 (/dev/sdb). Oct 09 05:59:00 backup noflushd[3449]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 09 05:59:35 backup noflushd[3449]: Spinning down disk 1 (/dev/sda). Oct 09 06:16:19 backup noflushd[3449]: Spinning up disk 1 (/dev/sda) after 0:16:42. Oct 09 06:20:47 backup noflushd[3449]: Quitting on signal... -- Reboot -- Oct 09 06:21:20 backup noflushd[2005]: Enabling spindown for disk 1 [sda,0:0:WDC_WD10EZEX-08M2NA0:WD-WCC3FEVR3SLZ:01.01A01:7200] Oct 09 06:21:20 backup noflushd[2005]: Enabling spindown for disk 2 [sdb,0:1:WDC_WD10EZEX-08M2NA0:WD-WCC3FPZ6VKF5:01.01A01:7200] Oct 09 07:13:22 backup noflushd[2005]: Error: Readahead /etc/resolv.conf failed. Oct 09 07:13:22 backup noflushd[2005]: Spinning down disk 2 (/dev/sdb). Oct 09 07:13:34 backup noflushd[2005]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 09 07:43:55 backup noflushd[2005]: Spinning down disk 2 (/dev/sdb). Oct 09 07:44:08 backup noflushd[2005]: Spinning up disk 2 (/dev/sdb) after 0:00:10. Oct 09 07:47:38 backup noflushd[2005]: Spinning down disk 1 (/dev/sda). Oct 09 08:14:09 backup noflushd[2005]: Spinning down disk 2 (/dev/sdb). Oct 09 09:31:10 backup noflushd[2005]: Spinning up disk 1 (/dev/sda) after 1:43:30. Oct 09 09:31:20 backup noflushd[2005]: Spinning up disk 2 (/dev/sdb) after 1:17:09.
I've tried to do some block dumps but all I ever see is a lot of md0_raid1 and jdb2/md0-8 (and sometimes readynasd):
[12594.030385] md0_raid1(872): WRITE block 8 on sdb1 (1 sectors) [12594.062095] jbd2/md0-8(887): WRITE block 3676064 on md0 (8 sectors)
I'm running X-Raid if that makes any differnece.
Hi there,
same for me after the update to 6.6.0. Now it is working better but it shows exactly the same behavior as yours. My 3 WD Red drives are waking up after 10 to 90 Minutes and sometimes seconds after the spindown. The 1 WD Green stays down longer (around 3-4 hours) and never comes up right after the spindown. I deactivated the spindown after 2 days cause this doesn't look right.
If you are comfortable with SSH, an easy to enable the block_dump option to noflushd is to add it to the TIMEOUT variable in /etc/default/noflushd. For example, if the content of that file contains "TIMEOUT=5", change it to "TIMEOUT=5 -b".
Then `systemctl restart noflushd`.
The logs you get after enabling the block_dump option would be useful.I posted my findings in this thread: https://community.netgear.com/t5/Using-your-ReadyNAS/Readynas-OS-6-6-drives-wont-spindown/m-p/1152307#M117501
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
