Mybook studio raid 0, empty after installing Mavericks

I have 2 LaCie RAID drives (4TB 4big Quadra connected via FireWire800 and 6TB LaCie 2big connected via Thunderbolt) that seemed to have been affected by this issue. Both were working fine under 10.8 and now Disk Utility reports ridiculous RAID configurations that have RAID slices spanning the two drives!

I just bought a new 6TB LaCie 2big so I could copy the data that I'm still able to read off the two other arrays. When I connected the new LaCie 2big, Disk Utility reports that it's RAID configuration is again spanning multiple enclosures which is just insane. I'm pretty convinced this is an issue with OS X...

Keeping all my external drives offline until there is a fix for this (hopefully soon).

I'm affected too, but in a weird way. I have two WD 3TB external drives, and when I plug them in, it takes about 10 mintues for the files to show up, then another 30 mintues for the files to be readable. I can't download anything to the disks, nor realistically work from the discs. I also can't backup the discs, as I upgraded both of my MBP's at the same time.

This is unacepptable APPLE and WD! A plague on both your houses. You had plenty of time to remedy such an important issue. Data loss of precious files is serious business both professionally AND personally. Fix it.

Bruce in Indy

Keeping all my external drives offline until there is a fix for this (hopefully soon).

Until then, standard USB HD non-RAID, with no control software is 100% fine for backups/ archives.

😊

USB drives will also be killed by this Maverick Maggot. Beware!!!

To find a better workaround, it would be nice, if everyone, who was affected by a data loss, could tell the community, if any other third party software for hard disk managing (e.g. WD Driver Manager) was installed on the affected system.

I have uninstalled my WD software stuff and until now every thing works fine (knock on wood).

Was anybody else successful with this workaround?

And I know, using standard USB drives will help. 😉

This is scary and unacceptable. This has occurred on my My Book Studio II 2 TB and my G-Tech Mini 750GB both connected via Firewire.

Both of them show with a "MyBook" and "EFI" partition AND are of course empty. And this seemed to happen when I connected them last night and they weren't connected throughout the day.

Needing solution...the data CANNOT be gone. Unacceptable!

Did you install software form WD, e.g. WD Drive Manager?

Whats awful is that new people keep coming to this forum after losing their data. This thread goes right back to Mavericks release date, and still new people are joining it – because there is no public announcement warning people not to upgrade if they are using the WD manager.

Apple and WD must be aware of this issue and working feverishly on a fix in the background, but in the interim more people are upgrading and losing their data every day, oblivious to the threat. Slow motion car wreck.

WD was running prior to the upgrade to Maverick. Haven't tried installing any other software, or reinstalling any WD software.

I'm not going to remove the drives yet, but I'm willing to send it to a data recovery specialist. This cannot happen the drive that I used to backup my backup is also affected.

You should remove the WD stuff manually. This will not bring back your data, but perhaps prevent from additional data loss.

This is NOT confined to WD external drives. I have LaCie RAID arrays (firewire 800 and thunderbolt) that have been borked by the 10.9 update.

Even a NEW LaCie 2big thunderbolt RAID array isn't handled correctly by my 10.9 install. There is something going on with OS X and RAID arrays and it isn't due only to WD software, there is something in OS X itself in addition.

Your are right. I have had a data loss on two Lacie drives either.

But I think this is not only a failure of Mavericks, but of the incompatible WD software, which also affects non WD drives.

Have you checked, if some WD software stuff is installed on your system? This would be very interesting for the community.

I got a new Lacie raid-system today and checked this with a Mavericks machine without WD driver or other additional management software. Until now no problem.

My other drives, which where killed before (one WD, one Lacie), are running without any problem on a Mavericks machine with uninstalled WD software. Until Sunday evening no problem (knock on wood).

I think I have the same problem. I have two external WD MyBook drives which I created a raid 0 with under Mountain Lion's disk utility (so no third party software used or firmware updates or such). After installing Mavericks, I get an error saying that I can't mount the drives and that I should run repair on them (which I'm afraid to do).

I don't know if the disks are corrupted already or if I should wait out a fix. I guess that they might be alright since they have never been mounted under Mavericks, but I also guess that the corruption might have made it unmountable.

Right now I'm downloading Mountain Lion to see if I can mount the disks with it installed.

what a train wreck

So I installed Mountain Lion but the error persists so the disk (or both disks) have been corrupted.

This is what the log says:

jnl: disk4: open: journal magic is bad (0x0 != 0x4a4e4c78)

hfs: late jnl init: failed to open/create the journal (retval 0).

hfs(3): Journal replay fail. Writing lastMountVersion as FSK!

hfs_mounthfsplus: hfs_late_journal_init returned (0)

hfs_mounthfsplus: encountered errorr (22)

hfs_mountfs: encountered failure 22

hfs_mount: hfs_mountfs returned 22

jnl: disk4: is_clean: journal magic is bad (0x0 != 0x4a4e4c78)

hfs: late journal init: volume on disk4 is read-only and journal is dirty. Can not mount volume.

hfs_mounthfsplus: hfs_late_journal_init returned (22)

hfs_mounthfsplus: encountered errorr (22)

hfs_mountfs: encountered failure 22

hfs_mount: hfs_mountfs returned 22

jnl: disk4: open: journal magic is bad (0x0 != 0x4a4e4c78)

hfs: late jnl init: failed to open/create the journal (retval 0).

hfs(3): Journal replay fail. Writing lastMountVersion as FSK!

hfs_mounthfsplus: hfs_late_journal_init returned (0)

hfs_mounthfsplus: encountered errorr (22)

hfs_mountfs: encountered failure 22

hfs_mount: hfs_mountfs returned 22

I don't really know what to do... Try to recover the data with possiblie data loss and getting all file names screwed up or wait for a fix from Apple. Using "first aid" or some external tool? This is a nightmare scenario...