New Firmware Version 1.02.12 for the My Book World I & II (10/19/11)

With Time Machine backups very slow compared to the FW  1.02.06, but was successful.
Now I have difficulty to access the shared folders with the Finder, even if the NAS is on the side bar and log on as usual with the mask to enter your username and password …but spins without going.

I apologize for my bad writing, but I translated with google.

Please give me advice, thanks!

Hi everyone,

If this is the first time that you have backed up using Time Machine in over 7-10 days, Time Machine will cark itself and need to reindex some things. If you have been using your Mac normally, what has been happening during your first few backups is that TM has had to create a very large number of folders/hard links to compensate.

My advice is to turn off Automatic Backups until you go to bed and allow TM to backup over Ethernet during the night. It should be ready in the morning.

-timeimp

This is one sucking update.

Just like saitarion  above, I also had problems with the update the first 5 times. But keep trying - for me it worked the 7th time!

First I tried automatic update 2 times, no luck.

Then I tried manual update 4 times, no luck.

Then I tried automatic update again, and it suddenly worked.

I rebooted the unit between some of the times. Just ONE of the SIX times of failure I got a proper error message from the web interface saying that the update failed. All the other times it looked like the drive went through a successful procedure, something counted to 100% and the web interface gave the impression of a restart/disconnection… but when nothing more happened during some 20 minutes I tried to reconnect with the drive and the web interface told me it’s still on version 1.02.10. Some serious sucking!

What I really can’t understand is… two things:

  1. How can a person who doesn’t think it’s important to care about how to treat people, choose to do work for lots and lots of people, in this case through being a programmer?

  2. How can a successful, serious(?) company like WDC hire such persons and let their low quality out on the market?

The next step is that our care of ill and elderly people are handled more and more by technology and computer programs. The care of your old mother will be handled mainly by programmers. If today’s low levels will not change dramatically very soon, it will be worse than not taking care at all.

Since the new firmware update is working just fine for some people, I suggest you post some relevent output from your system console or NAS logs instead of just ranting, which helps nobody.

Sorry, but I’m not just ranting - I’m also giving the advice to try again, and I’m describing how the update attempts looked from my perspective since I don’t see the same things described before by other users.

I’m joining “the conversation about all things WD.” This is “one place where you can talk to each other about how you’re using WD products and services. Ask questions, swap ideas, post and read information, opinions, and tips with others”, according to the description of the WD Community forum.

Log files and system consoles isn’t stuff that the community of users of common everyday products should have to deal with all the time. The developers, on the other hand, could deal with them much more.

Edit: quoted wrong post.

Spockdog wrote:

When I connect finder with My Book World I get message:

 

Something wrong with the volume’s CNID DB, using temporary CNID DB instead.Check server messages for details!

 

But after 2 error messages Finder is connected!!!

 

A reboot didn’t help.

 

TimeMachine doesn’t work, too.

 

Error-Message: The BackUp Volume doesn’t support AFP functions

 

I’m on Mac OSX Lion 10.7.2; My Book World 1 firmware 01.02.12 with MioNet (loaded manually today)

 

 

grrr

 

Any ideas?

 

I am investigating this, thanks for the feedback.  I am pretty sure I know what that issue is related too, but I am going to test a few things.  I’ll post back here with an update.

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 ?

Umpa2011 wrote:

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?

I am also having trouble with TM.  I can access my shares on the NAS but TM won’t recognize the backup drive on MyBookWorld.  Pre-Lion, I had two MyBookWorlds mounted in FInder, one for the share folders and one for TM backups.  Now the second one (backup) is gone and TM has nothing available for a backup.  I also had problems accessing Twonky but after several resets, reboots and cycling power on my router, I’ve been able to access Twonky.  As other users have mentioned, I also experienced the CNID DB error.  2 errors to be precise, when I first updated the MBWE firmware.  They have not reappeared.

Mac OS X 10.7.2

MBWE II Firmware - 1.02.12

Spockdog wrote:

When I connect finder with My Book World I get message:

 

Something wrong with the volume’s CNID DB, using temporary CNID DB instead.Check server messages for details!

 

But after 2 error messages Finder is connected!!!

 

A reboot didn’t help.

 

TimeMachine doesn’t work, too.

 

Error-Message: The BackUp Volume doesn’t support AFP functions

 

 

Hi!

I have the same problem after update :frowning:

UPDATE: after 2nd restart TM connected and it works!  I see that login process takes a lot of time.

My box has been running for 36 hours so far ok. As I said in one off my other post about the previous post is with version before I disabled twonkey and nominet as explained in this forum see below. This cured my original problems

but when I installed 1.02.10 and 12 twonky is up and running and so far all has been ok. YOU TRY THIS AT YOUR OWN RISK. Or search though the posts for the one about freezing up I think It is by hurtware. Good luck M

In the web configuration switch to Advanced Mode, then on the System tab using the Advanced button check the SSH Access checkbox on the top of the page, then Submit.
Using Putty or any other SSH client connect to your NAS’s IP address, and log in using “root” as username, and “welc0me” as password!
Now you are inside your NAS.
Type the following on the prompt (this will move/save the startup scripts to the /root/ folder and disable running of mionet and twonky main program and miocrawler it is unnecessary):
mv /etc/init.d/S9M_mionet /root/
mv /etc/init.d/S97twonkyserver /root/
mv /usr/mionet/bin/cvm /root/
mv /usr/mionet/changeNotifySocket /root/
mv /usr/mionet/plugin/miocrawler/miocrawler /root/
then reboot your NAS with
reboot
Disable all other unused services in the web configuration to free up some more RAM and make your NAS more stable.

I am running 1.02.12

morphy wrote:

My box has been running for 36 hours so far ok. As I said in one off my other post about the previous post is with version before I disabled twonkey and nominet as explained in this forum see below. This cured my original problems

but when I installed 1.02.10 and 12 twonky is up and running and so far all has been ok. YOU TRY THIS AT YOUR OWN RISK. Or search though the posts for the one about freezing up I think It is by hurtware. Good luck M

In the web configuration switch to Advanced Mode, then on the System tab using the Advanced button check the SSH Access checkbox on the top of the page, then Submit.
Using Putty or any other SSH client connect to your NAS’s IP address, and log in using “root” as username, and “welc0me” as password!
Now you are inside your NAS.
Type the following on the prompt (this will move/save the startup scripts to the /root/ folder and disable running of mionet and twonky main program and miocrawler it is unnecessary):
mv /etc/init.d/S9M_mionet /root/
mv /etc/init.d/S97twonkyserver /root/
mv /usr/mionet/bin/cvm /root/
mv /usr/mionet/changeNotifySocket /root/
mv /usr/mionet/plugin/miocrawler/miocrawler /root/
then reboot your NAS with
reboot
Disable all other unused services in the web configuration to free up some more RAM and make your NAS more stable.

You do realize that .12 is out right?

@krazydan

I am also experiencing EXTREME slowdowns even using Finder. On my MacBook Pro (running Lion) the logon to mount the drive used to take <1 second (pre 1.02.12 update), now it takes 30+ seconds to mount. Open a folder = another minute or longer just to view the directory. Good news is that my login under Lion seems to work, but the drive performance is basically unusable at this point.

BBBBBrandon wrote:


Umpa2011 wrote:

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.

Any info would be great.  Even an estimate.

Thanks.

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.

*groan*

Ideas?

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 :slight_smile:

I am running 1.02.12

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