Disk Utility Reports Permissions Repaired, but Don't Verify

I run permissions repair (as I've been having kernel panics), and there is a bunch of stuff that gets reported as fixed. However, as soon as the repair is complete, if I run Verify Disk Permissions, it reports back the same errors.
See the log below:
*Repairing permissions for “Hybrid”*
Permissions differ on "Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player", should be -rw-rw-r-- , they are -rwxrwxr-x .
Repaired "Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player".
User differs on "private/var/at", should be 0, user is 1.
Repaired "private/var/at".
Permissions differ on "usr/lib/libpcap.A.dylib", should be -rwxr-xr-x , they are -r-xr-xr-x .
Repaired "usr/lib/libpcap.A.dylib".
Permissions differ on "usr/share/sandbox/mDNSResponder.sb", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/sandbox/mDNSResponder.sb".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management- agent.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management- agent.jar".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/dt.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/dt.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/management -agent.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/management -agent.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/security/b lacklist", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/security/b lacklist".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries".
Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0/libprofilerinterface.sl".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0w/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0w/libprofilerinterface.sl".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0/libprofilerinterface.sl".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0w/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0w/libprofilerinterface.sl".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries".
Permissions differ on "usr/bin/awk", should be -rwxr-xr-x , they are -r-xr-xr-x .
Repaired "usr/bin/awk".
Permissions differ on "usr/bin/iconv", should be -r-xr-xr-x , they are -rwxr-xr-x .
Repaired "usr/bin/iconv".
Permissions differ on "usr/lib/libcharset.1.dylib", should be -r-xr-xr-x , they are -rw-r--r-- .
Repaired "usr/lib/libcharset.1.dylib".
Permissions differ on "usr/lib/libiconv.2.dylib", should be -r-xr-xr-x , they are -rw-r--r-- .
Repaired "usr/lib/libiconv.2.dylib".
Group differs on "usr/lib/libutil1.0.dylib", should be 80, group is 0.
Repaired "usr/lib/libutil1.0.dylib".
Group differs on "usr/lib/libz.1.1.3.dylib", should be 80, group is 0.
Repaired "usr/lib/libz.1.1.3.dylib".
Group differs on "usr/lib/libz.dylib", should be 80, group is 0.
Repaired "usr/lib/libz.dylib".
Permissions differ on "usr/share/file/magic/cafebabe", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/cafebabe".
Permissions differ on "usr/share/file/magic/compress", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/compress".
Permissions differ on "usr/share/file/magic/database", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/database".
Permissions differ on "usr/share/file/magic/erlang", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/erlang".
Permissions differ on "usr/share/file/magic/filesystems", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/filesystems".
Permissions differ on "usr/share/file/magic/fonts", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/fonts".
Permissions differ on "usr/share/file/magic/fortran", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/fortran".
Permissions differ on "usr/share/file/magic/linux", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/linux".
Permissions differ on "usr/share/file/magic/lisp", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/lisp".
Permissions differ on "usr/share/file/magic/python", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/python".
Permissions differ on "usr/share/file/magic/troff", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/troff".
Permissions differ on "usr/share/file/magic/windows", should be -rw-r--r-- , they are -r--r--r-- .
Repaired "usr/share/file/magic/windows".
Permissions differ on "usr/share/man/man1/bzcmp.1", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "usr/share/man/man1/bzcmp.1".
Permissions differ on "usr/share/man/man1/bzegrep.1", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "usr/share/man/man1/bzegrep.1".
Permissions differ on "usr/share/man/man1/bzfgrep.1", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "usr/share/man/man1/bzfgrep.1".
Permissions differ on "usr/share/man/man1/bzless.1", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "usr/share/man/man1/bzless.1".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
ACL found but not expected on "private/etc/apache2/httpd.conf".
Repaired "private/etc/apache2/httpd.conf".
ACL found but not expected on "private/etc/apache2/users".
Repaired "private/etc/apache2/users".
ACL found but not expected on "Library/Preferences/Audio".
Repaired "Library/Preferences/Audio".
ACL found but not expected on "Library/Preferences/com.apple.alf.plist".
Repaired "Library/Preferences/com.apple.alf.plist".
ACL found but not expected on "Library/Scripts/Script Editor Scripts/Dialogs/Dialog - 1 Btn.scpt".
Repaired "Library/Scripts/Script Editor Scripts/Dialogs/Dialog - 1 Btn.scpt".
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
ACL found but not expected on "System/Library/Keychains/X509Anchors".
Repaired "System/Library/Keychains/X509Anchors".
ACL found but not expected on "private/etc/hostconfig".
Repaired "private/etc/hostconfig".
ACL found but not expected on "private/etc/hosts".
Repaired "private/etc/hosts".
ACL found but not expected on "private/var/db/launchd.db/com.apple.launchd".
Repaired "private/var/db/launchd.db/com.apple.launchd".
ACL found but not expected on "private/var/yp/binding".
Repaired "private/var/yp/binding".
*Permissions repair complete*
*Verify permissions for “Hybrid”*
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r", should be lrwxr-xr-x , they are lrw-r--r-- .
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib", should be 0, user is 95.
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries", should be 0, user is 95.
Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
ACL found but not expected on "private/etc/apache2/httpd.conf".
ACL found but not expected on "private/etc/apache2/users".
ACL found but not expected on "Library/Preferences/Audio".
ACL found but not expected on "Library/Preferences/com.apple.alf.plist".
ACL found but not expected on "Library/Scripts/Script Editor Scripts/Dialogs/Dialog - 1 Btn.scpt".
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
ACL found but not expected on "System/Library/Keychains/X509Anchors".
ACL found but not expected on "private/etc/hostconfig".
ACL found but not expected on "private/etc/hosts".
ACL found but not expected on "private/var/db/launchd.db/com.apple.launchd".
ACL found but not expected on "private/var/yp/binding".
*Permissions verification complete*

jackjames wrote:
*Permissions repair complete*
as long as you see this, you're ok.
JGG

Similar Messages

Disk Utility reports minor repair required - how risky is this?

I was verifying permissions the other day and thought I'd check the hard drive as well. When running the verify hard drive it stopped with an error report as follows:
Volume Header needs minor repair
The Volume Macintosh HD needs to be repaired
Error the underliying task reported failure on exit. 1HFS volume checked. Volume needs repair.
The Macbook seem to be running fine. Should I run the repair or leave it. Someone once told me that if the Disk Utility fails to repair the problem it can leave the disk unusable. Any truth in that?
Thanks
Michael
iMac G4 15" flat screen : MacBook 1.83 (Tiger) Mac OS X (10.3.9)

Directory structure issues can lead to freezing, general slowness, startup issues (computer may not startup all the way), Applications or files may not open.
It is usually suggested to repair the disk with Disk Utility that came with the computer or a disk utility that is compatible with the operating system that you are using.
Here are some articles from Apple's knowledge base. Some are technical:
http://docs.info.apple.com/article.html?artnum=302411
http://docs.info.apple.com/article.html?artnum=13628
http://docs.info.apple.com/article.html?artnum=7565
http://docs.info.apple.com/article.html?artnum=19516
Directory structure issues usually are not HW issues, but is the way the computer or OS, stores/sorts information on the Hard drive.

Disk utility can't repair but can't access the HD to back-up files?

I'm relatively new to MACs and have a 2TB Seagate with a good portion of our family pics on it. I opened the Disk Utility and attempted to repair the HD but get the 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."
Here's where I'm stumped...I can't actually access the disk to back it up. At one point I was able to open the disk and see the files so I went and bought another HD to back it all up....but now I can't access it. I've found a few threads discussing using recovery software but the data isn't that important. I was using the HD as my Time Machine BU so I'm more nervous about re-formatting it and trusting it with my data again. Should I bother even reformatting it or just toss the thing?

You might try a force mount...
Launch/Utilities/Terminal and enter this command at the prompt
diskutil list
Press return. If it sees the disk, note the number of the disk (far left column) you want to mount.
Then, enter this command
mount /dev/(number of disk)
Put in the number no parenthesis.
Press return.
If you're able to mount copy off the data you need. Even if you can mount it, wouldn't I trust the disk again.
Try Drive Genius in demo mode to run a surface scan and see if there are any bad blocks.

Disk Utility: Strange permissions repair results

Hi,
can anyone explain what these results mean? (D.U. cannot fix these errors.)
Thank you very much!
Peter
Repairing permissions for “iMac”
Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
ACL found but not expected on "private/var/root/Library/Preferences".
ACL found but not expected on "private/var/root/Library".
ACL found but not expected on "private/var/root".
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Permissions repair complete
Message was edited by: Peter R.
Forget it - one should always browse the posts before posting yourself. I found it. Sorry.

Please search the discussions before posting. This question has been asked and answerd dozens of times now.
You can safely ignore these messages, or you can download and manually install the 10.5.1 update to get rid of most of them.
http://www.apple.com/support/downloads/macosx1051update.html

Disk Utility reports 'Volume could not be repaired' Now what?

Disk Utility reports that my internal HD cannot be repaired (I tried booting to the installation CD as-well-as a Superduper image with the same result). Here is the complete dialogue:
Verify and Repair disk “iMac_HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Illegal name
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Repairing volume.
The volume iMac_HD could not be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
1 volume could not be repaired because of an error
Repair attempted on 1 volume
1 volume could not be repaired
Unfortunately the backup image has the same problem, so no use restoring the internal HD from it. So what do I do now? I read on a forum that the 'illegal name' error is caused by Photoshop CS, but didn't see a solution. Help!
 20" Intel iMac (2.0GB RAM, 256MB VRAM, 500GB HD) Mac OS X (10.4.6)

I get this error occassionally too. In those cases I take my original install dvd, put it in, reboot and hold the c key.
It then starts an install (don't worry, it won't do anything). When the install screen appears, in the top menu you can select Disk Utility.
Repair the disk from there, it will probably manage now. I guess something is interfering with Disk Utility when all of OS X has loaded.
Once the disk is repaired, verify/repair permissions, exit the program and reboot (don't hold and press c this time around).
Hope this helps.
Lars.
20" iMac Core Duo Mac OS X (10.4.5)

Anyone clean their mac using the disk utility using the repair disk permissions??

anyone clean their mac using the disk utility using the repair disk permissions??

No. Threads don't hurt anything. If your computer is not functioning properly perhaps you need to try some basic maintenance. Let's start by having you do this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard 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 Utilities menu. 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 click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Next, try booting into Safe Mode then immediately restart normally. Safe mode is going to take a while so be patient. It's slow.
Next, create a new user account. Log out of your account then log into the new account. Try using iPhoto and the publishing button. Do they work now?
If you still have a problem, then do the following. If you don't want to go through the above then just start with the following and forget the others above.
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard 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 Utilities menu. 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 click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.

My external LaCie drive gets an error message "the disc you inserted was not readable by this computer." The only options offered are "ignore" or "eject" Disk Utility sees the disc but does not give a repair option. What can I do?

When I plug in my external LaCie drive I get an error message "the disc you inserted was not readable by this computer."
The only options offered are "ignore" or "eject"
Disk Utility sees the disc but does not give a repair option.
What can I do?

The good thing about mac-centric resellers such as OWC, is they have people on staff that can answer questions without you buying things first. They also have how-to information, and instructions are included in many of their products. I saw a link to watch a DIY video in one of their pages; an example of a RAID (with its own power supply) is shown on their drives page. Also a few in there, with no power supplies, for less money.
If I were looking to backup and perhaps also have a partition for a system clone, I'd consider something like one of these: http://eshop.macsales.com/shop/firewire/1394/USB/EliteAL/eSATA_FW800_FW400_USB
Some ideas on the RAID backup methods appear in google search, some of the pages are ideas and concepts; and the better ones also warn about using RAID for the only backup plan.
Oh, OWC has live chat. Haven't tried it, nor have I bought anything from them. I have what appears to be two products from them, but have not used either. One is in a box as-new, but has only USB2.0 ports & my Macs needed FW400/800. It has been said their RAM is a good way to upgrade, too. But I can't confirm!
A 'RAID-ready' unit for backup may be more versatile for just that, but I have not checked into these details. I use single HDDs in powered enclosures, and usually manually make backup clones to FW drives, of bootable OS X systems. Some of the OWC raid-ready use eSATA ports so that may not be viable for a computer without them.
The unused in-box external drive I have is like the base model in the link above. However mine is USB2.0 (maybe) and won't boot my older Macs due to hardware variance; and my preference would be for FireWire options, these models do offer that. But the one I have does not. Dual 500GB HDDs, and they could be used in tandem as a RAID. That would be a choice set up in software. I'm not sure and not interested enough to read up just now.
My backup method is not automatic, or a moving backup plan, if I don't get a move-on and make full system clones. I do make copies of photos and documents the manual way, to USB external drives; and occasionally backup to DVD or CD media. And USB flash, that helps to move files between computers without need to use file sharing via wi-fi. {Like Why fly? Walking is better exercise unless one is a bird. Squawk!}
https://www.google.com/#q=raid+backup+mac
Depending on the ports in your Mac, you may be able to use other cables to attach between a backup or externally enclosed hard disk drive with multiple partition and bootable clone in one of them. Not sure about the Thunderbolt, and where that is the main port, adapters are required to access other devices, as allowed.
Anyway, I am going on and on, yet not really saying anything.
My ideas would not be all that interesting to follow as a backup
plan when matching available newer hardware to task, but you
can get some into better ideas if you are not in a rush. Get a
good setup and then look into more an betterer stuff.
Good luck & happy computing!

Disk utility won't repair permissions (related to error -8003)

I have an odd, recurring problem I can't diagnose. Recently my seven-month-old MacBook Pro has begun showing an error code (-8003) when I try to do common, system-related things like empty the Trash. At the same time, Time Machine stops backing up and Disk Utility can't repair permissions. If I go into System Preferences I can't open the lock to make changes, even though my account is still clearly marked as the Admin account. All third-party applications run fine, so I can't quite figure out what's going on.
I've tried repairing the disk via TechTool to see if there was directory damage and it checks out fine. I've reformatted my TM backup disk with Disk Utiity according to Apple's instructions, used the Terminal to ensure my Trash and old TM files were properly deleted, etc. Nothing seems to have made a difference.
When I restart the problem goes away for a couple of hours and then – at some point that I haven't been able to identify – the problem starts up again. This is the case whether I'm working on the MacBook or if it's just sitting there idle.
Before I reinstall I wondered if anyone had run into a similar problem and had figured out what caused it.

error code (-8003) when I try to do common, system-related things like empty the Trash
That's a common symptom of throwing stuff from a Time Machine backup into the trash in the Finder, which is a big no-no and can irreversibly corrupt your backup. In the Terminal, type the following command:
sudo rm -rf ~/.Trash/*
Copy and paste that! Don't try to re-type it, I've seen people put a space in the wrong place and wipe their whole user folder. Type your password when prompted, and expect that nothing will show until you hit return.
Next, repair your Time Machine backup according to:
http://web.me.com/pondini/Time_Machine/A5.html
At the same time, Time Machine stops backing up
If the above troubleshooting doesn't fix your backup, you may have damaged it beyond repair. In that case, you'll have to erase it and start your backups over from scratch.
Disk Utility can't repair permissions
Where are you trying to repair permissions? Note that repairing permissions is only meaningful on a drive with a system installed on it, and only repairs permissions on a specific subset of the stuff on the drive. Also, note that there are permissions messages you can safely ignore... if you think it is failing because you're seeing them over and over, it's not failing.
If I go into System Preferences I can't open the lock to make changes, even though my account is still clearly marked as the Admin account.
I've never seen that before, and it may indicate you have much more serious problems with your computer. First, try repairing your hard drive with Disk Utility. Then trash the System Preferences preference file, located at:
~/Library/Preferences/com.apple.systempreferences.plist
...where '~' means "your home folder".

Help help!! Disk Utility reported can't repair my HD

Hello all I used Disk Utility (version 10.5.5) that comes with Mac OS X 10.4.6 to check my hard drive. The diagnostic returned a message that my drive needed to be repair. So I booted up with installation disc and did the repair.
One of the log says there is an error in red font "Invalid leaf record count"
and the repair results were as the following:
1HFS Volume repaired
1 Volume Could not be repaired.
What does "Invalid leaf record count" mean?? And why 1 volume in my drive can't be repaired? How do I repair it?
I only have 1 volume on my HD, I didn't partition my drive. So, what is causing the problem? Should I be ignored? What's the benefit of partitioning my drive?

Sometimes the file directory is corrupted or damage beyond Mac OS X's Disk Utility can repair, but don't panic just yet. Get a copy of Disk Warrior, boot from it and run it, it will build a brand new file directory and replace the old one, that should solve your problems, a lot of us here "swears" by Disk Warrior, in fact I had your similar problem, ran DW and problem solved.
As for disk partition, it is not really necessary in modern OS like the Mac OS X, one of the reason people partition disks (a long time ago) because in the older days of the older Mac OS, it is unable to read a large hard drive beyond a certain size, i.e. if you place a 250Gb (of course then there is no 250 yet) inside your Mac, your Mac probably can only read it is 120Gb large, so that's why you need to partition the drive into 2 or 3 to read.
People also partition drives to run and boot multiple OS, this is especially true maybe for tech guys etc, who may have OS X, various versions, and OS 9 running in different partitions.
Cheers

Disk Utility reports everything is fine but everything action is slow?

My 13in MacBook Pro has been running very slow lately. Disk Utility reports everything is fine yet the pinwheel shows up all the time and it takes forever to respond to a clicked app. What's going on?

First, back up all data immediately, as your boot drive might be failing.
Step 1
This diagnostic procedure will query the system log for messages that may indicate a hardware fault. It changes nothing, and therefore will not, in itself, solve your problem.
If you have more than one user account, these instructions must be carried out as an administrator. I've tested them only with the Safari web browser. If you use another browser, they may not work as described.
Triple-click anywhere in the line below on this page to select it:
syslog -k Sender kernel -k Message CReq 'Channel t|GPU D|I/O|nspace-h|n Cause: -' | tail | open -ef
Copy the selected text to the Clipboard (command-C).
Launch the 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. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. Normally the command will produce no output, and the window will be empty. If the TextEdit window (not the Terminal window) has anything in it, stop here and post it — the text, please, not a screenshot. The title of the TextEdit window doesn't matter, and you don't need to post that.
Step 2
There are a few other possible causes of generalized slow performance that you can rule out easily.
Reset the System Management Controller.
If you have many image or video files on the Desktop with preview icons, move them to another folder.
If applicable, uncheck all boxes in the iCloud preference pane.
Disconnect all non-essential wired peripherals and remove aftermarket expansion cards, if any.
Check your keychains in Keychain Access for excessively duplicated items.
Boot into Recovery mode, launch Disk Utility, and run Repair Disk.
If you're booting from an aftermarket SSD, see whether there's a firmware update for it.
If you have a MacBook Pro with dual graphics, disable automatic graphics switching in the Energy Saverpreference pane for better performance at the cost of shorter battery life.
Step 3
When you notice the problem, launch the Activity Monitor 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. Click Utilities, then Activity Monitor in the icon grid.
Select the CPU tab of the Activity Monitor window.
Select All Processes from the menu in the toolbar, if not already selected.
Click the heading of the % CPU column in the process table to sort the entries by CPU usage. You may have to click it twice to get the highest value at the top. What is it, and what is the process? Also post the values for % User, % System, and % Idle at the bottom of the window.
Select the System Memory tab. What values are shown in the bottom part of the window for Page outs and Swap used?
Next, select the Disk Activity tab. Post the approximate values shown for Reads in/sec and Writes out/sec (not Reads in and Writes out.)
Step 4
If you have more than one user account, you must be logged in as an administrator to carry out this step.
Launch the Console application in the same way you launched Activity Monitor. Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Select the 50 or so most recent entries in the log. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V). You're looking for entries at the end of the log, not at the beginning.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some personal information, such as your name, may appear in the log. Anonymize before posting. That should be easy to do if your extract is not too long.

My Macbook aliminium unibody from late 2008 will not boot. I reach the grey screen with the apple icon and the spinning grey gear. I used disk utility to boot it but it said integrity test failed. I don't know what to do can anyone please help?

My Macbook aliminium unibody from late 2008 will not boot. I reach the grey screen with the apple icon and the spinning grey gear. I used disk utility to boot it but it said integrity test failed. I don't know what to do can anyone please help?

Sounds like you may have a harddrive issue. You are probably going to need to get that changed out and then install the OS X again to get it going.

DiskWarrior and Disk Utility can't repair volume after 10.4.6 upgrade

I appreciate any advice on the following problem:
After installing the 10.4.6 update On April 4 (which installed just fine), I did my usual post-installation system maintenance including repairing permissions, running CRON scripts and cleaning the caches. I got a strange Apple Script error that flashed on and off the screen (too quickly for me to document) while I was cleaning the caches, then the process finished. Then when I used DiskWarrior as part of my usual maintenance, it "stuck" while saying that the process was slowed because of a disk error. I waited for an hour, and it never completed. I then restarted using the OS install disk, called up Disk Utility and selected Repair Disk. This is what I got:
Verifying volume "Macintosh HD"
Checking HFS Plus volume
Checking Extreme Overflow file
Checking Catalog file
Invalid node structure (in red font)
The volume Macintosh HD needs to be repaired (in red font)
Error: The underlying task reported failure on exit (in bold red font)
1 HFS volume checked
Volume needs repair (in bold red font)
I cannot repair this problem using either DiskWarrior or the OS installer disk with Disk Utility. In addition, I was unable to archive & install the system while using the OS install disk! I have tried repairing permissions and using DiskWarrior and the OS Installer disk again with no success.
I am able to work on my Mac, but things seem slower and I get occasional oddball errors that make no sense. A few times, applications have quit unexpectedly when they weren't before.
Am I going to have to initialize the hard drive and reload everything?
Many thanks!
--Melissa
Mac G5 (dual 2GHz) Mac OS X (10.4.6)

I had a similar experience after installing 10.4.6.
The messages I got in Disk Repair were:
Checking Catalog file.
Illegal name (in red)
Illegal name (in red)
Keys out of order (in red)
The volume Rich's HD could not be repaired. (red)
Error: the underlying task reported failure on exit. (In red)
After a long time on the phone with Apple, we decided to reinitialize the hard drive. I have reinstalled the OS and am in the laborious process of restoring my user files and non-Apple applications. What a hassle! And I am not even sure all will be restored to proper functionality.
Don't know if either yours or my disk failure are related to 10.4.6 but Apple better watch closely for user feedback. These are potentially disastrous problems for users if they have not backed up.

Disk Utility can't repair or verify?

Hi, my 12 G4 powerbook is running fine except the fan is on nearly all the time. I thought I'd try to repair (or verify) disk permissions to see if that might possible help. But every time I run it on the HD, it just spins for maybe 10 min then gives an error message indicated failure. Why can't Disk Utility find the permissions? The disk otherwise works fine. There's no partition and i'm the only user.
Thanks.
-wayne

HI Wayne,
*"thought I'd try to repair (or verify) disk permissions to see if that might possible help. But every time I run it on the HD, it just spins for maybe 10 min then gives an error message indicated failure."*
You can repair disk permissions from the Disk Utility application already on the drive. (Applications/Utilities) but I doubt that's the issue here.
Try resetting the PMU, *(not SMC)* instructions here: http://support.apple.com/kb/HT1431 Read the article carefully before doing this.
Can you boot from your restore disk? Restart your PBook while holding down the C key, pressing the power button and inserting your restore disk all at the same time. An Installer window will open, but do not proceed with any installations. Instead, from the Menu Bar, select Utilities > Disk Utility. In the Disk Utility window click First Aid, and then click Verify. If Disk Utility reports errors, click Repair. When Disk Utility is finished, from the Menu Bar, select Utilities/Startup Disk. Select MacintoshHD 10.x.x and click Restart.
If Disk Utility cannot repair the disk, there are several good disk utilities to look at. One is DiskWarrior and the other is TechToolPro.
Carolyn

Disk Utility can't repair Macintosh HD. What should I do?

Here is a "quick" synopsis of what has happened thus far:
About one month ago, my computer started getting very sluggish (ie, it would take forever to startup, would always freeze after sleep, etc.) I lived with it for about two weeks, since it would always run quickly after waiting ~30 minutes after starting/waking up. Eventually, this grew old. I browsed the internet and did multiple suggested fixes (reset PRAM, run Disk Utility, ran in Safe Boot Mode, etc.). Nothing seemed to work. I opted to zero out the harddrive and reinstall Mountain Lion after making a backup. That was about two weeks ago.
Everything worked fine, up until yesterday. Once again, things started getting slow. I decided to shut down my computer for the night and would check it in the morning. When I turned it on this morning, it wouldn't startup correctly. I could login, etc., but it was frozen and I couldn't open any applications without getting the spinning beach ball. I waited about an hour, but it was still slow/loading. I shut the computer down and booted it in Verbose Mode. I ran the various commands to check the conditions of my disk, but when I ran the "fsck -fy" command, I got an "I/O Error." I then tried rebooting my Mac, but it would get to the gray screen with the apple logo and the spinning wheel, and then the progress bar would appear. Before the progress bar did anything, it would shut itself down.
I then started the computer up and directly went to OS X Utilities. I went into Disk Utility and tried to check permissions and repair the disk. Only this time, Macintosh HD was grayed out and seemed to be unmounted. I couldn't get it to mount. I went into the Apple Store to have them run their own diagnostics. However, the apple store employee was unable to get the test working, so that was basically a bust. At this point, the computer still didn't turn on.
I got home and, just for kicks, held the "N" key while booting up my computer. For whatever reason, my computer started up (though it took a long time and there was a progress bar). Now, I made another backup of my disk and am wondering what to do. I ran Disk Utility again to repair my disk, but it says that Macintosh HD is not able to be repaired. When I checked permissions, there were tons of Input/Output Errors. Based on my research, it would appear that I have two solutions.
I can either purchase DiskWarrior and use that to try and solve my problem, or I could just get a new hard drive (and I would upgrade to a SSD or SSHD). DW is about $50 if I just download it, and the hard drive would cost me $150 or so. Since I don't know exactly what is wrong with the disk, I don't know if DW would be able to fix it. That being said, if the hard drive isn't the problem, there would be no reason for me to purchase a new one. I guess I would just like some advice, as to what you would do. I apologize for the long post.
TL;DR: Disk Utility can't repair Macintosh HD. Should I get DiskWarrior or a new harddrive?
Thanks in advanced!

Most importantly, youve already backed up all the data. All else is cake.
A new HD would cost you only $20 more than disk warrior,....theres no reason to repair a worthless crippled HD, .....new HD 1TB is $70.
Once you back up all the data on a failing HD, further diagnosis has no meaning,....not anymore.
Grab a 1TB or 750GB Toshiba/Hitachi (both used by Apple inside their Macbook Pro nonRetina,...both are made by Hitachi) 5400RPM SATA HD.
Forget the repair,.......repair only serves to bring a HD to a point of BACKUP.....since youve already done that, its now just wall art or trashbin fodder.
These are the same HD used by Apple in their Macbooks
http://www.amazon.com/MQ01ABD-2-5-Internal-Hard-Drive/dp/B0077CV2RO/ref=sr_1_1?i e=UTF8&qid=1376281905&sr=8-1&keywords=toshiba+1tb+2.5%22
In the future ALWAYS remember to have 2 backups for everything. 2 backups is 1, and 1 is none.
That way when something crashes (and they all do).....its no worries.

Upgraded to 10.5.6 and Disk Utility won't repair?

I upgraded to 10.5.6 and ran Disk Utility and got the report below. Should I be concerned about it?:
Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
Warning: SUID file "usr/bin/setregion" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Warning: SUID file "System/Library/Printers/IOMs/LPRIOM.plugin/Contents/MacOS/LPRIOMHelper" has been modified and will not be repaired.
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions differ on "private/var/spool/cups/cache/rss", should be drwxr-xr-x , they are drwxrwxr-x .
Permissions repair complete

No. TM backups are not usable to downgrade to an earlier version of OS X. Archive and Install is the proper method.
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
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.) 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 quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Disk Utility Reports Permissions Repaired, but Don't Verify

Similar Messages

Maybe you are looking for