if you temporarily stop twonkymediaserver, does the box run stable?
/etc/init.d/S97twonkyserver stop
(after reboot twonky will start again automatically)
if the box runs stable, a possible workaround could be to restart twonkyserver by crond at regular intervalls (e.g. at night). I have no idea about fixing twonky, but there is a Parameter in the configfile (/DataVolume/jewab/twonkymedia-server.ini)
streambuffer=131072
which seems a litte weird (my box has 128MB RAM ;-), you could change this to e.g.
However, I followed all your suggestions but my MBWE still freezes at night when our backup scripts run.
Everytime I go to work in the morning, I will not be able to access the MyBook through run and http. I was able to ping it though like what hurtware mentioned in his first post. I need to do a hard reset to be able to make it back online and accessible.
I already upgraded the firmware to 01.02.06 with MioNet 4.3.1.7. I also disabled inetd, twonky and mionet but still to no avail. I don’t even get 2 days uptime. Can’t get much info on the logs either.
that’s strange… I was quite successful (uptime nearly 2 weeks) with the same measures (upgrade to 1.02.06, inetd, twonky, mionet stopped). What I did additionally was formatting swap space (see here http://community.wdc.com/t5/My-Book-World-Edition/WD-World-Edition-white-light-freezes-locks-up/m-p/124738#M3630), sorry for those voodoo-advices but I am sort of desperate with this super-buggy-box, too I guess you transfer many GBytes per night? Please check your process list to be sure no twonkymediaserver, mionet or inetd is running.
After I posted in this thread, for some reason, the MBWE didn’t freeze up. I am not sure what’s going on here but I got almost 6 days uptime but today, i think it froze again.
Not really that much, probably like 1-2 GB only.
If you don’t mind, where can you get the CLI commands for this MBWE? Like for checking the process list. Thanks a lot for your help.
I think I figured out what’s going on. There was actually a server transferring a huge chunk of data in MyBook every night. I tried stopping the scripts for that particular server and I got 4 days uptime now.
I also stopped iTunes and AFP server because I’m not using it anyway.
Just to make sure, will the formatting of swap space affect any of the data in the MBWE?
Yes I think that is the problem, this box gets overloaded with large amounts of data, exactly what a real NAS should handle Maybe you got rid of this bug by deactivating unneeded services. I would recommend to observe if your MBWE is stable now, if you experience another crash reformat swap space. This does not affect any data on your drive but you must be absolutely sure to run the mkswap command on the swap partition and not on any data partition! You can check this by “cat /proc/swaps” or “swapon -s”, the output shows the right partition to format.
That’s good! Seems twonky is one of the culprits, let me know if you succeed with the streambuffer configuration. My box runs for about 2 weeks without crash now, too
Thank You, my box is working over 2 weeks now, too. I’m absolutely frustrated about the fact, that WDC does not only ignore this problem since more than 1 year, they even sell this “product” with a fatal systematic error at the time and they provide no qualified support or firmware updates.
I have problem with this disk since I bought it six months ago , and hoped that new versions will solve blocking issues, but for now …
Few weeks ago I have upgraded firmware to 1.02.05 , nothing was changed, disk still blocking and I had to hard reset it all the time, twonky media server not working.
Now I wanted to update to 1.02.06 ( it is not working anyway, so no harm done) but if I try automatic update I got msg.
"Your device is up to date " , and there is no file to do it manually. Any sugestion ?
I’m not so familiar with linux, but I think I had stopped twonky server from starting automatically, how to start it now manually.
Found out this topic y-day, had exactly the same problems with WD My Book World Edition.
Symptoms: only responded to ping, lowest front LED was lit, couldn’t access web interface, couldn’t access shared folders, no go with SSH.
Using latest firmware (01.02.06 with MioNet 4.2.27), disabled itunes, mionet, ftp, nfs and afp. Despite all that it hardly achieved uptime more than a couple of days, sometimes it went MIA two to three times a day. On several occasions it froze when i booted up one of the computers in network.
'Nyway, i followed hurtwares guides and disabled inetd and manually stopped twonky. Uptime now 1 days, 5:02, hot **bleep** I’ll keep you posted just FYI, to see if it helped…
If (or better yet, WHEN) it freezes again, i’m putting this piece of ■■■■ in permanent retirement. Even more so, because recently i got me a Qnap 219P NAS & UPS combo. This device NEVER! froze, getting uptimes of 90+ days, only rebooted it 3 times for fw upgrades. Now this is what i’d call a good SOHO NAS.
What a contrast to that utter WD piece of s***! I’d never thought WD can “afford” such a product.