Lines Matching full:disk

34 modify disk structures until you explicitly write them to disk, so if you
38 Ordinarily, \fBcgdisk\fR operates on disk device files, such as
41 can also operate on disk image files, which can be either copies of whole
42 disks (made with \fBdd\fR, for instance) or raw disk images used by
43 emulators such as QEMU or VMWare. Note that only \fIraw\fR disk images
45 disk image formats.
48 the disk. If it finds valid GPT data, \fBcgdisk\fR will use it. If
55 type codes may become corrupted if the disk uses unrecognized type codes.
57 GPT\-unaware OS. If you mistakenly launch \fBcgdisk\fR on an MBR disk, you
88 If Windows is to boot from a GPT disk, a partition of type \fIMicrosoft
99 each partition. The intent is to enable future disk utilities to use this
101 help in future disk maintenance. You can use GPT fdisk's relative partition
131 number, the device filename associated with the disk, and the disk's size
186 performance for all of these disk types. On pre\-partitioned disks, GPT
187 fdisk attempts to identify the alignment value used on that disk, but will
193 the alignment value in size. Some disk encryption tools require partitions
200 in\-memory partition table to a disk file using this option. The resulting
211 the partition on the disk. If a corresponding hybrid MBR partition exists,
230 original disk is not recommended.
250 specifies a position 40MiB from the start of the disk. You can specify
277 Verify disk. This option checks for a variety of problems, such as
281 unallocated disk space.
304 table to a disk when existing partitions on that disk are mounted. (The
322 the start or (more commonly) the end of the disk. Resizing the partition
330 MBR conversions work only if the disk has correct LBA partition
331 descriptors. These descriptors should be present on any disk over 8 GiB in
351 Booting after converting an MBR or BSD disklabel disk is likely to be