Mybook studio raid 0, empty after installing Mavericks

It's not coxorange I'm belittling, it is WD the criticism is aimed at.

They could explain these basic steps, instead they code tools that appear to have contributed to many users data loss. Sorry if that is how it came across.

Cozachevici wrote:

We did pay money for this in order to have secure data Raid0 (that was the ideea , not to loose any file) and now we lost all drive ???

Raid0 is for speed not for reliability, just one disk broken and you loose all your data.

You still need a backup if using Raid0.

From the article:

Following those instructions will take out WD SmartWare, and at that point you will be able to access the drive, without fear of destroying data.

My understanding is that this is happening to people who didn't install any WD software as well, on different HDD brands, both FW & USB and RAID & Non-RAID configurations.

I'm on a Late 2008 MBP (5,1), no WD SW ever installed, upgraded to Mavericks from Lion via app store on Oct 25. I have 1TB WD MyBook Studio (FW) and 2TB WD MyPassport for Mac (USB). I have not suffered any data loss yet and all my drives have been backed up to an additional Seagate USB drive.

I can't work without at least the FW drive connected as my audio software pulls 500GB+ of libraries/sample files from there.

Is there any particular way to monitor the HDD in case of faulire? Perhaps to help ID the root cause.

Hopefully Apple will provide a script to allow people to rollback until they straighten this egregious nightmare out. This should NOT have happened. One expects this from Microsoft but not from Apple, who I've always held to a higher standard.

Your'e right it looks like it is Mavericks at fault not just the WD tools, since the source isn't available it makes it difficult to see what is actually happening, let alone monitoring the change.

Can you boot to another OS (not the recovery partition) & make a clone of the important data? I wouldn't trust my only copy of data to Mavericks on an external disk at this stage.

You could setup a 10.8 install for this purpose if the 500GB changes often, so that you reboot & backup nightly for example. iPods & USB thumb drives will work at a stretch (but a lot slower than internal / spinning disks).

I ran into the same issue with my WD Studio II and the data loss also affected all external drives connected: They suddenly all show up as "MyBook" and the data is gone. Both drives were connected in a daisy-chain using Firewire.

An even more interisting fact is that after a 'Deep Scan' with 'Data Rescue 3' all files including the directory structure and the original file names could be recovered from the external 'Buffalo' disk. The same scan on the WD Studio II only found files without any information about directory structure or even the original file name.

Drew,

Fortunately I have access to a Retina MBP with ML this entire week, I was able to mount the Seagate drive and access the 3 partitions I created there (Mavericks TimeMachine, FW drive and USB drive backups respectively).

I will not connect that backup drive to the Mavericks machine until more information is available on the issue. Any additional files I create I'm leaving on the Mavericks machine/Dropbox.

markras,

As much as I would like a rollback script I don't think it's the Apple way. Yes this is an unfortunate event and anyone who manages huge amounts fo data is suddently finding themseves with their hands tied. We should push for an increased effort on testing by Apple and 3rd parties.

Thanks for your answer.

Drew Reece wrote:

Just use basic disk handling…

Unmount BEFORE powering down.

Wait for disks to stop spinning after the unmount before moving the case.

In the past ("WD Drive Manager" with "Safe ShutdownTM" active) I ejected the drive when my Time Machine backup was completed and everything seemed quiet. When the drive stopped spinning, I switched the drive off (button on the rear) and saw the "WD" icon in the menu bar disappear. I never had a damaged file.

So you mean when I would eject the drive - without "WD Drive Manager" - OS X would take care that this would happen only after copy operations (via FireWire from the Mac to the drive) would have been completed?

AFAIK when the drive is idle after a backup it performs defragmentation. When I would switch off the drive (button on the rear) - without "WD Drive Manager" - how would be ensured that write operations would have been completed before the shutdown?

Thanks again.

Talked to Apple today no news yet. They requested to get us much respons as possible via the feedback page of the support site

https://ssl.apple.com/support/feedback/

So please fill out the form and report this problem!

Whatever is happening on disk is under the control of the OS. It gets complex when there are 3rd party tools that want to "improve" this process, that's why it's best to avoid low level tools that Apple didn't write, sadly some people must use them for features that the OS cannot do any other way.

If you use the Finder's eject icon it should take action to ensure all read & write processes are complete. It should 'sync' any updates that have been held in memory or buffers for that disk.

Finder will warn you when there is something that cannot be stopped (like a Terminal window that has it's 'current working directory' inside that disk). The same is true of Time Machine, it will try to finish pending read/writes if you want to eject mid-process. Normally the extra delay is not too noticable, sometimes it can look like it has hung up.

I'm not sure that I fully agree with the idea that Time Machine will defragment data, I think it is a mis-translated concept that is simply easier to use to describe a nebulous idea… 'backup thinning'

Time Machine generates backups hourly, as a part of that process it also needs to delete older copies, for example at the end of the day, only the last copy is needed, at the end of the week & month the same situation is true. It also needs to account for backups that didn't complete.

This means it will periodically remove a lot of files & update links to the structure that describes the backup history (it looks like a bunch of folders, but they have metadata on them too).

I'm unclear on what point it does this purging, I have log entries that state…

com.apple.backupd[37271] No pre-backup thinning needed: 733.6 MB requested (including padding), 150.88 GB available

Which suggests it happens before the backup proceeds.

You can usually watch this in the 'All messages' section of /Applications/Utilities/Console (filter on "com.apple.backupd").

Hope that helps & doesn't compound the confusion 🙂

As I had said earlier (and which Apple informed me they deleted) Mavericks is a bug-plaqued OS, released in Microsoft fashion. That is to say, get a workable Alpah and push it out to the Users for Beta. I am really surprised Apple went down this road. The issues with the various hard disk drives in inexcuable.

Unfortunately I also belong to this club now. My WD Passport HDD 400GB USB with Time Machine backup (then Journaled) has been deleted and unmounted by Mavericks. I don't use any WD Software. Only Apple OSX.

Plus i have problems with a ANT USB stick from Garmin (but this is another issue).

If you could get any solution please inform us.

I will not try to recover my files (all my backups and all my audio files and all my photos were on this drive which I considered very reliable!!!) until Apple willl not issue a solution for this problem.

I am using a MacBook Air late 2010 with 2GB RAM and 64 GB SSD. 1.4GHz Intel Core Duo processor.

Message was edited by: Btta88

If additionally people can add information such as:

"Macbook Pro 2010"...... or "Imac 2009" etc. to aid in deduction of a clear chain of causation.

thank you 😊

As I had said earlier (and which Apple informed me they deleted) Mavericks is a bug-plaqued OS, released in Microsoft fashion. That is to say, get a workable Alpah and push it out to the Users for Beta. I am really surprised Apple went down this road. The issues with the various hard disk drives in inexcuable.

I would hope I am not actually reading into your post what I think I am right now, Markras. If you do mean well, please do take more care of your English spelling, and secondly try to word your message more gently. Even if you may be rightfully indignant in this awful matter.

If not, do not be surprised when somebody or other, sooner or later, calls you a troll... Sorry. And so far for the offtopic.

...there sre no spelling errors....