I reread again and agan...the answer is just push 'enter' tab.
Thanks God, Finally. I got my windows OS back normally
But...still have litle problem.
Why in windows OS I can not see my dATA folder (MAC2, I plan use it as my share folder, so I can read, and edit both from Mac OS and Windows OS)
How is it? Is it because type format of my partition is wrong (I format it with 'MAC OS Extended, journalized')?
If you redo the hybrid MBR and add partitions 4 and 5, accept default partition type, make only 5 bootable, then you will have access to whatever partition 4 is from within Windows again. I assume partition 4 is the data partition.
There is no safe way of having access to the original OS X partition as well. You can add partitions 2 4 5 to have access to both HFS+ partitions and Windows, but MBR cannot hold more than four entries. Which means you can't protect partition 3, there is no room in the MBR for it. So from the Windows perspective partition 3 will look like free space. If that's an OK risk for you to take, then create a hybrid MBR by adding partitions 2 4 5.
But this exemplifies why it is a bad idea to be making additional partitions on your boot drives. There's really no good reason for an additional HFS+ partition, where an additional folder would have done the same job just fine.
my problem is connected to topic Mountain Lion upgrade from Snow Leopard but it is connected to another partition created in Boot Camp in the past. I would like to ask you for help, I don't know how to solve my problem.
I have Macbook Pro 13 year 2011 (2.66 GHz version). When I started using it I have installed Boot Camp because I often switching to Windows. I have also created not just Boot Camp partition but another partition for data. So in Windows 7 there was C: for system and D: for data. From my previous experiences I have used D: for my all data. Now I have upgraded Snow Leopard to Mountain Lion. Everything was fine, also Boot Camp is working. But I have different problem as many users here in discussions which didn't see Boot Camp or cannot boot Boot Camp Windows after Mountain Lion upgrade. My situation is that "D:" partition disappeared. I really don't know what to do and it is very important for me to have this data back. Please could you help me? Is there chance to have my data on D: partition back? I really don't know why I didn't make backup before but I thought that it will be just upgrade in Mac partition from Snow Leopard to Mointain Lion but I have this problem...
I have had 85 GB for Mac, 100 GB for Boot Camp (C:) and the rest 133 GB for my data partition in Windows - D: before. Now there is situation where Windows Disk Management show 217,77 MB for Boot Camp but Properties in Windows Explorer for C: shows 100 GB like before. But there is no D partition. It seems that data are there but I don't know where. (please see attached pictures)
I have used parameters in terminal regarding your instruction in previous posts.
Please help me how to see again "D:" in Boot Camp Windows. Thank you
Michal-MacBook-Pro:~ Michal$ sudo gpt -r -vv show disk0
gpt show: disk0: mediasize=320072933376; sectorsize=512; blocks=625142448
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 625142447
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 166766768 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
167176408 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
168445952 456695808 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
625142415 32 Sec GPT table
625142447 1 Sec GPT header
Michal-MacBook-Pro:~ Michal$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 38913/255/63 [625142448 sectors]
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 166766768] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 167176408 - 1269544] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 168445952 - 456695808] HPFS/QNX/AUX
Michal-MacBook-Pro:~ Michal$ diskutil list
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Mac HD 85.4 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data BOOTCAMP 233.8 GB disk0s4
How did you originally create the two Windows partitions? Did you split Boot Camp into two from Windows or in Disk Utility?
If you had done it in Disk Utility, the GPT and MBR would have entries for two Microsoft Basic Data partitions. And the Mountain Lion installer should have simply refused to create a Recovery HD partition.
But I think you made the Windows data partition from Windows, which would only have updated the MBR, not the GPT. And OS X tends to honor the GPT as primary, which is a huge problem in cases where the MBR and GPT don't agree. There's some evidence that when OS X is upgraded, the MBR is being overwritten with the GPT partition layout, but since I haven't reproduced this myself I don't know exactly what does it or under what circumstances. But it's consistent with the problem you're having. The GPT partition scheme appears to have been used to replace the MBR, because what you're reporting to me the GPT and MBR contain the same information. And you have a Darwin Boot partition, which you shouldn't have if you already had four partitions in the GPT and MBR.
So I think you created the Windows data partition in Windows, which updated the MBR but not the GPT. The OS X installer sees the GPT has only three entries, adds one for Darwin Boot, assumes you still have the original sized Boot Camp partition and replaces the MBR.
So now your MBR reports the combination of Windows C: and D: which is why D: doesn't show up. The NTFS file system is still only 100GB, it has not be expanded. Basically it's a 100GB volume inside a 217GB partition.
There might be a way to use the total bytes "Capacity" in the Windows screen shot to figure out how to reconstruct an MBR for exactly the right number of sectors for C: and D: and get back D:. But I don't know how to do that, only guess how to do that. So if the data is really important you'll have to pay for data recovery from a data recovery service like Drive Savers. Maybe you show them this thread and this answer and they can give you a discount because it should be really easy for a data recovery service more familiar with NTFS than I am, to figure out the original MBR.
Basically this is Apple's mistake. They should not allow any partition modification of either MBR or GPT once a hybrid MBR has been created. They should only allow a user to change the partition map with a total reformat/reparition of the disk (start entirely from scratch). They even have a technote that says such disks should not be manipulated at risk of data loss, but sure enough Disk Utility manipulates such disks and routinely I see data loss, like yours, is the result.
Thank you Christopher for answer. So there is a chance to have my data back.
I have created the windows data partition in past, but I think the steps were:
- I have created Boot Camp partition with Windows 7 installation. Then I have shrink Mac partition to approx 85 GB and the rest formatted in Windows to have Windows data (D:) NTFS partition.
Do you have also any suggestion to use recovery software? Like GetDataBack for NTFS. Or this solution is not so reliable like to find NTFS expert company for data recovery?
It there also any way how to create backup of harddrive with exactly the same structure? When I will have backup of whole hardrive I can experiment with recovery software.
The most exact copy of a partition or disk is a sector copy. I use the command lind program dd to do that. Obviously you need a 2nd drive that has enough free space to hold the entire partition or drive disk image that will be created. And you need to make sure that the partition you're imaging isn't mounted. Which means if you're going to image the whole drive, you can't boot of that drive, you have to boot off something else.
The basic form of dd is
dd if=/dev/diskXsY of=/path/to/file.iso bs=256k
X=the disk device number
Y=the partition number
You can get that information 'from diskutil list'. And if you want to image the whole drive just use /dev/diskX as the if= value.
Disk Utility can also do sector copies but I can't always tell from the GUI when it's doing a sector copy or file copy. And it's slow, I think it's using 4KB block sizes, whereas with dd you can specify. A block size of 256k as I'm using above makes the process go a lot faster.
Just an FYI for those people who have tried to recover Windows by repairing/recreating their hybrid MBR using gdisk, only to find their Windows volume visible but corrupt and unrepairable. This is a last ditch effort, if the disk contains critical information you should have backups. If you don't have backups, I'll argue the data is not that important. If you argue back that it is, then I suggest professional data recovery. That price tag will make you more serious about backing up, I think.
For everyone else, once you have a sector backup (you can use something like
sudo dd if=/dev/diskX of=/dev/diskY
X= number of source disk
Y= number of destination disk
Note this will obliterate data on the Y disk, make sure you get it right from 'diskutil list'. The numbers aren't guaranteed to be the same between reboots. You can also read on variations of dd that include partition copies, as well as disk or partition copies to a file rather than to a whole disk.
OK finally, the last ditch effort is TestDisk. I just read about it as a suggestion, for another last ditch effort, by the maker of GPT fdisk (a.k.a. gdisk) on another forum. I haven't used it. But it looks like it might be able to recover from a case where the Windows volume was resized in Windows, which of course only updates the MBR, and corrupts the GPT. And then later, the MBR is getting nuked (corrupt in a crash, or replaced with a protective or new hybrid MBR in the course of an OS X upgrade) - resulting in the only bit of information on the disk that indicates the location of the Windows/Boot Camp volume being likewise nuked (bad Apple!).
So again, it's a specific use case. Most everyone else is best off making repairs of the GPT and MBR. Everyone is even better off with backups!