Now this one is very interesting and does make sense.> * * *
mybookW2 wrote:
It’s finally consistently going to sleep and staying there! It through my various tweaking of setting it appears the twonky seems to keep the drive awake due to the -1 value for checking for new files. I have now changed this to 1500 and the drive goes to sleep! I have noticed however I occasionally my iPad will wake The drive for no reason which may also prevent it from sleeping, so if you have a iOS device try turning it off for a bit to see what happens? iTunes and remote access is still enabled when it sleeps just invade you where wondering.
mybookW2 wrote:
It’s finally consistently going to sleep and staying there! It through my various tweaking of setting it appears the twonky seems to keep the drive awake due to the -1 value for checking for new files. I have now changed this to 1500 and the drive goes to sleep! I have noticed however I occasionally my iPad will wake The drive for no reason which may also prevent it from sleeping, so if you have a iOS device try turning it off for a bit to see what happens? iTunes and remote access is still enabled when it sleeps just invade you where wondering.
Can u explain me wich steps i have to follow?
All front end setting i changed. See http://YOUR.IP:9000 to get to the twonky server, all i have done is changed the value on database refresh from -1 to 1550, i also mapped the folders correctly, instead of the folder being /public i gave it another level ie /public/music but not sure if that makes any difference. I also disabled the twonky log as it overfills and is rubbish! But overwise itunes still enabled, and remote access. The only thing i notice is that IOS seems to wake the drive up when i connects to the wireless LAN. Please let us know if it works for you?
My MBL was continiously working and was busy by twonky updating its DB. Now i finally found what was the reason - by default sharing folder was set to /public. But I changed it to /Public/Shared Music, /Public/Shared Videos and /Public/Shared Pictures and moved appropriate content inside of those folders, but only folder by folder (file-by-file), not all at once, especially if folder (file) has a huge size. So I waited untill DB scan was completed and MBL goes to standby mode after certain period of time. LED in sleep mode lights in blue, BUT when it wakes up green color lights work very strange, it blinks for a while, then goes blank, then dim and it chages randomly even if nothing is writing/reading to/from MBL.
But i have just disabled twonky and the drive don’t sleep…
Have you changed the refresh value from-1 to something bigger see if that makes any difference
No, it remains -1, and correctly goes to sleep mode after predefined period of time
I changed the value but then i disabled twonky… and the drive still wake up after few minutes…
Does your drive stay asleep?
ashevchenko wrote:
No, it remains -1, and correctly goes to sleep mode after predefined period of time
Here u are my log user :
Nov 25 20:26:47 localhost logger: Enter standby
Nov 25 20:27:48 localhost logger: exit standby after 61
Nov 25 20:37:52 localhost logger: Enter standby
Nov 25 20:39:14 localhost logger: exit standby after 82
Nov 25 20:57:27 localhost logger: Enter standby
Nov 25 21:02:43 localhost logger: exit standby after 316
Nov 25 21:12:49 localhost logger: Enter standby
Nov 25 21:18:44 localhost logger: exit standby after 354
Nov 25 21:28:51 localhost logger: Enter standby
Nov 25 21:34:45 localhost logger: exit standby after 354
Nov 25 21:44:52 localhost logger: Enter standby
Nov 25 21:50:46 localhost logger: exit standby after 354
Nov 25 22:00:53 localhost logger: Enter standby
Nov 25 22:06:48 localhost logger: exit standby after 355
Nov 25 22:16:54 localhost logger: Enter standby
Nov 25 22:22:49 localhost logger: exit standby after 355
Nov 25 22:32:56 localhost logger: Enter standby
Nov 25 22:38:50 localhost logger: exit standby after 354
Nov 25 22:48:57 localhost logger: Enter standby
Nov 25 22:54:52 localhost logger: exit standby after 355
Nov 25 23:04:59 localhost logger: Enter standby
Nov 25 23:09:14 localhost logger: exit standby after 255
Nov 25 23:19:21 localhost logger: Enter standby
Nov 25 23:26:54 localhost logger: exit standby after 453
Nov 25 23:37:01 localhost logger: Enter standby
Nov 25 23:39:14 localhost logger: exit standby after 133
Nov 25 23:49:21 localhost logger: Enter standby
Nov 25 23:58:57 localhost logger: exit standby after 576
Nov 26 00:09:04 localhost logger: Enter standby
Nov 26 00:10:04 localhost logger: exit standby after 60
Nov 26 00:20:12 localhost logger: Enter standby
Nov 26 00:30:59 localhost logger: exit standby after 647
Nov 26 00:58:18 localhost logger: Enter standby
Nov 26 01:03:02 localhost logger: exit standby after 284
Nov 26 01:13:09 localhost logger: Enter standby
Nov 26 01:19:03 localhost logger: exit standby after 354
Nov 26 01:29:09 localhost logger: Enter standby
Nov 26 01:35:04 localhost logger: exit standby after 355
Nov 26 01:45:11 localhost logger: Enter standby
Nov 26 01:51:06 localhost logger: exit standby after 355
Nov 26 02:01:13 localhost logger: Enter standby
Nov 26 02:07:07 localhost logger: exit standby after 354
Nov 26 02:17:14 localhost logger: Enter standby
Nov 26 02:23:08 localhost logger: exit standby after 354
Nov 26 02:33:15 localhost logger: Enter standby
Nov 26 02:39:09 localhost logger: exit standby after 354
Nov 26 02:49:16 localhost logger: Enter standby
Nov 26 02:55:11 localhost logger: exit standby after 355
Nov 26 03:05:18 localhost logger: Enter standby
Nov 26 03:09:14 localhost logger: exit standby after 236
Nov 26 03:19:21 localhost logger: Enter standby
Nov 26 03:27:13 localhost logger: exit standby after 472
Nov 26 03:37:20 localhost logger: Enter standby
Nov 26 03:39:14 localhost logger: exit standby after 114
Nov 26 03:49:21 localhost logger: Enter standby
Nov 26 03:59:16 localhost logger: exit standby after 595
Nov 26 04:19:30 localhost logger: Enter standby
Nov 26 04:31:18 localhost logger: exit standby after 708
Nov 26 04:57:29 localhost logger: Enter standby
Nov 26 05:03:21 localhost logger: exit standby after 352
Nov 26 05:13:24 localhost logger: Enter standby
Nov 26 05:19:22 localhost logger: exit standby after 358
Nov 26 05:29:25 localhost logger: Enter standby
Nov 26 05:35:24 localhost logger: exit standby after 359
Nov 26 05:45:27 localhost logger: Enter standby
Nov 26 05:51:25 localhost logger: exit standby after 358
Nov 26 06:01:28 localhost logger: Enter standby
Nov 26 06:07:26 localhost logger: exit standby after 358
Nov 26 06:17:29 localhost logger: Enter standby
Nov 26 06:23:27 localhost logger: exit standby after 358
Nov 26 06:33:30 localhost logger: Enter standby
Nov 26 06:39:14 localhost logger: exit standby after 344
Nov 26 06:49:17 localhost logger: Enter standby
Nov 26 06:55:30 localhost logger: exit standby after 373
Nov 26 07:05:33 localhost logger: Enter standby
Nov 26 07:09:14 localhost logger: exit standby after 221
Nov 26 07:19:17 localhost logger: Enter standby
Nov 26 07:27:33 localhost logger: exit standby after 496
Nov 26 07:37:36 localhost logger: Enter standby
Nov 26 07:39:14 localhost logger: exit standby after 98
Nov 26 07:49:18 localhost logger: Enter standby
Nov 26 07:59:35 localhost logger: exit standby after 617
Nov 26 08:19:42 localhost logger: Enter standby
Nov 26 08:31:38 localhost logger: exit standby after 716
Nov 26 08:57:47 localhost logger: Enter standby
Nov 26 09:03:40 localhost logger: exit standby after 353
If that the case I would suggest one by one disabling features and enabling them until you find a possible solution. For example enable twonky disable iTunes, enable all disable remote access etc. this is what I tried to get my drive to sleep.
mybookW2 wrote:
If that the case I would suggest one by one disabling features and enabling them until you find a possible solution. For example enable twonky disable iTunes, enable all disable remote access etc. this is what I tried to get my drive to sleep.
- *So it does appear to sleep? Have you mapped the folders as above to ea h music, photos, video and not just /public see if that works? Note this will cause twonky to recreate the database you’ll also need to restart the twonky server, click the restart in the twonky menu.
Yes, it does go to sleep mode, everything is enabled and scan options set to -1. The only
problem is Led when it blinks green, I wrote before
Does it do it of the value -1 is changed to say 1000?
Arrrgh!!! DO NOT KEEP TWONKY’s LOGGING OPTION ENABLED FOR TOO LONG A TIME AND GET RID OF THE LOG WHEN YOU’RE DONE WITH IT !!!
Twonky writes it’s log to one of the system partitions with has limited space! 47Meg available to the temporary directory. When that fills all **bleep** could break loose! Also, with logging enabled and Twonky enabled, the MBL will not to go sleep. Been there, done that and singed my own fingers.
mybookW2 wrote:
All front end setting i changed. See http://YOUR.IP:9000 to get to the twonky server, all i have done is changed the value on database refresh from -1 to 1550, i also mapped the folders correctly, instead of the folder being /public i gave it another level ie /public/music but not sure if that makes any difference. I also disabled the twonky log as it overfills and is rubbish! But overwise itunes still enabled, and remote access. The only thing i notice is that IOS seems to wake the drive up when i connects to the wireless LAN. Please let us know if it works for you?
Not good. After successful install and reboot MBL no longer accessible via Quick View on taskbar. In fact WDDM smart status is not reporting any values (usage/temp). Also lost MBL in network places. IP address listed in router. Able to access via IP address. Remapped to network places and all folders and data present. Note trying to remap using WD quick view resulted in error “no local network found”. Able to acces twonky server via IP address:9000 and is working fine. Unable to use any of features Wd Quick view other than properties.
Windows XP SP3
Yeah, I can confirm the re-occurrence of this annoying bug.
No standby again! Wonder whether this is intentionally, as WD is a harddisk manufacturer.
this is great… i have two WD My Book 3TB NAS drives, both did firmware update and both are screwed. I cannot load WEB UI for both, shares still accessible…
I have a pathetic luck with this product as I will be returning these drives. These drives are already the 3rd replacement for one and 2nd replacement for another.
Really disapointed in the WD Brand. I will not buy another WD drive.
Anyone from Western Digital who is in-the-know can provide an answer why this is happening?
Touch actual wood, mine’s operating fine, but writing this, the update to the present firmware for me was not done through the Dashboard UI. Tried a manual update (don’t trust automatic update) and it seemed to freeze during the upload. That spooked me.
As I have SSL enabled what I did was put the firmware file onto the NAS’s drive and then invoked the script that updates from file and that worked fine.
I think from now on when I update the firmware, it won’t be through the Dashboard UI. Will place the file manually onto the MBL and directly invoke the script to perform the update.
My advise is… Right after you read this, enable the SSL feature.
Login to the Dashboard in the usual way, at the menu change to the browsers web address http://mybooklive.local/UI/ssh, load that page and enable it. Just in case the Dashboard UI dies. If you do, don’t put your NAS on the router’s DMZ or set a port forward to port 22 until you change the password from welc0me to something more secure.
mrWiggy wrote:
this is great… i have two WD My Book 3TB NAS drives, both did firmware update and both are screwed. I cannot load WEB UI for both, shares still accessible…
I have a pathetic luck with this product as I will be returning these drives. These drives are already the 3rd replacement for one and 2nd replacement for another.
Really disapointed in the WD Brand. I will not buy another WD drive.
Also not fixed is the simple SMB/CIFS protocol.
From 3 upgrades ago it becomes dead.
