Installed Mavericks and now my system partition needs repair

see what I got this morning, shame to WD

Dear WD Registered Customer,

As a valued WD customer we want to make you aware of new reports of Western Digital and other external HDD products experiencing data loss when updating to Apple's OS X Mavericks (10.9). WD is urgently investigating these reports and the possible connection to the WD Drive Manager, WD Raid Manager and WD SmartWare software applications. Until the issue is understood and the cause identified, WD strongly urges our customers to uninstall these software applications before updating to OS X Mavericks (10.9), or delay upgrading. If you have already upgraded to Mavericks, WD recommends that you remove these applications and restart your computer.

The WD Drive Manager, WD Raid Manager, and WD SmartWare software applications are not new and have been available from WD for many years, however solely as a precaution WD has removed these applications from our website as we investigate this issue. .

Sincerely,
Western Digital

I have the same error ""The partition map needs to be repaired because there's a problem with the EFI system partition's file system". When I attempt to repair the partition, I receive an alert that: "Live file system repair is not supported"."

I had a failed Bootcamp install, so I had to remove the bootcamp partition. I made the mistake of TRYING to remove the partion in Recovery & Disk Utility. I have done this dozens of time before using Moutain Lion, but this time (Mavericks) it failed.

I am (shockingly) still able to boot into windows, and was able to use Boot Camp Assistant to install a clean Windows 7. However, I STILL HAVE the "EFI" error.

Will I have to totally re-format my drive, and start ALL OVER fear both my Mavericks install, and my Windows 7 Install? THAT will not be fun. Even with a Time Machine backup. And, after reading other posts, I fear that if I try to reformat my drive, it will become unsable.

This is on a 1TB SSD, in a Late 2013 MacBookPro Retina. So, I can't take the drive out and mount in another (non Mavericks) computer.

The issue isn't specific to Western Digital. In my case, the affected storage device was a Seagate Barracuda, and no user-space storage management applications were involved.

It's interesting to note that the issue occurs with both HDD and SSD. This is a pretty strong suggestion that the problem is at the OS level, not the hardware level.

Yup, installed 10.9 on a 2008 3,1 17" MBP, in three days wouldn't wake up from sleep. Booted up in single user mode, ran applejack, no joy. Had to restore from time machine ext hd. Now another three days has passed and now almost complete system freeze. Only cursor is responsive. Had console open, nothing but "kernel : disk0: I/O error", whole window full. But last line before freeze, "syslogd,[19] unable to quarantine: 5". Dock is frozen with me trying to quit Firefox 25. Time to SMC reset or applejack. Ok SMC reset, rebooting forever.....still waiting...fans blasting at full.....still waiting......dang it, no hd! Again! Don't think it's the seagate hybrid drive. Trying applejack in single user mode...no joy, keep getti circle with line thru it

Recovery time, again. :-(

Posted from iPad mini, since MBP is in deep sheet.

Oh yeah, disk utility says "invalid content in journal". Trying to repair disk...again, disk utility can't repair disk, restore your backed up files". Ouch. Blah, should've waited for 10.9.9.

Same here. Nothing works anymore. No help from SMC, PRAM or safe boot.

Before the crash the system became very sluggish. Files started to be missing and it seems that Mavericks started to "destory" itself. Documents, Apps, images, etc. All started to delete itself.

Many people reported a similar "self-deletion" with external harddrives. Look here:

https://discussions.apple.com/thread/5475136?start=0&tstart=0

⚠If you have a RAID setup, data corruption is possible. Exact source determination has not been made yet.

Until there is resolution,... keep all RAID setups unconnected and consider other means for backup, such as simplex USB non-RAID backup.

see here:

https://discussions.apple.com/thread/5475136

The simple issue currently are that with Mavericks, Thunderbolt and FIrewire drives are not sleeping, ...this perpetual on-time can cause overheating,......as said, keep them unconnected unless in direct use.

WD is telling its customers to REMOVE WD SOFTWARE especially on WD MyBook

If you hav a WD with WD software, or a WD MyBook,...keep your WD MY BOOK unconnected right now until a resolution unless you have a backup of ALL DATA on your MyBook stored elsewhere

http://community.wd.com/t5/External-Drives-for-Mac/bd-p/passport_mac

Bill_S

Community Manager WESTERN DIGITAL

External Drives for Mac Experiencing Data Loss with Maverick OS (10/30/13)

There are reports of Western Digital and other external HDD products experiencing data loss when updating to Apple's OS X Mavericks (10.9). Western Digital is urgently investigating these reports and the possible connection to the WD Drive Manager, WD Raid Manager and WD SmartWare software applications.

Until the issue is understood and the cause identified, WD strongly urges our customers to uninstall these software applications on their systems before updating to OS X Mavericks (10.9), or delay upgrading. If you have already upgraded to Mavericks, WD recommends that you remove these applications and restart your computer. WD has removed these software applications from our web site solely as a precaution as we investigate this issue.

Peace

It has nothing to do with RAID, Thunderbolt or Firewire!!!!

I have an 2.5 internal Western Digital harddrive. So no Western Digital software, no thunderbolt, no USB drive, no RAID, no Firewire ... and yet Mavericks ate up my internal harddrive. It started to remove files until it crashed. No boot possible. Disk Utility says that disk need to be formatted.

ishouldknow

It has nothing to do with RAID, Thunderbolt or Firewire

I didnt post ALL the information in the above, rather on the thread link in the post.

Actually it has "almost everything to do with RAID".

I never claimed conventional were not affected, however your frustration is misplaced against myself.

Yes, I know all about this issue more than you realize, so your warning is misdirected.

ishouldknow

Before the crash the system became very sluggish

Actually on your internal HD, there is no indication the occurrence in the thread mentioned has anything to do with your HD crash.

Nobody is reporting ANY HD (external or internal) crash as per this problem, nor any internal HD being wiped, ....yours is merely, by all indication, a mere HD crash.

Peace. 😊

ok

Sharing "the rest of my story" in case others face something similar.

After my "EFI" error, I tried to change the size of my mac hard drive in Disk Utility (as always, booted from Recovery". It destroyed by Bootcamp partition, and my Mac partition. SO.....I tried to reformat and fully re-partition the drive. That failed. Apple support asked me to do a clean install (from online) of Mavericks, which I did. OS did install, but I still get the EFI error, and can still not chang my parition (without again destroying the contents). SMC, PRAM did nothing.

Apple is sending me a new computer. They think it is related to my 1TB SSD drive in my Late 2013 Retina MacBook Pro 15". So...this problem will become Apples problem.

I must say, Apple has the best customer service techs in the business ! ! (I had an unrelated call to Microsoft this week, and they proved to me why they are suffering as a company. My 5-year-old niece knows more about computers, and speaks better english, than Microsoft tech's do!)

I would suggest ONLY using Boot Camp Assistant, and NOT changning your own partition size until patches are released to address this issue with the 1TB SSD drive.

to uninstall WD software:

http://wdc.custhelp.com/app/answers/detail/a_id/11005/session/L3RpbWUvMTM4MzQ1Nj MwOC9zaWQvRVY3ZXZvRWw%3D

Update... Had to dump hd, nothing got it to work, I/O error so bad nothing can reset/access/erase the hd.

Luckily I had another empty hd to restore to. Now I'm back on track, one hard drive short though. Can't wait for 10.9.1, if that one doesn't destroy my hd. Journaling failed, as worse as the 10.4.8 prebinding prob. sheesh, I thought only NTFS/FAT32 had these probs. :-o

Indeed, it has nothing to do with RAID or Firewire, because my hard drive wasn't in a raid or a FireWire drive and it just happened to me, out of the blue.

All was going fine, suddenly my computer made a loud buzzing sound, and froze. I had to force an extinction. I rebooted in Recovery mode as I always do after a major problem like this, only to be faced with this message... hence my presence here (using another computer)

*** Update and solution ***

After browsing the web and reading a few threads, I solved the problem, at least on my computer.

Resetting the PMC didn't work for me.

Here's what I did, in minute details to help those who feel uneasy :

1. You will need an 8 GB USB flash drive, the OS X Mavericks installer file (you can redownload it from the App Store if you haven't kept a local copy), DiskMaker X. All this on another Mac you'll have to temporarily borrow to create a USB-based Mavericks Installer.
2. Using DiskMaker X, create a USB-based Mavericks Installer on the 8 GB USB flash drive, following the simple instructions. Aside from having to tell DiskMaker X where is the USB flash drive you want to use and where is the OS X Mavericks installer file (if it isn't on the Mac's boot partition), you don't have anything else to do except to wait for your USB-based Mavericks Installer to be ready.
3. Insert your USB flash drive (containing the Mavericks Installer) in a USB port of the problematic Mac.
4. While keeping the option (alt) key depressed, restart your Mac and keep the key pressed until you see an array of possible startup disks on screen.
5. Select the USB flash drive (containing the Mavericks Installer) in the list, and click on the arrow underneath to launch the Mac from the USB flash drive
6. You will be greeted with the usual Recovery disk interface
7. Select Disk Utility in the list
8. Select the problematic drive (and not the partitions on that drive) in Disk Utility
9. Select repair (for me, everything was repaired and was just fine at this point)
10. Select repair again and repeat until no further repairs are necessary
11. Check the partitions, to be sure.
12. Quit Disk Utility
13. In the Apple Menu, select Startup disk
14. Select your usual startup disk on your Mac (the one that was broken) and restart
15. When you hear the chime, you can remove the USB key
16. To be sure, I restarted again in Recovery Mode (Command-R), but this time from the main drive, and everything was fine in Disk Utility
17. Restart your Mac normally and be happy.
18. Make a backup of all your file immediately afterwards, just in case this is an impending doom warning...