Disk Utility Reports Error, Can't Repair

Well, I just ran a "verify disk" on my harddrive, this is the report.
"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.
Volume Bit Map needs minor repair
Checking volume information.
Invalid volume free block count
Invalid volume free block count
%@ instead of %@)",2)
2309912
2309813
Volume Header needs minor repair
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair"
But the repair button is gray and cannot be selected... please help!

You must boot the computer from your Tiger install disc in order to run Disk First Aid repair.
http://www.thexlab.com/faqs/durepairfns.html

Similar Messages

My external drive won't mount. Disk Utility says it can't repair disk and to backup the disk and reformat, but how can I do that if it won't mount?

My external drive won't mount. Disk Utility says it can't repair disk and to backup the disk and reformat, but how can I do that if it won't mount?

See mount section in 1st linked article.
Disk Unmount Using Terminal
Disk Utility – Force Mount Disk

Leopard and Norton Auto protect - Disk Utility Reports error on disk verify

Hi There,
Leopard 10.5.1, Norton Antivirus 10.1.1(2) with "auto protect on" has some incompatibility issue. Running "Verify Disk" from "Disk Utility" stops producing some error message in red colored text. Repair disk option is not available. However, verify disk on starting up with Leopard installation DVD shows no error. Verify Disk when starting up from Leopard 10.5.1 HD and norton auto protect disabled reports no error. So, looks like some compatibility issue.

I have been going crazy with this for the past fortnight: with theh rapiudity of the onset becoming far too frequent.
Norton AntiVirus AutoProtect could not continue. Please run LiveUpdate or reinstall AntiVirus and ReStart (Code:9)
This is what I get! I turn it back on, and zap. I reinstasll, and, zap.
I chatted with Symantic, they gave me a link for an update to the Stuffit engine, apparently may be a cause.
Well, that was No Use. Zap, you guessed it!
FYI:
I run iMacG5 17" 160HD, partitioned,Leopard on one partition, Tiger on the other. works well.
Oh, and, the Auto Protect doesn't zap in Tiger!
any ideas? I can share logs of Crash.
thanks, George.

Disk Utility Reports Errors

I have just erased my HD and reinstalled all my programs. Things were running fine for about a week. When I went to run a very disk... this is the message I received.
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.
Reserved fields in the catalog record have incorrect data
Checking volume bitmap.
Checking volume information.
me %@ needs to be repaired.",1)
Macintosh HD
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
I then used the Start Up DVD to run Disk Utility and it said 1 volume repaired, 1 volume can't be repaired. But all I did was run in on my HD... my 2 other External drives checked out OK...
So... what exactly is the problem... is my HD faulty or is this a problem arising from installing other programs like Limewire and Windows Media Player. I JUST wiped my system clean a week ago and need to figure out what is going on... any ideas...
Thanks,
Daryn
Powerbook G4 Mac OS X (10.4.3)

You're welcome.
The Format is Extended and Journaled...but what exactly does this mean???
If the hard drive format is Extended with Journaling enabled (which is done at the factory and requires reformatting the hard drive to change it), performing an Erase & Install will not change the hard drive format unless you select a different format when doing so.
Mac OS Extended format is a hard disk format that increases the number of allocation blocks on the disk. Mac OS Extended format optimizes the storage capacity of large hard disks by decreasing the minimum size of a single file.
Check this link for information about file system journaling.
http://docs.info.apple.com/article.html?artnum=107249
This link provided instructions for checking a hard drive for bad blocks.
http://docs.info.apple.com/article.html?artnum=24764
You should also check the Smart Status for the drive.
http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh1896.html
No... It is only 80G... should it be partitioned? Again what
does this really do???
No the hard drive should not be partitioned unless you want or need it partitioned. Some prefer partitioning their hard drive for various reasons. As an example, you can partition the hard drive into two partitions and install 10.3 on one partition or volume and 10.4 on the other providing the option to boot the computer from either the 10.3 or 10.4 partition or volume. Some create and use a separate partition or volume to store all data keeping OS X and all applications on the boot volume partition.
Should I erase the Limewire program and any files I downloaded???
I thought Macs were impervious to viruses... so I thought it would
be alright...
There is no computer operating system that is completely impervious to viruses and malware but OS X is about as close as it gets - especially when compared to the insecurity associated with Windows. Although there are no viruses that currently affect or infect OS X, there are some Trojans and malware that do. I could email you an AppleScript programmed to erase all data in your Home folder/directory. You would be prompted for your admin password before doing so but if you trusted me and/or what I sent you and you opened and ran such a malicious script, bad things can happen.
Not long ago, there was a download available via the P2P network with Limewire that indicated or was shown as a free install of Microsoft Office for OS X. The size of this download was not very large - not anywhere near the size required to include Office X but some unsuspecting folks downloaded and ran this malware which completely erased their entire Home folder/directory. No antivirus software would be any help with such a malicious script since not a virus.
There must be some trust involved when downloading software or files which is the reason we should do so from known and trusted sources only. If you choose to continue using Limewire (which most use for downloading music for free which is stealing from musicians and record labels in effect), if you are ever prompted to provide your admin password for any reason out of the blue when opening a file downloaded with Limewire, you should always decline.
After I did the reinstall... everything looked good for about a week
(no errors when I ran Verify disk) did I not really do a complete erase
and install? Did I go wrong during the install process???
I don't believe you did anything wrong during the install process. If you performed an Erase & Install using your Panther install package and then you upgraded to Tiger using the Tiger retail install package, are you checking the hard drive via Disk Utility when booted from the Tiger retail install package?
If so and there is a hard drive directory problem that Disk First Aid repair cannot successfully repair, your options are using a more substantial disk repair utility such as Disk Warrior (which is highly regarded for OS X but comes with no guarantee) or checking the hard drive S.M.A.R.T. status first and if OK, checking the hard drive for bad blocks per the links I previously provided and then re-install Panther and all included software included with the install package that shipped with your Mac. Afterwards, check the hard drive for any directory problems again via Disk Utility when booted from the Tiger retail install package before installing Tiger.

Disk Utility Reporting errors

Hi all,
i have a question which i don't understand. I have just got a new macbook for a few days and was repairing my disk permission and i have received the following errors;
2009-01-09 01:25:37 +0800: Disk Utility started.
2009-01-09 01:25:47 +0800: Repairing permissions for “Macintosh HD”
2009-01-09 01:25:47 +0800: Reading permissions database.
2009-01-09 01:25:47 +0800: Reading the permissions database can take several minutes.
2009-01-09 01:30:57 +0800: Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
2009-01-09 01:30:57 +0800: Warning: SUID file "System/Library/Filesystems/AppleShare/checkafp.app/Contents/MacOS/checkafp" has been modified and will not be repaired.
2009-01-09 01:30:58 +0800: Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
2009-01-09 01:30:58 +0800: Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
2009-01-09 01:30:58 +0800: Warning: SUID file "sbin/mount_nfs" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "sbin/umount" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "sbin/ping" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "sbin/ping6" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "sbin/route" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "usr/sbin/netstat" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "usr/sbin/traceroute" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "bin/rcp" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "System/Library/Extensions/webdavfs.kext/Contents/Resources/loadwebdav" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
2009-01-09 01:30:59 +0800: Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
2009-01-09 01:31:00 +0800: Warning: SUID file "usr/bin/setregion" has been modified and will not be repaired.
2009-01-09 01:31:00 +0800: Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
2009-01-09 01:31:01 +0800: Warning: SUID file "usr/libexec/ssh-keysign" has been modified and will not be repaired.
2009-01-09 01:31:02 +0800: Warning: SUID file "System/Library/Printers/IOMs/LPRIOM.plugin/Contents/MacOS/LPRIOMHelper" has been modified and will not be repaired.
2009-01-09 01:31:04 +0800: Warning: SUID file "Applications/System Preferences.app/Contents/Resources/installAssistant" has been modified and will not be repaired.
2009-01-09 01:31:07 +0800: Warning: SUID file "usr/bin/login" has been modified and will not be repaired.
2009-01-09 01:31:07 +0800: Warning: SUID file "usr/lib/sa/sadc" has been modified and will not be repaired.
2009-01-09 01:31:07 +0800: Warning: SUID file "usr/libexec/chkpasswd" has been modified and will not be repaired.
2009-01-09 01:31:08 +0800: Warning: SUID file "usr/bin/lppasswd" has been modified and will not be repaired.
2009-01-09 01:31:08 +0800: Warning: SUID file "usr/bin/quota" has been modified and will not be repaired.
2009-01-09 01:31:09 +0800: Warning: SUID file "usr/bin/ipcs" has been modified and will not be repaired.
2009-01-09 01:31:09 +0800: Warning: SUID file "usr/sbin/traceroute6" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/rlogin" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/rsh" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/at" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/atq" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/atrm" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/batch" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/chfn" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/chpass" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/chsh" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/newgrp" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/passwd" has been modified and will not be repaired.
2009-01-09 01:31:10 +0800: Warning: SUID file "usr/bin/top" has been modified and will not be repaired.
2009-01-09 01:31:11 +0800: Warning: SUID file "Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy" has been modified and will not be repaired.
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/appletviewe r", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/apt", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/extcheck", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/idlj", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jar", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jarsigner", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/javac", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/javadoc", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/javah", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/javap", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jconsole", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jdb", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jinfo", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jmap", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jps", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jsadebugd", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jstack", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jstat", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/jstatd", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/keytool", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/native2asci i", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/orbd", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/pack200", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/policytool" , should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/rmic", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/rmid", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/rmiregistry ", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:17 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/serialver", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/servertool" , should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/tnameserv", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/unpack200", should be -rwxr-xr-x , they are lrwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/unpack200", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/tnameserv", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/servertool" , should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/serialver", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/rmiregistry ", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/rmid", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/rmic", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/policytool" , should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/pack200", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/orbd", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/native2asci i", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/keytool", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jstatd", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jstat", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jstack", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jsadebugd", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jps", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jmap", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jinfo", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jdb", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jconsole", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javap", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javah", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javac", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jarsigner", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jar", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:18 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/idlj", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:19 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/extcheck", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:19 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/apt", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:19 +0800: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/appletviewe r", should be lrwxr-xr-x , they are -rwxr-xr-x .
2009-01-09 01:31:24 +0800: Group differs on "private/etc/cups", should be 0, group is 26.
2009-01-09 01:31:57 +0800:
2009-01-09 01:31:57 +0800: Permissions repair complete
2009-01-09 01:31:57 +0800:
2009-01-09 01:31:57 +0800:
Please advise what could be happening?
Thanks in advance

I must confess that that's a lot of warnings and messages.
If you re-run the permissions repair are they gone? Or are they still there?
I have found that using the manual combo update reduces the number of these warnings to just a few. I typically get the cups thing every so often and get a few SUID warnings but only two or three.
What you have, IMO, is an exceptionally large number of warnings.

Disk Utility says it can't repair hard drive...now what?

I managed to get Disk Utility to run the Repair, but it gave me a message that said after 3 attempts to repair the disk, it was unable to. Repair failed. Now what do I do? Any thoughts?

Ah, I see your other post is a duplicate of this thread. Regarding the "underlying task reported failure" message, are you getting that with respect to "temp#####" files? Per Using Disk Utility in Mac OS X 10.4.3 or later to verify or repair disks, you can ignore those messages.
DiskWarrior can often make repairs that Disk Utility cannot.
If you have access to another Mac, you can try FireWire target disk mode to backup/recover the eMac data.

Disk utility gives "Error: Partition map repair failed while adjusting structures to fit current whole disk size"

I am getting the following error when running Disk Utility (under ML) on an exteral USB hard drive:
Error: Partition map repair failed while adjusting structures to fit current whole disk size.
I get thsi when I ask Disk Utility to "Repair Disk" at the top level of the disk hierarchy (i.e. not on one of the partitions within the disk but on the disk itself). I was not getting this error with Lion on the same disk before I upgraded from Lion to ML.
It seems like a bug in ML. I found websites where they suggest that you just run Lion's Disk Utility and it will show the disk to be fine.
Any thoughts?

So, I finally seemed to have resolved things with the Seagate 4TB Firewire external drive. If you Google about, you will find a thread on Seagate's own support forum that describes how to disable the sleep function on the drive. You CANNOT ALLOW THE DRIVE TO SLEEP WHILE CONNECTED TO YOUR MAC.
After a lot of reading, here's what I think is happening: the drive goes to sleep, after some period of inactivity, and when you shutdown your Mac, OS X tries to write something to the drive as part of the dismount / disconnect / shutdown process. That fails in some manner, leaving the drive 'corrupted' at the filesystem or partition level.
Then, on the next boot-up, Mountain Lion tells you that it cannot repair the drive and it mounts as read only. Your only fix at that point is to re-partition / re-format and start over (which is big fun with 3TB of data to copy back on to the drive).
If you prevent the drive from sleeping, whenever it's connected to the MacBook, then the above process doesn't occur and voila, the drive just works. So far, I haven't had any problems with about a week of starting / shutting down my MacBook connected to the offending drive (translation: I was going to return the drive, but the problem is clearly with Mac OS X Mountain Lion).

After SL Install - Disk Utility reports permission problem - no repair

After installing SL. When I ran Disk Utility and repair permissions I came up with the following. Is there anything I should worry about? Should I repair the install with archive and install.
Repairing permissions for “Snow Leopard”
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" 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.
Permissions repair complete

Is there anything I should worry about?
No.
Should I repair the install with archive and install.
No, and you can't anyway. The Archive & Install option was removed in Mac OS X 10.6.
(47704)

USB Hard Drive that Disk Utility says it can't unmount

I have a 93.2 Gb Hard Drive (from an old G4 PowerBook) inside an enclosure with USB connection. While trying to recover data from it using Data Rescue (on a G4 PowerBook), Data Rescue II hung. After restart, the USB Hard Drive can not be read at all. Disk Utility says it can't repair it or erase it because it can't "Unmount" the disk. What can I do with the USB Hard Drive?

try this: open system preferences/spotlight/privacy and drag that external into spotlight privacy then try Disk Utility.

Disk Utility - get errors and disk utility can not repair, even start ext.

Hello
I am using Mac OS X 10.5 on a MacBook Pro intel 2.4 Ghz Intel Core 2 Duo, 2 GB RAM, Intel and Boot Camp / Win XP installed.
To check my user rights and repair the main HD I have installed 10.5 on my external 500 GB USB 2.0 HD. Started from it and started the disk utility trying to check and repair the Macintosh HD Partition (not win xp). I got following error messages:
2007-12-01 10:47:12 +0100: „Festplatten-Dienstprogramm“ wurde gestartet.
2007-12-01 10:47:20 +0100: Zugriffsrechte für „Macintosh HD“ reparieren
2007-12-01 10:53:51 +0100: Warnung: Die SUID-Datei „usr/libexec/load_hdi“ wurde geändert und wird nicht repariert.
2007-12-01 10:53:51 +0100: Warnung: Die SUID-Datei „System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool“ wurde geändert und wird nicht repariert.
2007-12-01 10:53:51 +0100: Warnung: Die SUID-Datei „System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum“ wurde geändert und wird nicht repariert.
2007-12-01 10:53:52 +0100: Warnung: Die SUID-Datei „System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner “ wurde geändert und wird nicht repariert.
2007-12-01 10:53:55 +0100: Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „private/var/root/Library/Preferences“ erwartet.
2007-12-01 10:53:55 +0100: Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „private/var/root/Library“ erwartet.
2007-12-01 10:53:55 +0100: Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „private/var/root“ erwartet.
2007-12-01 10:53:57 +0100: Warnung: Die SUID-Datei „System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig“ wurde geändert und wird nicht repariert.
2007-12-01 10:53:57 +0100: Warnung: Die SUID-Datei „System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig“ wurde geändert und wird nicht repariert.
2007-12-01 10:54:00 +0100: Warnung: Die SUID-Datei „usr/libexec/authopen“ wurde geändert und wird nicht repariert.
2007-12-01 10:54:01 +0100: Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „System/Library/CoreServices/Finder.app/Contents/Resources/CannedSearches/All PDF Documents.cannedSearch/Resources/version.plist“ erwartet.
2007-12-01 10:54:01 +0100: Warnung: Die SUID-Datei „System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool“ wurde geändert und wird nicht repariert.
2007-12-01 10:56:07 +0100: Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „Applications“ erwartet.
2007-12-01 10:56:07 +0100: Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „Library“ erwartet.
2007-12-01 10:56:11 +0100:
2007-12-01 10:56:11 +0100: Reparatur der Zugriffsrechte abgeschlossen
2007-12-01 10:56:11 +0100:
2007-12-01 10:56:11 +0100:
Translation: wurde geändert und wird nicht repariert. = was changed but was not repaired.
Because it can not repair the errors I have started "repair disk". It says "can not unmount Macintosh HD". Even if I have started from the external disk?
So I get my install CD (Mac OS X 10.5) and started from that. I got the same errors with that disk utility.
Can someone tell me, if this are "right" errors or do I have to try more to repair this errors? My computer is running fine.
I am a bit irritated now.
Best regards
arjello
Message was edited by: arjello
Message was edited by: arjello

Way back in Jaguar Disk Utility would pop up dozens of "advisory" messages of no interest nor meaning to anyone except possibly some programmers. This needlessly alarmed regular users. The same thing is happening again in Leopard. The SUID messages are not meaningful nor are they errors, in effect they are announcements that some list being consulted by the utility says one thing, the actual files say something else, Disk Utility is going to assume there is a reason for actual setting and not going to change it, but you (it's kind of assuming you are the programmer) should know this. If the "Die Zugriffssteuerungsliste" is German for ACL (Access Control List) it is the same deal: an ACL was found, but no one told Disk Utility there was suppose to be one.
If the messages bother you download the whole 110MB 10.5.1 update and run it. It quiets down the output for all the SUID statements save one. Might even shut down the ACL advisories--don't know because I haven't bothered to download 110MBs of updater, I just ran the patch update.
Francine
Francine
Schwieder

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)

Disk utility reports "Device could not be opened" - error when trying to format a new drive in a Mac Pro 1,1

MacPro 1,1 Quadcore 3 GHz (2006 "Woodcrest")
32 GB RAM
ATI Radeon HD 5770
OS X 10.7.5 Lion
I have encountered the following behavior when trying to format a new drive with disk utility. This description has also been send via the Mac Pro feedback as a bug report to Apple.
On searching the web and forums with this particular error message and behaviour I could not find any usful results. So maybe the following description may be helpful for some users.
Best regards.
1. Drive Bay 1 contains the original 250 GB Startupdisk. It works without errors.
2. Drive Bays 3 and 4 contain each a WD Caviar Black 2 TB SATA 3 HDD. They work without errors.
3. I have purchased a third WD Caviar Black 2 TB HDD.
4. In Drive Bay 2 there has been a Seagate 750 GB HDD, which worked in conjunction with all the other drives without error.
5. I exchanged the Seagate HDD in Drive Bay 2 with the new WD Caviar Black 2 TB HDD.
6. On starting the system, it will report to initialize the new drive.
7. On trying to initialize the new drive with disk utility it reports the error [translated from German] "Erasing of the volume has failed. The device could not be opened."
8. I thought that the drive is faulty. Thus I created an RMA-Case at WD. They exchanged the drive without problems.
9. On getting the exchanged WD Caviar Black 2 TB drive I put it in Drive Bay 2 as before.
10. On trying to erase and format the exchange drive I got the same error message "Drive could not be opened."
10.1 On selecting the physical drive in the devices list, disk utility reports all information in the bottom area of its window as usual, e. g. hard disk description, connection bus, type and place, capacity, write status, SMART-status, partition scheme.
10.1 On leaving that drive selected in the devices list and clicking the info-button, disk utility will also report additional information as usual, e. g. Name, Type, partition scheme, media-identification, media name, media type, device tree, … , number of relocated sectors, etc.. All this information appears to be valid, as can be compared to the other devices information inside the other Drive Bays. Also the disk numbering scheme appears to be standard - 4 HDDs give the numbering disk0, disk1, disk2, disk3.
10.2 From that information I conclude that the SATA-bus and connectors electrically work properly, the drive has spun up and can be accessed by the system normally.
11. I powered down the computer, took out the HDDs from Drive Bays 3 and 4 and put the caddy with the new exchange drive in Drive Bay 4 [Maybe, I could have also just left it alone in Drive Bay 2, or 3].
12. After powering on the system, disk utility will quick format the exchange drive without any error message. Also, when erasing again by selecting the option to write zeros to the drive, disk utility will finish without error.
13. After disk utility finished formatting, I put back the original drives into Drive Bay 3 and 4 and put the now newly formatted drive back into Drive Bay 2.
14. After switching on the computer the system start and login proceeds without any error message. All drives appear as expected on the desktop.

If anyone is reading this still looking for what caused the issue and how to fix it here is what I discovered.
The antivirus program our company uses, Bitdefender Antivirus Plus, was causing some of the PDF files not to open. After troubleshooting the different modules and settings the culprit was..
Scan SSL in Privacy Control Settings. Turning it OFF solved the problem and all the PDF files that previously would not open now open just fine. This issue has been sent to Bitdefender for them to review. If you use a different antivirus program and are having this issue try locating the Scan SSL setting and see if turning it off solves the problem.

Disk Utility Reporting Hardware Failure on Mac HD- Not Repairable

Hi! Looks like my hard drive is toast on my 24" aluminum case 24" imac. NOT under warranty although I bought it in Jan 09. DU reporting Mac HD in RED with message...'disk utility has detected hardware problem which cannot be repaired'. Ok. Will a simple hard drive replacement do the trick? Or, could there be additional grief? Thanks!

Do you have a backup of at least your personal data on the drive? If you do, you should try reformatting (erasing) the drive using Disk Utility, before giving up on it.
Restart from your Mac OS X installation disc, for the system you have installed currently; to do so, insert disc and restart with the C key held down. When you get to the first Installer screen (after language selection), go up to the menu bar. Under Utilities, select to run Disk Utility. In the sidebar, select the internal drive. On the +First Aid+ tab, run +Repair Disk+ (not +Repair Disk Permissions+ ). Do you still get that previous error at some point in this process? Do you get some other error that Disk Utility is not able to repair?

Disk Utility issue-Error: The underlying task reported failure on exit

When I run Disk Utility on the hard drive( repair permissions/verify disk), I see an "illegal name" message and the following error message and DU will not complete the "verify disk" function.
-Error: The underlying task reported failure on exit
What does this mean and how do I fix it?
Thanks, Pete
iMac 17 G5 Mac OS X (10.4.3) Igb ddr ram and winning attitude

Thanks, I have deleted the legal and legal. files but DU is erroring with this message now;
Volume Header needs minor repair
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit

In disk utility, it shows that my external hard drive is somehow unmounted and I can't access it in finder or repair it in Disk Utility. How can I get this working without losing my important data?

In disk utility, it shows that my external hard drive is somehow unmounted and I can't access it in finder or repair it in Disk Utility. How can I get this working without losing my important data?
Thank you!

When you erased the disk did you select Mac OS Extended Journaled as the format option?

Disk Utility Reports Error, Can't Repair

Similar Messages

Maybe you are looking for