- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ReadyNAS OS V6.9.3 - Discs don't spindown - still
Unfortunately I couldn't add to one of the number of other threads about this that go back to antiquity, which would have shown this is a long outstanding problem.
After every few updates I turn on spindown and hold my breath.
Every time I have been disappointed.
Including this time.
A represetative sample of the log, it just goes keeps on trying...but never get satisfaction...
Apr 17 09:14:04 ME-NAS-316A noflushd[17454]: Spinning down disk 1 (/dev/sda). Apr 17 09:14:07 ME-NAS-316A noflushd[17454]: Spinning down disk 2 (/dev/sdb). Apr 17 09:14:09 ME-NAS-316A noflushd[17454]: Spinning down disk 3 (/dev/sdc). Apr 17 09:14:16 ME-NAS-316A noflushd[17454]: Spinning up disk 1 (/dev/sda) after 0:00:09. Apr 17 09:14:16 ME-NAS-316A noflushd[17454]: Spinning up disk 2 (/dev/sdb) after 0:00:07. Apr 17 09:14:17 ME-NAS-316A noflushd[17454]: Spinning up disk 3 (/dev/sdc) after 0:00:06. Apr 17 09:26:05 ME-NAS-316A noflushd[17454]: Spinning down disk 4 (/dev/sdd). Apr 17 09:26:13 ME-NAS-316A noflushd[17454]: Spinning up disk 4 (/dev/sdd) after 0:00:05. Apr 17 09:27:44 ME-NAS-316A noflushd[17454]: Spinning down disk 5 (/dev/sde). Apr 17 09:27:47 ME-NAS-316A noflushd[17454]: Spinning down disk 6 (/dev/sdf). Apr 17 09:27:54 ME-NAS-316A noflushd[17454]: Spinning up disk 5 (/dev/sde) after 0:00:07. Apr 17 09:27:54 ME-NAS-316A noflushd[17454]: Spinning up disk 6 (/dev/sdf) after 0:00:05. Apr 17 09:29:27 ME-NAS-316A noflushd[17454]: Spinning down disk 1 (/dev/sda). Apr 17 09:29:30 ME-NAS-316A noflushd[17454]: Spinning down disk 2 (/dev/sdb). Apr 17 09:29:32 ME-NAS-316A noflushd[17454]: Spinning down disk 3 (/dev/sdc). Apr 17 09:29:40 ME-NAS-316A noflushd[17454]: Spinning up disk 1 (/dev/sda) after 0:00:10. Apr 17 09:29:40 ME-NAS-316A noflushd[17454]: Spinning up disk 2 (/dev/sdb) after 0:00:08. Apr 17 09:29:40 ME-NAS-316A noflushd[17454]: Spinning up disk 3 (/dev/sdc) after 0:00:06. Apr 17 09:41:28 ME-NAS-316A noflushd[17454]: Spinning down disk 4 (/dev/sdd). Apr 17 09:41:36 ME-NAS-316A noflushd[17454]: Spinning up disk 4 (/dev/sdd) after 0:00:05. Apr 17 09:43:07 ME-NAS-316A noflushd[17454]: Spinning down disk 5 (/dev/sde). Apr 17 09:43:10 ME-NAS-316A noflushd[17454]: Spinning down disk 6 (/dev/sdf). Apr 17 09:43:17 ME-NAS-316A noflushd[17454]: Spinning up disk 5 (/dev/sde) after 0:00:07. Apr 17 09:43:17 ME-NAS-316A noflushd[17454]: Spinning up disk 6 (/dev/sdf) after 0:00:05.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
Hi Michael_Oz,
Did you do any other job when you were doing Spinning down?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
@Icewaterhot wrote:Did you do any other job when you were doing Spinning down?
Yes & No. Not for the period of the snippet shown, or for that day, when it did the same 91 (times 6 drives) other times that day.
I do not typically access the NAS during the day & not on that day.
On a previous day, a Defrag was running, it did not try to spindow while it was runing, then tried after it finished.
Of the ~2000 attempts (divide by 6 drives) in the log, covering ~6 days, the longest time down was 18 seconds with 90%<12s.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
Do you have any apps installed?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
And I have just finished going thru the other logs, there is nothing apparent or out of the ordinary happening when it spins up.
The same as the other times I reported this for previous versions.
EDIT And antivirus is NOT enabled, nor is file search
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
Hmmm, now that I think about it, I'll have to test again.
But I'm pretty sure it will be the same.
I have SpiderOak backups caching blocks to the NAS, so it could have been doing a backup.
But there are times that PC was shutdown, when I think it still didn't spindown.
So I'll double check.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
Sorry I got side tracked.
Checked today, my PC was sleeping overnight so could not be accesing the NAS.
Logs show spin down then up seconds later all night. See snip below.
There is a PVR in psuedo-sleep with a Samba connection, but it does not do anything.
May 03 02:39:24 ME-NAS-316A noflushd[26371]: Spinning down disk 1 (/dev/sda). May 03 02:39:27 ME-NAS-316A noflushd[26371]: Spinning down disk 2 (/dev/sdb). May 03 02:39:29 ME-NAS-316A noflushd[26371]: Spinning down disk 3 (/dev/sdc). May 03 02:39:36 ME-NAS-316A noflushd[26371]: Spinning up disk 1 (/dev/sda) after 0:00:09. May 03 02:39:36 ME-NAS-316A noflushd[26371]: Spinning up disk 2 (/dev/sdb) after 0:00:07. May 03 02:39:36 ME-NAS-316A noflushd[26371]: Spinning up disk 3 (/dev/sdc) after 0:00:05. May 03 02:40:58 ME-NAS-316A connmand[3192]: ntp: adjust (slew): -0.000715 sec May 03 02:49:00 ME-NAS-316A noflushd[26371]: Spinning down disk 4 (/dev/sdd). May 03 02:49:03 ME-NAS-316A noflushd[26371]: Spinning down disk 5 (/dev/sde). May 03 02:49:05 ME-NAS-316A noflushd[26371]: Spinning down disk 6 (/dev/sdf). May 03 02:49:12 ME-NAS-316A noflushd[26371]: Spinning up disk 4 (/dev/sdd) after 0:00:09. May 03 02:49:12 ME-NAS-316A noflushd[26371]: Spinning up disk 5 (/dev/sde) after 0:00:07. May 03 02:49:12 ME-NAS-316A noflushd[26371]: Spinning up disk 6 (/dev/sdf) after 0:00:05. May 03 02:49:41 ME-NAS-316A noflushd[26371]: Spinning down disk 1 (/dev/sda). May 03 02:49:44 ME-NAS-316A noflushd[26371]: Spinning down disk 2 (/dev/sdb). May 03 02:49:46 ME-NAS-316A noflushd[26371]: Spinning down disk 3 (/dev/sdc). May 03 02:49:54 ME-NAS-316A noflushd[26371]: Spinning up disk 1 (/dev/sda) after 0:00:10. May 03 02:49:54 ME-NAS-316A noflushd[26371]: Spinning up disk 2 (/dev/sdb) after 0:00:08. May 03 02:49:54 ME-NAS-316A noflushd[26371]: Spinning up disk 3 (/dev/sdc) after 0:00:05. May 03 02:58:02 ME-NAS-316A connmand[3192]: ntp: adjust (slew): +0.000207 sec May 03 02:59:17 ME-NAS-316A noflushd[26371]: Spinning down disk 4 (/dev/sdd). May 03 02:59:20 ME-NAS-316A noflushd[26371]: Spinning down disk 5 (/dev/sde). May 03 02:59:22 ME-NAS-316A noflushd[26371]: Spinning down disk 6 (/dev/sdf). May 03 02:59:30 ME-NAS-316A noflushd[26371]: Spinning up disk 4 (/dev/sdd) after 0:00:10. May 03 02:59:30 ME-NAS-316A noflushd[26371]: Spinning up disk 5 (/dev/sde) after 0:00:08. May 03 02:59:30 ME-NAS-316A noflushd[26371]: Spinning up disk 6 (/dev/sdf) after 0:00:05. May 03 02:59:59 ME-NAS-316A noflushd[26371]: Spinning down disk 1 (/dev/sda). May 03 03:00:01 ME-NAS-316A noflushd[26371]: Spinning down disk 2 (/dev/sdb). May 03 03:00:04 ME-NAS-316A noflushd[26371]: Spinning down disk 3 (/dev/sdc). May 03 03:00:11 ME-NAS-316A noflushd[26371]: Spinning up disk 1 (/dev/sda) after 0:00:10. May 03 03:00:11 ME-NAS-316A noflushd[26371]: Spinning up disk 2 (/dev/sdb) after 0:00:07. May 03 03:00:11 ME-NAS-316A noflushd[26371]: Spinning up disk 3 (/dev/sdc) after 0:00:05. May 03 03:09:01 ME-NAS-316A CRON[11239]: pam_unix(cron:session): session opened for user root by (uid=0) May 03 03:09:01 ME-NAS-316A CRON[11243]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean) May 03 03:09:01 ME-NAS-316A CRON[11239]: pam_unix(cron:session): session closed for user root May 03 03:09:35 ME-NAS-316A noflushd[26371]: Spinning down disk 4 (/dev/sdd). May 03 03:09:37 ME-NAS-316A noflushd[26371]: Spinning down disk 5 (/dev/sde). May 03 03:09:40 ME-NAS-316A noflushd[26371]: Spinning down disk 6 (/dev/sdf). May 03 03:09:47 ME-NAS-316A noflushd[26371]: Spinning up disk 4 (/dev/sdd) after 0:00:10. May 03 03:09:47 ME-NAS-316A noflushd[26371]: Spinning up disk 5 (/dev/sde) after 0:00:07. May 03 03:09:47 ME-NAS-316A noflushd[26371]: Spinning up disk 6 (/dev/sdf) after 0:00:05. May 03 03:10:16 ME-NAS-316A noflushd[26371]: Spinning down disk 1 (/dev/sda). May 03 03:10:19 ME-NAS-316A noflushd[26371]: Spinning down disk 2 (/dev/sdb). May 03 03:10:21 ME-NAS-316A noflushd[26371]: Spinning down disk 3 (/dev/sdc). May 03 03:10:29 ME-NAS-316A noflushd[26371]: Spinning up disk 1 (/dev/sda) after 0:00:10. May 03 03:10:29 ME-NAS-316A noflushd[26371]: Spinning up disk 2 (/dev/sdb) after 0:00:08. May 03 03:10:29 ME-NAS-316A noflushd[26371]: Spinning up disk 3 (/dev/sdc) after 0:00:06. May 03 03:15:06 ME-NAS-316A connmand[3192]: ntp: adjust (slew): +0.000286 sec May 03 03:17:01 ME-NAS-316A CRON[11412]: pam_unix(cron:session): session opened for user root by (uid=0) May 03 03:17:01 ME-NAS-316A CRON[11416]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 03 03:17:01 ME-NAS-316A CRON[11412]: pam_unix(cron:session): session closed for user root May 03 03:19:52 ME-NAS-316A noflushd[26371]: Spinning down disk 4 (/dev/sdd). May 03 03:19:55 ME-NAS-316A noflushd[26371]: Spinning down disk 5 (/dev/sde). May 03 03:19:57 ME-NAS-316A noflushd[26371]: Spinning down disk 6 (/dev/sdf). May 03 03:20:04 ME-NAS-316A noflushd[26371]: Spinning up disk 4 (/dev/sdd) after 0:00:09. May 03 03:20:04 ME-NAS-316A noflushd[26371]: Spinning up disk 5 (/dev/sde) after 0:00:07. May 03 03:20:05 ME-NAS-316A noflushd[26371]: Spinning up disk 6 (/dev/sdf) after 0:00:06. May 03 03:20:33 ME-NAS-316A noflushd[26371]: Spinning down disk 1 (/dev/sda). May 03 03:20:36 ME-NAS-316A noflushd[26371]: Spinning down disk 2 (/dev/sdb). May 03 03:20:39 ME-NAS-316A noflushd[26371]: Spinning down disk 3 (/dev/sdc). May 03 03:20:46 ME-NAS-316A noflushd[26371]: Spinning up disk 1 (/dev/sda) after 0:00:10. May 03 03:20:46 ME-NAS-316A noflushd[26371]: Spinning up disk 2 (/dev/sdb) after 0:00:07. May 03 03:20:46 ME-NAS-316A noflushd[26371]: Spinning up disk 3 (/dev/sdc) after 0:00:05.
This NAS has never slept in it's life. It, and I are getting tired ...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
This is the same for me, RN102, no way to have spindown working...... and i'm absolutely sure that nothing and no one is using my nas.... no antivirus, no applications, no access from pc or lan or internet.....
Unfortunately this problem seems completely ignored by Netgear technicians....
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
You could maybe strengthen the case by disconnecting the NAS ethernet cable for a couple of hours - the re-attach it and get the logs again.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
@StephenB wrote:
You could maybe strengthen the case by disconnecting the NAS ethernet cable for a couple of hours - the re-attach it and get the logs again.
Done. It dosn't take a couple of hours. I'll be back in 30 min.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
If you are comfortable with SSH to see what processes are issuing the reads and writes, you can run:
-
# echo 1 > /proc/sys/vm/block_dump
Replace the 1 with 0 to stop logging. It generates *tons* of kernel log messages so you won't want to leave this enabled for too long.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
@Michael_Oz wrote:
@StephenB wrote:
You could maybe strengthen the case by disconnecting the NAS ethernet cable for a couple of hours - the re-attach it and get the logs again.
Done. It dosn't take a couple of hours. I'll be back in 30 min.
I'm back. Minus ethernet it still fails to spindown for long (10s).
See attached snip of system-journal. Note I have the noflushd -b option set.
@mdgm-ntgr wrote:
It generates *tons* of kernel log messages so you won't want to leave this enabled for too long.
@mdgm-ntgr How long it too long?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
Well with spin-down set to say every 5 minutes you might do it for just 15-30 minutes or so.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
Seems it is in systemd-journal? If so here is a sample
May 04 12:03:27 ME-NAS-316A kernel: kworker/u8:4(6991): WRITE block 702080 on md0 (128 sectors) May 04 12:03:27 ME-NAS-316A kernel: kworker/u8:4(6991): WRITE block 283264 on md0 (64 sectors) May 04 12:03:27 ME-NAS-316A kernel: kworker/u8:4(6991): WRITE block 702208 on md0 (64 sectors) May 04 12:03:27 ME-NAS-316A kernel: noflushd(4991): WRITE block 128 on md0 (8 sectors) May 04 12:03:27 ME-NAS-316A kernel: noflushd(4991): WRITE block 131072 on md0 (8 sectors) May 04 12:03:27 ME-NAS-316A kernel: systemd-journal(1517): dirtied inode 1879942 (system.journal) on md0 May 04 12:03:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdd1 (1 sectors) May 04 12:03:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sda1 (1 sectors) May 04 12:03:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdb1 (1 sectors) May 04 12:03:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdc1 (1 sectors) May 04 12:03:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdf1 (1 sectors) May 04 12:03:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sde1 (1 sectors) May 04 12:03:29 ME-NAS-316A noflushd[4991]: Spinning down disk 2 (/dev/sdb). May 04 12:03:29 ME-NAS-316A kernel: rnutil(6994): dirtied inode 9380 (event.sq3) on md0 May 04 12:03:29 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:29 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:29 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:31 ME-NAS-316A noflushd[4991]: Spinning down disk 3 (/dev/sdc). May 04 12:03:31 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:31 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:31 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:34 ME-NAS-316A noflushd[4991]: Spinning down disk 5 (/dev/sde). May 04 12:03:34 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:34 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:34 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:36 ME-NAS-316A noflushd[4991]: Spinning down disk 6 (/dev/sdf). May 04 12:03:36 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:36 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:36 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:39 ME-NAS-316A apache_access[3329]: Admin session from 192.168.1.15 ended after 3:05:54 May 04 12:03:44 ME-NAS-316A noflushd[4991]: Spinning up disk 1 (/dev/sda) after 0:00:15. May 04 12:03:44 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:44 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:44 ME-NAS-316A noflushd[4991]: Spinning up disk 2 (/dev/sdb) after 0:00:13. May 04 12:03:44 ME-NAS-316A noflushd[4991]: Spinning up disk 3 (/dev/sdc) after 0:00:10. May 04 12:03:44 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:44 ME-NAS-316A noflushd[4991]: Spinning up disk 5 (/dev/sde) after 0:00:08. May 04 12:03:44 ME-NAS-316A noflushd[4991]: Spinning up disk 6 (/dev/sdf) after 0:00:05. May 04 12:03:44 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:44 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:44 ME-NAS-316A kernel: kworker/u8:4(6991): WRITE block 4263688 on md0 (8 sectors) May 04 12:03:57 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdd1 (1 sectors) May 04 12:03:57 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sda1 (1 sectors) May 04 12:03:57 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdb1 (1 sectors) May 04 12:03:57 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdc1 (1 sectors) May 04 12:03:57 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdf1 (1 sectors) May 04 12:03:57 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sde1 (1 sectors) May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(3745): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: readynasd(3745): dirtied inode 4026532241 (LCD) on proc May 04 12:03:57 ME-NAS-316A kernel: kworker/u8:4(6991): WRITE block 4452808 on md0 (56 sectors) May 04 12:03:57 ME-NAS-316A kernel: kworker/u8:4(6991): WRITE block 4452880 on md0 (504 sectors)
I presume md0 is memory disk zero so should be ignored.
readynasd(3712): dirtied inode 4998455 (blkid.tab) on tmpfs
What about tmpfs, is that memory disk too?
md0_raid1(1383): WRITE block 8 on sdd1 (1 sectors)
Seems sus. That set sd[abcdef]1 repeats every ~30s.
And:
May 04 12:19:42 ME-NAS-316A noflushd[4991]: Spinning up disk 1 (/dev/sda) after 0:00:14. May 04 12:19:43 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:19:43 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:19:43 ME-NAS-316A noflushd[4991]: Spinning up disk 2 (/dev/sdb) after 0:00:13. May 04 12:19:43 ME-NAS-316A noflushd[4991]: Spinning up disk 3 (/dev/sdc) after 0:00:10. May 04 12:19:43 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:19:43 ME-NAS-316A noflushd[4991]: Spinning up disk 5 (/dev/sde) after 0:00:08. May 04 12:19:43 ME-NAS-316A noflushd[4991]: Spinning up disk 6 (/dev/sdf) after 0:00:06. May 04 12:19:43 ME-NAS-316A kernel: kworker/u8:3(6888): WRITE block 4263688 on md0 (8 sectors) May 04 12:19:55 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdd1 (1 sectors)
Assuming ~12s spinup time for disk 6, it seems the md0_raid1 WRITE is the cause?
Anyway over to you blue leader.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
in e.g. kernel.log or systemd-journal.log
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
@Michael_Oz wrote:
I presume md0 is memory disk zero so should be ignored.
No, it's the operating system partition which is mirrored on all the disks. That's why you see the write repeated 6 times (disks a - f).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
May 04 12:08:26 ME-NAS-316A kernel: kworker/u8:2(5345): WRITE block 707456 on md0 (64 sectors) May 04 12:08:26 ME-NAS-316A kernel: btrfs-transacti(1419): WRITE block 128 on md0 (8 sectors) May 04 12:08:26 ME-NAS-316A kernel: btrfs-transacti(1419): WRITE block 131072 on md0 (8 sectors) May 04 12:08:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdd1 (1 sectors) May 04 12:08:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sda1 (1 sectors) May 04 12:08:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdb1 (1 sectors) May 04 12:08:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdc1 (1 sectors) May 04 12:08:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdf1 (1 sectors) May 04 12:08:27 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sde1 (1 sectors) May 04 12:08:46 ME-NAS-316A noflushd[4991]: Spinning down disk 1 (/dev/sda). May 04 12:08:46 ME-NAS-316A kernel: rnutil(7549): dirtied inode 9380 (event.sq3) on md0 May 04 12:08:46 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:08:46 ME-NAS-316A kernel: readynasd(4042): dirtied inode 4026532241 (LCD) on proc May 04 12:08:46 ME-NAS-316A kernel: kworker/u8:2(5345): WRITE block 4263688 on md0 (8 sectors) May 04 12:08:46 ME-NAS-316A kernel: md0_raid1(1383): WRITE block 8 on sdd1 (1 sectors)
noflushd[4991]: Spinning down disk 1 (/dev/sda).
kernel: rnutil(7549): dirtied inode 9380 (event.sq3) on md0
Every Spin down is followed by rnutil log entry, I'm speculating that may be a candidate cause.
@mdgm-ntgr is there anything else I can provide to confirm the bug?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
BTW, as there is no sub-seconds shown & there are lots of events happening in the one second, can you confirm that your log dump preserves the order of events correctly?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
@mdgm-ntgr Anything more I can do to confirm this bug & hopefully get it fixed?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
So has this been recognised as a bug?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNAS OS V6.9.3 - Discs don't spindown - still
Hi Michael,
i had the same problem for a long time, from the beginning, and trought the different firmware updates, 6.9.3 included.....
Then Netgear team provided me a beta 6.9.4 to test, and it seems to work, at least for me.... checking the logs, the disk spindown after the time i have set (1h), and stay down....99% of times....
There are still very little occasions in which the disk restart a couple of seconds after the spindown command, but may be they are caused by a real needing...
So definitely the beta 6.9.4 fixed the problem for me.
Thanks Netgear,
regards, Luciano