Boot camp lost after upgrading to Yosemite from mountain lion

Loner T wrote:

Eugeniu_K wrote:

Did you had a chance to review the output above?

Apologies. Did not get a chance to look. The NTFS header is missing. If you can provide a brief set of events before you got into this situation, it may help suggest a path forward.

Testdisk (http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step) has proven very handy in the past, but a bit of forensics would be very illuminating.

There was nothing specific or different from the others here that had the same problem...

Just updated the OS to the latest Yosemite and it did broke my NTFS partition for Windows 7. I see the same picture as in the first post (disk0s4)

Didn't do anything with it except the outputs you asked...

I don't have experience in using TestDisk, and I really don't want to mess the things up even more... still hope there is a way to recover the NTFS boot option for Win7 😟

Were there any partition resizing done prior to the Yosemite upgrade?

Testdisk is a read-only utility (unless you choose to modify any partition information). It i used to locate NTFS partitions whose headers may be 'lost' or accidentally overwritten.

GPT Fdisk is used to re-write partition tables (no data changes).

You may be able to recover Windows if Testdisk can locate NTFS headers. It is a slow disk scan process to locate NTFS headers.

Loner T wrote:

Were there any partition resizing done prior to the Yosemite upgrade?

Testdisk is a read-only utility (unless you choose to modify any partition information). It i used to locate NTFS partitions whose headers may be 'lost' or accidentally overwritten.

GPT Fdisk is used to re-write partition tables (no data changes).

You may be able to recover Windows if Testdisk can locate NTFS headers. It is a slow disk scan process to locate NTFS headers.

Prior to Yosemite upgrade, there were two partitions: one for Mac and one for Windows, created more than three years ago... didn't make any resizing since then.

I was using the Windows partition most of the time.

What should I do next to locate the headers and re-write partition tables?

If you have downloaded Testdisk, and unzipped it in a specific directory, you can start it in OS X Terminal (you need to be in the directory where the testdisk binary is located) by

sudo ./testdisk /dev/rdisk0

Select EFI/GPT and run a Quick Search. Use the MS Data partition (which is your current partition) and run a Deeper Search.

This solved my problem as well! Million thanks, Loner T! Your help is truly appreciated!

Here is the result of Quick Search, which MS Data partition should I choose to continue?

Assuming the eFI entry is numbered 1, pick 4 and 5 and look inside using 'P - list files'.

Please do not use left/right arrow/cursor keys because it changes the partitions, and you want avoid making any changes via Testdisk.

Here is 4:

and 5:

Loner T wrote:

Assuming the eFI entry is numbered 1, pick 4 and 5 and look inside using 'P - list files'.

Please do not use left/right arrow/cursor keys because it changes the partitions, and you want avoid making any changes via Testdisk.

From the post above, looks like the line 4 is the one I need to recover, as it contains the Windows files.

Should I use the Right/Left arrows now to change its status from Deleted to Primary?

Do not use left/right arrow/cursor keys. They are valid on a PC, not a Mac. Do you see a System Volume Information entry in "4"?

Loner T wrote:

Do not use left/right arrow/cursor keys. They are valid on a PC, not a Mac. Do you see a System Volume Information entry in "4"?

This is what I see in "4"

What do you mean by "System Volume Information" entry? how does it look like?

This is what it should look like.

Loner T wrote:

This is what it should look like.

Found that in "16":

Here it is:

what should I do with it now? how to launch Gdisk?

The 6174 sector entry is too small to contain Windows. In '4' were there any additional files listed? You should have quite a few files which are Windows-related. Can you also check '5'?

Loner T

The 6174 sector entry is too small to contain Windows. In '4' were there any additional files listed? You should have quite a few files which are Windows-related. Can you also check '5'?

Here is 4:

and 5: