Mybook studio raid 0, empty after installing Mavericks

If you have experienced data loss with the following criteria then please open support cases with both Western Digital and Apple support:

• MacOS Mavericks 10.9
• WD Drive Manager / Raid Manager software installed
• data loss after a restart
• drives initialised to a single MyBook partition with exposed EFI partition
• loss of all existing partitions and directory structures

If you are an Apple developer then please report an issue with Apple Bug Reporter.

Running 10.9 on a 2008 MBP.

Have a 4 bay Drobo connected via Firewire 800.

Drobo has 4 1TB WD drives in the bays, with 8 partitions.

After the first update to Time Machine, and a restart, only 3 partitions mount. (Not by Time Machine partition, of course.)

Only hope I am holding out is that the data is still there is because when I open iMovie, the last project I was working on appears from a partition that is not mounting. And it allowed me to edit and save and re-open later. Dim hope, but the only hope I have at the moment.

My 1 Gb no-name USB3-disk just went down the drains, this after having spent three hours cleaning up lost mail-folders in Mail (in another thread here). What a disaster this is. In one week I have lost email and a disk. This has never happened to me before. This is terrible. This is what it looked like:

Nov 1 09:15:23 kires-Mac kernel[0]: USBMSC Identifier (non-unique): 0x00000000 0x411 0x1de 0x1, 3

Nov 1 09:15:29 kires-Mac.local fseventsd[40]: could not open <</Volumes/E-FAT32/.fseventsd/fseventsd-uuid>> (No such file or directory)

Nov 1 09:15:29 kires-Mac.local fseventsd[40]: log dir: /Volumes/E-FAT32/.fseventsd getting new uuid: CEDBD211-208F-4B4C-BDF8-F072AE832ECA

Nov 1 09:15:29 kires-Mac kernel[0]: hfs: mounted E-Mac on device disk2s1

Nov 1 09:15:30 kires-Mac.local com.apple.backupd[1894]: Error -35 while resolving alias to backup target

Nov 1 09:15:30 kires-Mac.local fseventsd[40]: Events arrived for /Volumes/E-Mac after an unmount request! Re-initializing.

Nov 1 09:15:30 kires-Mac.local fseventsd[40]: creating a dls for /Volumes/E-Mac but it already has one...

Nov 1 09:15:35 kires-Mac kernel[0]: hfs: unmount initiated on E-Mac on device disk2s1

Nov 1 09:15:44 kires-Mac kernel[0]: hfs: Initializing the journal (joffset 0x1d1c000 sz 0x5000000)...

Nov 1 09:15:44 kires-Mac kernel[0]: hfs: mounted MyBook on device disk2s2

Nov 1 09:15:44 kires-Mac.local mds[66]: (Normal) Volume: volume:0x7fdbf3011e00 ********** Bootstrapped Creating a default store:3 SpotLoc:/Volumes/MyBook/.Spotlight-V100 SpotVerLoc:/Volumes/MyBook/.Spotlight-V100/Store-V1 occlude:0 /Volumes/MyBook

You can refresh the GPT by reducing the partition size a few Mb.

Hi,

Same thing for me. I've got a WD myBook Studio2 4TB in raid 0 + FW800 and everything has just disappeared and renames itself "myBook"! I have wd- turbo drivers and Wd- manager program + Maverikcs.

I lost 1.7T data and i rescue (Data Rescue 3) 1.1T data.... just 700g lost.

... ****! 😟

mike-h wrote:

If you have experienced data loss with the following criteria then please open support cases with both Western Digital and Apple support...

Yes, please do this! As the Apple Support rep I talked to said, they're aware of it but the more cases they get registered, the faster they will find a fix.

Samed problem here with a Lacie porsche 2 To via USB. Few days ago, it was unmounted and, after a while, mounted with the two infamous partitions (EFI and MyBook). I've lost all my work and pics dor the last 6 years.

For now WD has started to communicate on the problem but Lacie seems to be silent. Does anyone have some news?

Sorry to hear you are joing our ranks Ianboo,

Can you look in your /System/Library/Extensions folder and see if there are any WD files listed?

Will help in deciding if this is a OS X 10.9 issue, or a problem with WD software they may have been installed years ago but still lurking in your system.

Thanks.

I noted that you used your WD My Studio for time machine backups. At initial setup in 2009 I didn't use any of the WD software just plugged it in and let time machine proceed. I am using Firewire 800. I haven't upgraded to Mavericks but wondered if my set up was similar to yours. Most of these messages about the problem seemed to have been about using discs for more than time machine back ups.

Thanks,

Carol

My hard drive is a Lacie and not a WD but I checked if I had any WD files on my system and I had some in System/Library/Applications. So I can't say if it's because of these files or mavericks but anyway, before I did the update to mavericks, I didn't have any problems with my Lacie.

My Firewire desktop Lacie which i connect through a thunderbolt adapter to my MBPR was not showing up until I changed the thunderbolt socket I was using. Sounds stupid but may be worth a try.

Ok, so I deleted all remaining WD Software but my activity monitor still shows thw WD Button Manager and neither I can find it anywhere nor I am able to stop it. It just shows that it is run by user 'root'.

Can someone please give me advice on how to remove it?

I stumbled upon this thread while browsing other very annoying bug reports I'm trying to fix on my old MacBook Pro...

I just downloaded EtreCheck and got this data before ejecting and disconnecting my drive(s), now I might just be paranoid but are the below partitions normal? After reviewing the Console I realized all mounts where done from s10 so maybe it's not related to the "overnight" dissasters I'm reading about i.e. multiple mount/unmount operations (my other drive has only 3 partitions)

FireWire Information:

0x1F2 Vendor 0x1F2 Device 0x100800 400mbit - 400mbit max

WD My Passport 071D 800mbit - 800mbit max

disk1s1 (disk1s1) <not mounted>: 32 KB

disk1s2 (disk1s2) <not mounted>: 29 KB

disk1s3 (disk1s3) <not mounted>: 29 KB

disk1s4 (disk1s4) <not mounted>: 29 KB

disk1s5 (disk1s5) <not mounted>: 29 KB

disk1s6 (disk1s6) <not mounted>: 262 KB

disk1s7 (disk1s7) <not mounted>: 262 KB

disk1s8 (disk1s8) <not mounted>: 262 KB

STUDIOHD (disk1s10) /Volumes/STUDIOHD: 1 TB (579.69 GB free)

I also noted that Spotlight was performing cointinuous Indexing operations on all my drives, Console has multiple entries of fseventsd:

10/28/13 6:48:12.039 AM fseventsd[49]: event logs in /Volumes/STUDIOHD/.fseventsd out of sync with volume. destroying old logs. (783 5 19795)

10/28/13 6:48:12.052 AM fseventsd[49]: log dir: /Volumes/STUDIOHD/.fseventsd getting new uuid: ECC75CA3-8949-44E7-8834-1F7BE73245E0

Is Spotlight causing this mess? I have not lost any data yet but I'm now afraid of connecting the drives EVER again.

One more reason not to invest 5K on a Mac Pro :/ sorry guys.

I suspect you may have an 'Apple partition map'. It's an older disk format that had lots of small partitions for OS 9 drivers if I recall correctly.

What I would do is…

Download an earlier OS from the App store (10.8 etc), use 'Lion disk maker' or manually create a bootable installer on a USB thumb drive (use Disk Utility to restore the InstallESD.dmg).

Boot from the USB installer hook up the disks, open Disk Utility & inspect the disks. It will tell you the partition format etc.

There should be no chance of Mavericks damaging these drives if it isn't running. You can also verify the state of these disks from the USB stick. Obviously errors could explain why fsevents is losing sync.

Running from USB can be really slow, because of the speed of thumb drives, but it's better than nothing.

You can also use a bootable installer CD if you have one & your Mac has the drive (most likly a 10.6 installer).

I'm not sure if the actual error has been isolated to specific models of disk, it looks like RAID versions are most at risk, so you are wise to keep them away from Mavericks until Apple or WD release more info.

I don't know if the fsevents log messages are good or bad, I suspect Spotlight has to reindex because it has new scanners in the new OS.

I have a DVD drive and an old Leopard + Snow Leopard disk - will these do the job too?

Seriosly considering a clean install of Lion though, theres just way too many porblems with the OS I have already lost a week worth of work due to them!