No gui option in disk utility for new hdd in white unibody mbp

Hello,
i replaced the harddisk in my white unibody macbook with an
Samsung Spinpoint M9T 1TB HDD out of a seagate backup portable drive.
disk utility can erase it, and partition it, but it does not show the option to create a GUI partition.
restoring from time machine backup does not work
installer for leopard, from the original dvd states that it needs that.
what can i do?
hope to hear from you.
ps:
on my imac and my mbp the bootable disk is mac os extended(journaled)
so no 'gui-partition' there

Aha! I only looked at 'format' list, didn't notice the 'option' list.
problem solved.
thank you !

Similar Messages

No Erase option in Disk Utility for an SSD Drive!

Hi guys,
Made a time machine copy on a 500gb external hard drive of my 13" MBP with a HDD currently in it.
Then took my 500gb SSD from an old 15" MBP, removed the HDD and put it in my 13" MBP.
Opened up 13" MBP in restore mode. Chose restore from time machine back up.
Choose the time machine external drive as source. Then chose the SSD drive to restore to.
Said it was erasing the drive... Asked for a password...
I typed in my usual password. It then said the SSD drive couldn't be erased.
Took the SSD out and put the original HDD back in.
Plugged the SSD into a firewire 800 caddy to try erase it in disk utility as an external.
This drive will show up in disk utility but the erase option isn't available.
I can repair the disk but it says the disk is perfectly fine.
I can click on the partition option but everything is greyed out and I can't partition it at all.
This drive will now no longer show up on the desktop or finder.
This is driving me crazy!
Just want to erase the SSD, use time machine to restore onto it and get busy.
Please help!
Thanks,
Chris

Aha! I only looked at 'format' list, didn't notice the 'option' list.
problem solved.
thank you !

Installing a new HDD to a Unibody MBP

Hello everyone,
I'm trying to install a new 7200RPM WD Scorpio Black 320GB HDD onto my new Unibody MBP, but having some issues.
After succesfully installing the HDD itself next to the battery, the computer won't boot up with the OS X disc that came with the MBP. It just spits it out of the machine with a folder with question mark blinking on the screen.
My current HDD is 320GB 5400RPM Hitachi (the stock one), and I have no problems with that hard drive.
what should I do?
Thanks in advance!
Message was edited by: AKBC

Not really sure what's up. When I did mine, I just held the C button down before I started it up and then let go after I got the install screen. I could hear it hitting the CD drive while it started up. So it works fine with the original hard drive? So it doesn't sound like it's the disk. I'm not sure I can help anymore. I'm assuming you checked and made sure the connection to the hard drive is secure and you are in fact using the correct install disk? (I think there are 2 and 1 is the install disk and I'm not sure what the other is)

How do I access Disk Utility for 10.7.1?

How do I access Disk Utility for 10.7.1? I found it in the forums a few weeks ago, used it, then lost the directions. This is a last ditch attempt
to use OS Lion. I parted my hair incorrectly when I installed and have been plagued by the dread rainbow spinning ball in EVERY application. Yes, every. Name one, Safari, Firefox, Text Edit, Mail, Excel, Word, iTunes, Garage Band, Calculator, Calender, iPhoto....yes, every, and I cannot
find a solution that works. I have back up files on two different hard drives 500 gig and 1 terrabyte with all my music, photo and writing files.
I am a writer and a musician so imagine the frustration. OS 10.6 is an option of course. My dedication to Apple and each new OS is deep so
I am hoping that somehow there will a fix, an upgrade, something that does not require me to go bac to the much more endangered species named OS.
hahhaa! Just stalled waiting for the ball to finish with it's random spinning.... SO, this is like a last desperate .... it just did two more stalls.
NO OTHER apps running, just little Firefox holding on for dear life, last desperate request for a fix.
MacKeeper has been great in sending helpful directions for getting the Antivirus to work after it mysteriously decided to stop working, Quite MacKeeper, go to Activity Monitor, force quit helper, start up MacKeeper and run program. It works!
SO before my third stall stops me, please post directions to open disk utility in administration mode so that I can do any further repairs that have not worked by using it from the open system. Also keychain synching stopped working with Lion.
Thanks to any and all who can help.

Press and hold Command-R keys and reboot. You'll then start up in the Lion Recovery HD. You'll find Disk Utility there.
Command-R to the rescue.
Just hold down Command-R during startup and Lion Recovery springs into action. It lets you choose from common utilities: You can run Disk Utility to check or repair your hard drive, erase your hard drive and reinstall a fresh copy of Lion, or restore your Mac from a Time Machine backup. You can even use Safari to get help from Apple Support online. And if Lion Recovery encounters problems, it will automatically connect to Apple over the Internet.

Re: How to Clone Using the Restore Option of Disk Utility

This is a revision to original post:
How to Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the backup or destination volume from the left side list.
3. Click on the Erase tab in the DU main window.
4. Set the format type to Mac OS Extended (Journaled) and click on the Erase button. Wait for volume to remount on the Desktop.
5. Click on the Restore tab in the DU main window.
6. Select the startup or source volume from the left side list and drag it to the Source entry field.
7. Select the backup or destination volume from the left side list and drag it to the Destination entry field.
8. Select the destination drive icon on the Desktop and press COMMAND-I to open the Get Info window. At the bottom in the Ownership and Permissions section be sure the box labeled "Ignore Permissions on this Volume" is unchecked.
9. Double-check you got it right, then click on the Restore button.

There is a checkbox option in the Restore dialog to Erase the Destination. Be sure you uncheck the option.

I used the "erase free space " option in disk utility and now my imac says the disk is full and wont let me download songs. please help!

i used the "erase free space " option in disk utility and now my imac says the disk is full and wont let me download songs. please help!

You could try repairing permissions with disk utility, I don't think you will have the option to repair the drive but you could verify it.
This may help you delete the files that DU made but did not remove when erasing the free space.
http://macosx.com/forums/mac-os-x-system-mac-software/317204-no-disk-space-after -failed-disk-utility-erase-free-space.html
When you get your SL disk it will not have the iLife applications, that would have been on the second install disk that should have been with the computer. I forget which version of iLife you will need for SL but I think it is this http://www.amazon.co.uk/Apple-iLife-Single-User-Mac/dp/B003XKRZES/ref=sr_1_1?ie= UTF8&qid=1409607702&sr=8-1&keywords=apple+ilife+11
A search of the forums will confirm or deny this.
As to whether a clean install will cure your problem, i.e. partition the HDD and install I would expect it to be yes, but there are no guarantees it is an old machine.

HT2055 Disk Utility for OS X 10.9.2

I need a Disk Utility for OS X 10.9.2 to add disk space to a partition and fix permissions.

You will find Disk Utility in your Utilities folder.
Repair the Hard Drive and Permissions - Mavericks, Lion/Mountain Lion
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu. Select Restart from the Apple menu.

Disk utility caps new disk images at 13 in pwd

This sounds crazy, which is why I'm posting it here. I'd love it if someone could try this because I've tried it on two different Mac Mini's (macmini3,1 - aka, 5 usb port version) and the same results. Snow Leopard 10.6.4, fully up to date.
I am making disk images of all the software the faculty here at the university will need to install. Using the GUI version of Disk Utility to create them. So far, three times this has happened. Each time at 13 items. Note that this is 13 ITEMS, not necessarily .dmg's. I tried consolidating dmg's into subfolders during the third go-around, but once the folder I'm dumping all the dmg's into reach 13 items (dmgs, subfolders, whatever), Disk Utility errors out during creating the next dmg.
If someone wants to try this, I'd love to hear the results.

The type of disc being made into a disc image doesn't matter. I'm doing this to back up university software for internal use only, but I've tried it with other content as well.
Storage is not the issue. This is a fresh install of Snow Leopard, with 160gb or so free. the first 13 disc images took about 9gb of space, the second set maybe about 20gb, and the third set about 15gb. Both df -h ./ and Finder's GET INFO show plenty of hard drive space.
This happened after the initial 13 discs and every 13 discs thereafter; no data is moved off the harddrive, it just needs to be moved out of the folder I'm dumping the images into. This is a valid workaround, but it feels like something is wrong.

Can one PPC Mac run Disk Utility for another's HD?

I have a PPC PowerBook that needs help. The Admin users are getting corrupted for some reason. I can still use other Users in Safe Mode.
I have another good PPC G3 desktop. Both running 10.5.8.
I can mount the bad HD on the good Mac's desktop but I can't run Disk Utility for it.
I've mounted with Ethernet and USB. Do I need Firewire? Do I need do try to use Target Mode?
Basically, I'm trying to use the good Mac as a startup disk for the bad one, I think.
Easy way? Thanks! JP
ps: My hunch is Firewire. I don't have any so I'm going to buy a cable soon. Unless someone here stops me! : )

Yes, you need Target Mode Firewire on both, a FW cable, then Disk Utility should be fine from one to the other.
Target mode...
http://support.apple.com/kb/HT1661
Sometimes Laptops need to have the FW cable unplugged & replugged after they'e in t mode to have it finally show up.

Disk Utility (in Recovery Mode) not seeing internal MBP SSD

MacBook Pro 11,3, Retina, 15-inch, Late 2013
Having an odd problem which occurred under both Mavericks (latest build) and Yosemite (10.10.1).
Under Mavericks, I could not boot at all into the Recovery Drive; I would get to the choose language screen and get the beachball of death. I do not recall exactly when this started happening, but it was long after the last update.
To repair my drive, I would boot into Target Disk Mode, hook the MBP to my wife's iMac, and run DiskWarrior to replace the directory on the main drive, and then run Disk Utility for Permissions Repair and Disk Repair, which would usually find no errors. I would then boot back into my account with no problem, but if I tried to boot into the Recovery Drive, it was the same issue.
If I booted from a Clone (made via Carbon Copy Cloner) of the Recovery Drive, I could get into Disk Utility, but the drive would not be recognized.
Flash forward, I did a nuke & pave of the MBP, a clean install of 10.10.1, and then started rebuilding my Mac's identity, per se (been meaning to do this for years; I think I haven't done a full/fresh install since about 10.2).
So I'm rolling along and decide to boot into Recovery Drive -- I'm able to get through almost everything without issue. I am hopeful. I launch Disk Utility, and then I see my drive -- "1 TB Apple SSD..." -- but below it, instead of the drive name, I see "disk0s2". I can't run repairs on anything.
I'm not keen on doing yet another nuke and pave. The system seems to be fine, everything is running without issue, and (bootable) backups are going along fine.
Any thoughts on what might be the issue? I've read something online regarding "Core Storage" issues with how the drive was formatted, but according to my info, I'm on a standard GUID Partition Table.

MacBook Pro 11,3, Retina, 15-inch, Late 2013
Having an odd problem which occurred under both Mavericks (latest build) and Yosemite (10.10.1).
Under Mavericks, I could not boot at all into the Recovery Drive; I would get to the choose language screen and get the beachball of death. I do not recall exactly when this started happening, but it was long after the last update.
To repair my drive, I would boot into Target Disk Mode, hook the MBP to my wife's iMac, and run DiskWarrior to replace the directory on the main drive, and then run Disk Utility for Permissions Repair and Disk Repair, which would usually find no errors. I would then boot back into my account with no problem, but if I tried to boot into the Recovery Drive, it was the same issue.
If I booted from a Clone (made via Carbon Copy Cloner) of the Recovery Drive, I could get into Disk Utility, but the drive would not be recognized.
Flash forward, I did a nuke & pave of the MBP, a clean install of 10.10.1, and then started rebuilding my Mac's identity, per se (been meaning to do this for years; I think I haven't done a full/fresh install since about 10.2).
So I'm rolling along and decide to boot into Recovery Drive -- I'm able to get through almost everything without issue. I am hopeful. I launch Disk Utility, and then I see my drive -- "1 TB Apple SSD..." -- but below it, instead of the drive name, I see "disk0s2". I can't run repairs on anything.
I'm not keen on doing yet another nuke and pave. The system seems to be fine, everything is running without issue, and (bootable) backups are going along fine.
Any thoughts on what might be the issue? I've read something online regarding "Core Storage" issues with how the drive was formatted, but according to my info, I'm on a standard GUID Partition Table.

Cannot boot. volume disappeared from boot option after Disk Utility (GUI) repair

I have a 13-inch MBP with the latest OS X version.
Problem
Yesterday, I went to the Recovery Mode and performed Repair on my boot volume. I was not having a problem, but I just wanted to verify and repair as a regular maintenance. The Disk Utility said some kind of error (I cannot remember, but something about EFI?), and I cannot start my computer since then (question mark folder icon when I try to boot).
I have tried the following
I tried to recover the drive by going into the Recovery Mode, but when I press Option key for boot options, I just have an empty grey screen have no option(not even the recovery volume). I have also tried to enter into the Single User Mode, but it goes straight back to the question mark folder icon. Just in case, I performed PRAM and SMC reset, but still no dice.
Next, I tried to boot with Command+R pressed, and the computer went into Internet Recovery Mode, which works fine. Then, I went to the Disk Utility, and my SSD is on the list with the volume that has OS X(only volume on the entire disk except recovery volume, etc). I use FileVault2, and I can unlock the volume and mount it without any problem. When I do Verify Disk, it says that the volume appears to be OK. Also, performed fsck using Recovery Mode's Terminal, and it still says that "The volume Macintosh HD appears to be OK," the exact same message that I got from GUI disk utility. I also tried to unlock and set the volume as a start-up disk, but I still get the question mark folder icon.
If you need further details, please let me know! Please save me!

Hello jukim,
Thanks for using Apple Support Communities.
Great troubleshooting done so far. Since you're still booting to the flashing question mark, even after repairing the disk, the next step would be to reinstall OS X.
A flashing question mark or globe appears when you start your Mac
https://support.apple.com/kb/TS1440
OS X Mavericks: Reinstall OS X
http://support.apple.com/kb/PH13871
Take care,
Alex H.

Disk Utility: for bad blocks on hard disks, are seven overwrites any more effective than a single pass of zeros?

In this topic I'm not interested in security or data remanence (for such things we can turn to e.g. Wilders Security Forums).
I'm interested solely in best practice approaches to dealing with bad blocks on hard disks.
I read potentially conflicting information. Examples:
… 7-way write (not just zero all, it does NOT do a reliable safe job mapping out bad blocks) …
— https://discussions.apple.com/message/8191915#8191915 (2008-09-29)
… In theory zero all might find weak or bad blocks but there are better tools …
— https://discussions.apple.com/message/11199777#11199777 (2010-03-09)
… substitution will happen on the first re-write with Zeroes. More passes just takes longer.
— https://discussions.apple.com/message/12414270#12414270 (2010-10-12)
For bad block purposes alone I can't imagine seven overwrites being any more effective than a single pass of zeros.
Please, can anyone elaborate?
Anecdotally, I did find that a Disk Utility single pass of zeros seemed to make good (good enough for a particular purpose) a disk that was previously unreliable (a disk drive that had been dropped).

@MrHoffman
As well pointed your answers are, you are not answering the original question, and regarding consumer device hard drives your answers are missleading.
Consumer device hard drives ONLY remap a bad sector on write. That means regardless how many spare capacity the drive has, it will NEVER remap the sector. That means you ALWAYS have a bad file containing a bad sector.
In other words YOU would throw away an otherwise fully functional drive. That might be reasonable in a big enterprise where it is cheaper to replace the drive and let the RAID system take care of it.
However on an iMac or MacBook (Pro) an ordinary user can not replace the drive himself, so on top of the drive costs he has to pay the repair bill (for a drive that likely STILL is in perfect shape, except for the one 'not yet' remaped bad block)
You simply miss the point that the drive can have still one million good reserve blocks, but will never remap the affected block in a particular email or particular song or particular calendar. So as soon as the file affected is READ the machine hangs, all other processes more or less hang at the same moment they try to perform I/O because the process trying to read the bad block is blocking in the kernal. This happens regardless how many free reserve blocks you have, as the bad block never gets reallocated, unless it is written to it. And your email program wont rewrite an email that is 4 years old for you ... because it is not programmed to realize a certain file needs to be rewritten to get rid of a bad block.
@Graham Perrin
You are similar stubborn in not realizing that your original question is awnsered.
A bad block gets remapped on write.
So obviously it happens at the first write.
How do you come to the strange idea that writing several times makes a difference? How do you come to the strange idea that the bytes you write make a difference? Suppose block 1234 is bad. And the blocks 100,000,000 to 100,000,999 are reserve blocks. When you write '********' to block 1234 the hard drive (firmware) will remap it to e.g. 100,000,101. All subsequent writes will go to the same NEW block. So why do you ask if doing it several times will 'improve' this? After all the awnsers here you should have realized: your question makes no sense as soon as you have understood how remapping works (is supposed to work). And no: it does not matter if you write a sequence od zeros, of '0's or of '1's or of 1s or of your social security number or just 'help me I'm hold prisoner in a software forum'.
I would try to find a software that finds which file is affected, then try to read the bad block until you in fact have read it (that works surprisngly often but may take any time from a few mins to hours) ... in other words you need a software that tries to read the file and copies it completely, so even the bad block is read (hopefully) successful. Then write the whole data to a new file and delete the old one (deleting will free the bad block and ar some later time something will be written there and cause a remap).
Writing zeros into the bad block basically only helps if you don't care that the affected file is corrupted afterwards. E.g. in case of a movie the player might crash after trying to display the affected area. E.g. if you know the affected file is a text file, it would make more sense to write a bunch of '-' signs, as they are readable while zero bytes are not (a text file is not supposed to contain zero bytes)
Hope that helped ;)

Disk utility finds new errors after every reboot

My problem: every time I reboot my computer, disk utility shows minor corruption of the catalog, attributes, and free space maps on my internal drive. If I boot into the Recovery partition and use Disk Utility to repair the drive, the repair succeeds, and runnin Verify Disk shows a clean file system. But once I boot into the OS from the HD, shut down, and restart, a new set of disk errors appears. The errors are never exactly the same (in mismatch of clusters, for example) but are always off by a few percent.
Things that may be related:
This is a new (1-wk-old) MBP 17" (late 2011 model), which I bought to replace an older 15" MBP running OSX 10.6. I used Migration Assistant to move my data and apps from a Time Machine backup of the old laptop to the new laptop. I then made a Time Machine backup of the new laptop, replaced the factory HD with a Seagate Momentus 720GB, 7200 rpm drive, and used Time Machine to do a complete restore of OS and data onto the new drive. I later used Bootcamp assistant to create an NTFS partition (which doesn't ever show errors).
Things I've already tried to fix the problem that haven't worked:
--Repaired disk permissions as well as the disk structure.
--Using the online recovery tool to do a complete reinstallation of Lion (preserving my data and apps, so not a clean install).
--Using TechToolPro DVD to do a deeper analysis and repair of the disk's volume structure. The repair succeeded, but the disk errors came right back.
--Uninstall every utility or extension that might possibly affect the hard drive.
--Disable all login items using the Accounts preferences pane.
--Disabled Spotlight by moving the entire volume into the Private area in Spotlight preferences.
--Reset the PRAM.
--Reset the SMC.
No joy from any of these. I haven't tried running fsck (is there any reason to?). I'd love to track down the program that is causing the disk corruption, but don't know how to do that.
I would be most grateful for any suggestions on diagnosing and permanently fixing this problem, as it does seem to make my system unstable and prone to crashing.

Thanks for responding. Yes, I should have mentioned that I used the TechToolPro boot DVD to do a thorough SMART scan on the drive as well as a full scan for bad sectors. No problems were found. I also did a long scan of the RAM to rule out memory errors.
I did remove the new drive and replaced it, taking extra care to ensure the connector was seated properly. But the disk corruption/repair/corruption cycle still reoccured.
I haven't put the factory drive back in to check whether the problem affects that (smaller, slower) drive as well. If it does, should I conclude that I have a H/W problem with, e.g. the drive controller chip or the drive cable in the laptop?
I wonder if this might be related to another problem I'm seeing with the laptop, which is that the lid closure doesn't work--the OS isn't able to detect when the lid is closed. It looks like the wire to the sensor goes through the same cable bundle as the SATA cable. Perhaps there is a defect in that bundle or connector.
I will try the factory disk. If the problem doesn't show up with that, then I guess I should focus again on the possibility of a defective HD. Is there some utility other than TechTool that would do an even more thorough check of the HD?

Unable to secure erase: "Security Options" in Disk Utility greyed out.

Ancient eMac running Leopard. I have moved data to new Mac and am ready to erase old computer and sell/give away.
Went to "Erase" tab in Disk Utilities and both the "Volume Format" option and "Security Options" fields/buttons are greyed out and uneditable. According to instructions, to erase the data I need to select "Security Options" to proceed to erase all the data on my hard drive.
How do I "ungrey" that button? Is there a lock somewhere to unlock? Something to disable first?

You cannot erase the hard drive of the eMac when it is in use. You have to insert the Mac OS X install disk, boot up from there and then erase the disk from the Disk Utility software included.

External drive not recognised in Finder or Disk Utility on new Mini

Hi,
I've just bought a new Mac Mini and it won't recognise my Seagate Expansion drive in either Finder or Disk Utility. The drive is fully accessible on my old Macbook (running Snow Leopard), and ran fine on my old iMac running Mavericks. I've tried the troubleshooting tips in other threads - Seagate External Hard Drive does not work on Yosemite - but since they refer to people upgrading to Yosemite, I'm wondering if this might be down to the hardware in the latest Mini models? Any info or ideas on what to try next would be hugely appreciated!
Thanks.

- Do other external USB drives work on your Mini?
- If you go to System Report (click on Apple icon in upper left and select About this Mac>More Info>System report) what shows for the drive under Hardware>USB? Yo should see the enclosure chip as well as the drive itself.
- Tr resetting the SMC and PRAM
- If you purchased the Mac within the last 90 days you still have free telephone support
Complimentary Support (USA)

No gui option in disk utility for new hdd in white unibody mbp

Similar Messages

Maybe you are looking for