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.

Similar Messages

  • 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 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 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

  • 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 reports a block count error for a deleted file?

    I carry out a regular scan of the hard drive and on occasions disk utility reports that a file has a bad block count. It is usually a large file like a CR2 or TIFF and is also one which has been deleted? Not only put in the trash but emptied the trash as well.
    The only other thing of note, which I havn't checked if it is relevent to my problem, is on occasion when I go to empty the trash it reports it can't be fully emptied as one of the files is still in use, even though it isn't? If I use secure empty trash it dletes the file.
    In case its relevent:
    I use Canon's DPP & ACR for CR2 files and PS CS6/CC for TIFF's. I also delete TIFFS from within Bridge CS6/CC.
    Both Disk Utility and Drive Genius report the SMART status as being OK.

    Hi Hollie, and welcome to the forums!
    Have you created images before successfully?
    Is this to/on your boot drive, or an external drive?
    Have you done any Disk/OS maintenance lately?
    We might see if there are some big temp files left or such...
    How much free space is on the HD, where has all the space gone?
    OmniDiskSweeper is now free, and likely the best/easiest...
    http://www.omnigroup.com/applications/omnidisksweeper/
    WhatSize...
    http://www.macupdate.com/info.php/id/13006/
    Disk Inventory X...
    http://www.derlien.com/
    GrandPerspective...
    http://grandperspectiv.sourceforge.net/

  • Disk Utility gives error and does not rebuild mirrored RAID

    After having a HDD fail on a mirrored RAID I replaced the HDD and attempted to rebuild. Disk Utility reports via Console that it can not find an Apple Boot partition to check size and then fails to repair the RAID. Details follow.
    Mac OS X v.10.4.8 Server
    Power Mac G3 (Blue & White)
    512MB RAM
    20GB ATA HDD – boot device on internal ATA bus
    4x 160GB ATA HDDs - setup in RAID scheme on Sonnet ATA/133 PCI card
    RAID configured using Mac OS X v.10.4.8's Disk Utility and is an Apple RAID version 2.
    RAID scheme <from "diskutil checkRAID" cmd>:
    Welcome to Darwin!
    [myserver:~] myadminuser% diskutil checkRAID
    RAID SETS
    Name: Mirror_2
    Unique ID: 5FF8AD5F-0892-482D-B430-C7069D63AFD2
    Type: Mirror
    Status: Online
    Device Node: disk3
    Apple RAID Version: 2
    # Device Node UUID Status
    0 disk0s3 1FB48B00-3E52-4C29-8F05-2ED8BDAE4544 Online
    1 disk6s3 BF2E69C6-698E-4D6A-A2A9-FE8CDAD8A7B1 Online
    Name: Mirror_1
    Unique ID: B448A09D-EC10-41EE-BA45-4D4071A88EA5
    Type: Mirror
    Status: Degraded
    Device Node: disk5
    Apple RAID Version: 2
    # Device Node UUID Status
    1 disk2s3 09AD5705-CF67-48B3-8E31-79983BD4781A Online
    0 disk4s3 23EB1952-8B18-4400-A6FE-22C2F707C097 Failed
    Name: StorageRAID1
    Unique ID: 2B8349AB-F553-4FD2-8440-C575791DA858
    Type: Stripe
    Status: Online
    Device Node: disk7
    Apple RAID Version: 2
    # Device Node UUID Status
    0 disk3 5FF8AD5F-0892-482D-B430-C7069D63AFD2 Online
    1 disk5 B448A09D-EC10-41EE-BA45-4D4071A88EA5 Online
    I configured this RAID scheme (two two drive mirrors striped together) according to this kbase document: http://docs.info.apple.com/article.html?artnum=304377
    As shown in the above "diskutil checkRAID" output I have a failed HDD. So I replaced the HDD with another 160GB cold spare. I added the new drive to the mirror "Mirror_1" also known as disk5 and hit rebuild. Received the normal message that all data on the new drive I was adding would be erased.
    I then receive the following error immediately in the Console Log:
    Rebuilding RAID "Mirror_1"
    2006-12-15 23:50:24.741 DiskManagementTool [375] WARNING: Could not find Apple Boot partition to check it's size, skipping disk5s-1s.
    Rebuilding RAID slice "disk4s3"
    Just to stem some confusion, the device ID disk4s3 has been used by the system for both the old failed HDD and the new replacement HDD.
    The result of this attempted rebuild is I end up with all the data from Mirror_1 on the new HDD but the new HDD is not successfully added to the RAID, therefore Mirror_1 is still degraded and my problem not resolved.
    I ran the appropriate rebuild cmd from both the GUI Disk Utility as described and from the CLI "diskutil repairMirror disk5 disk4s3" but no joy.
    Any help would be greatly appreciated. This volume houses a large amount of important data including user home directories so while some offline time may be required data loss would not be very acceptable.
    Thanks in advance and I will be happy to provide more information as necessary.

    I guess doing it in Terminal would fail too:
    diskutil repairMirror disk5 disk4

  • Disk utility reporting "Microsoft Reserved"

    Hello,
    I have been having a problem with Disk Utility reporting a NTFS volume as a Microsoft Reserved one. I run Windows XP on the NTFS partition, and use macdrive to access my HFS+ vol, but I cant use NTFS-3G to access the other way round, as it wont mount. Does anyone know of a method to possibly rescan the hard drive? rEFIt recognizes it.
    Thanks in advance.
    iMac 24" Mac OS X (10.4.9)

    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 reports smaller hard drive size than actual

    I have been using a 3tb external drive (Formatted mac osx journaled) without any problems on my mac mini.  Suddenly, it no longer allows me to write to the drive and more often it does not even recognize the drive when it is in the caddy.  The caddy supports USB3 and is fairly new.  The hard drive is a 7200rpm seagate. 
    When looking at the drive in disk utility, it states that the drive is 2.2 TB while the size is 3TB.
    Does anyone have similar problems? Any recommendations?
    Currently on OS X version 10.8.5.
    Thanks!
    When I insert the drive in the caddy I get the error message that it is not readable.  Disk utility reports it as 2.2tb.  The drive is a 3TB Seagate.

    Hi Eric,
    Can't really hook it up directly to a mac mini as the mini is pretty sealed.  I did connect it to a PC as I wanted to run SpinRite on it and SpinRite gave me an error message that the Drive Size reported was less than the actual physical drive size.
    SpinRite recommended not to perform any actions on the drive due to this discrepancy.
    Not sure where to go at this point.
    I could try to re-format the 3TB with OS X Journal and see if I get the 3tb back...

  • 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)  

  • Internal Hard Drive Died - Now replaced - Disk Utility Internal Error

    When using the original system disk to install OSX the new hard drive isn't recognised even though I have formatted it for an intel based mac (GUID Partition, Extended Journaled etc) using my imac . When launching Disk Utility from the system disk and trying to erase/partion the drive, I get the following error message "Disk Utility Internal Error - Disk Utility has lost its connection with the Disk Management Tool...". When connected to my imac using a converter it appears on my desktop. Any help would be greatly appreciated. The macbook in question is a 2006 (white). PLEASE HELP.....

    Hi - Thanks for your reply. I have tried that but it still doesn't work. I have had a look around online for the past couple of hours and I found a post that said that newer hard drives can't be recognised by an original 10.4 osx system disk. I would need to find a copy of 10.5 to install OSX on a new hard drive. I dont know if that's true because I dont have a copy of 10.5. Any thoughts would be appreciated!

  • Disk Utility internal error message

    I am receiving an error message every time I try to repair permissions on my MB running OS X 10.4:
    error:
    Disk Utility Internal Error
    Disk Utility has lost its connection with the Disk Management Tool and cannot continue. Please quit and re launch Disk Utility.
    Tried that several times to no avail. After quittting Disk Utility, system becomes very sluggish and Finder stops responding.
    I then booted from the installation CD and ran a Hard Disk integrity check. It checked Ok. Then I tried a permission repair and got the exact same error message quoted above.
    Any help?

    There was a problem with this a couple of years ago involving iTunes Library Receipt files. See [Mac OS X 10.3: Repair Disk Permissions 'Disk Utility has lost its connection with the Disk Management Tool.|http://docs.info.apple.com/article.html?artnum=303132].
    It seems unlikely that would surface now, but the suggested fix is worth trying. The article also mentions looking at Console log. Console is in Applications/Utilities.
    Also, see this recent thread in the Panther forum:
    http://discussions.apple.com/thread.jspa?threadID=1585878

  • Disk Utility: Burn error: 0x80020022 The device failed to respond...

    I've been working on archiving a ton of video to DVD. I'm using Dual-Layer discs to minimize the amount of physical storage space needed for the finished project. I burned several discs in iDVD in July and regularly received errors. Then the drive suddenly stopped loading any type of media. Anything I inserted would spin briefly and then eject. Repaired permissions and followed steps outlined here and here. Took the Mac back to the store where I bought it (sadly, not an Apple Store - nearest one is 12 hrs away) where naturally it performed flawlessly for the store rep.
    So I took it home and resumed burning, now saving as a disc image (ignoring iDVD's warning about the performance of DVDs burned this way) and using Disk Utility, since iDVD didn't seem to be reliable. Burned about 25 discs, error-free, in this fashion, then three days ago, got the error: "Unable to burn “Disc 19.img”. (The device failed to respond properly, unable to recover or retry.)"
    Retried the same image, and it worked. Then burned two more in the same fashion with no errors. Today I got the same error again. Logs are identical for each failed burn, except for the time span between certain lines.
    Price of DL media being what it is, I'd hate to keep ruining discs if there's something I can do to avoid it. I suppose it could be bad media, but it seems odd that I'd get two bum discs that close together after burning so many without issue. Checked the site and the forums, and there doesn't seem to be any answers. Does anyone have any ideas? (Other than "try a different brand of media." I've got a buttload of these discs and it's too late to return them now.) Even if it just helps determine where the issue lies. Warranty will be up soon, so if it's hardware related, I need to get it taken care of quick.
    Media: Philips DVD+R DL 8x
    *Drive info:*
    HL-DT-ST DVDRW GS21N:
    Firmware Revision: SA15
    Interconnect: ATAPI
    Burn Support: Yes (Apple Shipping Drive)
    Cache: 2048 KB
    Reads DVD: Yes
    CD-Write: -R, -RW
    DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
    Write Strategies: CD-TAO, CD-SAO, CD-Raw, DVD-DAO
    Media: Insert media and refresh to show available burn speeds
    DiscUtility.log:
    2009-10-03 08:54:01 -0600: Burning Image “Disc 22.img”
    2009-10-03 08:55:15 -0600: Image name: “Disc 22.img”
    2009-10-03 08:55:15 -0600: Burn disc in: “HL-DT-ST DVDRW GS21N”
    2009-10-03 08:55:15 -0600: Erase disc before burning: No
    2009-10-03 08:55:15 -0600: Leave disc appendable: No
    2009-10-03 08:55:15 -0600: Verify burned data after burning: Yes
    2009-10-03 08:55:15 -0600: Eject disc after burning
    2009-10-03 08:55:15 -0600:
    2009-10-03 08:55:15 -0600: Preparing data for burn
    2009-10-03 08:56:30 -0600: Opening session
    2009-10-03 08:56:35 -0600: Opening track
    2009-10-03 08:56:35 -0600: Writing track
    2009-10-03 09:01:37 -0600: Finishing burn
    2009-10-03 09:02:37 -0600: Closing session
    2009-10-03 09:02:38 -0600: Finishing burn
    2009-10-03 09:38:37 -0600: Burn failed
    2009-10-03 09:38:37 -0600: The device failed to respond properly, unable to recover or retry.
    2009-10-03 09:38:37 -0600: Additional information can be found in the ~/Library/Logs/DiscRecording.log log file.
    2009-10-03 09:38:37 -0600: Unable to burn “Disc 22.img”. (The device failed to respond properly, unable to recover or retry.)
    DiscRecording.log:
    Disk Utility: Burn started, Sat Oct 3 08:55:15 2009
    Disk Utility: Burning to DVD+R DL (CMC MAG D03) media with DAO strategy in HL-DT-ST DVDRW GS21N SA15 via ATAPI.
    Disk Utility: Requested burn speed was 47x, actual burn speed is 4x.
    Disk Utility: Burn failed, Sat Oct 3 09:37:15 2009
    Disk Utility: Burn sense: 4/44/90 Hardware Error,
    Disk Utility: Burn error: 0x80020022 The device failed to respond properly, unable to recover or retry.
    Message was edited by: Weasel42

    I have encountered the same problem. I have a Mac Book Pro from 2007, and it has gone through 3 DVD writers so far, all of which have ruined DVD+R DL disks. I have occasionally been able to burn one, but usually during verify, I get this error message:
    Communication to the disk drive failed: 0x8002022
    And disk utility fails with a "Invalid B-tree node size" error
    Oddly, when I try to burn a disk near capacity (6.5Gb or more) it is more likely to fail than if I burn a smaller disk.
    I've been using Memorex DVD+R DL disks, but I have used other brands in the past but they have failed, too. Out of about 50 disks so far, I have had success with about 5.

  • Disk Utility reports DVD disc does not have enough space

    I am trying to create backup DVDs of some valuable data using my Macbook
    I have used Disk Utility to create a disk image of the original DVD. When trying to burn the image to the blank DVD (4.7GB DVD-R), Disk Utility reports: 'The disc inserted does not have enough free space'. This occurs for both a disk/disc image of 4.26GB and one of a mere 451MB.
    Any ideas on how can I overcome this?
    PS: when is a disk a disc and vice-versa? Apple don't seem to know; the spellings above are verbatim.

    If you are trying to duplicate the DVD then I suggest trying this:
    Duplicate a CD or DVD
    1. Insert the DVD/CD;
    2. Open Disk Utility, and select the DVD/CD from the left side list (select the DVD/CD icon on top);
    3. from the DU File menu select New | Disk Image from Disk 1;
    4. Choose to format the disk image as DVD/CD Master, name the disk image and click Save;
    5. When the .cdr file is finished select it with mouse and press COMMAND-I to open the Get Info and check the box to lock the file;
    6. Choose the .cdr file from the left side list, click Burn, and insert a new, blank DVD or CD.
    Otherwise I would consider using backup software that can span a backup across multiple optical media such as Retrospect, Toast, etc. You can look for them at VersionTracker or MacUpdate.
    It's hard to offer more because you really did not provide any detail on precisely what you are doing and how you are trying to do it. More information may enable us to provide better suggestions.

  • 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.

Maybe you are looking for

  • Unable to upgrade itunes from 10.4.80 to 10.4.1

    Hi all, I'm trying to update my itunes software to version 10.4.1 but every time i try to do it i got this error (after Apple Store updater software has downloaded new files): "Error through installation of upgrade. if it persists choose from Tools>

  • Mac Pro boot sound on Cinema display

    Hey guys, Is it possible to run the Mac pro boot sound on my cinema display instead of the Mac pro's build in speakers? My macbook sounds more agressive than that Mac badboy . thanks! -Sam

  • Reading data from input stream on unix

    I have a program that reads data from input stream from the socket. If the data is over 1500 bytes it is sent in multiple TCP packets. Whats weird is, if I run the program in windows environment it waits till it receives all the packets but when I ru

  • Tinted Screen of Death

    I've had my PB G4 for two years, and I was downloading a CD to iTunes, after I was done, I closed iTunes, and reopened it about two hours later, and all but 20 songs were gone. I got them back but all of my created playlists were gone and the Date Ad

  • Recording sound directly from the web?

    I have Adobe Soundbooth CS3, and I'm trying to find a way to record a sound directly (on the wire) from a web page. I've been unable to do this, being relegated to the built-in microphone. One example, is recording the interesting "Audio Preview" on