Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MinimServer & HDD Sleep
17-04-2014, 18:44
Post: #11
RE: MinimServer & HDD Sleep
(17-04-2014 18:32)MikeSpragg Wrote:  
(17-04-2014 18:09)MikeSpragg Wrote:  OK, here you go - if you skip to the end and look for >> *****GOES QUIET******** ---vvv Then awakens here you'll notice it mentions about ohNet - and repeats this at 17:52, 17:54, 17:57, 18:05

It looks like a device is accessing Minim - but I've checked all devices and nothing is running that would.

Aha, I set ohNet logging to "None" - that's fixed it by the seems of things !

If MinimServer logging is set to Info, there will be no ohNet output in the minimserver.log file, so this is not what is preventing disk spin-down.

The "device" that is accessing MinimServer is presumably an application or service running on the QNAP. By disconnecting the QNAP network connection, you have eliminated the possibility of a device that is external to the QNAP.

This other application or service running on the QNAP is presumably doing some disk I/O that is preventing disk spin-down. The other possibility is that ohNet is doing some other disk I/O (i.e., not writing to the minimserver.log file).
Find all posts by this user
Quote this message in a reply
17-04-2014, 18:50
Post: #12
RE: MinimServer & HDD Sleep
(17-04-2014 18:44)simoncn Wrote:  
(17-04-2014 18:32)MikeSpragg Wrote:  
(17-04-2014 18:09)MikeSpragg Wrote:  OK, here you go - if you skip to the end and look for >> *****GOES QUIET******** ---vvv Then awakens here you'll notice it mentions about ohNet - and repeats this at 17:52, 17:54, 17:57, 18:05

It looks like a device is accessing Minim - but I've checked all devices and nothing is running that would.

Aha, I set ohNet logging to "None" - that's fixed it by the seems of things !

If MinimServer logging is set to Info, there will be no ohNet output in the minimserver.log file, so this is not what is preventing disk spin-down.

The "device" that is accessing MinimServer is presumably an application or service running on the QNAP. By disconnecting the QNAP network connection, you have eliminated the possibility of a device that is external to the QNAP.

This other application or service running on the QNAP is presumably doing some disk I/O that is preventing disk spin-down. The other possibility is that ohNet is doing some other disk I/O (i.e., not writing to the minimserver.log file).

Yes, thought it was too good to be true and just an oddity. Within 5 mins it shutdown - but 1 min later (in time it took me to post) started up again!

The applications running on the QNAP (aside from internal ones) are only MinimServer and JRE (I don't use it for anything else). If I shutdown MinimServer - everything goes quiet and stays that way. After 5 mins - the disks spin down and the green LED goes out (meaning that the disks are spun down).

If I leave MinimServer running. None of the above occurs (with networking connected or disconnected) green LED stays on and I can hear the disks are still running. If turn off MinimServer and leave JRE running - then green LED goes off (and stays off). If I turn off both apps - same result, all goes quiet and disks spin down after 5 mins and stay that way.

So, I can't help but think it's just MinimServer causing this spin-up and stay-up scenario.
Find all posts by this user
Quote this message in a reply
17-04-2014, 19:07
Post: #13
RE: MinimServer & HDD Sleep
(17-04-2014 18:50)MikeSpragg Wrote:  Yes, thought it was too good to be true and just an oddity. Within 5 mins it shutdown - but 1 min later (in time it took me to post) started up again!

The applications running on the QNAP (aside from internal ones) are only MinimServer and JRE (I don't use it for anything else). If I shutdown MinimServer - everything goes quiet and stays that way. After 5 mins - the disks spin down and the green LED goes out (meaning that the disks are spun down).

If I leave MinimServer running. None of the above occurs (with networking connected or disconnected) green LED stays on and I can hear the disks are still running. If turn off MinimServer and leave JRE running - then green LED goes off (and stays off). If I turn off both apps - same result, all goes quiet and disks spin down after 5 mins and stay that way.

So, I can't help but think it's just MinimServer causing this spin-up and stay-up scenario.

It seems that it is one of the internal QNAP applications or services that is doing this disk I/O resulting from its UPnP interactions with MinimServer.

Which QNAP applications and services are enabled? Which version of the QNAP firmware are you running?
Find all posts by this user
Quote this message in a reply
17-04-2014, 19:20
Post: #14
RE: MinimServer & HDD Sleep
(17-04-2014 19:07)simoncn Wrote:  
(17-04-2014 18:50)MikeSpragg Wrote:  Yes, thought it was too good to be true and just an oddity. Within 5 mins it shutdown - but 1 min later (in time it took me to post) started up again!

The applications running on the QNAP (aside from internal ones) are only MinimServer and JRE (I don't use it for anything else). If I shutdown MinimServer - everything goes quiet and stays that way. After 5 mins - the disks spin down and the green LED goes out (meaning that the disks are spun down).

If I leave MinimServer running. None of the above occurs (with networking connected or disconnected) green LED stays on and I can hear the disks are still running. If turn off MinimServer and leave JRE running - then green LED goes off (and stays off). If I turn off both apps - same result, all goes quiet and disks spin down after 5 mins and stay that way.

So, I can't help but think it's just MinimServer causing this spin-up and stay-up scenario.

It seems that it is one of the internal QNAP applications or services that is doing this disk I/O resulting from its UPnP interactions with MinimServer.

Which QNAP applications and services are enabled? Which version of the QNAP firmware are you running?

The only services running are those that I can't see - the ones such as Media, FTP, Web etc. aren't running, it's the latest version (4.1)
Find all posts by this user
Quote this message in a reply
17-04-2014, 19:47
Post: #15
RE: MinimServer & HDD Sleep
(17-04-2014 19:20)MikeSpragg Wrote:  The only services running are those that I can't see - the ones such as Media, FTP, Web etc. aren't running, it's the latest version (4.1)

Can you revert from 4.1 Beta to an earlier version to see if that fixes it?

Can you remember which firmware version you were running when you first noticed the problem?
Find all posts by this user
Quote this message in a reply
17-04-2014, 19:55
Post: #16
RE: MinimServer & HDD Sleep
(17-04-2014 19:47)simoncn Wrote:  
(17-04-2014 19:20)MikeSpragg Wrote:  The only services running are those that I can't see - the ones such as Media, FTP, Web etc. aren't running, it's the latest version (4.1)

Can you revert from 4.1 Beta to an earlier version to see if that fixes it?

Can you remember which firmware version you were running when you first noticed the problem?

To be fair, I've only had the unit a short time (4 months I think) and it's always been 4.1 (which seems to be in permanent beta!). I upgraded from 3.5 on day one and this definitely started after upgrading Minim I'm afraid (from .5? To .8)
Find all posts by this user
Quote this message in a reply
17-04-2014, 20:58
Post: #17
RE: MinimServer & HDD Sleep
(17-04-2014 19:55)MikeSpragg Wrote:  To be fair, I've only had the unit a short time (4 months I think) and it's always been 4.1 (which seems to be in permanent beta!). I upgraded from 3.5 on day one and this definitely started after upgrading Minim I'm afraid (from .5? To .8)

To find out exactly what is happening, I will need to see a full ohNet debug log covering a 30-minute period when the QNAP is disconnected from the network. Please do the following:

1) From the MinimWatch log window, set the logging level to Debug
2) From the MinimWatch properties dialog, set the ohnet.debug property to All-Timer
3) Close the MinimWatch log window and properties dialog
4) Disconnect the QNAP from the network
5) Leave the QNAP disconnected for 30 minutes
6) Reconnect the QNAP to the network
7) Copy the minimserver.log file to another location
8) From MinimWatch, reset the logging level to Info and the ohnet.debug property to Default
9) Zip the minimserver.log file that you copied in step 7) and attach it here

Many thanks!
Find all posts by this user
Quote this message in a reply
17-04-2014, 21:07
Post: #18
RE: MinimServer & HDD Sleep
(17-04-2014 20:58)simoncn Wrote:  
(17-04-2014 19:55)MikeSpragg Wrote:  To be fair, I've only had the unit a short time (4 months I think) and it's always been 4.1 (which seems to be in permanent beta!). I upgraded from 3.5 on day one and this definitely started after upgrading Minim I'm afraid (from .5? To .8)

To find out exactly what is happening, I will need to see a full ohNet debug log covering a 30-minute period when the QNAP is disconnected from the network. Please do the following:

1) From the MinimWatch log window, set the logging level to Debug
2) From the MinimWatch properties dialog, set the ohnet.debug property to All-Timer
3) Close the MinimWatch log window and properties dialog
4) Disconnect the QNAP from the network
5) Leave the QNAP disconnected for 30 minutes
6) Reconnect the QNAP to the network
7) Copy the minimserver.log file to another location
8) From MinimWatch, reset the logging level to Info and the ohnet.debug property to Default
9) Zip the minimserver.log file that you copied in step 7) and attach it here

Many thanks!


Ok, will do - my laptop is backing up to a share at mo so will get it to you ASAP.
Find all posts by this user
Quote this message in a reply
17-04-2014, 23:49
Post: #19
RE: MinimServer & HDD Sleep
(17-04-2014 21:07)MikeSpragg Wrote:  
(17-04-2014 20:58)simoncn Wrote:  
(17-04-2014 19:55)MikeSpragg Wrote:  To be fair, I've only had the unit a short time (4 months I think) and it's always been 4.1 (which seems to be in permanent beta!). I upgraded from 3.5 on day one and this definitely started after upgrading Minim I'm afraid (from .5? To .8)

To find out exactly what is happening, I will need to see a full ohNet debug log covering a 30-minute period when the QNAP is disconnected from the network. Please do the following:

1) From the MinimWatch log window, set the logging level to Debug
2) From the MinimWatch properties dialog, set the ohnet.debug property to All-Timer
3) Close the MinimWatch log window and properties dialog
4) Disconnect the QNAP from the network
5) Leave the QNAP disconnected for 30 minutes
6) Reconnect the QNAP to the network
7) Copy the minimserver.log file to another location
8) From MinimWatch, reset the logging level to Info and the ohnet.debug property to Default
9) Zip the minimserver.log file that you copied in step 7) and attach it here

Many thanks!


Ok, will do - my laptop is backing up to a share at mo so will get it to you ASAP.

Here you go !


Attached File(s)
.zip  minimserver.zip (Size: 225.97 KB / Downloads: 1)
Find all posts by this user
Quote this message in a reply
18-04-2014, 12:59 (This post was last modified: 18-04-2014 12:59 by simoncn.)
Post: #20
RE: MinimServer & HDD Sleep
(17-04-2014 23:49)MikeSpragg Wrote:  Here you go !

Thanks very much!

This log doesn't show any activity that could cause disk I/O. Here's a summary:

23:16:06 The NAS is disconnected from the network
23:16:06 The Monitor device sends out "alive" notifications on the loopback subnet
23:24:40 The MediaServer device sends out "alive" notifications on the loopback subnet
23:29:27 The Monitor device sends out "alive" notifications on the loopback subnet
23:38:09 The MediaServer device sends out "alive" notifications on the loopback subnet
23:42:18 The Monitor device sends out "alive" notifications on the loopback subnet
23:47:42 The NAS is reconnected to the network

If MinimServer logging is set to Info, this activity will not cause anything to be written to the log and will not cause any other disk I/O from the MinimServer/Java process.

If you are seeing disk I/O with MinimServer logging set to Info, this might be caused by something else on the QNAP that is handling the network activity generated by the "alive" notifications (for example, some kind of network logging). However, the timing of this "alive" activity doesn't fit with your earlier description that the disk I/O occurs regularly every 4 to 5 minutes.

Another possibility is that ohNet is doing something every 4 to 5 minutes that isn't being logged and is causing disk I/O. From my knowledge of how ohNet works, this seems very unlikely.

Can you produce a similar complete log of disk I/O activity for a 30-minute period when the NAS is disconnected from the LAN? This would be similar to the extracts you included in this post. When doing this, please set ohnet.debug to Default and MinimServer logging to Info. If I can see the complete picture over a 30-minute period, I might be able to spot some pattern.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)