Mybook studio raid 0, empty after installing Mavericks

Hi,

I removed all the wd services manually because the uninstaller is not available anymore by WD.

Look into:

• /System/Library/LaunchDaemons/ - System-wide daemons provided by Mac OS X
• /System/Library/LaunchAgents/ - Per-user agents provided by Mac OS X.
• ~/Library/LaunchAgents/ - Per-user agents provided by the user.
• /Library/LaunchAgents/ - Per-user agents provided by the administrator.
• /Library/LaunchDaemons/ - System-wide daemons provided by the administrator.

• Delete all starting with wd.... like wdservicemanager.
• Reboot and check the Activity Monitor for still running wd-processes.

There will be one left the "wdhelper".

Then the tricky part:

• Login as root (check Apple documents how to activate root)
• Go to ./usr/libexec
• Delete wdhelper by moving it to the trash bin.

Reboot and Voilà

May the force with you 😉

Does this include: com.apple.wdhelper.plist in /System/Library/LaunchDaemons/

It’s the only instance of a WD file I can find before doing the “root” login.

No "wd" Processes are running in Activity Monitor.

Also do I do all this before of after the Mavericks update?

I’m still running 10.8.5.

What if I'm not using any WD drives?

To my knowledge, wdhelper has nothing to do with Western Digital and should not be deleted..

Hi!

Actually I think that the "wdhelper" process could be unrelated to any WD software. It is a system process to manage something related to wireless diagnostic.

You can find out it yourself typing "man wdhelper" in a Terminal session. This is the output:

wdhelper(8) BSD System Manager's Manual wdhelper(8)

NAME

wdhelper -- WirelessDiagnosticsSupport.framework XPC helper launchd dae-

mon

SYNOPSIS

wdhelper

DESCRIPTION

wdhelper XPC helper tool for performing privileged operations for Wire-

lessDiagnosticsSupport.framework

BSD October 31, 2013 BSD

So I don't think it's a great idea to remove or disable it...

BTW add me to the group of the ones who are in trouble with this WD-Mavericks thing...

Yesterday evening one of my external drives (luckily not the WD RAID 1 with all my photos) has been complitely screwed up... Suddenly it was unmounted and, after a while, mounted with the two infamous partitions (EFI and MyBook). The disk IS NOT a WesternDigital but a single Lacie with a Fujitsu drive inside.

I have another external usb disk currently mounted without any problem (at least for the moment). The only differences i can find between the two is the partition table type. The one screwed up has a GUID partition table while the other, still operating properly, has an APT partition table...

I don't know if this could be a clue...

Matteo

It's on Mac Rumors now...finally:

http://www.macrumors.com/2013/10/31/western-digital-warns-external-hard-drive-cu stomers-over-mavericks-data-loss/

Does this help?

http://wdc.custhelp.com/app/answers/detail/a_id/3835

Hi,

you are right.

Put wdhelper back from the trash bin an rebooted.

Thanks for the advice

Roland

MatFoi

Suddenly it was unmounted and, after a while, mounted with the two infamous partitions (EFI and MyBook). The disk IS NOT a WesternDigital but a single Lacie with a Fujitsu drive inside.

Your post is unclear, the unmounted drive that came back as EFI and MyBook.........firewire or thunderbolt Lacie (Seagate) with the internal Fujitsu.

I assume its an OLDER external drive, since LaCie (now seagate owned) doesnt use Fujitsu anymore and Fujitsu was incorporated into Toshiba in 2009

Since your Fujitsu cam back as a "MyBook" what (then) WD software did you have on your Mac.

Again, what model etc. of Lacie is it?

PlotinusVeritas wrote:

Your post is unclear, the unmounted drive that came back as EFI and MyBook.........firewire or thunderbolt Lacie (Seagate) with the internal Fujitsu.

I assume its an OLDER external drive, since LaCie (now seagate owned) doesnt use Fujitsu anymore and Fujitsu was incorporated into Toshiba in 2009

Since your Fujitsu cam back as a "MyBook" what (then) WD software did you have on your Mac.

Again, what model etc. of Lacie is it?

Sorry for not being clear about hard drive model and other info...

The post was mainly meant to point out the fact that wdhelper process is unrelated to any WD software...

The affected drive, as you said, is an old USB Lacie (about 6 or 7 years old). The Fujitsu drive model is: FUJITSU MHW2120BH.

I had the WD Drive Manager installed on the system. The drive worked just fine for the first week after the update to Mavericks then, all of a sudden, ... BOOM!

:-(

The other disk, currently mounted and working flawlessly, is another USB Lacie with an Hitachi drive in it (Hitachi HTS723225L9A360 ).

Hope to have been clearer this time...

Matteo.

Apple Support rep returned about the case I opened last week regarding the issue. A senior advisor asked for more information about the drive and WD software. He said engineering is aware of the problem and they are looking into it.

WD is working on it, too. Too late for many, unfortunately. This will go down in history as an epic computer disaster.

MatFoi

Fujitsu drive failed via USB......I had the WD Drive Manager installed on the system.

Yes, thank you. All indications logically eliminate (as it should) any causation related to specifically Mavericks and specific HD hardware (be it Toshiba/ WD/ Seagate/ Hitachi)

Though some reports come across that bare formatted drives via USB are affected, it is unknown if these persons in fact have, unwittingly, lingering WD software installed.

Ignoring the sleep 'issue' between Firewire and thunderbolt which is of very minor importance and a seperate occurrence,.....there is all indication increasingly so, that while most (or quickest affected) affected in these threads are WD MyBook,.. there is more than sufficient indication that non-RAID bare USB formatted simplex enclosure HD are being affected. (but as to lingering WD software installed...?)

Ignoring the 5% of reports, for purpose of clarity of 'most' occurances,... indications all point to: 1. RAID, 2. WD software, & Mavericks incompatibility between both or either of these two.

But somehow there seems to be a difference in how Mavericks reacts to the existence of WD Software. For me there was none left under LaunchDaemons or LaunchAgents anywhere. All the WD programs were transferred to the folder incompatible software. Now I deleted them.

PlotinusVeritas, do you think this is catalog corruption, or the partition table getting damaged?

I've seen the suggestions for Disk Warrior (I just used it to fix a botched Mavericks update on an iMac). It's not clear if it was pre existing damage that was made worse by the Mavericks installer or if it was entirely caused by it.

I wonder if the free TestDisk would help to recover any partiton damage?

http://www.cgsecurity.org/wiki/TestDisk

Clearly it is not for everyone, it's a command line tool but it may help with the analysis - I have always found it to be very good.

PhotoRec also by CGSecurity can also do file recovery, however it suffers from the same lack of metadata that most file carving tools do.

Drew Reece

do you think this is catalog corruption, or the partition table getting damaged?

I dont know, Ive tested a long line of USB external HD, both enclosed and in dock all working fine so far of the 4 that are still connected..., and about to test a Mavericks upgrade from a boot volume with WD software installed and have an attached HFS+ formatted drive with worthless testing data.

Most all corrupted drives so far report EFI and Mybook, or just Mybook on the volume and loss of meta data

I wont speculate since its counterproductive to any useful help

There are several reports of corruption with great success of recovery using Techtool Pro 7

http://www.micromat.com/products/techtool-pro

Thank you that's good to know.

I wonder about backing up the partition tables to see if that is fast way to recover after breaking it. On MBR you can just dd a copy the first 512 bytes. I'm not sure about GUID tables.