Leopard Disk Utility SUID Errors

I just got leopard up and running safely and without any programs installed, after repairing disk permissions I am faced with these stupid messages:
2008-02-01 16:05:19 -0800: Repairing permissions for “Macintosh HD”
2008-02-01 16:12:15 -0800: Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
2008-02-01 16:12:16 -0800: Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
2008-02-01 16:12:16 -0800: Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
2008-02-01 16:12:16 -0800: Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
2008-02-01 16:12:17 -0800: Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
2008-02-01 16:12:17 -0800: Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
2008-02-01 16:12:18 -0800: Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
2008-02-01 16:12:18 -0800: Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
2008-02-01 16:12:20 -0800: Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
2008-02-01 16:13:45 -0800:
What is this? Why is leopard so buggy?

Read this:
http://docs.info.apple.com/article.html?artnum=306925
Then there's this thread:
http://discussions.apple.com/thread.jspa?threadID=1304471
And then of course, this one:
http://discussions.apple.com/thread.jspa?threadID=1305308

Similar Messages

Leopard Disk Utility and Input/Output error messages.

This post is describing a problem I had and how I managed to fix it. When I was researching the Input/Output error message I was getting a couple of people had mentioned this fix on the apple discussion boards, so I thought I would add my fix to support them. (Isn't google fab!) I've no idea if this is the right place for this so please bear with me.
Okay a bit of background:- over christmas we treated ourselves to leopard and as my laptop is now three years old I decided to do a complete reformat and installation. I used my 60GB iPod as an external harddrive and backed everything up. Installed Leopard no probs and was a very happy bunny.
The problem:- I then wanted to remove everything off my iPod. So I thought "I know I'll use Disk Utility".... I tried it with the 'default' setting and got an Input/Output error message straight away (irrespective of whether I did it as an extended journal or not.) When I tried it with the Zero Out option (can't remember exactly what it's called) it came up with the Input/Output error message right at the very end. Argh! iTunes and Finder no longer recognised it, but Disk Utility did.
My research:- After using google I saw some guys on here talking about formatting proper external harddrives using leopards disk utility and they were getting the same messages as me. It turns out it is a fault with Leopards Disk Utility. So I did what the guys recommended.
The solution:- (Thank god I had tiger!) I put in my tiger installation disk, clicked 'install tiger' and restarted the laptop. I clicked my my language, but then rather than going through the actual installation process I went to the top menu bars and chose Disk Utility (using tiger's disk one rather than my laptop's leopard one.) And erased the iPod there. Now when I quit the installation and opened my laptop up properly it worked, both iTunes and finder could see it!!! (I just had to restore my ipod in itunes - and now I'm happily transferring all my music back!)
I hope this helps someone in the same position as me!

I took it to work to use my Windows PC to try and format the drive, but got the same problem. I figured either the drive (it's a 2.5" that used to be inside my AlBook) or the external housing it lives is was faulty. Only way I could test without spending more money is by putting the 2.5" drive inside my powerbook, and booting the (Ti) powerbook from a bootable firewire ipod. I successfully booted from the ipod, and had the same problem with the now internal drive: only visible in disk utility, any attempt to erase fails. Also, I plugged the small 10 GB drive that WAS in the TiBook (but which I removed to put the other, problematic drive in) into the external housing, and it connected to other machines just fine.
Turns out the problem is the hard drive itself.
So now my question becomes: If disk utility can see the hard disk when it is connected (I have it back in the external enclosure now), but gives "input/output error" messages when I try to erase/format it, is there any way I can salvage this drive? It's an 80 GB drive, and I was looking forward to making it my internal TiBook drive (replacing the old 10 GB drive that's in there now).

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.

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 - 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 -- SUID FILES "will not be repaired"

Last night I ran Disk Utility.
After repair I received this message --
Warning: SUID file "usr/liveecec/load_hdi" had been modified and will not be repaired.
There is a list of nine similar SUID errors illustrated in screen snap shot at this link:
http://homepage.mac.com/boot321/Permission/PhotoAlbum12.html
I've recently upgraded to 10.5.1
Discovering nine problems that cannot be "repaired" by disk utility gives me concern.
I run a fairly conservative series of applications on my G5. Can anyone advise on what may be needed here?
thank you,
Mike

boot321 wrote:
On the link from Michael Conniff suggesting I read the article that Mac posted saying "not a cause for concern" -- there is only ONE Warning that is illustrated. Since I had a total of NINE, I thought that may have consequence....
Yes, the article appeared just after Leopard was released, when there was only one such message. The others appeared with 10.5.1.
Maybe this will all go away in 10.5.2
There has always been a lag between strange messages appearing and a KB article to explain them. In 10.2.2, we started seeing messages saying "We are using special permissions for the file or directory …". Initially there was just one: by 10.4.4, there were almost too many to count. In 10.4.5, Apple suppressed these messages because all they did was spread alarm around this and other forums.
I have no doubt we'll see the same happen with these SUID messages. If you're interested in what happened before, look at the links in this FAQ: Permissions Issues.

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.

Leopard Disk Utility repair on disk with Tiger partition?

I'm trying to repair a disk containing a bootable tiger partition using disk utility in Leopard and getting a "can't unmount disk error". Suggestions?

After not being able to unmount the Tiger partition it went through and tried to fix my Time Machine partition and gave me this error:
Invalid Index Key
The volume Time Machine could not be repaired after 3 attempts
Error filesystem verify or repair failed
Should I restart and try repairing it again? Do you think I'm getting that error on the TM partition because it couldn't unmount the Tiger partition or is my brand new TM disk hosed?

Boot Camp and Disk Utility giving Error for my Hard Drive Volume

When trying to partition my Hard Drive with Boot Camp, I get an error message after a while saying that it can't be partitioned because there is an error in the volume and that I should check it in Disk Utility. After running Verify Disk, it had told me that the file count was wrong and that I should repair my Disk. I have leopard installed, but only had access to a Tiger Install Disc, so after booting to that and apparently repairing successfully, I booted back onto my Hard Drive and ran Disk Utility's Verify Disk again. Now it said that my Volume Header needs minor repair. I still get the same message in Boot Camp. Running Verify and Repair Disk from the Tiger Install Disc tells me that everything is alright and the Hard Drive doesn' need repairing. I read on an Apple article that verifying a disk that's booted can produce inaccurate results, and that it shouldn't be worried about, but I can't install Windows because of this! What should I do?

Hi,
you have to boot from the Leopard OSX DVD in order to repair the Leopard OSX volume on your harddisk.
Using Disk Utility from an OSX version that is prior to the one you want to repair can indeed cause more errors than before.
So, search for the Leopard DVD.
Regards
Stefan

Disk Utility Partition Error

I updated from Tiger to Leopard, and in the last 2 wks noticed I had little remaining space on my hard disk. After checking in Disk Utility, however, I found that my hard disk partition had reduced from what should be a full 160Mb, to a mere 52Mb or so, but there is NOT another partition (just a grey area for the rest of the blank space)! When I try and increase my hard drive partition a little or even to the full amount, I get an error:
"Partition failed with error:
MediaKit reports partition (map) too small"
I've tried updating to 10.5.2, OS is totally up to date, and have tried starting up from Leopard install disk and using Disk Utility on that to try and increase partition, but all with same error.
Not sure if related, but when I try fix permissions, there are a few unfixed problems regarding ACL's (?), but no other issues.
Message was edited by: gwa75

I am having the same problems on 10.5.2. I have a maxtor onetouch 500gb, I reformatted it to work with time machine, and the partition on the disk is only 382.4gb, with a lot of grey space showing up. When I try to expand the Onetouch partition or create a new partition to fill in the space, it keeps giving me
"MediaKit error: size of disk too small" or something along those lines!

Snow Leopard Disk Utility not showing Disk

Heya, before anyone jumps to conclusion that the disk is just dead, please read the following info.
Background: Basically I'm upgrading to Snow Leopard and I had a striped RAID that I wanted to break and format. They held my Leopard install and I know there's issues w/ SL install seeing RAID (even doing disk boot didn't work for me) so I went the route of booting from SL disk and I broke the soft RAID.
_The problem:_ After I broke the RAID only one of the two HDs was showing up, the one in Bay 1. So I formatted it to see if for some reason it would do something about it. No dice. I even tried taking out the other disk and putting it in bay 1, but to no avail.
*So here's the weird part*: I booted with the Leopard disk and it saw both drives with no problem. The other one that wasn't showing up still was thinking it was part of it's own RAID but after I Erased it, it looked exactly the same stat wise as my other Seagate. So key point: _nothing wrong with the HD_.
_Other info:_ I went into the System Profiler on each booted OS disk and the Leopard one was showing both drives in the Serial-ATA section just fine, wheres Snow's Profiler said there was some error finding the info. Believe me I tried this several times, back and forth.
So has anyone had and/or fixed a problem like this where Snow Leopard's disk utility is only finding one (a specific one) hard drive that was perhaps previously raided?

Update : So I talked to Apple Support and they suggested installing Leopard on the one drive that is found and seeing if it recognizes the drive afterward. It did in fact find the drive just as I had named it. *The Bad*: obviously I can't create a soft RAID using the boot drive while actually booted up and of course the SL install disk still won't find the drive.
But there's a new development: I did the sleep wake test to make sure I didn't go through all this trouble for nothing (I was having a wake from sleep problem in Leopard) and after successfully waking it gave me a nice error saying how a drive was ejected improperly *and the drive no longer would show up in the finder* and the system profiler threw up another error.
I did the same sleep wake test booted in Windows 7 on my 3rd bay drive and both drives would show up and be usable (or at least readable) so I'm still pretty sure it's not the drive.
It must be something about OS X not wanting to power-up or read my other drive correctly, especially after sleeping?

Repeated Disk Utility & fsck errors - what to do next?

After nearly a year of flawless operation (yes, my warranty will soon expire), my iMac has suddenly started to misbehave. Disk Utility has reported finding errors which it is unable to repair. I've run fsck_hfs in single-user mode a couple of times, and after each reboot it again finds errors. Then I bought DiskWarrior and it repaired my drive. All was well for nearly a day, and now I'm back to the same situation. So, what to do now?
Should I reinstall the OS and just run it bare without any additional apps for a while, to see if I get more errors? (I've made a SuperDuper! bootable backup which I should be able to reboot from if needed). Or are these repeated errors to be more likely the sign of permanent problems with my hard disc, and I should go to the local Apple store without wasting any more time?
Fortunately I have a Powerbook to hold me over as a spare machine if I do have to give up my iMac.
All suggestions welcome.
Thanks
S

Since you have a backup I'd suggest you wipe the drive and reinstall. Do this:
Extended Hard Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Upon completion quit DU and return to the installer. Now complete the reinstallation of OS X.

Can I use the Leopard Disk Utility to repair a Tiger partition?

I have a multi-partition external disk, one partition has Tiger installed on it, while others have Leopard. (I used Leopard to partition the drive and then used SuperDuper! to copy my earlier Tiger backup from another disk to this disk.) Now I find I have errors on the partition with Tiger. Can I use the Disk Utility tool from my Leopard install to repair the Tiger partition? Earlier today I tried to boot from my Tiger install DVD and use the Disk Utility there to repair the partition, but it just hangs up and won't go forward.
thanks,
Chris Altwegg

You could use it, but if Tiger's Disk Utility couldn't fix it, it's doubtful Leopard's would fix it as well. You're better off using Disk Warrior from Alsoft.com.

Leopard Disk Utility SUID Errors

Similar Messages

Maybe you are looking for