Interesting… I’ve tweaked the Samba server to make the Public share read-only so maybe this has spared me from the problem?
Also, why is the firmware update that caused problems still available for download?
I do wonder why with the latest firmware my MBL is working pretty darn well. :neutral_face:
CaphWD wrote:
I’ve had confirmation from WD Support that upgrading to the latest firmware causes a bug that can cause the MBL to malfunction. They have not yet tracked down this bug. It would seem that at least in my case the malfunctioning can be triggered by simply copying files to the Public share. As I’ve already mentioned, turning off the Twonky server prevents the MBL failing in my case.
Why has WD not publicly admitted this? Why is it not mentioned on the WD MBL Firmware download page? If I’d have known this I wouldn’t have updated and I would have waited until it was fixed.
I have had the latest firmware 02.10.09-124 on 3 MBL’s without any of problems supposedly related to this version of the firmware - and the updates were done via the standard method - but not automatcally. I had to click on check for updates.
I should point out - that at the time the updates were applied - I had Twonky and all other remote access disabled on all 3 MBL’s (and still do). Maybe Twonky being disabled at the time of upgrade is the key to preventing the problem.
Interesting… I’ve tweaked the Samba server to make the Public share read-only so maybe this has spared me from the problem?
Also, why is the firmware update that caused problems still available for download?
I do wonder why with the latest firmware my MBL is working pretty darn well. :neutral_face:
Who knows Myron. Do you have Twonky disabled? Maybe tweaking Samba with respect to the Public share is the answer. To be honest, I just wanted something that I could backup my files to and access them from my phone. I’ve wasted too much time on this now, life’s too short and all that. They haven’t got a clue what the problem is yet they now want me to buy another one so I can post mine to them and they say they’ll reimburse me. You’ve got to laugh or you’d cry.
I should point out - that at the time the updates were applied - I had Twonky and all other remote access disabled on all 3 MBL’s (and still do). Maybe Twonky being disabled at the time of upgrade is the key to preventing the problem.
~Scott
Personally, I think the problem is Twonky related but maybe it just seems that way on my MBL. Good luck with your units.
Sent my MBL back and WD recieved it on the 24th of January and still showing delayed. What is the normal time frame to actually get one of these RMA’d? I already bought another unit from a different manufacturer and so far I am extremely pleased with it’s performance, but I still need my drive back because I promised it to my sister.
Sooooo sloooowwwwwww, started out at roughly 10mb, but now all it can do is 50kbs -TOPS - I best describe it as a concrete slab with an ethernet port sellotaped on.
You’re right customer support is a joke, they just bang on about firmware updates, and reboots (so far thats all I can see).
I am running a mac and a bt home hub 3 (btw This delivers my BB at 38mbs through wireless), I’ve tried doing the okey cokey with the ethernet ports and all sorts of voodoo chants…
Cant wait to get my work off this thing eventually… if it doesnt keep failing on the factory restore… and swap it for a 2tb usb drive (NOT WD OF COURSE) and have it running steadily and faster than 50kbs on my desktop.
I’ve wasted most of this week faffing around with this thing… if only I could have a time machine for the real time I have lost arsing around with this.
Sent my MBL back and WD recieved it on the 24th of January and still showing delayed. What is the normal time frame to actually get one of these RMA’d? I already bought another unit from a different manufacturer and so far I am extremely pleased with it’s performance, but I still need my drive back because I promised it to my sister.
Normal time frame is around a week, if it shows as delayed you may contact WD to verify the status of your RMA.
I do have Twonky disabled. Did use it but now don’t have a need to use it.
CaphWD wrote:
Myron wrote:
Interesting… I’ve tweaked the Samba server to make the Public share read-only so maybe this has spared me from the problem?
Also, why is the firmware update that caused problems still available for download?
I do wonder why with the latest firmware my MBL is working pretty darn well. :neutral_face:
Who knows Myron. Do you have Twonky disabled? Maybe tweaking Samba with respect to the Public share is the answer. To be honest, I just wanted something that I could backup my files to and access them from my phone. I’ve wasted too much time on this now, life’s too short and all that. They haven’t got a clue what the problem is yet they now want me to buy another one so I can post mine to them and they say they’ll reimburse me. You’ve got to laugh or you’d cry.
Regarding “sub-standard recovery procedures”. The my book live stores the root partition on one half of a raid 1 volume. The second half is unmounted. If you want to recover the device, all it has to do is resync the known-good partition back across to the normal one. I think this is close to ingenius, and the guy who implemented it deserves considerable credit. Not dismissal.
I’ve had nothing but success with my WD Live. But then, I see it as a low power debian server, and bought it largely because it runs a friendly linux install and has ssh access almost out of the box. I didn’t get on with twonky, so I uninstalled it. I wanted it to run a reasonably complicated backup scheme, so now it does. I’m toying with the idea of repurposing it as offsite backup, setting up encryption and blocking access aside from ssh. Nothing I’ve done with it is remotely complicated.
If you want a product that just works, however little you understand it, sod off to macintosh and annoy their tech support instead. If your drive was faulty, WD would replace it. You’re coming across as a moron though, so I entirely forgive them if they suspect the problem to be the user and not the device.
actually if someone was here to help those with issues with correct solutions, there would be no sarcasm. but all anyone gets here is the same mundane answers that can be found in the product literature. what people need here and the reason they come here is to get specific solutions to specific problems.
