Inconsistent Disk Utility Results

When I run Verify Disk in Disk Utility from my boot drive, it tells me the drive needs repair. See log below.
Then when reboot from the recovery partition and run Verify Disk from the recovery partition, it says the disk is okay. Same if I run repair disk. What gives?
Log:
Verifying volume “JDS Macintosh HD”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 5E521F4E-58F6-4069-B3C4-8F9FC44F58D7 on 1 device
disk0s2: Scan for Metadata Volume
Logical Volume Group has a 16 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify B9AFF121-97DC-4C18-AC82-DF352B0C4313
Load and verify 6795ADE3-BB8D-4D3C-AF19-34B0C5848617
Load and verify Freespace Summary
Load and verify Block Accounting
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 5E521F4E-58F6-4069-B3C4-8F9FC44F58D7 appears to be OK.
Checking file systemPerforming live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Invalid directory item count
(It should be 860 instead of 861)
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume JDS Macintosh HD was found corrupt and needs to be repaired.
Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.

Okay, I have got a bit farther into this. I used CarbonCopyCloner to clone my drive to an external Thunderbolt drive and booted from the external. When I ran verify disk from the external it reported the same errors on the internal as it did when verifying while booted from the internal. Moreover, Disk Utility was able to repair the errors.
So it seems there is a bug of some sort in running Disk Utility from the recovery partition. It neither correctly verifies the disk nor does it repair it.
The errors are not, apparently, false positives as suggested above. DU, when booted from the recovery disk, reports a drive as healthy when it is not.

Similar Messages

Disk Utility results

A few months ago I migrated from an iBook G4 w/Tiger to a MBP, and installed Leopard. I did a custom install, leaving out printer drivers, extra fonts and additional languages.
Since I began using this MBP, whenever I repair permissions I get a long list of results like the one below. This occurs no matter how many times I run it. On my iBook, I rarely had permissions that couldn't be repaired.
A lot the permissions are for FrontRow and iPhoto, two apps that I never use. I opened them both up once to see if they would run, and didn't notice anything odd.
Any suggestions why these permissions cannot be repaired?
Repairing permissions for “MBP”
Reading permissions database.
Reading the permissions database can take several minutes.
Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "private/var/spool/cups/cache/rss", should be drwxr-xr-x , they are drwxrwxr-x .
Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Library/QuickLook/iWork.qlgenerator/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions repair complete

HI Oregon,
You can ignore these messages as they are a result of recent updates. Your iBook is older hardware/software, especially FrontRow.
As long as you see, "Permissions repair complete" at the bottom, you are good to go.
About Disk Utility's Repair Disk Permissions feature
If you repair permissions and see, "SUID" ... same thing, read here.
http://support.apple.com/kb/TS1448
Carolyn

Running disk utility resulted in an error... what should I do next?

My MacBook Pro wasn't booting up today. I was getting the spinning wheel and after a minute or so it would restart, and it just continued to restart like that. Looking through the forums, I found some steps to take including starting in safe mode which didn't work for me. I have now rebooted with the install disk and gone into utilities - disk repair. The results: Invalid sibling link, Volume check failed, Error: The underlying task reported failure on exit, 1 volume could not be repaired because of an error.
The logic board was replaced under warranty within the last year. I will make an appointment at the genius bar... unfortunately the earliest I can go is 10am tomorrow, and I had planned on leaving on a road-trip tonight. I need my laptop on the trip as I'm doing some photography work for a resort. Is there anything else I can do to fix the error, or is my best bet to go to the genius bar? Thanks for your help!

Allan, excellent link. I had not seen that before. Thanks.
worldtrekker, to add to Allan's advice: I read through all the followup posts and recommend you do so before using this method. If you already have a current backup, nothing too much to worry about, except your pressing time-frame. If you do not have a backup, but you have another Mac and a FireWire cable available, I recommend booting into FireWire Target Disk Mode and backing up any important data you have on the internal HD before proceeding.
If you do have a portable bootable backup, that is another option, to boot/run from it tomorrow until you get the time to take care of the internal HD.
One other note: Allan first mentioned DW. That is probably the safest bet, but costs more than a new HD, so depends what your priorities are here. Do note that you can download/use DW (don't have to wait for a disc to be shipped), but DW can take many hours, in some cases days to perform its magic. Personally, I think it is a wise investment for anyone who depends on a Mac for income or to store important data. Good luck.

Mac OS 10.5.6 downloaded Firefox 3.6.13 Came as .dmg When I try to launch it says "Not Recognized". Right click for "Open With" refers me to Disk Utility when same results "Not Recognized"

About my Mac > G5 Desktop OS 10.5.6
Want to upgrade to Firefox 3.6.13
The download comes as a compressed file in .dmg format. When I attempt to launch the .dmg file to decompress I get a error message that says: The following disk images failed to mount: Image > Firefox 3.6.13 Reason > Not Recognized. When I right click to see what opening app it is directed to it says: Open with "DiskImageMounter (default). Disk Utility is offered as another opening resource when I direct the file to Disk Utility and go to Menu Bar select "File" then select "Open Disk Image" (or Cmd + "O") I get the same result. Have tried downloading the file twice more and get the same results

Vk2mh it sounds like the download was not complete or corrupted. Where are you downloading the update from? Have you tried downloading again?

Mac Pro not recognizing bootable DVDs and Disk Utility giving odd results.

My issue is complex, but I'll try my best to explain it as I can.
One has been resolved it seems, but I am including it so that the whole issue can be seen in context.
Friday, May 16, 2014
Last night, after rebooting my Mac Pro from my Bootcamp partition (I'm using Windows 7 Professional if that information is helpful) I received a kernel panic upon Mac OS X booting (Mac OS X 10.6.8).
My first action was to launch Disk Utility to verify the Mac HD, verify was stopped by disk utility citing that I should insert my Mac OS X install DVD and repair the disk.
I tried booting from my Snow Leopard install DVD. After the grey Apple logo appeared with the gear spinning below it remained for roughly ten to fifteen seconds (a little long) — then the Apple logo changed to. A grey prohibitory sign (circle with a diagonal line through it, the spinning gear remained. — I tried booting from the Snow Leopard DVD a few time, same result.
Following this I tried booting using Disk Warrior, same result again.
I tried booting both the Snow Leopard and Disk Warrior DVDs in both my upper and lower optical drives, with no change.
I decided to leave the issue and call Apple Support in the morning
Saturday, May 17, 2014
This morning I woke my Mac Pro from sleep, opened Disk Utility and tried verifying the hard drive to see if it was temporary — same result, 'please insert the Mac OS X install DVD and repair the drive.' — I also tried booting the install DVD again with no result.
I then booted my Mac into Safe Mode to check my hardware.
Upon opening Disk Utility and verifying my Mac HD — the result "Macintosh HD appears to be OK", rand the test again to see if this was an anomaly, but disk returned another pass.
I performed a normal restart of my system, although Finder was a little slower to load than normal, the system booted correctly. — I then launched Disk Utility and verified the Mac HD, it returned another pass.
This confused me, after a call to Apple Support the tech explained that 'sometime a Safe Mode boot will fix problems because it disables all non-essential processes when booting. — That makes sense to me.
However.
The issue of my Mac not recognizing bootable DVDs remains — it reads disks correctly, it just will not boot them.
Other steps I have taken to try and resolve this remaining issue.
1. a PRAM reset. — No change.
2. an SMC reset. — No change.
3. Removal of newly installed RAM. — I have tried both running the old and new RAM separately, no change using either combination.
4. Running bootable DVDs in different optical bays. — No change from both bays.
a. My upper drive is an MCE Blu-Ray/DVD combo drive, but I have booted from this drive before. (Less than six months old.)
b. My lower drive is LG DVD-RAM combo drive, I have also booted from this drive before. (Over one year old, replacement for an Apple optical drive.)
None of the above steps have helped, I still cannot boot from my optical drives — I always receive a prohibitory sign shortly after the Apple logo.
Other system information:
Mac OS X 10.6.8
8GB of RAM (4 x 2GB)
500GB Western Digital Caviar Blue HDD (less than a year old, boot drive for Mac OS X 10.6.8)
1TB Samsung HDD (for data storage and also containing Bootcamp partition)
2TB HDD (cannot remember manufacturer, contains Time Machine backups, as well as data storage)
ATI Radeon HD 5770 with 1GB of VRAM
Sorry for the long post but I really need to be able to boot from my optical drives.

Update: found an old Mountain Lion installation USB flash drive I created a while back.
I am able to boot from the ML USB flash drive, but am still unable to boot from my either my Snow Leopard Install DVD or my Disk Warrior DVD. — I have verified both DVD and they pass verification tests.
This leads me to believe that the problem resides either in the Mac, or in BOTH the Snow Leopard and Disk Warrior DVDs.
Since I am able to boot from a USB drive, I will look into the possibility of creating a bootable Snow Leopard drive, and perhaps also a Disk Warrior drive — at least until I can resolve the 'not able to boot from DVD' issue.

HT4790 My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages: Unable to bootstrap transaction group 2517: inconsistent crosscheck (the same with

My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages:
Unable to bootstrap transaction group 2517: inconsistent crosscheck
No valid commit checkpoint found
The volume xxxxxxxxxxxxxx(here it shows physical volume number) was found corrupt and can not be repaired.
Problems were encountered during repair of the partition map
Error: Storage system verify or repair failed.
(the same with 2518, 2519 and 2520 transaction group)
I suppose it is serious bug in Mac OS Lion managing FileVault and wonder what the help could be?

Most likely culprit is your Lacie drives which are notorious for flaky power supplies which cause just the sort of erratic behaviour that you describe. Have had similar issues myself. Lacie has been good about replacing my power converter-- twice. If you have seven of them, good luck finding the bad one or more. Like I said, the behaviour is erratic. Sometimes it'll work sometimes not. I can't comment on Samsung drives because I've never used them and have never heard anything about them. Same with Softraid. Why not just use Disk Utility. Sounds like you're ready for an external hardware raid. This will be much faster, much more reliable, and may even be cheaper than seven firewire drives. Check out G Tech, and Maxx Digital for starters.
Best of luck
Terry

Disk Utility Gives Differing Results...........

I used disk utility (Leopard, not from start up disk) to repair permissions and to verify the hard drive. Permissions repair worked fine (but v slowly), but verifying the disk brought up an error saying that the disk needed to be repaired. I therefore ran disk utility from the disk (ie holding c at startup etc....).
Running disk utility eventually resulted in green text saying that no repair of the disk was necessary.
I restarted, re-ran disk utility in Leopard and it still says the disk needs to be repaired. Onyx also says the disk needs to be repaired. I have run the extended hardware test, which said there are no problems.
Can anyone shed any light on why I am getting these different results and if I need to be worried???
Many thanks in advance!

There are a few important points to verify to ensure an external drive is bootable. Attach the external drive while started up normally. Run Disk Utility. Select the external drive in the left sidebar and look at the info at the bottom of the window. To be able to install Leopard on it, the Partition Map Scheme must be GUID Partition Table.
If it is GUID Partition Table, you can start up from the Mac OS X installation disk and select it as the target for installation. If the drive is not empty, the data already on it will not be affected, but you should probably back it up if it is valuable. After the installation, start up from the external drive and run Software Update to get all the updates. You will have to run Software Update a few times to get all the inter-dependent updates.
If it is not GUID Partition Table, you will need to re-partition it and change it to GUID Partition Table using Disk Utility's Partition tab. In this case, the drive will be erased.
Once you have done the installation and all the updates, you can run Disk Utility while started up from the external drive and select the internal drive for the Repair routine. Since the Repair process should be identical, hopefully the results will be consistent.

Live verification in Disk Utility show incomplete result.

Starting wth Mavericks, when I do live verification of boot drive in Disk Utility, the result shown in Disk utility is not complete and show tht drive is OK in green as it has been in the past.
The verification run without any error, but stop mid wy, not showing that drive is OK. I have to repeat the verification many times before the result that drive is OK show up. I hve filed bug with Aaple, and it is still with me.
Any friend here have experience this problem? When we can expect to have a fix?

I can't help.
I can confirm the same problem on my system, as reported in the similar thread I've started.

Disk Utility does not show any result....

Dear Apple Community,
on my mid 2012 Mac Book Air the disk utility test does not show any result. The test just stops at some point and can be restarted again, but does not show weather the SSD is damaged or not.
Does anyone know what this means?
Thanks a lot for your advice!

I think this happens to everyone (who uses "Live Verification") in Mavericks. Occasionally the output from the test shows correctly, but usually not. I guess this will get fixed someday.
Apple - Mac OS X - Feedback
For now, probably you will get best results from using command-r at startup to get into "recovery mode", then run disk utility from there.
charlie

Result of Disk Utility Verification/repair question!

Hi all. I just updated my OS X to 10.5.2 and downloaded a graphics update, then I proceeded to check permissions using Disk Utility. After completing verify and repair permissions the following entries were shown:
ACL found but not expected on "Application/Utilities"
ACL found but not expected on "Applications"
ACL found but not expected on "Library"
Can any one tell me what ACL means and if I should be concerned about these entries?

Hi Daniel L. I've installed the combo update 10.5.2, repaired the permissions with Disk Utility and for the first time since installing Leopard I have a clear entry with just the lovely message "Permissions Repaired".
Thank you very much for your guidance Daniel. All that now remains is for you to reply to this message so I can reward you with more points for solving my problem for me!
Thanks again, Denis.

Disk Utility resize results in corrupt BootCamp partition

Hello,
Yesterday I decided that I wanted to put Linux on my system: taking what was already a fully working boot camp partitioned drive, resizing the main mac partition to free up some space, and then install debian on that. I went into Disk Utility and resized the drive and that worked just fine, except that when the process was complete my boot camp partition was no longer bootable. It is also no longer labeled BOOTCAMP in the diskutility (though it is when I use diskutil list on the command line), but instead named after its block device (disk0s4 in this case).
I've tried everything I can think of. Disk Utility quickly became useless (repair disk? can't repair disk!), and any sort of attempt to mount the disk on the command line just gives me an "Input/output error," so no dice there. I really need the data off this partition and from what I can tell it seems that the partition is intact, its just the partition map that has been corrupted. I also tried rEFIt's gptsync utility which also did not work. Any suggestions would be very welcome, it's very important that I get the data off this partition.

Honestly, had this process even gotten to a point at which I was on my way to a triple boot I would be much more inclined to agree with you. Yes, I did make a mistake of not backing up before the resize, totally willing to admit that. Of course, that course of discussion leads nowhere in terms of solving this problem. We all know to back things up, most of us do, some don't, nothing new here..
Having said that, this problem has nothing to do with a triple booting. This problem stemmed completely from a simple resize of a HFS+ partition in Disk Utility (a partition, I might add, that was extremely large and mostly free, so overwriting data in the shrink was also not a concern). As far as I'm concerned, if Disk Utility can't resize the partition without destroying/corrupting data, then they shouldn't offer it as a feature. At very least display some sort of message. Maybe: "Hey there! This process USUALLY works, caveat emptor!" I might have been inclined to use _any_ other product.
I'm in the process of using Data Rescue 3 to analyze the drive, and hopefully retreive most of the files. As I previously stated, the actual problem here appears to be completely with a corrupt partition map (Data Recue is having no problem accessing the files so far), but I just don't have the time to dig too deeply into how that all works to solve the problem.

These are my Etrecheck Results. Any ideas why repair disk is greay'd out in disk utility app?

Hardware Information:
          MacBook Pro (17-inch, Early 2009)
          MacBook Pro - model: MacBookPro5,2
          1 2.66 GHz Intel Core 2 Duo CPU: 2 cores
          4 GB RAM
Video Information:
          NVIDIA GeForce 9600M GT - VRAM: 512 MB
          NVIDIA GeForce 9400M - VRAM: 256 MB
System Software:
          Mac OS X 10.6.8 (10K549) - Uptime: 0 days 1:5:39
Disk Information:
          FUJITSU MHZ2320BH FFS G1 disk0 : (298.09 GB)
                    (null) (disk0s1) <not mounted>: 200 MB
                    Macintosh HD (disk0s2) / [Startup]: 297.77 GB (7.54 GB free) (Low!)
          MATSHITADVD-R   UJ-868
USB Information:
          Apple Inc. BRCM2046 Hub
                    Apple Inc. Bluetooth USB Host Controller
          Seagate Backup+ BK 931.51 GB
                    (null) (disk1s1) <not mounted>: 32 KB
                    Seagate Backup Plus Drive (disk1s3) /Volumes/Seagate Backup Plus Drive: 931.39 GB (287.98 GB free)
          Apple Inc. Built-in iSight
          Apple, Inc. Apple Internal Keyboard / Trackpad
          Apple Computer, Inc. IR Receiver
FireWire Information:
Thunderbolt Information:
Kernel Extensions:
          com.AmbrosiaSW.AudioSupport          (3.2)
          com.avatron.AVExVideo          (1.7 - SDK 10.8)
          com.jft.driver.PdaNetDrv          (1.0.64)
          com.avatron.AVExFramebuffer          (1.7 - SDK 10.8)
Problem System Launch Daemons:
          [System] com.jft.PdaNetMac.plist 3rd-Party support link
          [System] org.samba.winbindd.plist 3rd-Party support link
Launch Daemons:
          [System] com.adobe.fpsaud.plist 3rd-Party support link
          [System] com.adobe.versioncueCS3.plist 3rd-Party support link
          [System] com.adobe.versioncueCS4.plist 3rd-Party support link
Launch Agents:
          [System] com.adobe.CS4ServiceManager.plist 3rd-Party support link
User Launch Agents:
          [not loaded] com.adobe.ARM.[...].plist 3rd-Party support link
          [not loaded] com.google.keystone.agent.plist 3rd-Party support link
          [not loaded] com.spotify.webhelper.plist 3rd-Party support link
User Login Items:
          GrowlHelperApp
          GrowlHelperApp
          iTunesHelper
          Palm Desktop Background
          Transport Monitor
          RemoteTapServer
          N067U_ButtonManager
          N124U_ButtonManager
          Skype
          AirDisplayStatusItem
          ScreenCapture
          PdaNetMac
          Dropbox
          Spotify
          TuneupMyMac
Internet Plug-ins:
          JavaAppletPlugin: Version: 13.9.8 - SDK 10.6 Outdated! Update
          FlashPlayer-10.6: Version: 12.0.0.77 - SDK 10.6 3rd-Party support link
          QuickTime Plugin: Version: 7.6.6
          Flash Player: Version: 12.0.0.77 - SDK 10.6 3rd-Party support link
          AdobePDFViewer: Version: 8.3.1 3rd-Party support link
          OfficeLiveBrowserPlugin: Version: 12.3.6 3rd-Party support link
          Google Earth Web Plug-in: Version: 7.1 3rd-Party support link
          Silverlight: Version: 5.1.20513.0 - SDK 10.6 3rd-Party support link
          iPhotoPhotocast: Version: 7.0
iTunes Plug-ins:
          Quartz Composer Visualizer: Version: 1.2
User Internet Plug-ins:
          CitrixOnlineWebDeploymentPlugin: Version: 1.0.94 3rd-Party support link
3rd Party Preference Panes:
          Adobe Version Cue CS3 3rd-Party support link
          Adobe Version Cue CS4 3rd-Party support link
          Air Display Preferences 3rd-Party support link
          Flash Player 3rd-Party support link
          Growl 3rd-Party support link
          RemoteTap 3rd-Party support link
Old Applications:
          None
Time Machine:
          Time Machine information requires OS X 10.7 "Lion" or later.
Top Processes by CPU:
              20%          mds
               3%          EtreCheck
               2%          WindowServer
               1%          hidd
               0%          coreservicesd
Top Processes by Memory:
          109 MB          mds
          98 MB          Finder
          90 MB          WindowServer
          74 MB          Dropbox
          45 MB          coreservicesd
Virtual Memory Information:
          2.10 GB          Free RAM
          761 MB          Active RAM
          466 MB          Inactive RAM
          466 MB          Wired RAM
          1.47 GB          Page-ins
          0 B          Page-outs

Yes, you cannot repair the startup volume from itself. Do the following:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
You need to either free up space on your hard drive or replace it with a larger drive. You should always have at least 20 GBs or 10% of the hard drive's capacity, whichever is larger, as free space.
Freeing Up Space on The Hard Drive
1. See Lion/Mountain Lion/Mavericks' Storage Display.
2. You can remove data from your Home folder except for the /Home/Library/ folder.
3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
4. Also see Freeing space on your Mac OS X startup disk.
5. See Where did my Disk Space go?.
6. See The Storage Display.
You must Empty the Trash in order to recover the space they occupied on the hard drive.
You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.

Movie skips/freezes periodically after burned using Disk Utility

I am trying to make copies of some home movies from the original DVD using Apple's Disk Utility. First, I created the master .cdr image and have burned several DVDs with inconsistent results.
I am using 8x Taiyo Yuden DVD-Rs and burning at 4x or 2x speed using the internal Superdrive. Sometimes the burned DVD will skip or freeze periodically, sometimes it will work fine.
I need to resolve this issue so that I can have consistent quality burns. Any suggestions?

I had this problem a year or two ago.
I don't think the built in imac DVD read /write drives are up to the task.
For quick reliable results:
Toast Titanium 8 and a Sony External Rewritable Drive.
The sony is a noisy brute but its fast and reliable.
I've burnt 100's of Taiyo Yuden DVD-Rs and had very few failures.

Disk utility is acting strange

Hello,
My Disk Utility is acting strange: I get inconsistent results on First Aid.
I get either "Volume Bit Map needs minor repair", "Keys out of order", "Invalid node structure", "Invalid volume file count", "Invalid volume free block count", or "Volume Header needs minor repair". I click Repair Disk. And after some clicking, the problems seem to go away, showing “the volume appears to be ok”. But the problem is that when I hit Verify Disk a couple of times, or a few minutes later, Disk Utility finds these problems again.
Does anybody know what might be going on here? This is my external backup drive; my internal Macintosh HD is fine. Well Disk Utility says so....
Thanks

Verify Disk performs what is known as "live verification" and may sometimes give spurious errors. This is what might be happening. To be sure, this really must be done from Disk Utility booted either from an external Volume or from the Install Disk. I would go straight to Repair Disk and not bother with Verify. Permissions Repair, on the other hand, should be done from the normal boot Volume.
How were you doing "Repair Disk"? You probably know that option will be dimmed out when you are booted normally.

IPod not recognized by iTunes & Disk Utility - Recognized by System Profile

I have a 40GB iPod Clickwheel (4th Gen?) that i'm trying to fix back to life since my mini was just stolen and i'm out on the road on tour all the time. my iPod actually powers up by itself just fine, the battery life is just peachy, and it can run independently without songs (i'm able to look around just as though i had songs on there - i can play games, alter settings, etc etc.).
However, there's a few things i've noticed!
When i go to the iPod's about menu (when disconnected from the computer), it shows there's no songs, that there's 0 capacity, 0 available - shows that the version is 3.1.1, the serial and model numbers, but the format is unknown.
I've tried plugging the dang thing into my computer to much avail - IF iTunes recognizes it, it says it needs to be restored -- GREAT! so i try to restore the iPod, however, i almost instantly get an error: The iPod cannot be restored because it is currently busy. When i clicked the help tag, it says it's a common problem in iTunes 7.0 - great, i have 8.0.2; and i've tried running everything from a restart on the ipod to a restart on the computer, updating all my system files, running the iPod in disk mode, etc, but nothing seems to make it want to restore.
when i look in system profiler; it shows that the iPod is hooked up to my USB port (which is just fine, and i've never had problems running a click-wheel iPod through that before); however both Disk Utility and iTunes do not acknowledge it's existence. what gives?
is my iPod a goner? how would i go about restoring this so i can use it? I've tried it on my Power PC (Specs below) as well as trying it on an iBook and iMac; with the same results every time. i know it's not the cable, because the iPod actually charged via that cable last night!
any help!?

If you can get it to show up in Disk Utility, try reformatting (erasing) it in Disk Utility. If that process completes without stalling or errors, quit Disk Utility and run iTunes. Immediately attempt to do another Restore to install the iPod's software and initialize.
If the iPod does not erase successfully (it should take less than one minute for a standard erase) in Disk Utility, the iPod's hard drive may be faulty.

Inconsistent Disk Utility Results

Similar Messages

Maybe you are looking for