Q: Mavericks corrupts external hard drive

Wow, so I read through 96 pages of different people stating various problems and solutions to this thread, to see if I could find a nugget that would help me fix my problem.  And I feel like most, if not all, of the solutions are speculative at best because Apple has not clearly stated that there is any issue with Mavericks regarding external hard drives no longer being detected.  I wish to add my descriptive problem to this graveyard, in hopes that someone out there sees the symptoms and can push me in the right direction.

My problem:  I have a Macbook Pro that had Mountain Lion OSX preinstalled, an external 1TB Toshiba USB HD, and an external 1TB WD USB HD, all worked great for well over a year.  Installed Mavericks a month ago, then suddenly both hard drives could no longer be detected after the upgrade.  However, if I plug either of these hard drives into my Windows 7 OS custom desktop machine, or even my Windows 7 HP laptop machine, I can both read/write to either the Toshiba hard drive or the Western Digital hard drive to this day (still works).  When I first got both of the hard drives over a year ago, I had formatted the Toshiba HD using my Macbook Pro (HFS), and I had formatted my WD HD using my Windows HP Laptop (NTFS).  I've tried to reset the System Management Controller (SMC) on my Macbook Pro, shutting down completely and restarting, and also ensuring power adapter is connected for power.  Both drives refuse to be detected since the Mavericks upgrade on my Macbook Pro on any of the USB ports on my laptop (I have two USB ports, one on each side of the laptop).  The USB cables are fine, the hard drives are fine as well (they function on two other machines).  This problem sounds like it is regardless of the hard drive manufacturer, and points to the Mavericks OS itself by Apple.  Perhaps I forgot to unmount them properly at some point in time, but I refuse to believe that my hard drives are actually unusable and "corrupted", and hope that Apple can submit an official fix for this problem that renders my backup solutions to be useless.

coffeebreath wrote:

…

Nov 12 10:58:54 kernel[0]: hfs_swap_BTNode: record #-1 invalid offset (0x0000)

Nov 12 10:58:54  kernel[0]: hfs: node=13216 fileID=4 volume=Backup001 device=/dev/disk4

Nov 12 10:58:54  kernel[0]: hfs: Runtime corruption detected on Backup001, fsck will be forced on next mount.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002d9 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 2260238336.

Nov 12 16:54:03 kernel[0]: disk3: device/channel is not attached.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002e4 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 1727528960.

Nov 12 16:54:03 kernel[0]: disk3: media is not present.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002e4 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 0.

Nov 12 16:54:03 kernel[0]: disk3: media is not present.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002e4 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 4000019382272.

Nov 12 16:54:03 kernel[0]: disk3: media is not present.

Nov 12 16:54:03 kernel[0]: CoreStorage::recover() PV 4D075818-755A-4A17-A270-5A55B5D2E483 from group "Backup001" (547C5767-6075-4522-8138-31976D157092) has been marked missing.

Nov 12 16:54:03 kernel[0]: disk3: memory allocation error.

Nov 12 16:54:03 kernel[0]: CoreStorage: terminating group "Backup001" (547C5767-6075-4522-8138-31976D157092) is BUSY

Nov 12 16:54:03  com.apple.kextd[21]: LVG changed

Nov 12 16:54:03  diskarbitrationd[30]: unable to repair /dev/disk3 (status code 0x00000008).

Nov 12 16:54:03  diskarbitrationd[30]: unable to mount /dev/disk3 (status code 0x00000001).

 

… This is the 3rd time OSX has corrupted the partition on this drive. …

What's logged was symptomatic of hardware problems – problems that can not be caused by the operating system.

Ok after looking hard at this issue and feeling frustrated at the discussion just being off topic a lot i need to ask this:

- I own the my book thunderbolt duo, does it effect this drive as well as the studio II?

- HOW do you remove the wd utilities fully from your mac hard drive, i just deleted the application and i don't think thats enough is it?

- I'm distraught! i researched the drive i should use and bought this after many being bought and sent back and now i find this?? this is DISGUSTING

- I don't know what to do, I am thinking of sending this drive back and getting a drobo?

- I also own Lacie prosche drives, external, 4tB as well and i read that THEY are also effected. ARE you joking? data safety is my primary concern!!! *** how do i   keep messing up!

- my data, if it is lost, it is the end of my life, trust me. I need HELP, i beg of you, anyone?

HOW do you remove all trace of the software? HOW? i cannot reformat, that is just not possible!

Add another sorry user to the list.

I waited a long time to install Mavericks to avoid any problems.

After installing it on my startup drive,

my external Seagate GoFlex 2TB hard drive with OS10.68 installed

suddenly quit mounting and is unrepairable even though it worked perfectly beforehand

and was tested and repaired multiple times before Mavericks was installed.

This hard drive damage issue seems to be much more than a coincidence

especially with so many instances reported, yet I still don't see any acknowledgement or solution from Apple.

I ran a recovery program and all my files seem to be there and undamaged but I can't get the disk to mount nor can I repair it.

What a mess.

Late to the party, but sounds like your disk has simply given up the ghost. Often updates and upgrades can be enough to tip a faulty or dying drive over the edge. If it needed to be repaired multiple times' as you say, then that is a good indication it was about to die. Buy a new external drive.

Pete

It didn't need to be repaired, it was checked for repairs (but no repairs were needed, and it was found to be in good shape) to make sure it was in good shape before I did the installation.

I repeated this process and checked all my disks multiple times in advance of the installation and everything was in tip top shape.  Check the comments and you'll see this same thing has happened to many, many people with healthy disks that suddenly went bad after installing Mavericks.

I'm suddenly having a similar issue.

I'm running a 1 TB My Book Studio Edition II with RAID 1 setting for timemachine on my 2008 iMac.

10.9.4 is my iOS version.

Timemachine was running without issue until approx 14 days ago, I was on work travel etc so now just looking at it, but basically the WD external is not mounting correctly, and Timemachine no longer works on it.

I'm nervous right now on the status of my external harddrive.

I do have another external harddrive that I clone, using Carbon Copy Cleaner and this one mounts ok and "appears" to be backing up my data correctly.

Similiar Corruption here on USB 3. external drive with installed 10.10 on it.

Previously had been running 10.9 on an HGST internal 1TB HD in my 2008 MBP for over a year.

Upgraded in-place to 10.10 on the 1TB HGST in the 08 MBP.  Ran fine for several days, no issues.

Pulled the drive from the 2008, placed it in an external USB 3.0 Go-flex enclosure i had lying around.

Tried to boot a new re-condition MBP Late 2012 i just received from Apple on-line using the external drive.  2012 MBP saw the boot

partitions correctly; Internally an untouched copy of 10.8 that came on the MBP from Apple, 2 boot parts on the external - recovery

and my 1TB personal drive on the HGST... MBP Tries to Boot.....  FAIL..

Now the 2012 MBP sees the external HGST as a Master Boot Record drive with no data or partitions on it.... WTH Apple.

I have a copy of my 10.9 OS that I'm going back to pronto.... No 10.10 at this School District - it's not safe at any speed.

RogerOut wrote:

 

blindeyetom wrote:

 

e2photo I would suggest don't update to Mavericks yet.  The issue is not just with WD software/Firmware, but with various interactions between Mavericks,

+1

 

And I owe you an apology for being so hard on you earlier in this thread.  I didn't realize the depth of this problem.  My fault and I'm sorry.

 

BTW, I think the early sign of OS driver problems began with 10.8.5, I can't let my machine sleep without the USB drives being ejected improperly, even though I have the supplemental update installed.

 

In addition, when I installed iTunes 11.1.3 over the weekend (so I could install iOS7 on my phone - DON'T get me started on that debacle) now I can't burn an audio disc in iTunes - "disc is in use by another program" error, even though nothing is using it. I can burn discs with Toast. Go figure. So I'm forced to update iTunes so I can install iOS7 and in turn, Apple breaks my cd burner.

 

Updates have become a joke in the past 2.5 years.

Evidently 10.8.5 is just as bad as Mavericks. It think the problem here is that Apple changed the sandbox policy for the OS, it now requires "Version 2" of the signing for apps. And it is more strict now.

The result is that some third party disk utilities that would normally load up during start-up and just work, now they get screwed up by Apple sandboxd so they only partially work or cause lots of problems. That's one theory.

And here is what my log logged like right when my Mac Pro decided to completely destroy the boot volume of my MacBook Pro, which was attached via external firewire target disk mode:

https://gist.github.com/gistya/6f8409a880fbe3e3741e

Graham Perrin wrote:

 

coffeebreath wrote:

…

Nov 12 10:58:54 kernel[0]: hfs_swap_BTNode: record #-1 invalid offset (0x0000)

Nov 12 10:58:54  kernel[0]: hfs: node=13216 fileID=4 volume=Backup001 device=/dev/disk4

Nov 12 10:58:54  kernel[0]: hfs: Runtime corruption detected on Backup001, fsck will be forced on next mount.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002d9 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 2260238336.

Nov 12 16:54:03 kernel[0]: disk3: device/channel is not attached.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002e4 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 1727528960.

Nov 12 16:54:03 kernel[0]: disk3: media is not present.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002e4 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 0.

Nov 12 16:54:03 kernel[0]: disk3: media is not present.

Nov 12 16:54:03 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002e4 detected for LVG "Backup001" (547C5767-6075-4522-8138-31976D157092), pv 4D075818-755A-4A17-A270-5A55B5D2E483, near LV byte offset = 4000019382272.

Nov 12 16:54:03 kernel[0]: disk3: media is not present.

Nov 12 16:54:03 kernel[0]: CoreStorage::recover() PV 4D075818-755A-4A17-A270-5A55B5D2E483 from group "Backup001" (547C5767-6075-4522-8138-31976D157092) has been marked missing.

Nov 12 16:54:03 kernel[0]: disk3: memory allocation error.

Nov 12 16:54:03 kernel[0]: CoreStorage: terminating group "Backup001" (547C5767-6075-4522-8138-31976D157092) is BUSY

Nov 12 16:54:03  com.apple.kextd[21]: LVG changed

Nov 12 16:54:03  diskarbitrationd[30]: unable to repair /dev/disk3 (status code 0x00000008).

Nov 12 16:54:03  diskarbitrationd[30]: unable to mount /dev/disk3 (status code 0x00000001).

 

… This is the 3rd time OSX has corrupted the partition on this drive. …

 

What's logged was symptomatic of hardware problems – problems that can not be caused by the operating system.

You're wrong. The OS can *think* it's seeing hardware problems when really it's a bug in the driver. The logs reflect what the OS *thinks* it's seeing. A bug in the drivers can certainly cause this problem.

This is a serious problem and I have had Mavericks delete a hard drive on me once already. Which was why I am still on 10.8.5. Apple does not seem to care anymore about its users or making sure these problems get fixed.

If they cared then they would read these forums and respond to us here and let us know they are working on these problems.

Strangely right when I typed that my hard drive randomly mounted.

11/4/14 5:32:38.389 PM coreservicesd[118]: Application App:"Finder" [ 0x0/0x37037]  @ 0x0x7fbbd5d15100 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x440440:) ), so denying.

11/4/14 5:32:38.389 PM WindowServer[137]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0x37037, securitySessionID=0x186a6, err=-13066

11/4/14 5:43:06.000 PM kernel[0]: Sandbox: sandboxd(5764) deny mach-lookup com.apple.coresymbolicationd

11/4/14 5:49:56.183 PM diskarbitrationd[18]: unable to repair /dev/disk8s2 (status code 0x00000008).

11/4/14 5:49:56.550 PM PGP Engine[347]: Processing disk8

Why would Finder not be in the fPermittedFrontASNs? Why would sandboxd be blocking com.apple.coresymbolicationd? Why would diskarbitrationd have been trying to repair my disk? I don't get it. It's like it marks the disk as damaged and then won't let it be mountable until it thinks it can fix it?

Unforunately I ran into this problem yesterday on my 5K iMac with Yosemite...I had two WD ext drives connected via daisy chain, one used for TM and the other for storage.

They never had an issue when I was in Mavericks so I didn't realize this issue.

Last night when I turned on my iMac the two drives showed as Mybook on desktop and there's nothing in it. There was also an unknown drive mounted as "EFI" on the desktop.

Now I am running rescue software on the storage drive...what a crap

How can I make sure the WD software is removed from my system?? I ran the uninstaller but still can see there's wdhelper in the activity monitor

wdhelper is part of the Operating System and nothing to do with Western Digital. Do not try to remove it.

Cheers

Pete

Thanks Pete.

Is there no other way to recover the data other than running rescue software? I lost all the file names of my data and it's painstaking to sort them out...