Mybook studio raid 0, empty after installing Mavericks

No WD disks have ever been installed on my system nor any WD software. My LaCie drives are certainly affected by the installation of 10.9, though. The WD software may be partly to blame but there is something else going on that is not connected with the WD software.

I see your error code----- Writing lastMountVersion as FSK

I've seen that before and it's discussed here

http://m.sooperarticles.com/technology-articles/data-recovery-articles/how-resol ve-mac-journal-magic-bad-error-340304.html

MAC operating system has a feature of journaling the file system due to which the chances of fault flexibility together with providing protection to the file system preventing from the hardware failure incidents and sudden power turn off. The journal plays vital role comprising all the confidential information that are required by the MAC operating system so that it could be returned to the previous working station.

These journals being vital component of the MAC operating system if gets corrupted, leads into serial results. It may turn the whole data inaccessible by means of turning the volume unmountable. Once user undergoes such disaster the only thing that leads to recover the situation is the valid backup as the data can be restored and the corrupted can be removed from the hard disk without being worried about the data loss issue.

Just trying to work out a common cause here.

it appears that it has happened to a couple of people without Western Digital WD being involved. Is this the case?

Is it RAID that is the common factor? Anyone experienced the blank disk 'MyBook' volume who didn't have it set up as some sort of RAID drive before the 10.9 Mavericks upgrade?

Cheers.

I have the same problem with my WD 1tb. I installed Mavericks some days ago and everything worked fine untill this morning. When I turned it on today it was blank. I have spoken to Apple support twice and they said they have no information of this happening to other customers and that it is unlikely that the problem is related to their operating system.😮 They haven't been helpful at all. And they were not aware of the discussion on this forum.

I had 2 LaCie RAID drives (one 4big Quadra 4TB connected via Firewire 800 and one 6TB LaCie 2big connected via Thunderbolt). After the 10.9 upgrade, the 4big started being sluggish with abnormally high amounts of disk activity. At some point (not sure exactly how long after the 10.9 upgrade), the contents of the 6TB LaCie 2big disappeared. I can still read (presumably, as the Finder lists files) the contents of the 4big (my Time Machine backup drive) but I've turned them all off to avoid any further corruption until this issue is fixed either by LaCie or Apple.

Even more strange, I just bought a new 6TB LaCie 2big in order to transfer what I can still access off the 4big. When I connected this drive, Disk Utility listed 2 RAID slices for it, one that appeared to belong to the 2big and one that appeared to belong to one of my other LaCie RAID drives.

This appears to point to something inherently broken in Mac OS X, I believe. I don't believe that any 3rd party software is installed to enable the LaCie drives to be read by Mac OS X so it isn't a problem with any LaCie software (I do have the "LaCie Desktop Manager" app installed, but I believe it only implements monitoring functions like the ability to change the RAID configuration).

Hi,

here my console log where you see that the OS is doing it or reacting on an inconsistance !

29.10.13 19:25:53.000 kernel[0]: hfs: unmount initiated on VIDEO_1TB on device disk6s3

29.10.13 19:25:54.040 Finder[2197]: CreateWithFileInfo failed to create URL with FSRef, falling back to blank icon.

29.10.13 19:25:54.040 Finder[2319]: CreateWithFileInfo failed to create URL with FSRef, falling back to blank icon.

29.10.13 19:25:54.113 iTunes[2492]: ApplePushService: APSConnection being used without a delegate queue

29.10.13 19:25:54.550 diskmanagementd[2497]: unmount blocked by dissenter PID=2492 (/Applications/iTunes.app/Contents/MacOS/iTunes) status=0x0000c010 log=unknown message=(null)

29.10.13 19:26:01.000 kernel[0]: hfs: Initializing the journal (joffset 0xe8e000 sz 0x2800000)...

29.10.13 19:26:01.000 kernel[0]: hfs: mounted MyBook on device disk3s2

29.10.13 19:26:01.272 mds[89]: (Normal) Volume: volume:0x7fa055055200 ********** Bootstrapped Creating a default store:3 SpotLoc:/Volumes/MyBook/.Spotlight-V100 SpotVerLoc:/Volumes/MyBook/.Spotlight-V100/Store-V1 occlude:0 /Volumes/MyBook

29.10.13 19:26:01.970 fseventsd[53]: could not open <</Volumes/MyBook/.fseventsd/fseventsd-uuid>> (No such file or directory)

29.10.13 19:26:01.974 fseventsd[53]: log dir: /Volumes/MyBook/.fseventsd getting new uuid: BCFCAADF-FF62-4141-ACB6-A044CAFBCF24

29.10.13 19:26:01.974 fseventsd[53]: disk logger: failed to open output file /Volumes/FATBOY500/.fseventsd/000000000f331e8e (No such file or directory). mount point /Volumes/FATBOY500/.fseventsd

29.10.13 19:26:01.974 fseventsd[53]: disk logger: failed to open output file /Volumes/FATBOY500/.fseventsd/000000000f331e8e (No such file or directory). mount point /Volumes/FATBOY500/.fseventsd

29.10.13 19:26:03.684 coreservicesd[37]: Received request to reset fmod watch. Latest received id is 23838845711203. Latest sent id is 23838845711203

29.10.13 19:26:03.684 coreservicesd[37]: Received request to reset fmod watch. Latest received id is 23838845711203. Latest sent id is 23838845711203

29.10.13 19:26:03.684 coreservicesd[37]: Received request to reset fmod watch. Latest received id is 23838845711203. Latest sent id is 23838845711203

29.10.13 19:26:03.684 coreservicesd[37]: Received request to reset fmod watch. Latest received id is 23838845711203. Latest sent id is 23838845711203

29.10.13 19:26:03.704 mds[89]: (Normal) Volume: volume:0x7fa051018800 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /private/var/tmp/MPWYVRPJ

29.10.13 19:26:04.000 kernel[0]: hfs: Initializing the journal (joffset 0x1d1c000 sz 0x5000000)...

29.10.13 19:26:04.000 kernel[0]: hfs: mounted MyBook on device disk6s2

29.10.13 19:26:04.250 mds[89]: (Normal) Volume: volume:0x7fa052833000 ********** Bootstrapped Creating a default store:3 SpotLoc:/Volumes/MyBook 1/.Spotlight-V100 SpotVerLoc:/Volumes/MyBook 1/.Spotlight-V100/Store-V1 occlude:0 /Volumes/MyBook 1

29.10.13 19:26:05.100 fseventsd[53]: could not open <</Volumes/MyBook 1/.fseventsd/fseventsd-uuid>> (No such file or directory)

29.10.13 19:26:05.100 fseventsd[53]: log dir: /Volumes/MyBook 1/.fseventsd getting new uuid: E90833D0-619E-4EF2-93DB-40923BF2DD88

29.10.13 19:26:05.299 mds[89]: (Normal) Volume: volume:0x7fa053916000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /private/var/tmp/MPJZCCNA

29.10.13 19:26:09.000 kernel[0]: Sandbox: mdworker(2551) deny file-read-data /BILDER/iPhoto Merge/Contents/PkgInfo

29.10.13 19:26:09.000 kernel[0]: Sandbox: mdworker(2551) deny file-read-data /BILDER/iPhoto Merge/Contents/PkgInfo

29.10.13 19:26:09.000 kernel[0]: Sandbox: mdworker(2551) deny file-read-data /BILDER/iPhoto Merge/Contents/PkgInfo

29.10.13 19:26:09.000 kernel[0]: Sandbox: mdworker(2551) deny file-read-data /BILDER/iPhoto Merge/Contents/PkgInfo

29.10.13 19:26:09.000 kernel[0]: Sandbox: mdworker(2551) deny file-read-data /BILDER/iPhoto Merge/Contents/PkgInfo

29.10.13 19:26:11.654 mds[89]: (Normal) Volume: volume:0x7fa052946800 ********** Bootstrapped Creating a default store:3 SpotLoc:/Volumes/EFI/.Spotlight-V100 SpotVerLoc:/Volumes/EFI/.Spotlight-V100/Store-V1 occlude:0 /Volumes/EFI

29.10.13 19:26:11.798 fseventsd[53]: could not open <</Volumes/EFI/.fseventsd/fseventsd-uuid>> (No such file or directory)

29.10.13 19:26:11.798 fseventsd[53]: log dir: /Volumes/EFI/.fseventsd getting new uuid: 3EE2F1B9-AA28-4EFA-97CA-FDCADE328774

29.10.13 19:26:11.845 mds[89]: (Normal) Volume: volume:0x7fa055053e00 ********** Bootstrapped Creating a default store:3 SpotLoc:/Volumes/EFI 1/.Spotlight-V100 SpotVerLoc:/Volumes/EFI 1/.Spotlight-V100/Store-V1 occlude:0 /Volumes/EFI 1

29.10.13 19:26:12.044 fseventsd[53]: could not open <</Volumes/EFI 1/.fseventsd/fseventsd-uuid>> (No such file or directory)

VIDEO_1TB destroyed to Mybook and EFI

FATBOY500 destroyed to Mybook and EFI

and... AUDIO_1TB is still save due to iTunes was running at that time :-)

Remark: All are single disks, no RAID.

Thanks Apple

i have a 2TB MyBook Studio that was config'd using RAID 1 via the WD Manager. i have not plugged it in at all since updating to 10.9 (due to reading these horror stories) so i should not (hoefully) have any data corruption until this is fixed. of course, i have tons of data on it that i need to access...

my question is this: since the 2 discs should be perfectly mirrored, could i pull one of them out and mount it via my adapter mounting kit, or drop them in a different enclosure? or had that WD manager "infected" the disks themselves? should i just sit tight and wait for Apple/WD to find a fix? i certainly don't want to force myself into a recovery scenario, so i'd rather wait unless someone has done what i proposed with good results. thanks everyone.

To work out a common cause seems to be very helpful.

Here is my complete story:

I upgrade my MacBook Pro on Saturday. Several external disks where connected. But no problem at all during update and afterwards. Before starting the upgrade process, I made a copy of the downloaded installer on a single external Lacie rugged disk without any raid configuration.

I connected the Lacie to my daughters iMac, made a copy of the installer to the desktop and started the upgrade process. I left the Lacie connected during the upgrade. Upgrade was fine, but afterwards the Lacie was killed => to partitions where shown: "MyBook" and "EFI". Both were empty. No problem, the Lacie was only filled with non critical data. On my daughters iMac no raid was configured. Another Lacie disk was also connected, but this disk was not affected. Because we used a WD disk with this iMac before, the WD Raid Manager and the WD Turbo driver were installed. All disk where connected via FW800.

=> to sum it up: no raid, WD software installed, one disk crashed

On Sunday suddenly my external drives connected with my MacBook Pro were killed: to partitions on each disk, both named "MyBook" and "EFI". Lost my time machine backup (no problem for me) and my photo storage (also no problem, because I made a fresh copy on a seperate external disk before).

One disk was a Lacie with only a single partition, the other a WD with two disks configured as raid 1 using the WD disk manager.

=> to sum it up: one disk with raid, WD software installed, two disks crashed

The raid was configured using the WD software. In this case the Mac OS does not know anything about the raid, because this is handled inside the enclosure. The mac os disk utility only shows one single disk.

After this mess, I got rid of the WD software on all my machines:

• the MacBook Pro runs with one WD disk (which is still configured a raid 1 inside) and one Lacie since removal without a problem
• the iMac runs with one Lacie since removal without a problem

From my point of view the WD software seems to be the guilty one. Why should a bug in the Mac OS disk controller software name a reconfigured disk "MyBook"?

Hello,

Same thing for me. I've got a WD myBook Studio 6TB in raid 1 and everything has just disappeared and renames itself "myBook"! I really hope apple or wd will find a way to recover our data I can't believe otherwise!

Hmm, I think we got at least some kind of response – the WD Drive Manager for Mac is gone from the WD downloads Page:

http://support.wdc.com/product/download.asp?groupid=114&lang=en

What about external Firewire (Time Machine) Backup HDs formated using only Disc Utility's Partitioning/formatting feature? I'm pretty sure I used GUID(sic)? I haven't gone Mavericks yet... Mostly 'cause I am a Maverick.... I only live on the "Bleeding Edge" when it come to serious" Security Updates".

this could either be good news or bad... hoping for the former!

I also have a WD myBook Studio 6TB. My data is still ok but my drive is acting strange as since updating to mavericks my drive is always spinning even when i turn my computer off. I just did a search to see if other people are having the same problem and i've found this very long forum thread. I've now double double backed my stuff up. My raid manager version number is 1.1.4. maybe looking for an update to make it stop spinning.

deltaguru Switzerland

Remark: All are single disks, no RAID.

It would be helpful if you would say WHAT external "NON RAID" setup you had

firewire/ thunderbolt?

how was it formatted?

what enclosure was used?

etc.

MiB67Hamburg Hamburg, Germany

to sum it up: no raid, WD software installed, one disk crashed

Thanks, helpful information there 😊

That surely is a firm indication of something seriously amiss with the former WD Drive Manager for Mac... On the other hand, as somebody has just suggested to me: this whole thing just might also be related to the controller chip and/or firmware in the external enclosures. Seeing it is not solely limited to WD and/or Raid. Just wondering.

But something completely different: has any one of you tried to get back your lost data via Datarescue 3 ( http://www.prosofteng.com/products/data_rescue.php)?

It has surely been of great help to me in the past, but I don't know if it is Mavericks compatible yet.

Just my 2 cents.