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.
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.
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.
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)?
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://: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.
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.
I mentioned earlier about the no ago shares when trying to back up to Timemachine. Left it connected via Ethernet last night. Dunno what changed but it’s sorted. Backup done. Cheers WD, this seems alright so far now. That was my only niggle.
Unfortunately it is not working for me. I just received a replacement drive due to the previous bad firmware. I installed the new drive and updated it to the latest 1.02.12 through the web configuration page using auto update. Time machine worked for about 3 hours when the drive disappeared. I was still able to log in to the drive through the web interface. This was the same symptom I had with the previous firmware. I restarted the drive through the web interface. This time, it did not solve anything. Time machine can see the drive, but when it starts to back up it says “looking for back up drive” for a few minutes. Then, a windows comes up showing the backup file in the drive and then I get an error message: the backup disk image “/volumes/WD_Backup/Matias’s macbook pro.sparsebundle” could not be accessed (error -1).
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)?
/Magnus
Here’s another clue to what might be wrong with the firmware: I am able to connect to the MBW via the router, but ONLY if the computer is connected via ethernet to the router. Wireless connection fails.
To sum it up:
Connect the computer to the router with a cable – Time Machine works fine.
Connect the computer to the router wirelessly – The MBW is not visible on the network.
This firmware clearly has some issues - but there are several of us on here who for whom TM is working well over wireless, so while we wait for a new firmware I’d continue tweaking settings on MBW and OsX (and post some logs) to find out why it works on some systems, and not others.
With some detailed MBW and Console logs the WD staff reading this (you are there, aren’t you?!) could maybe work out what is going wrong - I know from experience it’s impossible to help anyone based on a description of the problem.
In case anyone missed my earlier post, here’s what fixed all the problems for me - no idea which steps actually helped!
Os X
Complete permissions repair from recovery disk, NOT within a normal session.
Run Keychain First Aid (in Keychain access menu
NAS:
Disable HDD standby
Changed password for user wd_backup
Corrected NAS time setting
I’m also using a static IP, no NTP service, ftp & afp enabled, ssh disabled, nfs enabled with an “*” (wildcard) in the “IP allowed” field.
Thanks a lot, I think this is what finally made it!
I had tried it before, but it is important to also set the router to always use the same IP address for the MBW. So, now the router is set to always use 192.168.1.68 for the MBW, and the MBW is set to use 192.168.1.68 as well (Basic Mode > Network > Network Mode: Static).
Now I’m just waiting for the indexing to finish and backup of ~150 GB to begin…