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
112 If Windows is to boot from a GPT disk, a partition of type \fIMicrosoft
123 each partition. The intent is to enable future disk utilities to use this
125 help in future disk maintenance. You can use GPT fdisk's relative partition
143 in\-memory partition table to a disk file using this option. The resulting
167 the partition on the disk. If a corresponding hybrid MBR partition exists,
206 from the start of the disk. You can specify locations relative to the start
220 is reset to the default (1 MiB, or 2048 sectors on a disk with 512-byte
246 partitions on the disk. If you want them to match, you can use this option.
259 Verify disk. This option checks for a variety of problems, such as
263 this command displays a summary of unallocated disk space.
300 damaged, you can use this option to load the backup from disk and use it
302 partition entries if you've just converted an MBR disk to GPT format, since
303 there will be no backup partition table on disk.
313 from disk. It's only likely to be useful if you've tried to use the backup
333 inserted between partitions when they were created, and if the disk is under
340 OSes, or those that can't boot from a GPT disk, to access up to three of
341 the partitions on the disk by creating MBR entries for them. Note that
343 particularly when hybrid\-unaware GPT utilities are used to edit the disk.
357 but the original disk is not recommended.
384 will attempt to convert BSD disklabels stored on the main disk when
392 Verify disk. This option is identical to the 'v' option in the main menu.
396 Write table to disk and exit. This option is identical to the 'w' option in
448 Move backup GPT data structures to the end of the disk. Use this command if
449 you've added disks to a RAID array, thus creating a virtual disk with space
451 GPT data structures to the end of the disk, where they belong.
455 Randomize the disk's GUID and all partitions' unique GUIDs (but not their
456 partition type code GUIDs). This function may be used after cloning a disk
461 Change disk GUID. Each disk has a unique GUID code, which \fBgdisk\fR
468 help if a disk utility, OS, or BIOS doesn't like the CHS values used by the
492 normally located just before the backup metadata at the end of the disk, but
504 performance for all of these disk types. On pre\-partitioned disks, GPT
505 fdisk attempts to identify the alignment value used on that disk, but will
511 alignment value in size. Some disk encryption tools require partitions to be
561 partitions in this way has no effect on their disk space allocation; it
571 \fBf\fR option on the new disk.
575 Verify disk. This option is identical to the 'v' option in the main menu.
580 repartition a GPT disk using \fBfdisk\fR or some other GPT\-unaware program.
613 table to a disk when existing partitions on that disk are mounted. (The
647 the start or (more commonly) the end of the disk. Resizing the partition
655 MBR conversions work only if the disk has correct LBA partition
656 descriptors. These descriptors should be present on any disk over 8 GiB in
676 Booting after converting an MBR or BSD disklabel disk is likely to be