Lines Matching refs:disk
77 more information on what data structures are damaged when a damaged disk
102 when creating a new partition table (that is, partitioning a blank disk or
108 - On Linux, the p/-p/--print command now shows the disk's model name, as
112 when accessing disk image files, even on Linux.
127 else on the disk. The main reason I know of to do this is if the disk is
177 this feature when gdisk detects that it can't write to the disk under OS
228 if a subsequent command causes changes, they'll be written to disk.
230 would wipe the disk but not create a partition table; to create a blank
256 - Altered warning displayed when run from Windows on non-GPT disk, because
266 …(https://github.com/ceph/ceph/blob/9bcc42a3e6b08521694b5c0228b2c6ed7b3d312e/src/ceph-disk#L76-L81):
271 89C57F98-2FE5-4DC0-89C1-F3AD0CEFF2BE/0xf804 (Ceph disk in creation), and
272 89C57F98-2FE5-4DC0-89C1-5EC00CEFF2BE/0xf805 (Ceph dm-crypt disk in
322 mid-disk that might not be backup GPT data structures, which could
331 - If the GPT data seem to be damaged in some way or if the disk seems to
332 be a hybrid MBR and if the MBR partition(s) don't fit on the disk, the
333 verify (v) function now warns of this condition, and writing the disk if
365 on sector 1: Previously, a disk with multiple 0xEE partitions would
376 VirtualBox's EFI) to ignore the disk.
382 as /dev/disk* devices. The result is that, when using the /dev/rdisk*
384 the disk or rebooting.
391 "gdisk -l" operation will change an MBR disk to a GPT disk without
434 it at the start of the disk AND IF fewer than three partitions are
446 - Changed code that writes the partition table so that a disk sync
474 - Added disk's name to message stating that a disk write was successful.
502 disk (as well as in some other situations).
522 restriction that the size be equal to or less than the disk's sector
525 disk's sector size is larger than the GPTHeader data structure size (512
547 though, so if you suspect a disk may be bad and want to use one of these
572 when converting a disk from MBR format (but, oddly, not when creating a
576 big for the disk.
582 on some disks (particularly those created by Microsoft's disk
652 - Enhanced disk replication features ('u' on the experts' menu in gdisk; -R
654 table from a larger to a smaller disk, so long as all the partitions fit
655 on the smaller disk. In sgdisk, the secondary GPT data are moved
656 automatically if disk sizes don't match. In gdisk, the secondary GPT data
657 are moved automatically if the target disk is smaller than the source
658 disk; if the target disk is larger than the source disk, the user is
664 when smaller alignment is detected on the disk to 300 GB.
691 in which an MBR has overwritten an APM disk.
751 creation of disks with duplicate partitions. When told to create a disk
761 - Enable disk-wipe (-z and -Z) and verification (-v) operations in
762 sgdisk even if the disk is badly damaged.
797 sgdisk). This option randomizes the disk's GUID and all partitions'
798 GUIDs. Intended for use after cloning a disk with a utility that copies
799 the GUIDs intact (such as a raw dd copy) if you want each disk copy to
802 - Added -u/--partition-guid and -U/--disk-guid options to sgdisk. These are
805 disk's GUID. The GUID may be either a fully specified GUID value or 'R'
814 the disk.
826 BIOS to boot with a GPT disk. See http://www.rodsbooks.com/gdisk/bios.html
838 (e.g., files of 0 length passed as disk images).
853 - Changed the sequence in which GPT data structures are written to disk;
862 - Protective MBRs now have disk signatures of 0x00000000, to better
898 possible to convert back to MBR any disk that started that way, provided
899 no partitions were added or resized when the disk was in GPT form; and
959 - Changed the code to create a new MBR unique disk signature whenever a new
963 the existing MBR disk signature in most cases, but this resulted in
964 values of 0x00000000 whenever an empty disk was partitioned, and often in
973 conversion. (This was already done in full-disk BSD-to-GPT conversions.)
1006 count=34" will do this on Linux for a disk with a typical-sized GPT table
1061 - Moved all disk I/O functions to the new DiskIO class. This helps with the
1064 cross-platform disk I/O code.
1073 - Fixed bug that returned incorrect disk size on 32-bit versions of
1076 - Fixed bug that prevented FreeBSD version from working on disk image
1101 more error checking on disk I/O.
1132 end of the disk.
1148 Linux, thus causing problems when editing partition tables in disk images
1170 - Fixed minor display bug that caused number of sectors on the disk to be
1191 - Added the ability to work on disk image files (raw files for virtual
1192 machines, backup images, etc.). The program assumes that all such disk
1202 or BSD disklabel was detected on the disk.
1218 partition creation if there are small bits of free space on the disk.
1276 - Tweaked the disk type identification code to warn users to re-sync their
1280 only have an effect on a poorly partitioned MBR disk that contains an
1282 corrupted disk by using the hybrid MBR for data recovery.
1287 Map (APM) on the disk.
1325 to the ability to boot from a GPT disk, at least on BIOS-based machines.
1329 of the disk using fdisk or other GPT-unaware tools. (GNU Parted will wipe
1343 kernel and/or GCC version.) The disk size, of type uint64_t, was not
1351 - Fixed bug that caused display of options after a disk-write error.
1367 definition is only there to keep MBR-only disk utilities from messing
1368 with the disk.
1392 locations on disk; used in my internal-use-only GPT-wiping program.