Mac mini disk utility error
Yesterday I tried doing the OS 10.4.4 update and when my computer rebooted, it kept on restarting the window manager every 5 seconds or so. I thought there might be a problem with the install,so I decided to reinstall 10.4.2 from the install disk. When it came to the second disk, the install kept failing. I had put in a new 1GB memory card in, so I pulled that out and put back the original 512 MB card in case that might be the problem. 10.4.2 installed, but when I went through to install the combo update for 10.4.4, it kept failing (don't know the error. It was on a dialog box). I read somewhere on the forum to try the Disk Utility program to check my disk and when I did, the repair failed. It said:
Keys out of order
Re-building B-tree
Error: The underlying task reported failure on exit.
Help?
Jonesy is correct. You have some file directory damage. The file directory is the document that tells your Mac where all the files are. A simple re-install of Mac OS X will not overwrite this kind of error. You have two options: erase and install (after backing up all your important files) to erase the errors or purchase a third party utility, like that is more sophisticated than Apple's own Disk Utility at repairing these kinds of errors.
-Doug
Similar Messages
-
Disk Utility Error: The underlying task reported failure on exit 1
#!/bin/bash
# Author : Bill Hernandez
# Location : Plano, Texas
# Updated : Saturday, June 6, 2009 (1:48 PM)
# script name : setdisk_ownerenabled
# make sure to set permissions to execute
<hr>
# Description :
<hr>
# I've noticed that sometimes when using disk utility I cannot repair permissions, or I might get :
# ERROR: The underlying task reported failure on exit 1
# This shell script seems to have solved the problem.
# It worked very well for me,
# IF YOU USE THIS SCRIPT, IT IS AT YOUR OWN RISK...
# DO NOT USE IT UNLESS YOU UNDERSTAND WHAT IT DOES
# After running it, it is best to restart before using Disk Utility again
<hr>
# Details :
<hr>
# After partitioning a disk using "Disk Utility", and then begin using it, at some point I would get
# an arror message when trying to save to one of the partitions, yet when I looked at the permissions
# everything looked fine. I would then try to use Disk Utility to repair permissions and end up with a
# cryptic error that pretty much told me nothing.
# I noticed that while in Disk Utility, if I selected a partition the lower LH corner of the dialog
# showed : Owners Enabled : No
# I tried selecting the partitions at the Desktop and doing a (CMD-I) and at the very bottom of each
# info dialog there was a checkbox :
# [ ] ignore ownership of this volume
# which I would check, even after logging in as root, and I couldn't seem to get a consistent way
# to get rid of the permissions dialog failure, so I found the vsdbutil command which can be used
# as follows to get partition, or disk info :
# $ vsdbutil -c /Volumes/driveor_partitionname
# ----> Permissions on '/Volumes/driveor_partitionname' are enabled.
# if it is not enabled you can enable the disk or partition using :
# $ vsdbutil -a /Volumes/driveor_partitionname
# It will set "Owners Enabled : Yes"
# This below script loops through the mounted disks, partitions, etc. and gives you information.
# You can leave the three flags below all set to TRUE, or selectively use what you want and change
# the rest to false...
<hr>
# CHOOSE {"TRUE", "FALSE"}
<hr>
getvolumestatus="TRUE" # get "Owners Enabled : (Yes|No)" status
setvolumestatus="TRUE" # set "Owners Enabled : Yes"
list_volumes="TRUE" # show volume names
<hr>
# DO NOT CHANGE ANYTHING BELOW HERE
<hr>
if [ $getvolumestatus == "TRUE" ]; then
echo '============================='
echo '$getvolumestatus'
echo '============================='
# get "Owners Enabled : (Yes|No)" status
for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
vsdbutil -c $i
done
fi
<hr>
if [ $setvolumestatus == "TRUE" ]; then
echo '============================='
echo '$setvolumestatus'
echo '============================='
sudo echo -n
# set "Owners Enabled : Yes"
for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
sudo vsdbutil -a "$i"
echo "setting Owners Enabled : Yes for ---> $i"
done
fi
<hr>
if [ $list_volumes == "TRUE" ]; then
echo '============================='
echo '$list_volumes'
echo '============================='
for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
echo $i
done
fi
<hr>
As it turns out, this didn't completely solve the problem, it solved part of the problem.
Here is a summary to the root cause of the problem.
SUCCESS...
Problem Summary : The system crashed and would hangup during boot, tried many things, until I eventually erased the disk and started over again.
iMacG5 24 GHZ Intel with One internal disk partitioned into 3 logical drives
Cub_1 OS X 10.5.7
Cub_2 OS X 10.5.7 (Carbon Copy Cloner backup of Cub_1)
Cub_3 OS X Server 10.5.7 (standard os x server setup)
At some point after setting up standard preferences, OS X Server crashed.
When I tried to restart, the machine would hang up during boot.
Finally after several attempts, ran Disk Utility from install dvd and repaired Cub_3
When I tried to run "Repair Permissions" on Cub_3 from install dvd, I got an error
Disk Utility Error: The underlying task reported failure on exit 1.
Rebooted, and started in single user mode (CMD-S) during boot until I saw the unix commands on the screen
RAN : root # fsck -fy
Then I began seeing the same command filling the screen :
posix_spawnp("/usr/sbin/mDNSResponder") could not find file or directory
Called Enterprise Support and spoke to Frank Alcorn, he said this was most likely a permissions problem and asked me to try repairing permissions from the install dvd. I told him about the error, but nevertheless I tried it again and got the same Disk Utility Error: The underlying task reported failure on exit 1..
He asked me to try booting into single user mode again, and to try
root # chmod 775 /
root # reboot
During the reboot process the machine got hung up again, and could not get the single user mode to work at all.
Frank said the command needed to be :
root # chmod 1775 /
Frank asked me if I had changed anything in file sharing, and I told him I had. He asked me what I had shared, and I said the entire drive Cub_3. He asked me what I had done for permissions, if I had denied permissions to anyone. I told him that I had set myself up as the only user that could have access to it, and when he said that's where the problem was the lightbulb went off, and it made sense.
Shortly after I set the sharing preferences is when the server crashed. It all makes sense now...
Frank said not to share the entire disk, only portions (share points) of it. I had done this in Panther Server, and Tiger Server and it worked fine, but apparently Leopard Server works a little differently, maybe more secure.
It seems to me that if sharing the entire disk, which is what I needed would cause such a problem there should have been some sort of warning from the operating system, but there wasn't. I had run into this problem several times over the past three weeks since I had started working with Leopard Server, but in each case I ended up re-installing OS X Server and starting over again.
I told him I would try to reboot from the OS X partition (Cub_1) and try it from there.
He asked me to let him know if it worked, and I said I would...
Problem FIX :
I booted back into the partition containing OS X (Cub_1) and did the following via the Terminal.
$ su - root
$ chmod 1775 /
$ reboot
During the reboot process I held down the (OPTION) key, and selected Cub_3 (the os x server partition) and sure enough after a few minutes of holding my breath the login window magically appeared. So I logged in, and did not have to re-install the server. Hallellujah....
This solved the boot hang problem. It is great to finally have an answer. In retrospect it makes sense, but that's why its hindsight...
The reason for sharing the entire disk in my mind was that since I was the only user on the system, it was easier to have one disk mounted on my workstation rather than several folders. It made sense to me, it still does. I don't need a bunch of folders, just one disk is easier... -
My 500gb mac mini disk space is being used by something called "backup" (451gb). I have nothing left to work with. I can't find where this file(s) is so I can delete it.
For information about the Other category in the Storage display, see this support article. If the display seems to be inaccurate, try rebuilding the Spotlight index.
Empty the Trash if you haven't already done so. If you use iPhoto, empty its internal Trash first:
iPhoto ▹ Empty Trash
Do the same in other applications, such as Aperture, that have an internal Trash feature. Then restart the computer. That will temporarily free up some space.
According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation—not the mythical 10%, 15%, or any other percentage. You also need enough space left over to allow for growth of the data. There is little or no performance advantage to having more available space than the minimum Apple recommends. Available storage space that you'll never use is wasted space.
See this support article for some simple ways to free up storage space.
You can more effectively use a tool such as OmniDiskSweeper (ODS) or GrandPerspective (GP) to explore the volume and find out what's taking up the space. You can also delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one. Note that ODS only works with OS X 10.8 or later. If you're running an older OS version, use GP.
Deleting files inside a photo or iTunes library will corrupt the library. Changes to such a library must be made from within the application that created it. The same goes for Mail files.
Proceed further only if the problem isn't solved by the above steps.
ODS or GP can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
Install the app in the Applications folder as usual. Quit it if it's running.
Triple-click anywhere in the corresponding line of text below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C.
For ODS:
security execute-with-privileges /A*/OmniDiskSweeper.app/*/M*/* 2>&-
For GP:
security execute-with-privileges /A*/GrandPerspective.app/*/M*/* 2>&-
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Paste into the Terminal window by pressing command-V. You'll be prompted for your login password.
The application window will open behind other open windows. When you scan a volume, the window will eventually show all files in all folders, sorted by size. It may take a few minutes for the app to finish scanning.
I don't recommend that you make a habit of doing this. Don't delete anything as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.
When you're done with the app, quit it and also quit Terminal. -
My daughter told me her Mac mini isn't booting up past the grey screen. I put in the install disk and started it up pressing "C" and used Disk Utility to attempt to figure out what's up. I got the following error message:
Could not repair due to underlying task failure on exit (-9972)
Does this mean the hard drive is toast? I don't have any HD repair software-with all my Macs I've never run across a problem that the boards here or Disk Utility couldn't fix for me. I don't know if she damaged the drive (she claims the cat chewed on the edge of the mini-sounds a bit like the "dog ate the homework"), or if it failed. It was purchased last year when Tiger was released, so it should still be under warranty. Any ideas about what I could try next?
Thanks
~margaret
17 iMac G4 1.25GHz 160GIG HD Mac OS X (10.4.3) G4 iBook, Mac mini, 10G iPod, iPod mini (pink!), Apple IIGSDale, although the -9972 error is probably some serious data error on the drive, which can sometimes be solved by an Erase & Install of Mac OS X, the fact that the Hardware Test reports an issue probably means that the data error was caused by physical damage on the drive.
I have to say that I find your post(s) most unhelpful. It' true that the informatin contained in them can be useful, however, you could have made the effort to sort it for iMargB. The fact that you didn't, plus your posting of the exact same post in two different threads, makes me feel that you are in a hurry, and that you sacrifice quality to quantity. Trying to help as many people as possible is a good thing, however, we are here to help (or to be helped), not to overwhelm people with information, hoping that they will figure it all out on their own.
iMargB, the Hardware Test is not part of Mac OS X, it is a system-specific volume, which explains why it is included on your original disc rather than on the Tiger one. Your guess of using the latest OS's Install disc was a good one though, when it comes to using Disk Utility for example : attempting to repair a Tiger installation with a Panther disc is not a good idea, as it might damage it instead, because of the differences between Panther and Tiger.
Although I know little about the Hardware Test's error messages, the "Master" part is not what would worry me, as it could just be the position of your hard drive's jumper (which could be Master, Slave, or Cable Select). However, if the Mass Storage test is failing, I would suspect a hardware issue with the drive itself. Hardware Test is known to miss a few things sometimes, but the reverse isn't true. Thus if it reports a bad drive, I think it is safer to assume that there is an issue than to assume that Hardware Test is wrong. Moreover, the "Invalid Node Structure" is very likely due to physical damage (as I already said), therefore, zeroing out all data and reisntalling Mac OS X or using Disk Warrior could be very temporary fixes.
If you have a FireWire cable, I would suggest booting your Mini in FireWire Target Disk Mode to retrieve as much data as you can, with another Mac such as your iMac or iBook. Instructions can be found here. There may still be a chance that the other Mac could see the drive, so not all your data would be lost. Then, I would take it to Apple for repair, as the drive could be failing. -
MacBook Pro Stuck in Recovery Loop; Disk Utility Error
I am getting the error: Disk Utility Stopped Repairing "disk0s2" - says disk utility can't repair the disk and I will need to reformat the disk and restore my files. This appears to be the startup disk (could be wrong) - as I am currently in recovery mode and any time I reboot, I am taken back to recovery mode and there are no start-up disks available to be selected.
When I run Disk Utility on my Internal HD (or what appears to be - this is 250 GB Hitachi) - I get the all clear that everything appears to be working correctly.
I do have TMbackups saved to a NAS. My MacBook Pro has been running very slowly as of recent (slight boost after upgrading to Yosemite, but then returned to slow performance).
I am running OS X Server on it - and have considered migrating that to a Mac Mini (yet to be purchased) - but want to get a better idea of options before I pull that trigger. I also want to make sure my MacBook Pro is recoverable and can still be used.
1. What is the risk of reformatting just the startup disk "disk0s2"? Is that even possible?
2. Is MacBook Pro in need of service at the apple store? Or can this be completed by me? (I have above average ability, but no wizard)
3. My logic on best practice to recover MBP and then add Mac Mini, migrating OS X Server to it: (all recommendations/suggestions welcome)
a. reformat MBP startup disk
b. restore TMbackup
c. use migration wizard to migrate OS X Server to Mac Mini
d. reformat MBP again, starting from scratch and install fresh copy of Yosemite
I had also considered just a fresh build of OS X Server on a new Mac Mini and starting fresh with the MBP. I don't use a ton of services on OS X Server so think my rebuild would be less time intensive than most.
Appreciate all the feedback.Well, your hard drive (flash storage) is good, at least. Here's what I would try next (before making a trip to the Apple Store or an AASP):
Boot into your Recovery partition and reinstall OS X. This won't damage or erase any of your user files, etc., just give you a fresh installation of Mountain Lion. Since your hardware seems to be OK, it could be that the system has just become corrupt and reinstalling it may 'fix' the problem.
Call back if that doesn't work...
Clinton -
I've got a mid-2011 MacBook Air running OS 10.7.4. When I run Disk Utility in repair disk mode, I get a pop up that says "Alert - Storage system verify or repair failed" and in the details window it says "Problems were encountered during repair of the partition map" and (in ominous red type) "Error: Storage system verify or repair failed."
What makes this problem strange is that I only encounter this error message when running Repair Disk from the MacBook Air's hard drive. Whenever I boot from an external drive and run Disk Utility on the MacBook Air disk from the external, I get no error message. I've run Disk Warrior on the MacBook Air disk as well, but it doesn't indicate that there are any problems.
I called Apple Support and they told me to take it to the Apple Store and get the hard drive replaced, which is nice of them but which still means that I'm going to be without a computer for a few days if not longer and I'll have to deal with the hassle of transferring files. I'd much prefer to fix the problem without having to replace the drive, assuming the problem is fixable.
Any advice?The item you select does it appear somewhat like this:
Of course the content is different, but I'm more interested in the structure you see. On your computer you see Macintosh HD whereas on mine it says Lion HD.
If so, then in order to repair Macintsoh HD you have to boot from a different drive because you cannot repair the active startup volume. When you select the top entry and click on the Repair Disk button all that does is repair or replace the drive's partition map.
Now, if the partition map is damaged, then the only way to fix it is to repartition the SSD. Doing so will erase all the data on the drive. So you need to make a backup of Macintosh HD on a cleanly erased external drive. I would suggest using the cloning option in Disk Utility to clone the SSD to the external HDD:
Clone Lion using Restore Option of Disk Utility
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.
Select Disk Utility from the main menu then press the Continue button.
Select the destination volume from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the destination volume from the left side list and drag it to the Destination entry field.
Select the source volume from the left side list and drag it to the Source entry field.
Double-check you got it right, then click on the Restore button.
Destination means the external HDD. Source means the internal SSD.
Once you have your backup then you may proceed to repartition the SSD.
Step One: Boot from the external drive. Restart the computer and after the chime press and hold down the OPTION key until the boot manager appears. Select the icon for the external drive then click on the downward pointing arrow button.
Step Two: Partition the SSD
1. Open Disk Utility in the Utilities folder of the HDD.
2. After DU loads select your new hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
Step Three: Clone the HDD to the SSD
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Check the box labeled Erase destination.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means the SSD. Source means the HDD.
Step Four: Open the Startup Disk preferences and select the SSD Macintosh HD volume. Click on the Restart button. You should boot from the SSD. Eject the external drive and disconnect it from the computer. -
Disk Utility Error "no valid packages"
Hi,
I have a PowerBook G4 with 1GB RAM.
I've noticed a significant system slowdown lately. Programs take longer to open and respond, and it's rather annoying. I came to the forums to seek some remedy, and tried to run a Disk Utility to check that everything there is at least okay. But when I click on verify permissions, I get an error that says "no valid packages." Does anyone know what this means and how to fix it (if it needs fixing; I'm assuming this isn't a good thing, whatever it is!).
Thanks.
LoriHi librarygirl and Welcome to the Discussions!
Mac OS X 10.3, 10.4: Disk Utility shows a "No Valid Packages" alert
Disk Utility can't verify or repair permissions on the Mac OS X 10.3 or 10.4 volume if the "BaseSystem.pkg" file is not in /Library/Receipts.
This alert appears when you try to repair permissions with Disk Utility:
"First Aid failed
"Disk Utility stopped repairing permissions on '(volume name)' because the following error was encountered: No valid packages"
In the Disk Utility text window, this message appears in red text:
"Error: No valid packages (-9997)"
This happens when the BaseSystem.pkg file is not in /Library/Receipts.
Solution
If you've moved this file, move it back to /Library/Receipts. You shouldn't normally remove any files from /Library/Receipts.
If the file has been deleted, replace it by copying it from a different computer that uses Mac OS X 10.3 or 10.4, or by reinstalling Mac OS X 10.3/10.4 from an installation disc.
"Reinstall" means you can install 10.3 or 10.4 from a disc, if it's the same version of 10.3/10.4 (such as 10.3.3 on both the installation disc and computer). If the version of 10.3/10.4 on the computer is newer than what's on the install disc, then use the install disc to perform an Archive and Install installation instead, then update to a later version of Mac OS X.
Joe -
Disk utility error when erasing an external hard drive
Hi,
Not sure if this is the most appropriate fourm list to post this but I thought I'd give it a try.
I am running snow leopard on my MBP and am trying to use disk utility to erase and format an ext. HD. While the disk icon does not show up on the desktop when I connect it to my mac, Disk utility does show the ext. hd in the left column, but no matter what format I try, even just using one partition and selecting zero out all data, I get the following error: "disk erase failed with the error: POSIX reports: The operation couldn't be completed. Cannot allocate memory".
Is the hd dead? Are there other options? I do have disk warrior, version 4.1.1 and it does not regonize the ext. hd.
Please advise.
Thanks,Thanks for the reply. Yes, I did select the ext hd as the one I wanted to erase (my internal hd is my start up drive). After I selected the ext hd, (there is no volume listed under it so the only thing I can select is the hd itself). that is when I selected erase and then Mac journaled, then named the hd and then after selecting erase, I got the error. Also as a matter of note, if I select firstaid, both the repair and verify permissions are dimmed, so I can't even try to repair the disk. That is when I tried disk warrior hoping that could examine the hd, but since it is not mounted on the d/t, it doesn't show as a drive to check. I don't understand why the ext hd shows up in disk utility, but not the d/t. Also of note is the fact that when I connect that ext had to my Mac with a fw cable, a window opens saying that the drive is not readable and do I want to initialize it or ignore. I choose to initialize and that is when I get the error. Also of note is that I have tried both security options of "don't erase data" and "zero out data" and still get the same error.
Hope this clarifies things a bit. -
Hi,
Fed up with seeing the spinning beach ball I decided to reformat my MacBook Pro...
After backing up everything on an external hard drive I put in the OSX install DVD, restarted the machine and held down 'C'.
I followed the install prcedure, clicking next a few times etc...
I then went into Utilities > Disk Utility. I chose 7-Pass to erase the Macintosh HD and set it off erasing.
I checked the process an hour in and message on screen read:
Secure disk erase failed with the error:
could not open disk
The internal hard drive no longer exists in the disk utility so I cant retry erasing it.
The only thing that appears in disk utility is the OSX install DVD.
I can't even shut down the mac as everything under the apple tab is greyed out!
I'm guessing this means my hard drive is broken right?
If anyone has any other ideas of what to try I'd really appreciate that.
How do I turn the machine off?
If my hard drive is gone then should I consider getting an SSD drive?
Any recommendations for such a drive would be great.
Hope you can help!Did you partition the drive?
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive. -
Disk Utility Error 61 when attempting to create disk image on external driv
I would like to make occasional archive backups of my three macintosh computers. I bought a new Western Digital 2TB drive for this purpose, and formatted it as Mac OS Extended. Trying to do a disk image backup using Disk Utility, I follow the directions:
- Startup from an install DVD.
- Start Disk Utilities and select "Restore"
- Drag "Macintosh HD" into the Source box
- Click on "New Image" and select compressed and 128-bit AES encryption
This leads to the error message: Unable to create "....." (error -61)
I have enocountered this problem both with my iMac G5 and a MacBook, both running Leopard.
Does anyone know what this error means, what I am doing wrong, and/or if there is another way to create disk image backups? Help!1. For reasons I don't know disc images seem to become more fragile the larger they get. They also can be subject to file corruption that affects the entire disc image, whereas file corruption on a clone would only affect certain files.
2. You cannot put multiple clones on the same volume. Each clone must be on a separate volume, but you can have multiple volumes on a single drive simply by partitioning the drive accordingly. Of course you need a drive large enough to accommodate each clone. Each clone should be to a space equal to the capacity of the cloned drive.
3. I'm not a big fan of TM, although I must confess it has become more reliable since it's release, especially with Snow Leopard. However, there are many backup utilities that can create clones, perform incremental updates, and archive changed files. See the following:
Backup Software Recommendations
Carbon Copy Cloner
Data Backup
Deja Vu
Silver Keeper
MimMac
Retrospect
Super Flexible File Synchronizer
SuperDuper!
Synchronize Pro! X
Synk Pro
Synk Standard
Tri-Backup
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files. -
Worrying Disk Utility Error Message
When I click verify disk in Disk Utility, a worrying error message comes up saying " The underlying task did not complete on exit" giving the error message
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Invalid volume free block count
(It should be 24694657 instead of 24694833)
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
I can't repair the volume as it is greyed out.
Help! This is a brand new MacBookPro, I've only had it a couple of days!So far I have never had any problems with them personally so I don't do an Erase & Install.
I'm sure we're all happy for you although problems do happen. Problems with the installation and even hardware problems. Thing is, often these issues aren't apparent until some time later.
The way I see it, the time and effort required to do an "Erase and Install" (which include a zero write to the drive) is a known… about 3 hours. To my mind, even there's a remote chance that this stops a potential problem in its tracks before it's a problem it's worth the time spent. 3 hours over the lifetime of a Mac OS X installation is not a lot to give up.
Additionally, by zero writing to a drive, it does allow you to see if your drive is on one way performing correctly. All four of my 300GB drives in my Mac Pro wrote zeros within one minute of each other. I know these drives won't have issues when being told to write a ton of data. Whithout doing this I would never know.
Now I did the same thing with my parents' 750GB drives and one finished in 3 hours and the other was still going at 5 hours. Now you can't tell me there's not something up there. So at what point would you like to have found that out?
How much time, let alone money, does it cost to do something later on?
Just like tools like Monolingual. How many issues with updates are caused by such tools? Again, how much time is lost to debug and maybe fix such issues? Thing is, we don't know although if you had a customised installation from the outset it wouldn't matter as you wouldn't be using such tools.
But hey… everyone's got their own opinion. All I know is that my systems always seem to go better and faster than every other Mac owners I know. -
Disk Utility errors: No such file -or- No space left on device (50GB+ free)
I am trying to make an image out of a _NTFS formatted_ parition, using around 4,5GB of data, of a freshly installed Windozs. It's for debugging tons of machines I have been given (to debug..) and I need an image done. Note that debating if using an image as a solution is good or not is not the point of this thread.
When I try to make a new image out of the parition (clicking "New Image"), using the defaults settings, I enter my admin pass, then I'm being shown "No space left on device". Wierd. The device I am writing the image onto has 51GB left, and the Trash is emptied.
I tried changing the image format to all the possible types in Disk Utility, but I get the same error: No space left on device.
I then changed the device, this time I used a volume with 10GB free on it. Then, I only managed to get a standard DMG compressed image, where I need a "DVD/CD master" one. I'm still confused, because no other image type worked.
Then I tried making a new image (not from a disk or volume, empty) and then just copy data to it (I'm sure it's really not the way to go, but still). After creating the empty image (I opted for an 8GB, DVD burnable style, "DVD/CD master"), I got the wierd error: No such file (straigth after the image creation, in Disk Utility).
More info about volumes and stuff:
Data to be imaged:
A single partition on a volume (connected with IDE to Mac Pro, but I don't see why it would matter)
Where I can save it:
I got a big bunch of volumes right here, internally.
I tried one with 50GB free, but failed. Another one, on another disk, with 10GB, but failed.
Also, this error comes often in Disk Utility and other unix OS I think, and mostly for no real known reason (in OS X), as most issues I found were still unresolved.
Thanks for any helpHey,
Im having the same exact problem.
Toast even says it has a medium error with this drive.
I cant burn with toast and it wont play other DVD-R movies
that I have burnt on other systems.
What is the fix? -
Hey there, i am trying to create a new blank disc image in order to burn some data files. I am using disk utility, File -> New -> Blank Image: Give it a name, specify size (700mb,80 min cd) no encryption or anything. trying to use FAT so my windows machine can read it (says the help file) however i get an error "Can't create "disk name.dmg" (invalid argument)"
Making the format osx journaled doesn't come up with the same error. whats goin on?Works fine here - check System Profiler/Logs for related errors.
Also check free space and be sure you have write permission to your target save locale. -
How to reinstall OS X? Disk Utility error. HELP!
My iMac failed start up normally so I have to enter the recovery mode (by holding the option key or command+R).
After researching online, I found my mac might have been corrupted. So I tried to use the first aid option in disk utility to verify and repair it but evertime I clicked repair, it shows a message "Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.""
I don't think I have a time machine backup as I tried the time machine back up option but there were no back-ups found. I can't create one now either since I'm on the starting gray screen. So I don't want to erase and reinstall since I don't have a back up.
So then I tried to reinstall OS X (Yosemite). But after following the first few steps, when it asks to choose the disk where you want to install the OS, it either says "this disk is locked" or "cannot install on Macintosh/Recovery HD." I still have about 273 GB available.
I've tried all this many times but it doesn't seem to work. I'm really stuck now and don't know any other option so please HELP!If you want to preserve the data on the startup drive, and it's not already backed up, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data, you can skip this step.
There are several ways to back up a Mac that is not fully functional. You need an external hard drive or other storage device to hold the data.
1. Start up from the Recovery partition, from Internet Recovery, or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
If you use FileVault 2, then you must first unlock the startup volume. Select its icon ("Macintosh HD," unless you gave it a different name.) It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. Enter your login password when prompted.
2. If Method 1 fails because of disk errors, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
3. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
4. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data. -
Disk Utility Error - "Underlying task reported failure on exit"
I've been having a problem opening Logic 7.1 (it will crash at startup every time) and I got the advice to repair disk permissions. Both 'verify disk permissions' and 'repair disk permissions' work, but when I go to 'verify disk' I get the following readout/error:
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect block count for file 5AD8D6E5d01
(It should be 92 instead of 0)
hecking multi-linked files.",0)
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume bitmap.
,0)
Checking volume information.
Invalid volume free block count
(It should be 2859750 instead of 2859751)
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
So I can't complete a rapair because it has this error. I'm wondering how I can fix this and if it could be the cause of the error that I get every time I open Logic. Thank you all in advance for your help!Al
Disk Utility cannot repair this type of error.Not sure this is always the case, Al. I've had "incorrect block count" errors repaired in the past, so it must be worth a try before spending money (although I regard money spent on DiskWarrior as good insurance!)
Cam
It has to be worth you at least trying to Repair the error.
I think the first thing you should try is a Safe Boot, which will automatically run the disk checking and repair routines: Mac OS X: Starting up in Safe Mode. If the check during Safe Boot is unable to repair the disk, your system will shut down rather than continuing, otherwise it will have successfully repaired the disk.
If this doesn't work, you should try Disk Utility from the Install Disk. First read these articles: Mac OS X 10.4 Help: About testing and repairing a disk, and Using Disk Utility and fsck to resolve startup issues or perform disk maintenance.
Let us know how this goes.
Maybe you are looking for
-
Failed to install enterprise manager under linux
When I installed Oracle 10g(10.2.0.1) under linux, I got an error when running /ora01/db/oracle/product/10.2.0.1/bin/emca within oracle universal installer. The emConfig.log file shows such error: oracle.sysman.emcp.exception.EMConfigException: Inval
-
2015-02-16_20-08-17:INFO:exit-code: 0 2015-02-16_20-08-17:INFO:pdp command with shell out /usr/bin/sudo -u oracle /bin/sh -c '(cd /agent12c/oem/core/12.1.0.4.0/cfgtoollogs && /agent12c/oem/core/12.1.0.4.0/bin/zip -q -r /tmp/remoteArchivesADXD2VSR103
-
My computer is running low on RAM, and when I look at what processes are using the most memory, firefox is the number one using between 28,000 to 93,000k, so I'm guessing that it has a memory leak. And because of that memory leak I have to update fir
-
Photoshop CS6 - not responding and most of the window is white
Every time I start PSCS6 I get that. No idea why. It gets like that and it's not responding. Please help
-
Hello , This problem is little different . When IDOC is processed it enters status 51 Error:Enter the requested delivery quantity If we keep break point in respective fn module and reprocess the idoc then it enters status 68 Error : no further pro