Mavericks corrupts external hard drive

No WD external drives (or another other for that matter), just the LaCie's.

idontknownousername

That's interesting – and there is no WD external drive involved in your case?

I indicated to you from the beginning that while WD build-quality on consumer HD is low,......a "hard drive is a hard drive"

All HD,...... WD, Seagate, Toshiba, Hitachi, are all just mechanical bricks. There are only 4 conventional HD mfg. on earth.

The issue here is 1. RAID, .....2. control software (if this is any case at all),.... and a 'minor' issuewith 3. Firewire and Thunderbolt (firmware / SATA bridge?) as manifesting in 'sleep issues',...........

....all 3 of which aspects manifested after 10.9 OS update.

Peace 😊

Plot, have you lost any data?

I have just another example of the update to OS X 10.9 causing hard drives to be displayed as empty.

Update completed on the MacBook Pro without problem but after restarting 4 hard drives where first renamed as 'EFI' and then renamed as 'mybook'.

1 drive was a WD MyBook connected via firewire. 2 where Samsung s2 portables, and 1 was a Seagate. These were connected via USB.

I've copied all system logs from the period it happened which was over a few minutes.

Guy i just figured out how to fix my problem!!! 🙂 🙂 🙂

My problem was that my WD myPassport did not mount. After spending 20 + hours using Data Rescue it got my data but all the names were gone and stuff.

So my drive would show up in disk utility but would not mount. Here is what you do: Right click the HD and click unlock drive. Then enter your password. My Drive appears in finder with all files in tact!! Hope this helps some people

Hi, I just tried what you suggested, but "Unlock Drive" does not appear as an option either in Disk Utility or the Finder when you right click on the drive. Can you be a bit more specific where you found that option? Thanks.

Mine didn't show up in finder but it showed up is disk utility as Not mounted. Right click then unlock drive and enter password. Only works if your drive is password protected and is not mounting.

coops17

Pardon, but password protected HD unlocking is not the issue at all this thread.

Peace. 😊

I was brought to this forum because my hardrive didn't show up and shows empty because of my upgrade to mavericks. I just posted to try and help people that were maybe in the same boat as me. As for the myBook portion of the thread mine has worked perfectly since the update. I never used RAID or any WD managing software. Hope this helps.

My Passport for Mac 1TB shows up but Time Machine gets stuck "preparing backup" and I can only eject by "force eject" after Mavericks upgrade.

yes USB connected drives are also borked by this Apple/WD debacle

ds3372

My Passport for Mac 1TB shows up but Time Machine gets stuck "preparing backup"

Actually thats perfectly normal, most everyone has undergone the same thing.

After new OS install, time machine has to sort thru endless 1000s of files before it starts to backup.

A quick way around this is if you have another HD, you can make a NEW Time Machine backup,...will only take then a hour or so instead of endless hours (sometimes 20+ hours)

No I haven't used any WD software in many years. They were just sitting in my App folder.

I might add here as well. I have similar issues. I use two WD MyBook external drives which I created a raid 0 in Mountain Lion's disk utility. After Mavericks install I'm unable to mount the raid partition even though it is recognized in disk utility and the raid is "online". I have never used any third party tools or drivers.

This is the log:

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 tried downgrading to Mountain Lion but the same issue persists so the disks are already corrupted even though they have never been mounted.

I don't know what to do. Wait for a fix from Apple, try to repair with "first aid" or some third party tool but if the file names gets screwed up most of the data is wasted anyway...

Here is a way to force the GPT disk index to refresh itself. It was used to correct disk problems in the past, so could work here too.

https://discussions.apple.com/thread/5468359?answerId=23515858022#23515858022