- Joined
- Jan 12, 2011
- Messages
- 4
- Mac
- Classic Mac
- Mobile Phone
[size=+2]Short Story:[/size]
After resizing partitions on my I've ended up with a GPT table that is out of sync with the MBR. Is there any way to sync the GPT with the MBR and not the other way around (like gptsync)? I've looked into gdisk and the f recovery command, but it seems to suggest deleting partitions
[size=+2]Long Story:[/size]
I originally had my hard drive partitioned with Windows 7 partition owning 250GB while OS X owned the rest. However, as I got more into PC gaming I decided to resize the partitions to grant Windows 7 more space. Considering that I didn't own an external hard drive large enough to back up my windows partition, I decided to truncate my OS X partition with GParted and grow my Windows partition within Windows 7 itself (because GParted gave me a warning that moving the partition within Linux would cause boot errors). I was able to expand the Windows 7 partition within windows and everything seemed to be hunky dory (I even added a considerable amount of data to this newly expanded partition). Upon rebooting a few days later, I found that the Windows 7 partition no longer booted. I realize now that modifying the partition within windows was probably a big mistake as windows only read the MBR (and thus the GPT partition table was left unchanged). Now the GPT displays this:
While the MBR displays this:
The GPT thinks that there is a bunch of unallocated space, when in reality Windows 7 is already using this "unallocated" space. Is there any safe way to sync the GPT table with the MBR table?
After resizing partitions on my I've ended up with a GPT table that is out of sync with the MBR. Is there any way to sync the GPT with the MBR and not the other way around (like gptsync)? I've looked into gdisk and the f recovery command, but it seems to suggest deleting partitions
(I'd like to keep the data on both partitions in-tact if at all possible)Warning! This will destroy the currently defined partitions! Proceed?
[size=+2]Long Story:[/size]
I originally had my hard drive partitioned with Windows 7 partition owning 250GB while OS X owned the rest. However, as I got more into PC gaming I decided to resize the partitions to grant Windows 7 more space. Considering that I didn't own an external hard drive large enough to back up my windows partition, I decided to truncate my OS X partition with GParted and grow my Windows partition within Windows 7 itself (because GParted gave me a warning that moving the partition within Linux would cause boot errors). I was able to expand the Windows 7 partition within windows and everything seemed to be hunky dory (I even added a considerable amount of data to this newly expanded partition). Upon rebooting a few days later, I found that the Windows 7 partition no longer booted. I realize now that modifying the partition within windows was probably a big mistake as windows only read the MBR (and thus the GPT partition table was left unchanged). Now the GPT displays this:
Code:
# Start LBA End LBA Type
1 40 409639 EFI System (FAT)
2 409640 1049763839 Mac OS X HFS+
3 1436043264 1953523711 Basic Data
While the MBR displays this:
Code:
# A Start LBA End LBA Type
1 1 409639 ee EFI Protective
2 409640 1049763839 af Mac OS X HFS+
3 * 1049763840 1953523711 07 NTFS/HPFS
The GPT thinks that there is a bunch of unallocated space, when in reality Windows 7 is already using this "unallocated" space. Is there any safe way to sync the GPT table with the MBR table?