Mybook studio raid 0, empty after installing Mavericks

Can you please post a link to the firmware update.

Thanks

Leo

My drive that Mavericks killed is a Western Digital MyBook Studio II 6 TB, no RAID, connected via Apple's Thunderbolt to FireWire 800 adapter. Seems most other affected drives where RAID.

It's my Time Machine drive and it was the second time I connected it since moving to Mavericks. The first time everything seemed OK. I have several other WDC drives, some of which have been touched by Mavericks. I don't dare reconnecting them now.

With this long beta period of Mavericks, this cannot have gone unnoticed by Apple and WDC? If the latest firmware update I can find helps, why is there no information about this at WDC?

It's the SATA card inside the MyBook attached to the WD drive.

Without logic it seems WD failed to address this fault,...namely they had months to prepare

I rebooted from an external Lion drive, and connected the killed My Book. It was still empty, but you meant to use an older system just to be able to safely use a data retrieval tool, right? Not that the drive magically would be resurrected? (I was just hoping...)

The latest published firmware is the same as the one I had in the drive that was wiped.

>My drive that Mavericks killed is a Western Digital MyBook Studio II 6 TB, no RAID

Jan, it looks like you have the same drive as mine. It's a RAID with two hard disks inside.

You're right, of course. I'm just tired. It's a RAID 0.

raid 0. That's not good , no independent drive redundancy

Do you have an alternate Mac you can access for data extraction?

PlotinusVeritas, please stop spreading FUD. This has nothing todo wether its a RAID 0/1/5 or whatever. I have the same drives (4TB) in RAID1 and still everything was gone.

Joining the club here... I woke up this morning to find my 2TB RAID 1 completely wiped. All of my music, videos and projects have dissapeared.

It's strange though, it happened only a few days after installing Mavericks, not directly after. I guess it happened in the middle of the night. I did notice my MBP (retina) acting funny the night before, fans at full speed and a bit slow, but I'm not sure if that has anything to do with anything.

Maybe there's something in the console log? I'll dig through that to see if there's any nuggets of information that we could raise to developers.

All in all, I'm bracing for the worst. I tested it on an iMac with Mountain Lion and it came up with nothing.

***** to be us!

I also am trying Disk Drill as many of you are suggesting. It's pulling up a bunch of really strange files that I've never seen before. Weird music and videos too. I'm going to let it run and see what happens.

This issue is very serious and is resulting in people losing their important data. Personally I have only lost my backups so far, but if anything happens to my laptop I will be in trouble. It will be very inconvenient for me to have to go buy a new backup drive as well.

Blaming this on the hardware developers like WD is horribly misguided and reeks of Apple apologism at its worst. No operating system should ever delete the contents of a hard drive under any circumstances. Period.

Apple needs to communicate on this issue immediately and let people know what to do to recover their data, if possible. If not, we need to know, so we can start using these drives for backups again or buy new ones if need be. Apple can't continue to remain mute on the topic however, it's gravely irresponsible.

Do we know that it's Mavericks that's doing this? Or the WD RAID driver?

Furthermore, do we know of people using RAID arrays with non-WD drives experiencing this issue?

Update: Disk Drill is working for me and is slowly but surely salvaging files. However, the files are being taken out of context and just being dumped into file-type folders (Audio, Pictures, Documents, etc.) rather than their original file/folder structure. I'm assuming metadata is also affected because of the file names (file0000001.jpg, file0000003.wav, etc.). This can be higely problematic for people that are meticulous with organizing their data.

Its happening on 80% WD Raid My Book on this board and others, and happening entirely on Firewire and Thunderbolt drives

Its seen on O Raid and 1 Raid both alike.

also occurring on LaCie (Seagate) FW drives.

until resolution , use external USB drives proven to work with Mavericks. 😊

It also affected by WD MyBook USB single mechanism drive and another single mechanism

WD drive connected by FireWire. I'm reasonably confident that it is the MyBook Studio II drive management software, and it obviously affects drives connected via difference protocols. I've sent my main drive off for professional recovery.

Blake McKimmie

confident that it is the MyBook Studio II drive management software,

Yeah, .....HD software for personal computers should NEVER be used. Been warning many people about that for a long time.

If its not too late you would not have to send your drive out for expensive recovery, rather attach to another Mac and extracting the HD and putting into a HD dock would be enough for data extraction

That is the first step the "data recovery" people do anyway.