1#@!#!123s

: / proc / thread-self / root / usr / share / doc / gdisk /
Filename : gdisk.html
back
Content-type: text/html; charset=UTF-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Man page of GDISK</TITLE>
</HEAD><BODY>
<H1>GDISK</H1>
Section: GPT fdisk Manual (8)<BR>Updated: 1.0.8<BR><A HREF="#index">Index</A>
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>

<A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2>

gdisk - Interactive GUID partition table (GPT) manipulator
<A NAME="lbAC">&nbsp;</A>
<H2>SYNOPSIS</H2>

<B>gdisk </B>

[ -l ]
<I>device</I>

<P>
<A NAME="lbAD">&nbsp;</A>
<H2>DESCRIPTION</H2>

GPT fdisk (aka <B>gdisk</B>) is a text-mode menu-driven program for
creation and manipulation of partition tables. It will automatically
convert an old-style Master Boot Record (MBR) partition table or BSD
disklabel stored without an MBR carrier partition to the newer Globally
Unique Identifier (GUID) Partition Table (GPT) format, or will load a GUID
partition table. When used with the <I>-l</I> command-line option, the
program displays the current partition table and then exits.
<P>
GPT fdisk operates mainly on the GPT headers and partition tables; however,
it can and will generate a fresh protective MBR, when required. (Any boot
loader code in the protective MBR will not be disturbed.) If you've created
an unusual protective MBR, such as a hybrid MBR created by
<B>gptsync</B> or <B>gdisk</B>'s own hybrid MBR creation feature,
this should not be disturbed by most ordinary actions. Some advanced data
recovery options require you to understand the distinctions between the
main and backup data, as well as between the GPT headers and the partition
tables. For information on MBR vs. GPT, as well as GPT terminology and
structure, see the extended <B>gdisk</B> documentation at
<I><A HREF="http://www.rodsbooks.com/gdisk/">http://www.rodsbooks.com/gdisk/</A></I> or consult Wikipedia.
<P>
The <B>gdisk</B> program employs a user interface similar to that of Linux's
<B>fdisk</B>, but <B>gdisk</B> modifies GPT partitions. It also has the
capability of transforming MBR partitions or BSD disklabels into GPT
partitions. Like the original <B>fdisk</B> program, <B>gdisk</B> does not
modify disk structures until you explicitly write them to disk, so if you
make a mistake, you can exit from the program with the 'q' option to leave
your partitions unmodified.
<P>
Ordinarily, <B>gdisk</B> operates on disk device files, such as
<I>/dev/sda</I> or <I>/dev/hda</I> under Linux, <I>/dev/disk0</I> under
Mac OS X, or <I>/dev/ad0</I> or <I>/dev/da0</I> under FreeBSD. The program
can also operate on disk image files, which can be either copies of whole
disks (made with <B>dd</B>, for instance) or raw disk images used by
emulators such as QEMU or VMWare. Note that only <I>raw</I> disk images
are supported; <B>gdisk</B> cannot work on compressed or other advanced
disk image formats.
<P>
The MBR partitioning system uses a combination of cylinder/head/sector
(CHS) addressing and logical block addressing (LBA). The former is klunky
and limiting. GPT drops CHS addressing and uses 64-bit LBA mode
exclusively. Thus, GPT data structures, and therefore
<B>gdisk</B>, do not need to deal with CHS geometries and all the problems
they create. Users of <B>fdisk</B> will note that <B>gdisk</B>
lacks the options and limitations associated with CHS geometries.
<P>
For best results, you should use an OS-specific partition table
program whenever possible. For example, you should make Mac OS X
partitions with the Mac OS X Disk Utility program and Linux partitions
with the Linux <B>gdisk</B> or GNU Parted program.
<P>
Upon start, <B>gdisk</B> attempts to identify the partition type in use on
the disk. If it finds valid GPT data, <B>gdisk</B> will use it. If
<B>gdisk</B> finds a valid MBR or BSD disklabel but no GPT data, it will
attempt to convert the MBR or disklabel into GPT form. (BSD disklabels are
likely to have unusable first and/or final partitions because they overlap
with the GPT data structures, though.) GPT fdisk can identify, but not use
data in, Apple Partition Map (APM) disks, which are used on 680x0- and
PowerPC-based Macintoshes. Upon exiting with the 'w' option, <B>gdisk</B>
replaces the MBR or disklabel with a GPT. <I>This action is potentially
dangerous!</I> Your system may become unbootable, and partition type codes
may become corrupted if the disk uses unrecognized type codes. Boot
problems are particularly likely if you're multi-booting with any
GPT-unaware OS. If you mistakenly launch <B>gdisk</B> on an MBR disk, you
can safely exit the program without making any changes by using the 'q'
option.
<P>
The MBR-to-GPT conversion will leave at least one gap in the partition
numbering if the original MBR used logical partitions. These gaps are
harmless, but you can eliminate them by using the 's' option, if you like.
(Doing this may require you to update your <I>/etc/fstab</I> file.)
<P>
When creating a fresh partition table, certain considerations may be in
order:
<P>
<DL COMPACT>
<DT><B>*</B>

<DD>
For data (non-boot) disks, and for boot disks used on BIOS-based computers
with GRUB as the boot loader, partitions may be created in whatever order
and in whatever sizes are desired.
<P>
<DT><B>*</B>

<DD>
Boot disks for EFI-based systems require an <I>EFI System Partition</I>
(<B>gdisk</B> internal code 0xEF00) formatted as FAT-32. I recommended
making this partition 550 MiB. (Smaller ESPs are common, but some EFIs have
flaky FAT drivers that necessitate a larger partition for reliable
operation.) Boot-related files are stored here. (Note that GNU Parted
identifies such partitions as having the &quot;boot flag&quot; set.)
<P>
<DT><B>*</B>

<DD>
Some boot loaders for BIOS-based systems make use of a <I>BIOS Boot
Partition</I> (<B>gdisk</B> internal code 0xEF02), in which the secondary
boot loader is stored, possibly without the benefit of a filesystem. (GRUB2
may optionally use such a partition.) This partition can typically be quite
small (roughly 32 to 200 KiB, although 1 MiB is more common in practice),
but you should consult your boot loader documentation for details.
<P>
<DT><B>*</B>

<DD>
If Windows is to boot from a GPT disk, a partition of type <I>Microsoft
Reserved</I> (<B>gdisk</B>
internal code 0x0C01) is recommended. This partition should be about 128 MiB
in size. It ordinarily follows the EFI System Partition and immediately
precedes the Windows data partitions. (Note that old versions of GNU Parted
create all FAT partitions as this type, which actually makes the partition
unusable for normal file storage in both Windows and Mac OS X.)
<P>
<DT><B>*</B>

<DD>
Some OSes' GPT utilities create some blank space (typically 128 MiB) after
each partition. The intent is to enable future disk utilities to use this
space. Such free space is not required of GPT disks, but creating it may
help in future disk maintenance. You can use GPT fdisk's relative partition
positioning option (specifying the starting sector as '+128M', for
instance) to simplify creating such gaps.
<P>
</DL>
<A NAME="lbAE">&nbsp;</A>
<H2>OPTIONS</H2>

<DL COMPACT>
<DT><B>-l</B>

<DD>
List the partition table for the specified device and then exits.
</DL>
<P>

<P>
Most interactions with <B>gdisk</B>
occur with its interactive text-mode menus. Three menus exist: the main
menu, the recovery &amp; transformation menu, and the experts' menu. The main
menu provides the functions that are most likely to be useful for typical partitioning tasks, such as creating and deleting partitions, changing partition type codes, and so on. Specific functions are:
<P>
<DL COMPACT>
<DT><B>b</B>

<DD>
Save partition data to a backup file. You can back up your current
in-memory partition table to a disk file using this option. The resulting
file is a binary file consisting of the protective MBR, the main GPT
header, the backup GPT header, and one copy of the partition table, in that
order. Note that the backup is of the current in-memory data structures, so
if you launch the program, make changes, and then use this option, the
backup will reflect your changes. Note also that the restore option is on
the recovery &amp; transformation menu; the backup option is on the main menu
to encourage its use.
<P>
<P>
<DT><B>c</B>

<DD>
Change the GPT name of a partition. This name is encoded as a UTF-16
string, but proper entry and display of anything beyond basic ASCII values
requires suitable locale and font support. For the most part, Linux ignores
the partition name, but it may be important in some OSes. GPT fdisk sets a
default name based on the partition type code. Note that the GPT partition
name is different from the filesystem name, which is encoded in the
filesystem's data structures.
<P>
<DT><B>d</B>

<DD>
Delete a partition. This action deletes the entry from the partition table
but does not disturb the data within the sectors originally allocated to
the partition on the disk. If a corresponding hybrid MBR partition exists,
<B>gdisk</B> deletes it, as well, and expands any adjacent 0xEE (EFI GPT)
MBR protective partition to fill the new free space.
<P>
<DT><B>i</B>

<DD>
Show detailed partition information. The summary information produced by
the 'p' command necessarily omits many details, such as the partition's
unique GUID and the translation of <B>gdisk</B>'s
internal partition type code to a plain type name. The 'i' option
displays this information for a single partition.
<P>
<DT><B>l</B>

<DD>
Display a summary of partition types. GPT uses a GUID to identify partition
types for particular OSes and purposes. For ease of data entry, <B>gdisk</B>
compresses these into two-byte (four-digit hexadecimal) values that are
related to their equivalent MBR codes. Specifically, the MBR code is
multiplied by hexadecimal 0x0100. For instance, the code for Linux swap
space in MBR is 0x82, and it's 0x8200 in <B>gdisk</B>. A one-to-one
correspondence is impossible, though. Most notably, the codes for all
varieties of FAT and NTFS partition correspond to a single GPT code (entered
as 0x0700 in <B>gdisk</B>). Some OSes use a single MBR code but employ many
more codes in GPT. For these, <B>gdisk</B> adds code numbers sequentially,
such as 0xa500 for a FreeBSD disklabel, 0xa501 for FreeBSD boot, 0xa502 for
FreeBSD swap, and so on. Note that these two-byte codes are unique to
<B>gdisk</B>. The type code list may optionally be filtered by a search
string; for instance, entering <I></I><B>linux</B> shows only partition type
codes with descriptions that include the string <I>Linux</I>. This search is
performed case-insensitively.
<P>
<DT><B>n</B>

<DD>
Create a new partition. This command is modeled after the equivalent
<B>fdisk</B> option, although some differences exist. You enter a partition
number, starting sector, and an ending sector. Both start and end sectors
can be specified in absolute terms as sector numbers or as positions
measured in kibibytes (K), mebibytes (M), gibibytes (G), tebibytes (T), or
pebibytes (P); for instance, <I></I><B>40M</B> specifies a position 40MiB
from the start of the disk. You can specify locations relative to the start
or end of the specified default range by preceding the number by a '+' or '-'
symbol, as in <I></I><B>+2G</B> to specify a point 2GiB after the
default start sector, or <I></I><B>-200M</B> to specify a point 200MiB
before the last available sector. Pressing the Enter key with no input
specifies the default value, which is the start of the largest available
block for the start sector and the end of the same block for the end
sector.
<P>
<DT><B>o</B>

<DD>
Clear out all partition data. This includes GPT header data,
all partition definitions, and the protective MBR. The sector alignment
is reset to the default (1 MiB, or 2048 sectors on a disk with 512-byte
sectors).
<P>
<DT><B>p</B>

<DD>
Display basic partition summary data. This includes partition
numbers, starting and ending sector numbers, partition sizes,
<B>gdisk</B>'s partition types codes, and partition names. For
additional information, use the 'i' command.
<P>
<DT><B>q</B>

<DD>
Quit from the program <I>without saving your changes</I>.
Use this option if you just wanted to view information or if you make a
mistake and want to back out of all your changes.
<P>
<DT><B>r</B>

<DD>
Enter the recovery &amp; transformation menu. This menu includes emergency
recovery options (to fix damaged GPT data structures) and options to
transform to or from other partitioning systems, including creating
hybrid MBRs.
<P>
<DT><B>s</B>

<DD>
Sort partition entries. GPT partition numbers need not match the order of
partitions on the disk. If you want them to match, you can use this option.
Note that some partitioning utilities sort partitions whenever they make
changes. Such changes will be reflected in your device filenames, so you
may need to edit <I>/etc/fstab</I> if you use this option.
<P>
<DT><B>t</B>

<DD>
Change a single partition's type code. You enter the type code using a
two-byte hexadecimal number, as described earlier. You may also enter a
GUID directly, if you have one and <B>gdisk</B> doesn't know it.
<P>
<DT><B>v</B>

<DD>
Verify disk. This option checks for a variety of problems, such as
incorrect CRCs and mismatched main and backup data. This option does not
automatically correct most problems, though; for that, you must use
options on the recovery &amp; transformation menu. If no problems are found,
this command displays a summary of unallocated disk space.
<P>
<DT><B>w</B>

<DD>
Write data. Use this command to save your changes.
<P>
<DT><B>x</B>

<DD>
Enter the experts' menu. Using this option provides access to features you
can use to get into even more trouble than the main menu allows.
</DL>
<P>

<P>
<DL COMPACT>
<DT><B>?</B>

<DD>
Print the menu. Type this command (or any other unrecognized command) to
see a summary of available options.
<P>
</DL>
<P>

The second <B>gdisk</B> menu is the recovery &amp; transformation menu, which
provides access to data recovery options and features related to the
transformation of partitions between partitioning schemes (converting
BSD disklabels into GPT partitions or creating hybrid MBRs, for instance).
A few options on this menu duplicate functionality on the main
menu, for the sake of convenience. The options on this menu are:
<P>
<DL COMPACT>
<DT><B>b</B>

<DD>
Rebuild GPT header from backup. You can use the backup GPT header to
rebuild the main GPT header with this option. It's likely to be useful if
your main GPT header was damaged or destroyed (say, by sloppy use of
<B>dd</B>).
<P>
<DT><B>c</B>

<DD>
Load backup partition table. Ordinarily, <B>gdisk</B>
uses only the main partition table (although the backup's integrity is
checked when you launch the program). If the main partition table has been
damaged, you can use this option to load the backup from disk and use it
instead. Note that this will almost certainly produce no or strange
partition entries if you've just converted an MBR disk to GPT format, since
there will be no backup partition table on disk.
<P>
<DT><B>d</B>

<DD>
Use main GPT header and rebuild the backup. This option is likely to be
useful if the backup GPT header has been damaged or destroyed.
<P>
<DT><B>e</B>

<DD>
Load main partition table. This option reloads the main partition table
from disk. It's only likely to be useful if you've tried to use the backup
partition table (via 'c') but it's in worse shape then the main partition
table.
<P>
<DT><B>f</B>

<DD>
Load MBR and build fresh GPT from it. Use this option if your GPT is corrupt
or conflicts with the MBR and you want to use the MBR as the basis for a new
set of GPT partitions.
<P>
<DT><B>g</B>

<DD>
Convert GPT into MBR and exit. This option converts as many partitions as possible
into MBR form, destroys the GPT data structures, saves the new MBR, and exits.
Use this option if you've tried GPT and find that MBR works better for you.
Note that this function generates up to four primary MBR partitions or three
primary partitions and as many logical partitions as can be generated. Each
logical partition requires at least one unallocated block immediately before
its first block. Therefore, it may be possible to convert a maximum of four
partitions on disks with tightly-packed partitions; however, if free space was
inserted between partitions when they were created, and if the disk is under
2 TiB in size, it should be possible to convert all the partitions to MBR form.
See also the 'h' option.
<P>
<DT><B>h</B>

<DD>
Create a hybrid MBR. This is an ugly workaround that enables GPT-unaware
OSes, or those that can't boot from a GPT disk, to access up to three of
the partitions on the disk by creating MBR entries for them. Note that
these hybrid MBR entries can easily go out of sync with the GPT entries,
particularly when hybrid-unaware GPT utilities are used to edit the disk.
Thus, you may need to re-create the hybrid MBR if you use such tools. Unlike
the 'g' option, this option does not support converting any partitions into
MBR logical partitions.
<P>
<DT><B>i</B>

<DD>
Show detailed partition information. This option is identical to the 'i'
option on the main menu.
<P>
<DT><B>l</B>

<DD>
Load partition data from a backup file. This option is the reverse of the 'b'
option on the main menu. Note that restoring partition data from anything
but the original disk is not recommended.
<P>
<DT><B>m</B>

<DD>
Return to the main menu. This option enables you to enter main-menu commands.
<P>
<DT><B>o</B>

<DD>
Print protective MBR data. You can see a summary of the protective MBR's
partitions with this option. This may enable you to spot glaring problems
or help identify the partitions in a hybrid MBR.
<P>
<DT><B>p</B>

<DD>
Print the partition table. This option is identical to the 'p' option in
the main menu.
<P>
<DT><B>q</B>

<DD>
Quit without saving changes. This option is identical to the 'q' option in
the main menu.
<P>
<DT><B>t</B>

<DD>
Transform BSD partitions into GPT partitions. This option works on BSD
disklabels held within GPT (or converted MBR) partitions. Converted
partitions' type codes are likely to need manual adjustment. <B>gdisk</B>
will attempt to convert BSD disklabels stored on the main disk when
launched, but this conversion is likely to produce first and/or last
partitions that are unusable. The many BSD variants means that the
probability of <B>gdisk</B> being unable to convert a BSD disklabel is
high compared to the likelihood of problems with an MBR conversion.
<P>
<DT><B>v</B>

<DD>
Verify disk. This option is identical to the 'v' option in the main menu.
<P>
<DT><B>w</B>

<DD>
Write table to disk and exit. This option is identical to the 'w' option in
the main menu.
<P>
<DT><B>x</B>

<DD>
Enter the experts' menu. This option is identical to the 'x' option in the
main menu.
<P>
<DT><B>?</B>

<DD>
Print the menu. This option (or any unrecognized entry) displays a summary
of the menu options.
<P>
</DL>
<P>

The third <B>gdisk</B> menu is the experts' menu. This menu provides advanced
options that aren't closely related to recovery or transformation between
partitioning systems. Its options are:
<P>
<DL COMPACT>
<DT><B>a</B>

<DD>
Set attributes. GPT provides a 64-bit attributes field that can be used to
set features for each partition. <B>gdisk</B> supports four attributes:
<I>system partition</I>, <I>read-only</I>, <I>hidden</I>, and
<I>do not automount</I>. You can set other attributes, but their numbers
aren't translated into anything useful. In practice, most OSes seem to
ignore these attributes.
<P>
<DT><B>b</B>

<DD>
Swap the byte order for the name of the specified partition. Some
partitioning tools, including GPT fdisk 1.0.7 and earlier, can write the
partition name in the wrong byte order on big-endian computers, such as the
IBM s390 mainframes and PowerPC-based Macs. This feature corrects this
problem.
<P>
<DT><B>c</B>

<DD>
Change partition GUID. You can enter a custom unique GUID for a partition
using this option. (Note this refers to the GUID that uniquely identifies a
partition, not to its type code, which you can change with the 't' main-menu
option.) Ordinarily, <B>gdisk</B> assigns this number randomly; however,
you might want to adjust the number manually if you've wound up with the
same GUID on two partitions because of buggy GUID assignments (hopefully
not in <B>gdisk</B>) or sheer incredible coincidence.
<P>
<DT><B>d</B>

<DD>
Display the sector alignment value. See the
description of the 'l' option for more details.
<P>
<DT><B>e</B>

<DD>
Move backup GPT data structures to the end of the disk. Use this command if
you've added disks to a RAID array, thus creating a virtual disk with space
that follows the backup GPT data structures. This command moves the backup
GPT data structures to the end of the disk, where they belong.
<P>
<DT><B>f</B>

<DD>
Randomize the disk's GUID and all partitions' unique GUIDs (but not their
partition type code GUIDs). This function may be used after cloning a disk
with another utility in order to render all GUIDs once again unique.
<P>
<DT><B>g</B>

<DD>
Change disk GUID. Each disk has a unique GUID code, which <B>gdisk</B>
assigns randomly upon creation of the GPT data structures. You can generate
a fresh random GUID or enter one manually with this option.
<P>
<DT><B>h</B>

<DD>
Recompute CHS values in protective or hybrid MBR. This option can sometimes
help if a disk utility, OS, or BIOS doesn't like the CHS values used by the
partitions in the protective or hybrid MBR. In particular, the GPT
specification requires a CHS value of 0xFFFFFF for over-8GiB partitions,
but this value is technically illegal by the usual standards. Some BIOSes
hang if they encounter this value. This option will recompute a more normal
CHS value -- 0xFEFFFF for over-8GiB partitions, enabling these BIOSes to
boot.
<P>
<DT><B>i</B>

<DD>
Show detailed partition information. This option is identical to the 'i'
option on the main menu.
<P>
<DT><B>j</B>

<DD>
Adjust the location of the main partition table. This value is normally 2,
but it may need to be increased in some cases, such as when a
system-on-chip (SoC) is hard-coded to read boot code from sector 2. I
recommend against adjusting this value unless doing so is absolutely
necessary.
<P>
<DT><B>l</B>

<DD>
Change the sector alignment value. Disks with more logical sectors per
physical sectors (such as modern Advanced Format drives), some RAID
configurations, and many SSD devices, can suffer performance problems if
partitions are not aligned properly for their internal data structures. On
new disks, GPT fdisk attempts to align partitions on 1 MiB boundaries
(2048-sectors on disks with 512-byte sectors) by default, which optimizes
performance for all of these disk types. On pre-partitioned disks, GPT
fdisk attempts to identify the alignment value used on that disk, but will
set 8-sector alignment on disks larger than 300 GB even if lesser alignment
values are detected. In either case, it can be changed by using this
option.
<P>
<DT><B>m</B>

<DD>
Return to the main menu. This option enables you to enter main-menu commands.
<P>
<DT><B>n</B>

<DD>
Create a new protective MBR. Use this option if the current protective MBR
is damaged in a way that <B>gdisk</B> doesn't automatically detect and
correct, or if you want to convert a hybrid MBR into a &quot;pure&quot; GPT with a
conventional protective MBR.
<P>
<DT><B>o</B>

<DD>
Print protective MBR data. You can see a summary of the protective MBR's
partitions with this option. This may enable you to spot glaring problems
or help identify the partitions in a hybrid MBR.
<P>
<DT><B>p</B>

<DD>
Print the partition table. This option is identical to the 'p' option in
the main menu.
<P>
<DT><B>q</B>

<DD>
Quit without saving changes. This option is identical to the 'q' option in
the main menu.
<P>
<DT><B>r</B>

<DD>
Enter the recovery &amp; transformations menu. This option is identical to
the 'r' option on the main menu.
<P>
<DT><B>s</B>

<DD>
Resize partition table. The default partition table size is 128 entries.
Officially, sizes of less than 16KB (128 entries, given the normal entry
size) are unsupported by the GPT specification; however, in practice they
seem to work, and can sometimes be useful in converting MBR disks. Larger
sizes also work fine. OSes may impose their own limits on the number of
partitions, though.
<P>
<DT><B>t</B>

<DD>
Swap two partitions' entries in the partition table. One partition may be
empty. For instance, if partitions 1-4 are defined, transposing 1 and 5
results in a table with partitions numbered from 2-5. Transposing
partitions in this way has no effect on their disk space allocation; it
only alters their order in the partition table.
<P>
<DT><B>u</B>

<DD>
Replicate the current device's partition table on another device. You will
be prompted to type the new device's filename. After the write operation
completes, you can continue editing the original device's partition table.
Note that the replicated partition table is an exact copy, including all
GUIDs; if the device should have its own unique GUIDs, you should use the
<B>f</B> option on the new disk.
<P>
<DT><B>v</B>

<DD>
Verify disk. This option is identical to the 'v' option in the main menu.
<P>
<DT><B>z</B>

<DD>
Zap (destroy) the GPT data structures and exit. Use this option if you want to
repartition a GPT disk using <B>fdisk</B> or some other GPT-unaware program.
You'll be given the choice of preserving the existing MBR, in case it's a
hybrid MBR with salvageable partitions or if you've already created new MBR
partitions and want to erase the remnants of your GPT partitions. <I>If you've
already created new MBR partitions, it's conceivable that this option will
damage the first and/or last MBR partitions!</I> Such an event is unlikely, but
could occur if your new MBR partitions overlap the old GPT data structures.
<P>
<DT><B>?</B>

<DD>
Print the menu. This option (or any unrecognized entry) displays a summary
of the menu options.
<P>
</DL>
<P>

In many cases, you can press the Enter key to select a default option when
entering data. When only one option is possible, <B>gdisk</B>
usually bypasses the prompt entirely.
<P>
<A NAME="lbAF">&nbsp;</A>
<H2>BUGS</H2>

Known bugs and limitations include:
<P>
<DL COMPACT>
<DT><B>*</B>

<DD>
The program compiles correctly only on Linux, FreeBSD, Mac OS X, and Windows.
Linux versions for x86-64 (64-bit), x86 (32-bit), and PowerPC (32-bit) have been
tested, with the x86-64 version having seen the most testing. Under FreeBSD,
32-bit (x86) and 64-bit (x86-64) versions have been tested. Only 32-bit
versions for Mac OS X and Windows have been tested by the author, although
I've heard of 64-bit versions being successfully compiled.
<P>
<DT><B>*</B>

<DD>
The FreeBSD version of the program can't write changes to the partition
table to a disk when existing partitions on that disk are mounted. (The
same problem exists with many other FreeBSD utilities, such as
<B>gpt</B>, <B>fdisk</B>, and <B>dd</B>.) This limitation can be overcome
by typing <B>sysctl kern.geom.debugflags=16</B> at a shell prompt.
<P>
<DT><B>*</B>

<DD>
The fields used to display the start and end sector numbers for partitions
in the 'p' command are 14 characters wide. This translates to a limitation
of about 45 PiB. On larger disks, the displayed columns will go out of
alignment.
<P>
<DT><B>*</B>

<DD>
In the Windows version, only ASCII characters are supported in the
partition name field. If an existing partition uses non-ASCII UTF-16
characters, they're likely to be corrupted in the 'i' and 'p' menu options'
displays; however, they should be preserved when loading and saving
partitions. Binaries for Linux, FreeBSD, and OS X support full UTF-16
partition names.
<P>
<DT><B>*</B>

<DD>
The program can load only up to 128 partitions (4 primary partitions and
124 logical partitions) when converting from MBR format. This limit can
be raised by changing the <I>#define MAX_MBR_PARTS</I> line in the
<I>basicmbr.h</I> source code file and recompiling; however, such a change
will require using a larger-than-normal partition table. (The limit
of 128 partitions was chosen because that number equals the 128 partitions
supported by the most common partition table size.)
<P>
<DT><B>*</B>

<DD>
Converting from MBR format sometimes fails because of insufficient space at
the start or (more commonly) the end of the disk. Resizing the partition
table (using the 's' option in the experts' menu) can sometimes overcome
this problem; however, in extreme cases it may be necessary to resize a
partition using GNU Parted or a similar tool prior to conversion with
<B>gdisk</B>.
<P>
<DT><B>*</B>

<DD>
MBR conversions work only if the disk has correct LBA partition
descriptors. These descriptors should be present on any disk over 8 GiB in
size or on smaller disks partitioned with any but very ancient software.
<P>
<DT><B>*</B>

<DD>
BSD disklabel support can create first and/or last partitions that overlap
with the GPT data structures. This can sometimes be compensated by
adjusting the partition table size, but in extreme cases the affected
partition(s) may need to be deleted.
<P>
<DT><B>*</B>

<DD>
Because of the highly variable nature of BSD disklabel structures,
conversions from this form may be unreliable -- partitions may be dropped,
converted in a way that creates overlaps with other partitions, or
converted with incorrect start or end values. Use this feature with
caution!
<P>
<DT><B>*</B>

<DD>
Booting after converting an MBR or BSD disklabel disk is likely to be
disrupted. Sometimes re-installing a boot loader will fix the problem, but
other times you may need to switch boot loaders. Except on EFI-based
platforms, Windows through at least Windows 7 doesn't support booting
from GPT disks. Creating a hybrid MBR (using the 'h' option on the recovery &amp;
transformation menu) or abandoning GPT in favor of MBR may be your only
options in this case.
<P>
</DL>
<P>

<P>
<A NAME="lbAG">&nbsp;</A>
<H2>AUTHORS</H2>

Primary author: Roderick W. Smith (<A HREF="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</A>)
<P>
Contributors:
<P>
* Yves Blusseau (<A HREF="mailto:1otnwmz02@sneakemail.com">1otnwmz02@sneakemail.com</A>)
<P>
* David Hubbard (<A HREF="mailto:david.c.hubbard@gmail.com">david.c.hubbard@gmail.com</A>)
<P>
* Justin Maggard (<A HREF="mailto:justin.maggard@netgear.com">justin.maggard@netgear.com</A>)
<P>
* Dwight Schauer (<A HREF="mailto:das@teegra.net">das@teegra.net</A>)
<P>
* Florian Zumbiehl (<A HREF="mailto:florz@florz.de">florz@florz.de</A>)
<P>
<P>
<A NAME="lbAH">&nbsp;</A>
<H2>SEE ALSO</H2>

<B><A HREF="/cgi-bin/man/man2html?8+cfdisk">cfdisk</A></B>(8),

<B><A HREF="/cgi-bin/man/man2html?8+cgdisk">cgdisk</A></B>(8),

<B><A HREF="/cgi-bin/man/man2html?8+fdisk">fdisk</A></B>(8),

<B><A HREF="/cgi-bin/man/man2html?8+mkfs">mkfs</A></B>(8),

<B><A HREF="/cgi-bin/man/man2html?8+parted">parted</A></B>(8),

<B><A HREF="/cgi-bin/man/man2html?8+sfdisk">sfdisk</A></B>(8),

<B><A HREF="/cgi-bin/man/man2html?8+sgdisk">sgdisk</A></B>(8),

<B><A HREF="/cgi-bin/man/man2html?8+fixparts">fixparts</A></B>(8).

<P>
<I><A HREF="http://en.wikipedia.org/wiki/GUID_Partition_Table">http://en.wikipedia.org/wiki/GUID_Partition_Table</A></I>
<P>
<I><A HREF="http://developer.apple.com/technotes/tn2006/tn2166.html">http://developer.apple.com/technotes/tn2006/tn2166.html</A></I>
<P>
<I><A HREF="http://www.rodsbooks.com/gdisk/">http://www.rodsbooks.com/gdisk/</A></I>
<P>
<A NAME="lbAI">&nbsp;</A>
<H2>AVAILABILITY</H2>

The <B>gdisk</B> command is part of the <I>GPT fdisk</I> package and is
available from Rod Smith.
<P>

<HR>
<A NAME="index">&nbsp;</A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
<DT><A HREF="#lbAE">OPTIONS</A><DD>
<DT><A HREF="#lbAF">BUGS</A><DD>
<DT><A HREF="#lbAG">AUTHORS</A><DD>
<DT><A HREF="#lbAH">SEE ALSO</A><DD>
<DT><A HREF="#lbAI">AVAILABILITY</A><DD>
</DL>
<HR>
This document was created by
<A HREF="/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR>
Time: 23:27:51 GMT, June 09, 2021
</BODY>
</HTML>