This would in theory allow the disk to mount on older systems that don’t support GPT. If you’ve read that and are wondering why there are no 128MB gaps after each non-ESP partition, note the article doesn’t mention that those gaps are only added after HFS+ partitions when defined directly within the partition table, and not when encapsulated within a Core Storage logical volume group.įor example, an 8GB USB drive partitioned with original Disk Utility to use GPT for two HFS+ partitions looks like:ĭisk: /dev/disk2 geometry: 974/255/63 This follows the behaviour described in Secrets of the GPT. Then our remaining partitions, another boundary alignment gap, and the secondary GPT table and header. The ESP is 409600 sectors * 512 bytes per sector / 1024 bytes per KB / 1024 KB per MB = 200MB. Then at sector 34 there’s a 3KB gap so that the first partition starts on a 4KB boundary (i.e. The protective MBR occupies one 512-byte sector, the GPT header occupies the next sector, and the partition table entries follow.
The gpt tool shows everything, and counts according to 512-byte sectors.
0 kommentar(er)
