- WD Community
- News & Assistance
- New to Community
- Forum Feedback
- Software & Apps
- WD Software
- WD Mobile Apps
- Software & Accessory Ideas
- WD TV Live Streaming
- Live Streaming Discussions
- Live Streaming Firmware
- Live Streaming Ideas
- Live Streaming Issues
- WD TV Live Hub
- Hub Discussions
- Hub Firmware
- Hub Themes
- WD TV Live Hub Ideas
- WD TV Live Hub Issue Reporting
- WD TV Play
- WD TV Play
- Live & Live Plus
- Live Discussions
- Live Firmware
- Elements Play
- Elements Play
- External Drives
- Mac Externals
- PC Externals
- Portable Drives
- External Drive Ideas
- Network Devices
- Networking Devices
- Live Duo
- My Book Live
- Other Network Drives
- Network Product Ideas
- Internal Drives
- Desktop & Portable
- Internal Drive Ideas
- Nuevo a La Comunidad
- Los Productos de WD
- Software y Accesorios
- Reproductores Multimedia
- Unidades de Red
- Unidades Externas
- Unidades Internas
- Neu in der Community
- WD Produkte
- WD Programme
- WD TV Media Player
- Netzwerk Laufwerke
- Externe Laufwerke
- Interne Laufwerke
- Annunci e Novita'
- Nuovo per La Comunita'
- Prodotti WD
- Programmi & Accessori
- Riproduttori Multimediali
- Dischi di Rete
- Dischi Esterni
- Dischi Interni
- WD TV Legacy
- Hub Network
- Live Networking
- WD TV HD
- WD TV Mini
- WD Photos
- Other Software & Accessories
- Hard Drives
- WD ShareSpace
- Other Externals
- Other Internal Drives
10-21-2011 10:51 PM
I updated, then did a full system restore as there were no files that i needed on this nas. Re-set it all up. Lasted 12 hours and now it has locked up. Can't ssh, can't get to web admin BUT can ping it from terminal. why ?
Did you enable SSH access in the web UI previously? Can you even access the web ui at this point?
Hi after a reboot all is fine, after a few hour (like this morning) the unit has locked up. My other MBWE's that are not on the new firmware are fine. SSH is enabled but not working after lockup. After lockup I cannot access the device ar all, except for ping.
10-21-2011 10:52 PM
I'm just wondering about the file size of the new firmware update. I currently have no internet at home due to changing ISPs so I only have my phone data. I downloaded the firmware installer which mentions about downloading modules for the firmware. Anyone know how big the firmware upgrade ends up being?
I just don't want to start the process and then realise the download is too big, thereby forcing me to cancel the ungrade midway, potentially corrupting my NAS.
Any info would be great. Even an estimate.
10-21-2011 11:18 PM
The update for me had had 2 effects.
1. Much longer to login (both Lion and SL)
2. Only one of my users can login using Finder (both Lion and SL). All others fail to connect over the network using Finder even though I have deleted them all and recreated them. I can login fine in the browser using all users credentials.
10-22-2011 01:20 AM
Hope, again :-)
After three reboots of My Book World1 TimeMachine is running (after nearly 3 months it took the whole night to backup).
Mounting NAS via Finder takes more than one minute (when TimeMachine is running).
Mounting NAS via Finder takes about 30 seconds when TimeMachine is not running.
I'm on Lion and SnowLeoapard and 1.02.12
SnowLeopard Mac needs even more than 2 minutes to mount NAS with Finder (when TimeMachine is running)
and about 30 seconds when TM is not running.
It has been a few seconds on 1.02.06 !!!!
I think, you WD should do some touching up on the firmware.
But I'm glad to use TimeMachine again :-)
10-22-2011 02:21 AM
I can't connect to my MBW 4TB (white lights) via my router. I've updated to Firmware version 1.02.12, no problem, but I can't use Time Machine the way I want to.
If I connect the MBW directly to my computer (Lion 10.7.2), it shows up all right via Bonjour, and I can use Time Machine. If I connect it to my router (Thomson TG784), I'm unable to use Bonjour. I can connect to it using the IP number (and I can change the unit's settings), but I still can't use Time Machine.
Also, I cannot connect to the unit via the router on my other Mac (running Snow Leopard 10.6.8).
Someone on this thread suggested turning HDD standby off, which I did, but it doesn't help. Someone else suggesting turning Twonky server off, however I can't figure out how to do so.
I have SSH access disabled, as well as MioNet.
Something strange: When I look at users (Basic mode), WD_Backup (Time Machine User) seems to be diabled – there is a red cross beside it.
Any suggestions (besides waiting for a new Firmware update)?
10-22-2011 02:28 AM
I've updated to the latest firmware (1.02.12) and have to report the upgrade went smoothly for me on the 2 WD Mybook WE drives I have (WE I and WE II).
I do however have 2 issues with the latest firmware update:
- After rebooting the drive it appears that the twonky media server does not rebuild its database. In order to get TM to display the stored files I now seem to have to do a manual rebuild of the database.
This is done from the maintenance menu after going to the twonky config page (http://<server-ip>:9000/config)
- Connecting the the shared drives seems to take a very long time from OSX; connection from windows seems to be fine. Once connected all seems to work fine. This includes the use of Time Machine from the mac - long connection time, but fine once connected.
The connection times from the mac is in the order of 45 second.
For me these latest issues are no more than a minor annoyance - as long as I'm able to store and access my data and media files I'm happy.
10-22-2011 04:17 AM - last edited on 10-22-2011 12:41 PM by oxter
With this firmware MBW doesn't appear on my MacBookPro ! With 1.02.06 no problem ! Really it's the last time I will buy a DD from WD ! [Deleted]
10-22-2011 08:21 AM
WOW! Am I the only one that had the upgrade to .12 go smoothly?
Went thru the automatic upgrade process...took 10-20 minutes.
Maybe it's because I use NO features except file sharing.
At this point, it's been about 30 min since upgrading. No probs yet.
The big test will be when I pull my laptop, go on site and come back - that's what tanked the drive under .10
Will keep you advised.
10-22-2011 10:56 AM - edited 10-22-2011 11:28 AM
Having very much the same problem as Umpa2011.
Upgrade to 1.02.12 was completed on first try.
But since then the drive has frozen just like on the 10 release. I only use the drive for file share and nothing else. After it has frozen you cannot see it in the network divices, no mapped shares work, Web UI does not load to see config but you can ping the drive 100%.
I only have Vista and Windows 7 connecting to the drive and mostly from the Vista laptop.
Dont know how to solve... Any suguestions welcome... Maybe someone from WD would like to connect to my system and run a few test when this happens.
http://www.youtube.com/watch?v=zIqtZraOxDU (This is the showing of the device that can reply with a ping but not be accessed.)