You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Hello everyone,
After repairing Bootcamp thanks to Loner T (i tested the next os x out).
I found the original size of my Machintosh HD partition. I was stupid enough to make the partition larger to the original size again.
Now Bootcamp is called Disk0s4. Could someone help me out?
MacBook Pro (Retina, 15-inch, Early 2013), OS X Mavericks (10.9.4), GHOSTING (and long shutdown issues)
Macbook Pro with Retina display (early 2013) / 500GB / i7(ivy bridge) / GeForce 650m
- OS X 10.9.4 and Windows 8.1 in bootcamp (the install disk is from windows 8.0)
I ran testdisk>photorec for just a few seconds to see if it came up with files and it did. The most were low res images, java stuff etc. (i guess from the windows programs) I saw a few images i put on there myself.
Please take a look at the following two links -
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
http://www.cgsecurity.org/wiki/Data_Recovery_Examples#Recovery_of_a_lost_and_dam aged_NTFS
The first link has screen shots that help quite a bit.
What am i looking for?
Using the step-by-step sec ion, you are looking for your Windows files. If you can identify the files, the Start/End/size information is what you need to record.
Once you have that, post it here for recording purposes.
Then the Windows 8.1 Automatic Repair can be tried.
Ok, i'll do that. It's analyzing now, i'll post the results once finished.
Thanks for you patience 🙂
You are doing the hard work, not I. We can do it slowly, and ensure that there is not data loss. 😉
( If the solution is very complicated i'm willing to do a clean Mavericks install and reinstall windows 8 through bootcamp)
It's currently analyzing, I think this will take a while.
My recommendation is to at least try a W8.1 repair. If it fails, what you are suggesting is the ultimate fallback. It is quite a bit of work.
One suggestion, since you have 2013 Mac, you may want to not use Bootcamp to install windows, but 8.1 supports EFI on newer macs. I have that installed on one of my machines, and it is far easier and does not have as many issues as the MBR implementation does. Resizing volume is also much simpler.
If all other options are exhausted in recovery, would you be willing to try the EFI path?
I would, but my install disk is Windows 8.0, is that a problem?
If i would reinstall mavericks (and later using a USB thumb drive, will erasing the harddrive and doing a clean install fix the issues?
(> scan is currently at 73%, it started at 68%)
Windows 8.0 should also have EFI support.
Please look at this link - http://forums.macrumors.com/showthread.php?t=1557919
Ok that's nice. I do see there are some problems After installing Windows i don't necessarily need to change any partition again so bootcamp is okay with me.
If i would reinstall mavericks (and later on windows with bootcamp or EFI) using a USB thumb drive, will erasing the harddrive and doing a clean install fix the issues?
The scan is at 78% right now. I posted a picture of the progress so far.
Yes, a clean install and then Bootcamp should fix your issue. EFI installation has some GPU/Audio issues depending on which specific Mac model you have.
If you do not want to look for deleted partitions via Testdisk, it can be abandoned. It depends on how much time and energy you have to spend on this. If you have a TM backup, a Command+r and restore before the changes will also get you up and running.
Ok, i don't have time machine but i have all of my video's, documents, music and pictures backed-up on an external harddrive.
Will windows accept the product key when i reinstall through EFI and Bootcamp?
(Scan is at 82%)
It should, but it should be verified. I have not run into issues with Windows and EFI for product keys.
Bootcamp doesn't work, again.
