Lines Matching full:disk
36 modify disk structures until you explicitly write them to disk, so if you
40 Ordinarily, \fBgdisk\fR operates on disk device files, such as
43 can also operate on disk image files, which can be either copies of whole
44 disks (made with \fBdd\fR, for instance) or raw disk images used by
45 emulators such as QEMU or VMWare. Note that only \fIraw\fR disk images
47 disk image formats.
59 partitions with the Mac OS X Disk Utility program and Linux partitions
63 the disk. If it finds valid GPT data, \fBgdisk\fR will use it. If
72 may become corrupted if the disk uses unrecognized type codes. Boot
74 GPT\-unaware OS. If you mistakenly launch \fBgdisk\fR on an MBR disk, you
111 If Windows is to boot from a GPT disk, a partition of type \fIMicrosoft
122 each partition. The intent is to enable future disk utilities to use this
124 help in future disk maintenance. You can use GPT fdisk's relative partition
142 in\-memory partition table to a disk file using this option. The resulting
166 the partition on the disk. If a corresponding hybrid MBR partition exists,
202 from the start of the disk. You can specify locations relative to the start
240 partitions on the disk. If you want them to match, you can use this option.
253 Verify disk. This option checks for a variety of problems, such as
257 this command displays a summary of unallocated disk space.
294 damaged, you can use this option to load the backup from disk and use it
296 partition entries if you've just converted an MBR disk to GPT format, since
297 there will be no backup partition table on disk.
307 from disk. It's only likely to be useful if you've tried to use the backup
327 inserted between partitions when they were created, and if the disk is under
334 OSes, or those that can't boot from a GPT disk, to access up to three of
335 the partitions on the disk by creating MBR entries for them. Note that
337 particularly when hybrid\-unaware GPT utilities are used to edit the disk.
351 but the original disk is not recommended.
378 will attempt to convert BSD disklabels stored on the main disk when
386 Verify disk. This option is identical to the 'v' option in the main menu.
390 Write table to disk and exit. This option is identical to the 'w' option in
434 Move backup GPT data structures to the end of the disk. Use this command if
435 you've added disks to a RAID array, thus creating a virtual disk with space
437 GPT data structures to the end of the disk, where they belong.
441 Randomize the disk's GUID and all partitions' unique GUIDs (but not their
442 partition type code GUIDs). This function may be used after cloning a disk
447 Change disk GUID. Each disk has a unique GUID code, which \fBgdisk\fR
454 help if a disk utility, OS, or BIOS doesn't like the CHS values used by the
474 boundaries by default, which optimizes performance for all of these disk
476 alignment value used on that disk, but will set 8-sector alignment on disks
526 partitions in this way has no effect on their disk space allocation; it
536 \fBf\fR option on the new disk.
540 Verify disk. This option is identical to the 'v' option in the main menu.
545 repartition a GPT disk using \fBfdisk\fR or some other GPT\-unaware program.
579 table to a disk when existing partitions on that disk are mounted. (The
613 the start or (more commonly) the end of the disk. Resizing the partition
621 MBR conversions work only if the disk has correct LBA partition
622 descriptors. These descriptors should be present on any disk over 8 GiB in
642 Booting after converting an MBR or BSD disklabel disk is likely to be
