Benches macOS

9

Formats and Partitions of Disk Images

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I am confused by the options presented when creating a new disk image using Disk Utility. Disk Utility Help is flawed. It has very limited info and some of the info it does have refers to options that do not exist. I wanted to understand what the following choices effect:

1.In the partitions menu the choices are:

Hard Disk

CD/DVD

No partition map

Single partition - Apple Partition Map

Single partition - Master Boot Record Partition Map

Single partition - GUID Partition Map

Single partition - CD/DVD

Single Partition - CD/DVD with ISO data

2.In the Image Format the choices are:

read/write disk image

sparse disk image

sparse bundle disk image

3. I also notice that certain sizes of disk image are not available with certain Volume Formats. The minimum disk image size with Mac OS Extended is 5MB while with Mac OS Extended (journaled) it is 10MB and with Mac OS Standard and MS-DOS (FAT) 2.5MB and 5MB are available. What are the consequences of these format choices?

I have found the info in Disk Utility's help very thin and confusing; like this line: "If you don’t need to add more files to the disk image, choose read-only." There is no read-only option I can find.

As far as all the different partition options, I can find almost no info that is useful.

I can find no info at all related to sparse and sparse bundles.

I have check the help each time a new update has come out.

9 replies

Sign in or join Beachball Help to reply.

  1. 0

    CFSchukat

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Looking into the
    diskutil manpage explains most of the different partition formats. Most importantly, the Single Partition formats are APM (to start up a PowerPC-based Macintosh computer, *to use the disk as a non-startup disk with any Mac*, or to create a multi-platform compatible startup disk,) MBR (This is the DOS/Windows-compatible partitioning scheme,) GUID (This is the partitioning scheme used to start up an Intel-based Macintosh computer.) This should explain some confusion. Googling "no partition map" brought up a comment that such (lack of) partition was used by OS9 to create disk images. Overall, this seems to be the Swiss Army Knife functionality to create a plethora of suitable images.

    CD/DVD images (should) adhere to standards such as ISO-9660 and its extension Joliet, which has to do with the filesystem on such media. It's generic standards to read CD/DVD data on other operating systems. I think this is more a power-user choice, especially if you want your disk image to burn to CD/DVD.

    This explanation is not complete by any means, but I think it illustrates some differences.

    As for image format, empty images can be read/write, which generates the specified size, in full. Sparse Images are dynamic in size, as they grow when adding data until they reach their specified capacity. Apple developed Sparse Bundles with Leopard, which (as the name suggests) are multiple files in a folder which the system recognizes as one convenient file, and you can open them by choosing "Show Package Content." The benefit of Sparse Bundles seem to be their internal, multi-file structure, all part of one, but not exceeding 8MB. These files are called Bands, and if you use time-machine and you added a small file to your 8GB Sparse disk image, it will only backup the small internal Band that got changed - and NOT the whole 8GB.

    Sparse Images are backwards compatible, Sparse Bundles are Leopard and upward.

    As example, I just want to create a disk image to safely keep personal files (medical, tax, etc) private. This should function like any extra peripheral hard drive of my mac. So, I generate a 4.7GB volume, Mac OS X Extended (Journaled) 256-bit AES decrypted, Single Partition APM, Sparse Bundle.

    With that, I should be able to use such image transparently like any other hard drive on my mac, with the benefit of encryption, labels, comments, etc.

    Again, different specs for different purposes. For most people, a simple sparse image/bundle with default values is the way to go.

  2. 0

    baltwo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Launch the Terminal.app in /Applications/Utilities/, copy & paste this command in, and hit the return key:

    *man diskutil*

    that'll tell you everything about the various Disk Utility functions.

    Likewise, *man hdiutil* describes how to manipulate disk images and *man drutil* describes how to interact with CD/DVD burners.

  3. 0

    toddlydavis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well, that was very interesting stuff, but it does not answer many of my questions. I understand how to implement the various options, I just do not understand the effects.

  4. 0

    baltwo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Exactly what effects are you trying to determine?

  5. 0

    KJK555

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    First of all, don't confuse creating partitions with making images. Once a volume or disk is created

    you can make an image of the volume (on a fixed drive) or a disk (such as a cd/dvd).

    The image will copy whatever file system is on the volume or disk.

    You are not limited to just volume or disk images, you can make an image of a folder as well

    if you are only interested in copying data.

    Kj

  6. 0

    toddlydavis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I am not sure what effects I am trying to determine. I do not understand the consequences of certain choices of the options presented.

    Case in point. In the partition menu for creating a new image there is a choice for "Hard Disk" and "Single partition - GUID Partition Map" I thought that GUID Partition Map was a type of Hard Disk partition. Also there is the choice for "No partition map". What would happen to my new image if I used this option?

    I would also like to know the effects of selecting a sparse bundle vs a sparse. Are there advantages to one over the other?

  7. 0

    toddlydavis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    And here is an interesting addition:

    I created an encrypted sparse image alongside my regular encrypted image. If I change data in the the sparse image it gets backed up by Time Machine even while the image is still mounted while changes to the regular encrypted image only gets backed up by Time Machine when it is not mounted. Does this sound right?

  8. 0

    CFSchukat

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Looking into the
    diskutil manpage explains most of the different partition formats. Most importantly, the Single Partition formats are APM (to start up a PowerPC-based Macintosh computer, *to use the disk as a non-startup disk with any Mac*, or to create a multi-platform compatible startup disk,) MBR (This is the DOS/Windows-compatible partitioning scheme,) GUID (This is the partitioning scheme used to start up an Intel-based Macintosh computer.) This should explain some confusion. Googling "no partition map" brought up a comment that such (lack of) partition was used by OS9 to create disk images. Overall, this seems to be the Swiss Army Knife functionality to create a plethora of suitable images.

    CD/DVD images (should) adhere to standards such as ISO-9660 and its extension Joliet, which has to do with the filesystem on such media. It's generic standards to read CD/DVD data on other operating systems. I think this is more a power-user choice, especially if you want your disk image to burn to CD/DVD.

    This explanation is not complete by any means, but I think it illustrates some differences.

    As for image format, empty images can be read/write, which generates the specified size, in full. Sparse Images are dynamic in size, as they grow when adding data until they reach their specified capacity. Apple developed Sparse Bundles with Leopard, which (as the name suggests) are multiple files in a folder which the system recognizes as one convenient file, and you can open them by choosing "Show Package Content." The benefit of Sparse Bundles seem to be their internal, multi-file structure, all part of one, but not exceeding 8MB. These files are called Bands, and if you use time-machine and you added a small file to your 8GB Sparse disk image, it will only backup the small internal Band that got changed - and NOT the whole 8GB.

    Sparse Images are backwards compatible, Sparse Bundles are Leopard and upward.

    As example, I just want to create a disk image to safely keep personal files (medical, tax, etc) private. This should function like any extra peripheral hard drive of my mac. So, I generate a 4.7GB volume, Mac OS X Extended (Journaled) 256-bit AES decrypted, Single Partition APM, Sparse Bundle.

    With that, I should be able to use such image transparently like any other hard drive on my mac, with the benefit of encryption, labels, comments, etc.

    Again, different specs for different purposes. For most people, a simple sparse image/bundle with default values is the way to go.

  9. 0

    toddlydavis

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks,

    Good Stuff. That is great info about the Sparse Bundle. I will be switching all my images to Sparse Bundles. I look forward to Time Machine only needing to back up changed parts of a image. Very Cool and should help preserve more space on my Time Machine Drive.

    Couple of questions you raised though. Why create your personal files image as a Single Partition APM? Why not no partition map, or Guid Partition or Hard Disk?