Apple + How To. How to Manage Disks and Volumes with OS X’s Disk Utility. Posted on November 3rd, 2015 by Kirk McElhearn If you need to format, partition, or otherwise work with hard drives on a Mac, Apple's Disk Utility is the tool you use.
![Fat32 vs mac os extended Fat32 vs mac os extended](http://www.intego.com/mac-security-blog/wp-content/uploads/2015/10/du3.png)
Paul, Is this a Mybook 'Studio?' Hmmm, I wasn't aware that these came pre-formatted as case-sensitive. Then again, I wouldn't expect them to be journaled, either. Just goes to show how much I know 😉 For use with Time Machine, a volume must be formatted as 'Mac OS Extended (journaled).' It should never be case-sensitive. Notice that I say 'volume.' The drive, itself, needs to be using the 'GUID' partition scheme for an Intel Mac, and the 'APM' partition scheme for a PPC Mac.
Probably, you'll need to format (or partition) the drive. My guess would be that it is using either the 'APM' scheme, or worse, the Windows-centric 'MBR' scheme (which would render it completely useless for Time Machine). At the very least, you'll need to format the volume to get rid of the case-sensitivity.
![Mac os extended vs journaled Mac os extended vs journaled](/uploads/1/2/5/4/125449009/163599795.jpg)
In other words, it would be prudent to copy the data off of the drive. That said, the software you will find 'pre-loaded' on the drive is pretty useless in Leopard, IMO. Paul, Is this a Mybook 'Studio?' Hmmm, I wasn't aware that these came pre-formatted as case-sensitive. Then again, I wouldn't expect them to be journaled, either. Just goes to show how much I know 😉 For use with Time Machine, a volume must be formatted as 'Mac OS Extended (journaled).' It should never be case-sensitive.
Notice that I say 'volume.' The drive, itself, needs to be using the 'GUID' partition scheme for an Intel Mac, and the 'APM' partition scheme for a PPC Mac. Probably, you'll need to format (or partition) the drive.
My guess would be that it is using either the 'APM' scheme, or worse, the Windows-centric 'MBR' scheme (which would render it completely useless for Time Machine). At the very least, you'll need to format the volume to get rid of the case-sensitivity. In other words, it would be prudent to copy the data off of the drive.
That said, the software you will find 'pre-loaded' on the drive is pretty useless in Leopard, IMO. Scott, Many thanks for the reply. I am new to Mac and need all the help I can get. Regarding your reply, let me clarify a couple of things. The drive is a Mybook Studio I purchased from an Apple Store. It was pre-formatted as extended (journaled) NOT case sensitive.
The only reason I mentioned case sens is that I saw in another thread in this forum that someone had a similar volume that was case sensitive. I understand from your posting that I want the volume to be just extended (journaled). Is this correct? Also, regarding the drive itself, mine is listed as APM. I do have an Intel Mac (Core2Duo).
Given this, do I need to reformat it as GUID or is it OK as APM? Thanks again, Paul. Paul, As Nerowolfe stated, you'll need to change the partition scheme from APM to GUID. This can be accomplished by formatting or by partitioning.
Since this is a 1 TB drive (right?), you might want to partition it with 2 volumes: One for use with Time Machine, and one to use as you see fit for additional storage. The partition scheme is chosen in the 'Options.' Dialogue of the partition tab in Disk Utility. If you do create multiple partitions (half and half would be a good place to start), make sure you use the first partition for Time Machine, and the second for your own stuff (the first one will be on top in the graphical representation shown in Disk Utility; you'll understand when you see the partition tab).
This way, you can expand the Time Machine volume at any later time by deleting the second partition. Disk Utility allows this dynamic re-sizing of volumes, but volumes can only be expanded toward the end of the drive, when a volume that comes after is deleted to create the room.
I fully agree that you want to keep your Time Machine Volume HFS+ (Journaled and case insensitive). You're likely to get both subtle and obvious issues if you use any case sensitive HFS+ format. However, I disagree with the statement about the need for GUID partitioning. This is not needed for removable drives such as Firewire or USB drives, even if you're going to boot off them.
To make your Firewire / USB drives compatible with both Intel- and PPC-based Macs, use APM partitioning, and then make your Time Machine volume HFS+ (Journaled, case insensitive). Make all internal drives on Intel machines GUID-based. My understanding about APS vs. GUID where booting Macs is concerned is this: You need to have a GUID-based destination when running the OS X installer on Intel machines.
You need to have an APS-based destination when running the OS X installer on PPC machines. However, once OS X has been installed, you can copy the system from a GUID partition to an APS partition and it can be used to boot the machine. We have a number of Firewire drives with APS partitioning that contain both Intel and PPC booting systems, either copies of various DVDs, or hand-built loads that we use for a variety of purposes. I wasn't describing things quite right: it's not a matter of the drive being fixed or removable, it's just that I tend to have systems with bootable internal system+user drives and removable external data drives.
To keep things simple, the internal drive wants to be GUID-based on Intel machines (so that you can install systems on to it) and the external drive wants to be APS-based on all machines (so that you can plug it in to any Mac). Time Machine, however, may be an exception to the rule; it looks like it requires GUID partitioning on Intel Macs. The issue of APS and GUID where booting Leopard is concerned is discussed here. Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only.
Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.