OS X Mavericks install - Corrupted Harddrive

I have the same issue and I am not able to switch back to my original OS. Everything is on the hard drive..

I'm going to SUE Apple for this!

Also having the problem. I have a back up, but not very recent and there are some very important files I need to save. Please someone help!

Same issue here. I thought it was my hard drive coincidentally going bad, but the chances of that are slim. Tried repairing the disk using disk utility, no joy. Next step, I'll boot using original DVD boot discs and then restore using most recent time machine backup.

This is exactly what has happened to me. All I do is upgrade to Mavrick and now it will only boot up my 30GB boot camp partition because my 700GB of mountain lion is now corrupt. This is crazy.

I found that booting in safe mode will allow me to access all of my files, and back up. Unfortunately I am going to have to do a clean wipe and restore from backup.

Same problem here. What a nightmare! So much for getting any other work done today.

av8tr SE US

I thought it was my hard drive coincidentally going bad, ..but the chances of that are slim.

How did you come to that conclusion against logic and lack of evidence?

data is data is data,......if a HD is "fated" to fail in writing data, it can and will do so.

😊

I tried to update to OSX Mavericks last night. At -43 minutes, Installation error came and said that hard drive is corrupted and need to backup my data.

I can't even re-install my old Mountain Lion on it.

NVRAM was cleaned and still couldn't restart in recovery mode. My MBP is useless now.

APPLE, YOU NEED TO TEST YOUR SOFTWARE BEFORE MAKING IT AVAILABLE TO THE PUBLIC.

JUST BECAUSE IT IS FREE, YOU PRODUCTS CAN'T BE BUGGY AND CAUSE END USERS TROUBLES .

you boot into safe mode y holding the shift key at start up right? My macbook wont even do that, it just boots up to my windows bootcamp if i hold shift or not when i restart. It really doesn't seem like I can do anything, even if I did just want to completely wipe the drive and start from scratch. If there was a way to access my HD and get some important files out and THEN wipe it down I would defintely do that. Ill be calling support soon if someone doesn't offer a solution, can't find much online :\

Worked for me by holding shift as soon as the start up chime starts, and holding it down until the apple logo and a spinning wheel/progress bar appears.

I didn't really come to a scientific conclusion... Just making a guess as to probability. It seems unlikely, though not impossible, that my hard drive decided to fail at the exact same moment that I decided to upgrade to mavericks. Then I found this thread and saw other people were having a similar, if not the same problem. It leads me to believe that if I decided not to upgrade, my computer would still be working today. Could be a coincidence; I think that's unlikely though. It seems to me something about the mavericks upgrade process somehow corrupted my HD.

I did CMD+OPTION+P+R four times to clear NVRAM, then CMD+R to boot in recovery mode.

It boots into safe mode but can't install new or my old Mountain lion.

I had backed up my data to an extrnal drive, so data loss is not an issue.

My disk is in read only mode and can't do anything with it.

Probably I will try to reformat it and install again.

It looks like APPLE released buggy Mavericks without putting into rigorous testing.

Shame on apple. They should replace my 2012 MBP with new one for free.

this happened on my mac air. it then gave me two options, a back arrow or an ok button. i clicked the back arrow hoping to just escape the install and avoid losing my data. instead, the back arrow instigated the install! i was shocked to find that after the install everything seems fine. no data lost and new os working. not sure why tho.....

Same issue here on my MacBook Pro. Seems to be a bug in the Mavericks upgrade process while it creates the partition with the installation files.

Back Arrow did not do the trick here...

Tried to repair the disk with diskutility which did not work. Mounting in target mode either....

at the moment running data rescue in the hope to be able to recover the data at least.