Disk Utility Disk Error

When running disk utility this past weekend I came across the following errors:
Invalid Volume Free Block Count
(It should be 146352250 instead of 146352248)
The Volume Macintosh HD was found to be corrupt and needs to be repaired.
This hard drive is relatively new … the original 500 Gig drive I had in it crashed in June (1 year and 8 months old) so I went to Tekserve and replaced it with a 750 gig drive - effectively, the drive inside my machine is only 5 months old.
Any suggestions?

alessandroab wrote:
Any suggestions?
Yes, you can backup, Zero erase the drive and reinstall OS X, update, programs and finally files.
Zeroing maps off failing sectors, making the data on them more reliable. One should try to do this, or the Erase Free Space option, before any major data writes or formats on a drive to decrease the chances of coming across a newly failed sector.
It also checks the drive as it writes across the entire drive, if there is a major issue, then better to learn about it upfront while the warranty and purchase is still fresh so you can get it exchanged, rather than later on when you decide to address the last portion of the drive and find out.
Drives always ship out with a few bad sectors, some fail along the way. The drive likely works just file it's perhaps the directory info on those bad sectors failed and why you got the problem.
I've only had one hard drive fail in 28 years of using Mac's. One drive! It just died one morning and failed to boot.
All the other minor issues were resolved with a Zero erase, so now I do it upon all new hard drives and before a major write occurs.
You should learn how to clone your boot drive as well, it comes in great asistance, you can boot off the external clone, zero and reverse clone in a few hours, nealry effortlessly.
https://discussions.apple.com/message/16276201#16276201

Similar Messages

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.

Phantom restarts / crashes with Maverick. Restore Disk Utility, disk can't be repaired says "live system repair is not supported" Is there a fix yet? Or is Maverick "FREE" because Apple no longer offers free phone support?

Phantom restarts / crashes with Maverick. Under restore Disk Utility, disk can't be repaired says "live system repair is not supported" Is there a fix yet? Or is Maverick "FREE" because Apple no longer offers free phone support?

Get onto the integrated iOS + Mac OS and end support for "legacy" Mac 10.8 and earlier.
Force older hardware users like me to upgrade to new hardware which is where $$ are.
Make apps work across tablets, phone, and computer with similar (though not the "same" app, but able to read and use the same file format).
Simplify.
I don't think anyone incl. Microsoft knew Windows 8.1 was going to be a free upgrade, I didn't and read that it would be more like $30.
No OS is ready for everyone on the day it is launched. iOS 7 is now 7.04 and climbing, Mac OS tends to really not be ready until the last patch and version is out, often a year or more after it was first issued. Ship it, then plan to fix the bugs left in or that surface.
www.macperformanceguide.com is saying "No" to Maverick for now. Of course there will be no "No" on new Mac Pro 2013 6,1 when those ship (Late Jan? )

Disk Utility returning error

Hello, I am trying to zero out all data on one volume of my OWC Firewire hard drive. I am receiving an "Underlying task error" both when I try to zero erase or Verify/Repair. Any thoughts on this?
Thank you,
Ian McLeod

Boot with your install disk, select your language, and, when the menu bar pops up, select Utilities->Disk Utility and try repairing it from there. If it works, then then try the zero out data option. If it works, then, check the internal HD. When finished, quit DU, Utilities->Startup Disk, select the internal and click restart.

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 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 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 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 says "Error: The underlying task reported failure on exit"

So I decide to play around with Bootcamp for the first time, and I go through the install but it kicks me out, telling me there was some kind of HDD error. It points me to Disk Utility, and I click on Verify Disk, and then I get the following error:
Verifying volume “MacBook”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Illegal name
Illegal name
Checking multi-linked files.
Checking multi-linked files.
g Catalog hierarchy.",0)
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Volume Header needs minor repair
Volume Header needs minor repair
0 %)
The volume MacBook needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
So I do some searching, and Apple tells me that I need to reformat! ***?! There is nothing wrong with my HDD, or at least so I thought. No clicks, no shutdowns, nothing. Does this mean that soon my HDD might die? And if not, how the **** do I go about installing Bootcamp now?
Here's Apple's support document:
http://docs.info.apple.com/article.html?artnum=302411
Thanks much.
MacBook Mac OS X (10.4.8)

You don't need to reformat.
Put your first installation disk in and reboot, holding down the C key when you hear the chimes. When the installation program starts, start Disk Utility from the menu and select your system drive, then do a verify/repair from there.
The reason it can't repair it is because Disk Utility won't do a low level repair on the system drive in case important system files are moved. When you boot off the CD, your system drive isn't in use and can be repaired easily.

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

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

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

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.

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!

Disk Utility Disk Error

Similar Messages

Maybe you are looking for