I reckon that the Time Machine software scripting in Mavericks has a bug in it, that causes it to start again and make a brand new Time Machine record.
According to an Apple support statement: "Time Machine is a backup utility, not an archival utility, it is not intended as offline storage.
In other words if Time Machine fails, you should still have all your original data in it’s proper place.
You do, don’t you?
I don’t understand why several folk are panicking over this issue!!!
Ok, the drive reset om Mavericks seems to only be happening when the wd drive manager is loaded. I tried without it for some days, and the unit did not reset. Today I tried and re installed wd drive manager and after a cold boot the unit was reset. (all files gone, and drive name reset to default.). So it seems the wd drive manager is not compatible with Mavericks GM:
I use raid 1. It’s still a raid 1 even with out any WD software, the mac just sees one big disk. I don’t think Drive utilities works with the legacy drives…
I got so tired of this so I just pulled the plug on the wd my book studio II, in fact I’m thinking of taking the drives out of the unit and installing them in an Icy dock raid usb 3 cabinett instead.
I also got this problem after installing Mavericks yesterday…this morning I almost got some heart faliure…
I Checked the WD with DiskDrill, and all the files are there and recoverable. (tested on a small amount, but no file structure…13 yrs of files in erratic order…oj oj. )
Same thing happened to me with a WD My Book Studio Edition II 6TB. After calling WD numerous times they gave up and asked me to ask Apple what Mavericks does to their raid drive and to try recovering my data with a recovery software. 5TB archive gone at the moment, with a partial backup. I’ve never seen anything like this. Very serious and desperate situation.
As soon as I installed OS X 9.0 I received an error message that my WD External drive was not compatible, and since then all backups have failed.
I emailed WD tech support asking if a fix is in the works, but have not yet received a reply.
So, if WD reads this, please reply and let us know if you are going to make your products compatible with OS X 9.0, and when and how will the fix be distributed to users like me?
I don’t claim to be any expert but my guess is that Apple’s (software?) RAID took over and reconfigured the RAID. WD Drive Manager is obviously imcompatible with Mavericks as it appears multiple times in the menu bar everytime the drive is mounted and does not go away without a restart. The Empty/“MyBook” state of the drive is stuck no matter where I tried it (OS 10.8 and 10.6 with and without WD software).
My drive was killed too. Looked just like ccontreras’ screen shot, with that EFI volume as well.
RAID 0, My Book Studio II 6 TB, connected via Apple’s Thunderbolt-to-FireWire-800 adapter.
I dared to connect my Thunderbolt My Book a couple of times, and it seems fine. But I have eight other My Book Studio firewire drives that I don’t know what to do with. They all have the latest firmware from WDC, just like the one that got wiped.
After the inital install of Mavericks everything was okay.
After restarting “Poof” Data gone. The WD Raid Manager kicked in and all was lost. Now there is one partition called EFI and one called MyBook.
Interestingly my USB Stick, which was connected too, showed three volumes, instead of one (EFI, OSX Boot, Data).
Wuuaaaahhhha
Edit: I checked the MyBook with the HD Utility from OS X. It told me that the Partition Scheme was damaged. So I repaired it. After that I wanted to make sure, that the RAID 1 was still working. So I started the RAID Manager from WD and build a new RAID 1. Guess what? After finishing there was the EFI Partition visible again and the HD Utility told me again, that the Partition Scheme was damaged. For me this looks really like that the WD RAID Manager is the culprit. I uninstalled it and hope that my RAID is working nevertheless. At the moment I make a new backup of my System…