Lines Matching full:disk
30 want to make one or two quick changes to a disk. (The program may query the
35 Ordinarily, \fBsgdisk\fR operates on disk device files, such as
38 can also operate on disk image files, which can be either copies of whole
39 disks (made with \fBdd\fR, for instance) or raw disk images used by
40 emulators such as QEMU or VMWare. Note that only \fIraw\fR disk images
42 disk image formats.
53 partitions with the Mac OS X Disk Utility program and Linux partitions
57 the disk. If it finds valid GPT data, \fBsgdisk\fR will use it. If
69 partition type codes may become corrupted if the disk uses unrecognized
106 If Windows is to boot from a GPT disk, a partition of type \fIMicrosoft
117 each partition. The intent is to enable future disk utilities to use this
119 help in future disk maintenance.
174 in\-memory partition table to a disk file using this option. The resulting
197 help if a disk utility, OS, or BIOS doesn't like the CHS values used by the
209 the partition on the disk. If a corresponding hybrid MBR partition exists,
221 Move backup GPT data structures to the end of the disk. Use this option if
222 you've added disks to a RAID array, thus creating a virtual disk with space
224 GPT data structures to the end of the disk, where they belong.
229 sectors on the disk. A script may store this value and pass it back as
236 sectors on the disk. A script may store this value and pass it back as
252 Convert an MBR or BSD disklabel disk to a GPT disk. As a safety measure, use of
258 Randomize the disk's GUID and all partitions' unique GUIDs (but not their
259 partition type code GUIDs). This function may be used after cloning a disk
285 but the original disk is not recommended. This option will work even if the
286 disk's original partition table is bad; however, most other options on the
304 you to specify a valid disk device filename.
308 Convert disk from GPT to MBR form. This option takes from one to four
324 disk
338 the disk. Note that if used on a completely blank disk, this is likely to
349 most other operations, fail on a damaged disk. If you want to prepare a
350 disk you know to be damaged for GPT use, you should first wipe it with -Z
352 disk's original partition table is bad; however, most other options on the
366 to disk.
374 way has no effect on their disk space allocation; it only alters their
382 \-G option on the new disk.
387 partitions on the disk. If you want them to match, you can use this option.
403 will attempt to convert BSD disklabels stored on the main disk when
415 .B \-U, \-\-disk-guid=guid
416 Set the GUID for the disk. The GUID may be a complete GUID or 'R' to set a
425 Verify disk. This option checks for a variety of problems, such as
429 command displays a summary of unallocated disk space. This option will work
430 even if the disk's original partition table is bad; however, most other
441 want to repartition a GPT disk using \fBfdisk\fR or some other GPT\-unaware
444 disk has been repartitioned for MBR using a GPT\-unaware utility; however,
446 first or end of the last MBR partition. If you use it on a valid GPT disk,
454 more suitable if you want to repartition a disk after using this option,
455 and completely unsuitable if you've already repartitioned the disk.
478 Non\-GPT disk detected and no \fI\-g\fR option
491 Disk replication operation (-R) failed
506 table to a disk when existing partitions on that disk are mounted. (The
531 the start or (more commonly) the end of the disk. Resizing the partition
539 MBR conversions work only if the disk has correct LBA partition
540 descriptors. These descriptors should be present on any disk over 8 GiB in
560 Booting after converting an MBR or BSD disklabel disk is likely to be
