|check||Checks the tables for validity, difference and device for presence of protective MBR.|
|Print header data and partition list.|
|erase||Erases existing tables. (In real, only signatures are erased.)|
|Create empty tables.|
|edit||Run interactive editing of tables.|
|fix||Fix consistency of tables. If one table (either primary or backup) is invalid, it is cloned from valid one. If tables differ, primary table is copied to backup one.|
|newids||Assign new GUIDs to header and all partitions. This is needed after byte-to-byte disk cloning.|
|Write PMBR to device (with one protective partition).|
gpte recognizes the following options:
|Work only with primary table. (Not recommended for normal use)|
|-backup||Work only with backup table. (Not recommended for normal use)|
|Define block size to use instead of one recognized from device. If gpte isnt given any size and cant get one from the device, fallback value is 512.|
|Specify linear block address for backup GPT header. (For use when size being saw now is not the same as during work, e.g. for parts of RAID volume.) Default is device size in blocks minus 1.|
Valentin Nechayev <email@example.com>
Intel EFI specification (http://www.intel.com/technology/efi/).
Intel EFI specification puts some restrictions to possible actions. E.g. one cannot enter editing both tables before primary and backup tables forcefully set identical.
This tool is very hackerish.
Some checks are omitted now (e.g. not to overlap with other partitions).
This version does not know anything for partition names.