Readynas OS 6.6 drives wont spindown

[Ildefonse]

I tried dacwe's solution and it bloody works !!!

I commented the last lines (about LCD) of /etc/noflushd/spindown.sh and spinup.sh

Thanks a lot!

[yuan_1202]

am trying it now. will report back.

[yuan_1202]

-- Logs begin at Sat 2016-10-29 21:10:46 WEST, end at Sun 2016-10-30 07:54:31 WET. --
Oct 29 21:10:49 YUAN-NAS noflushd[1826]: Enabling spindown for disk 1 [sda,0:0:TOSHIBA_HDWE140:Z5M8KE82F58D:FP2A:7200]
Oct 29 21:22:07 YUAN-NAS noflushd[1826]: Error: Readahead /etc/resolv.conf failed.
Oct 29 21:22:07 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 29 21:26:15 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 0:04:06.
Oct 29 21:37:38 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 29 21:52:25 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 0:14:44.
Oct 29 22:01:37 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 29 23:32:22 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 1:30:43.
Oct 29 23:38:53 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 30 02:58:10 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 4:19:14.
Oct 30 03:03:11 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 30 04:23:02 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 1:19:48.
Oct 30 04:28:03 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 30 06:06:53 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 1:38:48.
Oct 30 06:11:54 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 30 07:27:06 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 1:15:10.
Oct 30 07:32:06 YUAN-NAS noflushd[1826]: Spinning down disk 1 (/dev/sda).
Oct 30 07:54:19 YUAN-NAS noflushd[1826]: Spinning up disk 1 (/dev/sda) after 0:22:10.

doesnt seem to work. the wakeup frequency seems to be reduced, from minutes to now every hour or so.  but still wakes up for no reason. 

[jojax14]

Hi all,

I thought I would share my experience.

Back in October I upgraded my RN102 from 6.5.1 to 6.6.0 (with an intermediate step through 6.5.2 as required).  Since being on 6.6.0 the spindown messages show the disk (single disk - I am running this in a 1-disk config with no RAID) is spinning up after 10 seconds of spindown (occasionally 5 seconds, occasionally 20 seconds, but mostly 10).  I have confirmed this as the unit is in a relatively quiet room and you could hear the HD spinning down and then spinning up again before the platters have completely stopped.

I took the advice of this thread and commented out the LCD line from the script.  After restarting the service, this issue now appears to be resolved and I am no longer seeing the constant spin down/up sequence.

However, I shudder at the thought that my poor hard disk has gone through a spin down/up cycle 2000-odd times since the upgrade to 6.6.0.  I sure hope this gets resolved in a future firmware update!

[yuan_1202]

-- Logs begin at Wed 2016-11-02 07:05:33 WET, end at Wed 2016-11-02 18:27:42 WET. --
Nov 02 07:00:29 YUAN-NAS noflushd[1831]: Enabling spindown for disk 1 [sda,0:0:TOSHIBA_HDWE140:Z5M8KE82F58D:FP2A:7200]
Nov 02 07:36:18 YUAN-NAS noflushd[1831]: Error: Readahead /etc/resolv.conf failed.
Nov 02 07:36:18 YUAN-NAS noflushd[1831]: Spinning down disk 1 (/dev/sda).
Nov 02 07:36:26 YUAN-NAS noflushd[1831]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 07:51:27 YUAN-NAS noflushd[1831]: Spinning down disk 1 (/dev/sda).
Nov 02 07:51:35 YUAN-NAS noflushd[1831]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 08:06:36 YUAN-NAS noflushd[1831]: Spinning down disk 1 (/dev/sda).
Nov 02 08:06:44 YUAN-NAS noflushd[1831]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 08:21:45 YUAN-NAS noflushd[1831]: Spinning down disk 1 (/dev/sda).
Nov 02 08:21:52 YUAN-NAS noflushd[1831]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 08:36:53 YUAN-NAS noflushd[1831]: Spinning down disk 1 (/dev/sda).
Nov 02 08:37:01 YUAN-NAS noflushd[1831]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 08:52:02 YUAN-NAS noflushd[1831]: Spinning down disk 1 (/dev/sda).
Nov 02 08:52:09 YUAN-NAS noflushd[1831]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 09:00:19 YUAN-NAS noflushd[1831]: Quitting on signal...
-- Reboot --
Nov 02 17:00:29 YUAN-NAS noflushd[1843]: Enabling spindown for disk 1 [sda,0:0:TOSHIBA_HDWE140:Z5M8KE82F58D:FP2A:7200]
Nov 02 17:36:38 YUAN-NAS noflushd[1843]: Error: Readahead /etc/resolv.conf failed.
Nov 02 17:36:38 YUAN-NAS noflushd[1843]: Spinning down disk 1 (/dev/sda).
Nov 02 17:36:46 YUAN-NAS noflushd[1843]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 17:51:48 YUAN-NAS noflushd[1843]: Spinning down disk 1 (/dev/sda).
Nov 02 17:51:55 YUAN-NAS noflushd[1843]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 02 18:06:57 YUAN-NAS noflushd[1843]: Spinning down disk 1 (/dev/sda).
Nov 02 18:07:10 YUAN-NAS noflushd[1843]: Spinning up disk 1 (/dev/sda) after 0:00:10.
Nov 02 18:22:12 YUAN-NAS noflushd[1843]: Spinning down disk 1 (/dev/sda).
Nov 02 18:22:20 YUAN-NAS noflushd[1843]: Spinning up disk 1 (/dev/sda) after 0:00:05.

nop  not fixed at all using dacwe's method. it seemed to performing spin down for a few of hours for a few times after i implemented the fix. but when i check the log today heres what i got.  have to stop the spindown function now i dont think this will do hard drive any good.

seriously netgear, fix this sh*t.

[Skywalker]

I can't reproduce anything like what you're seeing, but I do see some occasional short spindown times.  We've made a couple enhancements, and so far I've had good success with these packages: ARM or x86_64.  Install through Apps -> Upload.

[yuan_1202]

Nov 03 21:27:42 YUAN-NAS noflushd[2057]: Spinning down disk 1 (/dev/sda).
Nov 03 21:31:10 YUAN-NAS noflushd[2057]: Spinning up disk 1 (/dev/sda) after 0:03:25.
Nov 03 21:38:12 YUAN-NAS noflushd[2057]: Spinning down disk 1 (/dev/sda).
Nov 03 21:53:32 YUAN-NAS noflushd[2057]: Spinning up disk 1 (/dev/sda) after 0:15:17.
Nov 03 21:54:33 YUAN-NAS noflushd[2057]: Quitting on signal...
Nov 03 21:54:33 YUAN-NAS noflushd[2754]: Enabling spindown for disk 1 [sda,0:0:TOSHIBA_HDWE140:Z5M8KE82F58D:FP2A:7200]
Nov 03 22:10:19 YUAN-NAS noflushd[2754]: Spinning down disk 1 (/dev/sda).
Nov 03 22:10:27 YUAN-NAS noflushd[2754]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 03 22:47:30 YUAN-NAS noflushd[2754]: Spinning down disk 1 (/dev/sda).
Nov 03 22:47:37 YUAN-NAS noflushd[2754]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 03 23:00:06 YUAN-NAS noflushd[2754]: Quitting on signal...
Nov 03 23:03:08 YUAN-NAS noflushd[1567]: Enabling spindown for disk 1 [sda,0:0:TOSHIBA_HDWE140:Z5M8KE82F58D:FP2A:7200]
Nov 03 23:37:38 YUAN-NAS noflushd[1567]: Spinning down disk 1 (/dev/sda).
Nov 03 23:37:46 YUAN-NAS noflushd[1567]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 03 23:52:46 YUAN-NAS noflushd[1567]: Spinning down disk 1 (/dev/sda).
Nov 04 07:42:38 YUAN-NAS noflushd[1567]: Spinning up disk 1 (/dev/sda) after 7:49:49.
Nov 04 07:58:20 YUAN-NAS noflushd[1567]: Spinning down disk 1 (/dev/sda).
Nov 04 07:58:28 YUAN-NAS noflushd[1567]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 04 08:13:30 YUAN-NAS noflushd[1567]: Spinning down disk 1 (/dev/sda).
Nov 04 23:19:01 YUAN-NAS noflushd[1567]: Spinning up disk 1 (/dev/sda) after 15:05:28.
Nov 04 23:34:02 YUAN-NAS noflushd[1567]: Spinning down disk 1 (/dev/sda).
Nov 04 23:34:10 YUAN-NAS noflushd[1567]: Spinning up disk 1 (/dev/sda) after 0:00:05.
Nov 04 23:49:11 YUAN-NAS noflushd[1567]: Spinning down disk 1 (/dev/sda).
Nov 05 23:19:00 YUAN-NAS noflushd[1567]: Spinning up disk 1 (/dev/sda) after 23:29:46.
Nov 05 23:34:01 YUAN-NAS noflushd[1567]: Spinning down disk 1 (/dev/sda).
Nov 06 16:07:32 YUAN-NAS noflushd[1567]: Spinning up disk 1 (/dev/sda) after 16:33:28.

managed to revert back to version 6.4.2, and the spindown worked as normal.

so i think there is definitely something wrong with the current 6.6.0 version.

[mdgm-ntgr]

That's not a supported downgrade. You may run into some weird issues as a result.

[yuan_1202]

With all due respect, the "v6.6 upgrade" isn't exactly issue free is it?

All I did was using a hex editor to change the version number in an official v6.4.2 file to v6.6. I hardly see it introducing any problem, other the bugs inherently with v6.4.2. Hey at least my hard drive isnt sufferring...

[mdgm-ntgr]

With the core OS upgrade there are some major changes to the core OS. Installing the older core OS over the top of the new one can lead to some weird issues. Of course if you want to backup your data, do a factory reset (wipes all data, settings, everything) and restore your data from backup that is a bit diffferent. However you can brick some systems attempting certain downgrades.

Did you try the package from Skywalker before you downgraded?

[yuan_1202]

Unfortunately I did the downgrade before skywalker replied with that patch.

Since spindown working fine now I prefer leaving it be. For me all I want is a reliable and efficient network drive and I got that now. Will update to 6.6 or higher version once the prolem is confirmed to be resolved.

Maybe someone else can offer help on testing the patch?

[Rootax]

I don't use spin down anymore, but I remember, under 4.x firmwares , UPnP, Netbios, an NTP used to wake up the disks for no good reason. Disabling this protocols/function was the only solution for having decent "spin down" time.

Don't know if it can help with 6.6.x firmwares.

[StephenB]

---

@Rootax wrote:

...I remember, under 4.x firmwares , UPnP, Netbios, an NTP used to wake up the disks for no good reason.

---

Of course OS activity can wake the disks up, since the OS runs of the disks. 

Netgear is clearly working on the problem.  I don't see much need to experiment right now, it's easy enough to disable spin-down for a little while if it is misbehaving.

[yuan_1202]

not sure if you guys noticed, in my log after v6.4.2 reversion, although the spindown works, i.e. the hard drive will stay off until next user activity, there is still a 5 second spin up routine before the "proper" spin-down.

i feel that this is THE initial bug, and in the v6.6 update this bug is somehow "multiplied", resulting in the endless wake-up spin down loop. 

[Skywalker]

Here's logs from two systems I've been running with the update I posted earlier:

● noflushd.service - Idle Disk Spindown Daemon
Loaded: loaded (/lib/systemd/system/noflushd.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2016-11-04 15:00:34 PDT; 4 days ago
Main PID: 17845 (noflushd)
CGroup: /system.slice/noflushd.service
└─17845 /usr/sbin/noflushd -d -n 5
Nov 04 15:00:34 justin-rn102 systemd[1]: Started Idle Disk Spindown Daemon.
Nov 04 15:00:34 justin-rn102 noflushd[17845]: Enabling spindown for disk 1 [sda,0:0:WDC_WD3000HLFS-01G6U0:WD-XXXXXXXXXXXX:04.04V01:10000]
Nov 04 15:05:39 justin-rn102 noflushd[17845]: Spinning down disk 1 (/dev/sda).
Nov 04 18:17:34 justin-rn102 noflushd[17845]: Spinning up disk 1 (/dev/sda) after 3:11:52.
Nov 04 18:22:34 justin-rn102 noflushd[17845]: Spinning down disk 1 (/dev/sda).
Nov 07 10:06:04 justin-rn102 noflushd[17845]: Spinning up disk 1 (/dev/sda) after 64:43:27.
Nov 07 10:11:14 justin-rn102 noflushd[17845]: Spinning down disk 1 (/dev/sda).

and

● noflushd.service - Idle Disk Spindown Daemon
   Loaded: loaded (/lib/systemd/system/noflushd.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2016-11-04 18:07:50 PDT; 3 days ago
 Main PID: 5192 (noflushd)
   CGroup: /system.slice/noflushd.service
           └─5192 /usr/sbin/noflushd -d -n 5

Nov 04 18:07:50 justin-rn104 systemd[1]: Started Idle Disk Spindown Daemon.
Nov 04 18:07:50 justin-rn104 noflushd[5192]: Enabling spindown for disk 4 [sda,0:3:WDC_WD2002FYPS-02W3B0:WD-XXXXXXXXXXXX:04.01G01:5400]
Nov 04 18:07:50 justin-rn104 noflushd[5192]: Enabling spindown for disk 3 [sdb,0:2:WDC_WD2003FYYS-02W0B1:WD-XXXXXXXXXXXX:01.01D02:7200]
Nov 04 18:07:50 justin-rn104 noflushd[5192]: Enabling spindown for disk 2 [sdc,0:1:WDC_WD2002FYPS-01U1B0:WD-XXXXXXXXXXXX:04.05G04:5400]
Nov 04 18:07:50 justin-rn104 noflushd[5192]: Enabling spindown for disk 1 [sdd,0:0:WDC_WD2002FYPS-02W3B0:WD-XXXXXXXXXXXX:04.01G01:5400]
Nov 04 18:07:50 justin-rn104 noflushd[5192]: Error: Readahead /etc/resolv.conf failed.
Nov 04 18:12:56 justin-rn104 noflushd[5192]: Error: Readahead /etc/resolv.conf failed.
Nov 04 18:12:56 justin-rn104 noflushd[5192]: Spinning down disk 4 (/dev/sda).
Nov 04 18:12:58 justin-rn104 noflushd[5192]: Spinning down disk 3 (/dev/sdb).
Nov 04 18:13:01 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 04 18:13:03 justin-rn104 noflushd[5192]: Spinning down disk 1 (/dev/sdd).
Nov 04 18:17:16 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 0:04:13.
Nov 04 18:21:32 justin-rn104 noflushd[5192]: Spinning up disk 4 (/dev/sda) after 0:08:34.
Nov 04 18:21:32 justin-rn104 noflushd[5192]: Spinning up disk 3 (/dev/sdb) after 0:08:31.
Nov 04 18:21:42 justin-rn104 noflushd[5192]: Spinning up disk 1 (/dev/sdd) after 0:08:36.
Nov 04 18:26:33 justin-rn104 noflushd[5192]: Spinning down disk 4 (/dev/sda).
Nov 04 18:26:35 justin-rn104 noflushd[5192]: Spinning down disk 3 (/dev/sdb).
Nov 04 18:26:43 justin-rn104 noflushd[5192]: Spinning down disk 1 (/dev/sdd).
Nov 04 18:26:55 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 04 21:38:41 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 3:11:44.
Nov 04 21:43:42 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 05 06:25:13 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 8:41:29.
Nov 05 06:30:14 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 05 12:05:17 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 5:35:01.
Nov 05 12:05:23 justin-rn104 noflushd[5192]: Spinning up disk 3 (/dev/sdb) after 17:38:45.
Nov 05 12:05:23 justin-rn104 noflushd[5192]: Spinning up disk 1 (/dev/sdd) after 17:38:38.
Nov 05 12:05:33 justin-rn104 noflushd[5192]: Spinning up disk 4 (/dev/sda) after 17:38:58.
Nov 05 12:11:14 justin-rn104 noflushd[5192]: Spinning down disk 4 (/dev/sda).
Nov 05 12:11:16 justin-rn104 noflushd[5192]: Spinning down disk 3 (/dev/sdb).
Nov 05 12:11:19 justin-rn104 noflushd[5192]: Spinning down disk 1 (/dev/sdd).
Nov 05 12:11:36 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 06 00:00:31 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 11:48:52.
Nov 06 00:05:32 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 06 06:47:16 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 7:41:42.
Nov 06 06:52:16 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 06 12:05:12 justin-rn104 noflushd[5192]: Spinning up disk 3 (/dev/sdb) after 24:53:53.
Nov 06 12:05:13 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 5:12:54.
Nov 06 12:05:23 justin-rn104 noflushd[5192]: Spinning up disk 4 (/dev/sda) after 24:54:07.
Nov 06 12:05:23 justin-rn104 noflushd[5192]: Spinning up disk 1 (/dev/sdd) after 24:54:02.
Nov 06 12:11:04 justin-rn104 noflushd[5192]: Spinning down disk 4 (/dev/sda).
Nov 06 12:11:07 justin-rn104 noflushd[5192]: Spinning down disk 3 (/dev/sdb).
Nov 06 12:11:09 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 06 12:11:11 justin-rn104 noflushd[5192]: Spinning down disk 1 (/dev/sdd).
Nov 07 03:17:15 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 15:06:04.
Nov 07 03:22:16 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 07 10:06:13 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 6:43:55.
Nov 07 10:06:23 justin-rn104 noflushd[5192]: Spinning up disk 1 (/dev/sdd) after 21:55:09.
Nov 07 10:11:24 justin-rn104 noflushd[5192]: Spinning down disk 1 (/dev/sdd).
Nov 07 10:11:36 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 07 10:19:20 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 0:07:41.
Nov 07 10:24:20 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 07 12:05:13 justin-rn104 noflushd[5192]: Spinning up disk 3 (/dev/sdb) after 23:54:04.
Nov 07 12:05:13 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 1:40:50.
Nov 07 12:05:23 justin-rn104 noflushd[5192]: Spinning up disk 4 (/dev/sda) after 23:54:16.
Nov 07 12:05:23 justin-rn104 noflushd[5192]: Spinning up disk 1 (/dev/sdd) after 1:53:57.
Nov 07 12:10:54 justin-rn104 noflushd[5192]: Spinning down disk 4 (/dev/sda).
Nov 07 12:10:57 justin-rn104 noflushd[5192]: Spinning down disk 3 (/dev/sdb).
Nov 07 12:10:59 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 07 12:11:02 justin-rn104 noflushd[5192]: Spinning down disk 1 (/dev/sdd).
Nov 08 12:05:12 justin-rn104 noflushd[5192]: Spinning up disk 3 (/dev/sdb) after 23:54:13.
Nov 08 12:05:12 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 23:54:10.
Nov 08 12:05:22 justin-rn104 noflushd[5192]: Spinning up disk 4 (/dev/sda) after 23:54:25.
Nov 08 12:05:22 justin-rn104 noflushd[5192]: Spinning up disk 1 (/dev/sdd) after 23:54:18.
Nov 08 12:10:53 justin-rn104 noflushd[5192]: Spinning down disk 4 (/dev/sda).
Nov 08 12:10:56 justin-rn104 noflushd[5192]: Spinning down disk 3 (/dev/sdb).
Nov 08 12:10:59 justin-rn104 noflushd[5192]: Spinning down disk 2 (/dev/sdc).
Nov 08 12:11:01 justin-rn104 noflushd[5192]: Spinning down disk 1 (/dev/sdd).
Nov 08 15:29:38 justin-rn104 noflushd[5192]: Spinning up disk 2 (/dev/sdc) after 3:18:37.
Nov 08 15:29:38 justin-rn104 noflushd[5192]: Spinning up disk 1 (/dev/sdd) after 3:18:35.
Nov 08 15:30:08 justin-rn104 noflushd[5192]: Spinning up disk 3 (/dev/sdb) after 3:19:09.
Nov 08 15:30:13 justin-rn104 noflushd[5192]: Spinning up disk 4 (/dev/sda) after 3:19:17.

[yuan_1202]

the log entry:

Nov 04 18:07:50 justin-rn104 noflushd[5192]: Error: Readahead /etc/resolv.conf failed.

what does it mean? 

[Skywalker]

It's nothing to worry about.  We try to cache several commonly-used files just before spindown to make sure we can serve read requests for those files without going to the disk. resolv.conf is a symlink in 6.6.0, so this fails.  But in practice it's normally read so often that we don't need to force it into cache, since it's almost certainly there already.

[hemingray]

Just adding my name to the list of people with the spindown/spinup issue since going to 6.6. Hope there is a fix soon, it's highly annoying. I'm running RAID 1 with 4TB WD40EFRX drives.

[Skywalker]

I posted a fix earlier in this thread.  We also released 6.6.1 Beta 1 on the community yesterday, which addresses spindown.

[Doc_Holliday]

I installed the Beta some days ago and it seems to fix the problem.

[FramerV]

Hi Doc_Holliday,

Thank you for sharing your resolution and/or workaround. We appreciate your contribution to the community. 

Feel free to post any suggestions, questions, recommendations or anything about your NAS that you think needs attention or will help others.

Regards,

[hemingray]

Thank you! It has fixed the issue for me as well.

[yuan_1202]

heres the log after installing 6.6.1 beta 3 last night:

Dec 13 22:31:21 YUAN-NAS noflushd[1856]: Enabling spindown for disk 1 [sda,0:0:TOSHIBA_HDWE140:Z5M8KE82F58D:FP2A:7200]
Dec 13 23:06:49 YUAN-NAS noflushd[1856]: Spinning down disk 1 (/dev/sda).
Dec 13 23:17:09 YUAN-NAS noflushd[1856]: Spinning up disk 1 (/dev/sda) after 0:10:17.
Dec 13 23:32:12 YUAN-NAS noflushd[1856]: Spinning down disk 1 (/dev/sda).
Dec 14 07:54:09 YUAN-NAS noflushd[1856]: Spinning up disk 1 (/dev/sda) after 8:21:55.
Dec 14 08:11:30 YUAN-NAS noflushd[1856]: Spinning down disk 1 (/dev/sda).
Dec 14 18:32:24 YUAN-NAS noflushd[1856]: Spinning up disk 1 (/dev/sda) after 10:20:51.

so the spindown seems to be working.

....However.... during the spin-down period according to the log, I still seemed to hear the hard drive working............... like the "dip reading/writing" I mentioned previously. and this was not present when I rolled back to 6.4.2. i really don't know what's going on.

[yuan_1202]

Hi skywalker

I suspect the spindown is not working still in the beta version. Please see the video attached below (I am very sorry about my poor camera technique, but please bear with me and look at these two videos with patient).

in the first video you can see that the hard drive is working, doing stuff every few seconds (see the hard drive green led flashing every once a while). you can even hear the hard drive "dip working" as well if you listen careful enough. This "dip" activity is always there throughout the day, non-stop.

the in the second video in which i went to check the log. The log showed that the hard drive only came alive after logged in to admin page. This means that during the first video, all those hard drive activities happened during the supposedly hard drive spin-down period, which is surely not right.

the two videos were taken together, one immediately after another.

https://youtu.be/UaiXt1Uqv4U

https://youtu.be/Wkt6W2eT2k0

So I do not think spindown issue is fixed, even though you somehow "fix" the log.

This problem was not present in any version earlier than 6.6.0 so it must have something to do with the updates made in 6.6.0.

[FramerV]

Hi yuan_1202,

Based on the description of the issue that you have provided, I may need to check this with others who can probably assist you and get back to you as soon as possible.

Thanks for your cooperation!

Regards,