GParted FAQ
Gnome PARTition EDitor. You can also think of GParted as Graphical Partition Editor.
There is no difference. GParted was originally conceived as partition editing software but there are many other names that encompass the same or similar functionality including: Partition Management, Partition Manager, Partition Editing, Partition Editors, and Partitioning Software.
Yes. You do not have to pay money to use Gparted. You have the freedom to run, copy, distribute, study, change and improve Gparted. GParted is free software.
GParted is the partition editor application.
GParted Live is a small bootable GNU/Linux
distribution that contains the partition editor application.
You will need Parted >= 1.7.1 and Gtkmm >= 2.8.x
Get Parted from http://www.gnu.org/software/parted/
and Gtkmm from http://gtkmm.org/
Also, several file systems are supported through their native tools. See the features page for more information on these tools.
Short answer: Yes, it is safe :)
By using the official tools for each file system and performing
extensive checks before any actual operation I think GParted is as
safe as it can/should be.
Of course you have to realize I cannot give any guarantees, so you
should probably make a backup of important data before toying with
your partitions.
NOTE: If you move a partition that is used in the operating system
boot process (for example the C: drive in Windows), then the operating
system might fail to boot.
To fix this problem you will need to repair the boot
configuration.
See FAQ #13 for Linux/GRUB.
See FAQs #14, #15, and
#16 for Windows.
See FAQ #21 for Mac OS X.
Nope, that is, not one an ordinary human being will ever reach.
I myself tested it with up to 150 operations and it went smoothly.
HOWEVER, I think it's wise to keep the amount of succesive
operations limited. After all it's your data which is at risk.
Especially when doing complex operations (copy,resize) I advise you to
take it one step at a time.
When resizing boot NTFS partitions, it is advisable to perform this as
a single operation only. After resizing, boot into Windows twice to
allow Windows to perform its checking operations.
Well, in theory you could go on and create logical partitions
infinitely; however, all operating systems impose some limit.
For Linux it is the device number allocation that limits support.
For IDE devices 64 minor numbers are reserved for each disk.
For instance /dev/hda is major 3 minor 0, /dev/hda1 is major 3,
minor 1, etc up till /dev/hda63.
For SCSI devices only 16 minor numbers are allocated for each disk, so
there Linux only supports 15 partitions. Devices that use the SCSI
driver have names like /dev/sda.
NOTE: When GParted is linked with libparted 3.1+, the limit of
15 partitions is removed.
1. The partition is mounted and modifying a mounted partition is
DANGEROUS. Just unmount the partition or in case of swap, disable
it (use swapoff).
2. At startup gparted decides which operations on which file systems
are supported. For instance, to create an ext3 file system gparted
needs mkfs.ext3. If this cannot be found on your system, the creation
of an ext3 file system is not possible and therefore disabled in
gparted. The same goes for copy, resize etc....
3. Check that you are running the latest version of GParted (menu
entry Help -> About). The features page
shows which operations are supported for the most recently released
version of GParted.
That's because those file systems can only be resized when they are mounted and you can only mount a file system if the kernel has support for it.
1. Check the BIOS settings. This problem can be caused when the BIOS indicates that a floppy drive is present, but no physical floppy drive is installed.
2. A work around is to start gparted from the command line and pass the name of the device(s) you wish to partition.
E.g., gparted /dev/hda
GParted version 0.3.6 (and many earlier versions) created a file to
prevent problems that occur if a device is automounted while gparted is
working on the device.
This file is removed when GParted exits normally.
However, if GParted terminated abnormally it could leave this file on the computer.
Newer GParted versions (0.3.7 and greater) do not use this file, and instead rely on hal-lock to acquire device locks.
To fix the problem you can do one of the following:
1. Remove the file /usr/share/hal/fdi/policy/gparted-disable-automount.fdi
    or,
2. Start and then exit gparted. This will also remove the file.
The cause of this problem is that the absolute physical hard disk sector
containing the start of the stage2 file has changed.
When GRUB is installed, this absolute position is hard-coded into GRUB stage1.
GRUB stage1 might be installed in one of two places; at the beginning of the hard disk, or at the beginning of the boot partition.
To fix this problem you will need to reinstall GRUB.
This will update stage1 with the new hard-coded absolute position of the stage2 file.
More information can be found at the following link:
Fixing GRUB Boot Problem
NOTE: GRUB2 is the default boot loader and manager for Ubuntu since
version 9.10 (Karmic Koala). For help with GRUB2 see the
Ubuntu documentation
for GRUB2.
The following article by the How-To Geek contains useful
information regarding resizing your Windows 7 or Vista partition, and
getting it to boot again.
Using GParted to Resize Your Windows 7 or Vista Partition
If your PC did not come with a complete Vista installation CD, you can
download a Vista Recovery Disc at the following link:
Windows Vista Recovery Disc
If your PC did not come with a complete Windows 7 installation CD, you
can download a Windows 7 System Recovery Disc at the following link:
Windows 7 System Recovery Disc
The following commands are entered at the command line when using the
Recovery Console from the Windows Vista or Windows 7 installation
disk.
To repair the Master Boot Record of the boot disk:
bootrec /fixmbr
To write a new partition boot sector to the system partition:
bootrec /fixboot
To rebuild the Boot Configuration Data (BCD) store:
bootrec /rebuildbcd
For more details refer to the following link:
How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows
The following commands are entered at the command line when using the
Recovery Console from the Windows XP installation disk.
To repair the Master Boot Record of the boot disk:
fixmbr
To write a new partition boot sector to the system partition:
fixboot
To rebuild the boot.ini configuration file:
bootcfg /rebuild
For more details refer to the following links:
Fixmbr,
Fixboot,
Bootcfg
Tips on how to improve the ability to shrink NTFS partitions can be found in the GParted Manual here.
Forum member cmdr wrote some detailed instructions on resizing NTFS partitions that can be found at the following link:
Forum Post - Resize-Windows
Sometimes after a disk configuration change, Windows will change the
drive letter assignment (e.g., from C: to D:).
If this occurs for the boot drive letter, then see:
How to restore the system/boot drive letter in Windows
If this occurs for a non-boot drive letter, then see one of the following links:
How to change drive letter assignments in Windows XP
How to change, add, or remove a drive letter in Windows Vista
If you encounter an error message similar to the above, then please refer to the following link:
Problems Resizing File Systems with GParted
Please refer to the GParted live manual
Tips on Booting GParted Live.
Intel-based Mac OS X uses a combination of GPT and MBR partition
tables. Sometimes when using older GParted versions to modify the
partitions on a Mac, the GPT is changed but not the MBR.
See Bug
586910 - MBR does not reflect the GPT partition map.
This problem can be repaired with the rEFIt application.

