(19-04-2014 21:12)MikeSpragg Wrote:  

(19-04-2014 21:08)simoncn Wrote:  

(19-04-2014 20:10)MikeSpragg Wrote:  Unfortunately, it's software - the upgrade is inevitable :-)

It isn't inevitable unless the current version breaks for some reason. No sign of that at the moment.

Quote:Microsoft Networking (Standalone Server)
Advanced -
Local Browser (Checked)

I have found it is essential to disable Local Master Browser to get spin-down to work.

Quote:Allow only NTLMv2 [you won't have this]

I do have this checkbox. It is unchecked but I don't this would make a difference.

Quote:Enable Async I/O (Highest SMB v2.0) [you won't have this]
Are all checked

Network Service Discovery,
UPnP Discovery Service (Checked) - will uncheck
Bonjour (Checked) - although this isn't needed so will uncheck it.

That's odd - never disabled master browser and, of course, spin down does occur. Just checked system since other changes, still running (led on) so I can make this change but fear it won't make a difference.

(19-04-2014 21:16)MikeSpragg Wrote:  Also, just noticed this in the minimserver.log

20:20:45.432 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:22:27.485 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.
20:30:52.122 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

20:35:44.431 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:44:59.432 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

20:45:08.535 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:52:52.397 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

21:05:45.569 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
21:11:57.496 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

There are long gaps in-between - but, eventually, it updates again....


z

(19-04-2014 21:12)MikeSpragg Wrote:  That's odd - never disabled master browser and, of course, spin down does occur. Just checked system since other changes, still running (led on) so I can make this change but fear it won't make a difference.

(19-04-2014 21:35)simoncn Wrote:  Also, I have found the QNAP admin console browser tab must be closed in order for spin-down to occur.

(19-04-2014 21:33)simoncn Wrote:  

(19-04-2014 21:16)MikeSpragg Wrote:  Also, just noticed this in the minimserver.log

20:20:45.432 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:22:27.485 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.
20:30:52.122 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

20:35:44.431 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:44:59.432 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

20:45:08.535 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:52:52.397 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

21:05:45.569 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
21:11:57.496 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.

There are long gaps in-between - but, eventually, it updates again....


z

This is expected if you have the logging level set to Debug. For spin-down to occur, you must set the logging level to Info.

(19-04-2014 21:38)simoncn Wrote:  

(19-04-2014 21:35)simoncn Wrote:  Also, I have found the QNAP admin console browser tab must be closed in order for spin-down to occur.

If you have any QNAP network shares open from another computer, I would also suggest disconnecting these.

(19-04-2014 21:40)MikeSpragg Wrote:  Well, that's interesting then - as it is set to Info.

MinimWatch - Properties | System | Info

Quote:MinimWatch - Options | Properties - ohNet.Debug default
MinimWatch - Options | Show Log - Info

(19-04-2014 21:49)simoncn Wrote:  

(19-04-2014 21:40)MikeSpragg Wrote:  Well, that's interesting then - as it is set to Info.

MinimWatch - Properties | System | Info

I don't see any such setting. Can you clarify where you have set Info in MinimWatch - Properties | System?

Quote:MinimWatch - Options | Properties - ohNet.Debug default
MinimWatch - Options | Show Log - Info

This is the wrong place. You need to set ohnet.debug in MinimWatch - Properties and you need to set Info in MinimWatch - Show log.

(19-04-2014 21:53)MikeSpragg Wrote:  When you right click MW - there is the menu on the right click - this shows Rescan | Properties | Show Log (this is set to ohNet.Debug = Default)

Quote:Then there are two more on Options | Properties (Watch) - this is Info
Options | Show Log (Watch) - this is Info

(19-04-2014 22:18)simoncn Wrote:  

(19-04-2014 21:53)MikeSpragg Wrote:  When you right click MW - there is the menu on the right click - this shows Rescan | Properties | Show Log (this is set to ohNet.Debug = Default)

You need to do the following:

1) Right-click the minim icon and select Show log. This will display the log window for the server.
2) In this window at the lower left, there is a combo-box named 'Logging level'. You need to set this to Info. If you do this, you won't get any ohNet messages in the minimserver.log file on the server.

Quote:Then there are two more on Options | Properties (Watch) - this is Info
Options | Show Log (Watch) - this is Info

These options control MinimWatch logging only. They don't affect logging on the server.