How can a Windows partition be resized after Windows is installed?
"You need to delete the Windows partition using the Boot Camp Assistant, and start over to change the size of the Windows partition. Back up your important Windows files first."
Anyone who goes to Disk Utility to resize their OS X partition to create free space, and then goes to Windows to resize the Windows volume using that newly created free space will find that Windows vanishes upon any major OS X upgrade. This happens with 10.7, 10.8 and 10.9.
When doing the resize this way, the Windows utility only updates the MBR partition map, not the GPT. When the installer scripts find the GPT and MBR aren't in sync'd it wipes out the correct MBR and replaces it with the wrong GPT information, causing Windows to vanish.
Because the necessary information to find Windows is only in the MBR, when resizing in this manner, once it's replaced during the OS X upgrade process the information is lost and it becomes a major data rescue operation to get it back.
So if you want to prevent it, you need to fix the GPT before you start the OS X upgrade. There are no GUI tools to fix this. Apple's tools always defer to the GPT. It's much, much easier to fix this before starting the OS X upgrade.
Always have been a silent reader, so first time post here. I have a MBP (15" Late 2011) at home that me and my wife share (I use mac, while she uses windows 7 sp1).
Now to the point. I had created three partitions (For 512gb drive) as below:
step1: Created a bootcamp partition of 80GB
step2: Shrinked OSX partition to 256 gb using disk utility
step3: Created a 170gb partition using disk utility and formatted to exFat
step4: Installed windows 7 on bootcamp partition
Now, before I update to Maverick, I'm trying to make sure that the Bootcamp partition remains usable. After all, the wify uses it, and had it been crashed, it'll be kinda life risk!
So, I need the expert's advise for this, whether it is safe for me to update or not. For your clearer understanding here are the output of two commands mentioned above:
sudo fdisk /dev/rdisk0
Disk: /dev/rdisk0 geometry: 60801/255/63 [976773168 sectors]
Signature: 0xAA55
Starting Ending
#: 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 - 488281248] HFS+
3: 07 1023 254 63 - 1023 254 63 [ 488953856 - 331571200] HPFS/QNX/AUX
*4: 07 1023 254 63 - 1023 254 63 [ 820525056 - 156248064] HPFS/QNX/AUX
gpt -r -vv show /dev/rdisk0
gpt show: /dev/rdisk0: mediasize=500107862016; sectorsize=512; blocks=976773168
gpt show: /dev/rdisk0: Suspicious MBR at sector 0
gpt show: /dev/rdisk0: Pri GPT at sector 1
gpt show: /dev/rdisk0: Sec GPT at sector 976773167
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 488281248 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
488690888 262968
488953856 331571200 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
820525056 156248064 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
976773120 15
976773135 32 Sec GPT table
976773167 1 Sec GPT header
Many many thanks for your time reading this.
P.S. I'm not a computer noob
, but new to this scene. So, don't want to take risks w/o pre-cautions. Thanks.
