Invalid number of extended attributes during Verify Disk.

I keep getting invalid number of extended attributes when I run Verify Disk. I run Repair Disk from the Recovery HD, it appears to fix the problem, and then when I restart, I get the same error again. It is causing some apps not to open. It seems to have started happening right after I did the latest OS update. Does anyone have any suggestions? Thank you.

Update
I found my OS 10.4 Install Disk, started from it, ran disk utility on my startup disk and got:
"Invalid Catalog Record Type"
Disk Utility couldn't fix it, but it gave me the following complex verbiage:
"FSCK_HFS (159) Malloc:* Deallocation of a pointer not malloced: 0X83000; this could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug"
If I understood that, I probably wouldn't be posting in the first place.
When I ran Disk Utility from the hard drive again, it now tells me "Invalid Catalog Record Type" as well so maybe I repaired something.

Similar Messages

When I restore my Mac with Time Machine and then want to partition my disk, Disk Utility always says incorrect number of extended attributes

When I need to restore my Mac from a time machine backup and then partition my hard disk (the disk inside the computer not the time machine disk), Disk Utility always says "Incorrect Number of Extended Attributes". I then boot into Recovery HD and run disk repair. The result? "The volume Macintosh HD appears to be OK". So then I reboot into normal OS and try the partition again, still Incorrect number of extended attributes. I have even tried /sbin/fsck -fy in single-user mode but it still says the volume is ok. I have tried partition my disk in the recovery HD and it still fails.
Can anyone please help me solve this problem?

Try something stronger, such as DiskWarrior or TechTool Pro.
iMac refurb (27-inch Mid 2011), OS X Mavericks (10.9.4), SL & ML, G4 450 MP w/Leopard, 9.2.2

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported. Is this a bug in Mavericks?

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported.
This happens not just with the SSD in my Mac Mini, but with another SSD in my MacBook (both now running Mavericks). So far as I know, all of the kit I am using is in good order (despite the file corruption reports). So I am beginning to wonder if it could be due to a bug in Mavericks? Both SSD drives have been formatted to MacOS Extended (journaled) format. Should I have used a different format, I wonder?
Has anyone else encountered this issue?
Does anyone have a solution?
Or an explanation that might help my investigation of the issue?
Thanks guys,

I understand that the Corsair Force 3 is not one of the SSD drives that are supported on Apple Macs.
I did try downloading and using Trim Enabler, but the error message came up both when it was off and when it was on.
I understand that not everyone thinks Trim Enabler is a good program, though there is a new version out now, so I may give it another try.

Leopard install failed: Incorrect # of Extended Attributes

Tried to install Leopard. Incorrect number of Extended Attributes. Could not be repaired using Disk Utility/First Aid. ERROR: Filesystem verify or repair failed. Please help avoid erase and install. Hard drive is Journaled HFS Plus Volume.

I have the same problem.
Anybody has an answer yet?

Macbook Pro won't mount during target disk mode

I don't know what to do.
I was using Safari today when the whole computer froze. Nothing was responding, so I had to force shut down.
When I went to restart, I got a gray screen with the apple logo and a progress bar; the bar will take a while to fill, then the computer shut down completely. Happens every time now.
I tried booting in safemode and it didn't work; the command prompt details said "Incorrect number of thread records. (4, 29503)" and "Incorrect number of extended attributes (It should be 381007 instead of 381008)"....... What does that mean????
I tried booting the backup drive and running disk utility to diagnose the problem, and it said the disk is unable to be repaired etc.
Now I'm trying to salvage my important files by using the firewire target disk mode with another mac. My macbook pro won't even mount; disk utility said it can't be mounted and is damaged.
Please help--what do I do to save these files???

My workflow was like this:
Partitioned fresh hard drive into 2 partitions: 1 for OS clone, 1 for data recovery
Used Carbon Copy Cloner (an excellent tool) to clone working OS to 1st partition
Attached harddrive to malfunctioning MBA
Held Option on malfunctioning MBA and booted to cloned drive
Once booted, I used old-school Data Rescue II to salvage data from MBA internal drive to my data recovery partition. (Probably need a newer / better data recovery program, as this one changed file names, moved things around, was generally not that awesome...)
Used Disk Util from booted clone to format MBA internal drive.
Used Carbon Copy Cloner to clone to formatted MBA internal drive.
Shut down, disconnected external drive, MBA booted normally.
Think that's everything. I've been touting the excellence of Carbon Copy Cloner for a while now for backups. In my opinion it's much more thorough than Time Machine backups, as you don't need a functioning OS. You can boot to a clone -- time / life saving!

Solaris 9 Extended Attributes

Hi,
I am interested in extended attribute implementation details on TMPFS and NFS file systems.
'fsattr' man contains following:
" Conceptually, the attribute model is fully general. Extended
attributes can be any type of file (doors, links, direc-
tories, and so forth) and can even have their own attributes
(fully recursive). As a result, the attributes associated
with a file could be an arbitrarily deep directory hierarchy
where each attribute could have an equally complex attribute
tree associated with it. Not all implementations are able
to, or want to, support the full model. Implementation are
therefore permitted to reject operations that are not sup-
ported. >>>>For example, the implementation for the UFS file
system allows only regular files as attributes (for example,
no sub-directories) and rejects attempts to place attributes
on attributes.<<<<
Rest of man pages have no information about this feature. I would like to know:
-Is there any kind of limitation on TMPFS or NFS similar to UFS (what can be attribute)?
-What are allowed attribute types on TMPFS or NFS?
-What is point of extended attributes on 'tmpfs'?
-What is maximum number of extended attributes (if exist)?
Does anyone know where to find documentation?

Can you be more specific as to the information you require?
I take it you're interested in the filesystem extended attributes?
A good starting point would be the runat(1) man page but if there's
something specific you're interested in please let me know.
Cheers,
Peter.

Can't repair Macintosh HD in Disk Utility (extended attributes)

Hi all,
I have a Retina Macbook Pro with one of them new fancy SSDs in it. I'm running 10.9.3 all up-to-date and am a bit computer-savvy, but I'm more than puzzled by what my Mac has been doing as of late.
When trying to install Windows via Bootcamp, I ran into an error message in the Partitioning step of the process. I hopped into Disk Utility, figuring I could simply partition from there (something in me trusts Disk Utility more than the Boot Camp Assistant). Partition failed!
I then executed the "Verify Disk" command in Disk Utility, only to be told I needed to restart from the Recovery Partition and use the "Repair Disk" function of Disk Utility then. Log of this whole event is at the end of this post, but the offending line seems to be
2014-06-12 20:59:30 -0400: Checking extended attributes file.
2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
I then restarted and followed these instructions. "Verify Disk" found no errors, nor did "Repair Disk." I rebooted, only to be met with the same problem!
Is there some sort of lower-level command I can use to repair my disk if I boot in Single User mode or something?
Thanks,
Nathan
2014-06-12 20:58:30 -0400: Disk Utility started.
2014-06-12 20:58:36 -0400: Verifying partition map for “APPLE SSD SD512E Media”
2014-06-12 20:58:36 -0400: Starting verification tool:
2014-06-12 20:58:36 -0400: Checking prerequisites
2014-06-12 20:58:36 -0400: Checking the partition list
2014-06-12 20:58:36 -0400: Checking for an EFI system partition
2014-06-12 20:58:36 -0400: Checking the EFI system partition’s size
2014-06-12 20:58:36 -0400: Checking the EFI system partition’s file system
2014-06-12 20:58:36 -0400: Checking all HFS data partition loader spaces
2014-06-12 20:58:36 -0400: Checking booter partitions
2014-06-12 20:58:36 -0400: Checking booter partition disk0s3
2014-06-12 20:58:36 -0400: Checking file system
2014-06-12 20:58:36 -0400: Checking Journaled HFS Plus volume.
2014-06-12 20:58:36 -0400: Checking extents overflow file.
2014-06-12 20:58:36 -0400: Checking catalog file.
2014-06-12 20:58:36 -0400: Checking multi-linked files.
2014-06-12 20:58:36 -0400: Checking catalog hierarchy.
2014-06-12 20:58:36 -0400: Checking extended attributes file.
2014-06-12 20:58:36 -0400: Checking volume bitmap.
2014-06-12 20:58:36 -0400: Checking volume information.
2014-06-12 20:58:36 -0400: The volume Recovery HD appears to be OK.
2014-06-12 20:58:36 -0400: Checking Core Storage Physical Volume partitions
2014-06-12 20:58:36 -0400: Checking storage system
2014-06-12 20:58:36 -0400: Checking volume
2014-06-12 20:58:36 -0400: disk0s2: Scan for Volume Headers
2014-06-12 20:58:36 -0400: disk0s2: Scan for Disk Labels
2014-06-12 20:58:36 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
2014-06-12 20:58:36 -0400: disk0s2: Scan for Metadata Volume
2014-06-12 20:58:36 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
2014-06-12 20:58:36 -0400: Start scanning metadata for a valid checkpoint
2014-06-12 20:58:36 -0400: Load and verify Segment Headers
2014-06-12 20:58:36 -0400: Load and verify Checkpoint Payload
2014-06-12 20:58:36 -0400: Load and verify Transaction Segment
2014-06-12 20:58:36 -0400: Incorporate 0 newer non-checkpoint transactions
2014-06-12 20:58:36 -0400: Load and verify Virtual Address Table
2014-06-12 20:58:36 -0400: Load and verify Segment Usage Table
2014-06-12 20:58:36 -0400: Load and verify Metadata Superblock
2014-06-12 20:58:36 -0400: Load and verify Logical Volumes B-Trees
2014-06-12 20:58:36 -0400: Logical Volume Group contains 1 Logical Volume
2014-06-12 20:58:36 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
2014-06-12 20:58:36 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
2014-06-12 20:58:36 -0400: Load and verify Freespace Summary
2014-06-12 20:58:36 -0400: Load and verify Block Accounting
2014-06-12 20:58:36 -0400: Load and verify Live Virtual Addresses
2014-06-12 20:58:36 -0400: Newest transaction commit checkpoint is valid
2014-06-12 20:58:36 -0400: Load and verify Segment Cleaning
2014-06-12 20:58:36 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
2014-06-12 20:58:36 -0400: The partition map appears to be OK
2014-06-12 20:58:36 -0400:
2014-06-12 20:58:36 -0400: Verifying volume “Macintosh HD”
2014-06-12 20:58:36 -0400: Starting verification tool:
2014-06-12 20:58:36 -0400: Checking storage system
2014-06-12 20:58:37 -0400: Checking volume
2014-06-12 20:58:37 -0400: disk0s2: Scan for Volume Headers
2014-06-12 20:58:37 -0400: disk0s2: Scan for Disk Labels
2014-06-12 20:58:37 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
2014-06-12 20:58:37 -0400: disk0s2: Scan for Metadata Volume
2014-06-12 20:58:37 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
2014-06-12 20:58:37 -0400: Start scanning metadata for a valid checkpoint
2014-06-12 20:58:37 -0400: Load and verify Segment Headers
2014-06-12 20:58:37 -0400: Load and verify Checkpoint Payload
2014-06-12 20:58:37 -0400: Load and verify Transaction Segment
2014-06-12 20:58:37 -0400: Incorporate 0 newer non-checkpoint transactions
2014-06-12 20:58:37 -0400: Load and verify Virtual Address Table
2014-06-12 20:58:37 -0400: Load and verify Segment Usage Table
2014-06-12 20:58:37 -0400: Load and verify Metadata Superblock
2014-06-12 20:58:37 -0400: Load and verify Logical Volumes B-Trees
2014-06-12 20:58:37 -0400: Logical Volume Group contains 1 Logical Volume
2014-06-12 20:58:37 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
2014-06-12 20:58:37 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
2014-06-12 20:58:37 -0400: Load and verify Freespace Summary
2014-06-12 20:58:37 -0400: Load and verify Block Accounting
2014-06-12 20:58:37 -0400: Load and verify Live Virtual Addresses
2014-06-12 20:58:37 -0400: Newest transaction commit checkpoint is valid
2014-06-12 20:58:37 -0400: Load and verify Segment Cleaning
2014-06-12 20:58:37 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
2014-06-12 20:58:37 -0400: Checking file system
2014-06-12 20:58:37 -0400: Performing live verification.
2014-06-12 20:58:37 -0400: Checking Journaled HFS Plus volume.
2014-06-12 20:58:37 -0400: Checking extents overflow file.
2014-06-12 20:58:37 -0400: Checking catalog file.
2014-06-12 20:58:59 -0400: Checking multi-linked files.
2014-06-12 20:59:30 -0400: Checking extended attributes file.
2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
2014-06-12 20:59:30 -0400: 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.
2014-06-12 20:59:30 -0400:
2014-06-12 20:59:30 -0400: Disk Utility stopped verifying “Macintosh HD”: 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.
2014-06-12 20:59:30 -0400:

I'm having a similar problem with my G4 Desktop.
I have a 2nd internal hard drive and 2 FW Drives.
None of them are able to be verified or repaired using DU.
I get the following message: "Verify volume failed with error Could not unmount disk." And then some message about "make sure that all your files are closed."
I tried soft-booting by holding the shift-key down just as a trouble-shooting idea and I was able to verify and the drives were working well. However, when I restarted in normal mode I was not able to verify or repair.
What is my G4's problem? Why does it need to use that secondary drive in order to operate? What do I need to do to fix it?
Any suggestions?
G4 Dual 1.42 Mac OS X (10.4.6) 1 Gig Ram / 2 Internal Hard Drives

ORA-01722: invalid number Error during R12.1.1 upgrade

Dear Experts,
During u6678700 driiver upgrade,one of the woker failed with the following error:
ATTENTION: All workers either have failed or are waiting:
FAILED: file jairgmsetupmig.sql on worker 1.
ATTENTION: Please fix the above failed worker(s) so the manager can continue.
From the adwork001.log ,
sqlplus -s APPS/***** @/&un_ja &batchsize 3 u03/oracle/CRP1PROD/apps/apps_st/appl/ja/12.0.0/patch/11
5/sql/jairgmsetupmig.sql 12
DECLARE
ERROR at line 1:
ORA-01722: invalid number
ORA-06512: at line 105
Could not find much in internet.
Please advice.

From the adwork001.log ,
sqlplus -s APPS/***** @/&un_ja &batchsize 3 u03/oracle/CRP1PROD/apps/apps_st/appl/ja/12.0.0/patch/11
5/sql/jairgmsetupmig.sql 12
DECLARE
ERROR at line 1:
ORA-01722: invalid number
ORA-06512: at line 105Have you tried to check line 105 in the script and see if it gives any clue?
Could not find much in internet.
The only hit I have found in (Bug 7120055 : FAILED: FILE JAIRGMSETUPMIG.SQL ON WORKER 1) but it does not tell much, so you may need to log a SR and get more details about this bug.
Thanks,
Hussein

ORA-01722: invalid number - Error during implicit conversion (10g vls 11g)

I am facing oracle error for few SELECT queries in 11g which were working fine in 10g environment.
Oracle Version:
10g - 10.2.0.5.0
11g - 11.2.0.3.0
We are storing numeric values under CHAR or VARCHAR2 column in few tables. This is known design issue & it can't be changed for now.
I know this will work fine until all the data is numeric in those columns for respective table. Because by some reason, if any row got character value for that column then implicit string to number conversion will fail and this error can occur. But I have verified that there is no data issue.
But I can see difference in the execution plan! But not able to recognize the reason issue.
Any other pointers on why the queries are failing in 11g would be of great help..
Example SQL:
Note that table structure and data is same in both the environments.
View Definition -
CREATE OR REPLACE FORCE VIEW CIMSOS.LC_LOCATIONS
(   COUNTRY_ID,    PRODUCTID,
   LANGUAGE_ID,   LOCATION_NAME,
   LOCATION_SHORT_NAME,   TAG_ID,   LOCATION_DEFINITION,
   COMPOSITEKEY,   GLOBAL_LOCATION_KEY,
   CPRODUCTKEYID,   CMODVERSION)
AS
   SELECT
          CCOUNTRY_ID AS COUNTRY_ID,
          CPRODUCTID AS PRODUCTID,
          CLANGUAGE_CODE AS LANGUAGE_ID,
          CLOCATION_NAME AS LOCATION_NAME,
          CLOCATION_SHORT_NAME AS LOCATION_SHORT_NAME,
          CTAG_ID AS TAG_ID,
          CLOCATION_DEFINITION AS LOCATION_DEFINITION,
          CCOMPOSITEKEY AS COMPOSITEKEY,
          CGLOBAL_LOCATION_KEY0 AS GLOBAL_LOCATION_KEY,
          cproductkeyid,
          cmodversion
     FROM mct_35193, goldencopy
    WHERE     cproductkeyid = productkey
          AND cmodversion = version
          AND catalogid = 35193;Facing issue for SQL query based on above view:
** In 10g Env
SELECT * FROM LC_LOCATIONS WHERE productid = 75;
-- It executes successfully and provide required results.
Explain Plan:
SELECT STATEMENT ALL_ROWSCost: 12 Bytes: 416 Cardinality: 4
     4 NESTED LOOPS Cost: 12 Bytes: 416 Cardinality: 4
          1 INDEX RANGE SCAN INDEX CIMSOS.GOLDENCOPY_INDX1 Cost: 10 Bytes: 30,225 Cardinality: 2,015
          3 TABLE ACCESS BY INDEX ROWID TABLE CIMSOS.MCT_35193 Cost: 1 Bytes: 89 Cardinality: 1
               2 INDEX UNIQUE SCAN INDEX (UNIQUE) CIMSOS.XPK_MCT_34342 Cost: 0 Cardinality: 1 ** In 11g Env
SELECT * FROM LC_LOCATIONS WHERE productid = 75;
ORA-01722: invalid number
Explain Plan:
SELECT STATEMENT ALL_ROWSCost: 40 Bytes: 8,692 Cardinality: 82
     3 NESTED LOOPS Cost: 40 Bytes: 8,692 Cardinality: 82
          1 TABLE ACCESS FULL TABLE CIMSOS.MCT_35193 Cost: 22 Bytes: 819 Cardinality: 9
          2 INDEX RANGE SCAN INDEX CIMSOS.GOLDENCOPY_INDX1 Cost: 2 Bytes: 135 Cardinality: 9
-- Executes when value is passed as character.
SELECT * FROM LC_LOCATIONS WHERE productid = '75';

The problem doesn't appear to be related to the Oracle version, at least not directly. If your query plan does the string to number conversion before eliminating the rows that have non-numeric data, you'll get an error. If the query plan eliminates the rows that have non-numeric data before doing the conversion, the query will succeed. It is entirely possible that you'd get the "bad" plan in 10g or the "good" plan in 11g.
You can capture the query plans from your 10g database and move them over to the 11g database. Oracle has a nice white paper on upgrading from 10g to 11g that walks you through that process.
Of course, you really don't want to be dependent on the optimizer picking the "right" plan, you really want to fix the underlying data model issue.
Justin

Cannot create or replace : The specified extended attribute name was invalid.

New problem arrived today. Trying to copy a file from 10.6 server with an XP (SP3) client. I get this error:
Cannot create or replace (file name here): The specified extended attribute name was invalid.
The contents of the file can be copied, but not the folder. Other files can be copied. There are no funny characters. The name is not too long. I propogated the permissions on the share and that had no affect. The problem exists on three different XP systems. Can't find extended properties that could be causeing a problem. Any ideas?

Nikon just released a Firmware update today for the D750

Verify Disk: Invalid Volume File Count

So... I'm not really sure what to do or what exactly is wrong. I'm hoping not to reboot or reinstall all together, but if I have to... I suppose there's no choice.
I tried 'Verify Disk' from the utilities, but is fails and says
Invalid volume file count
(It should be 712836 instead of 712840)
Invalid volume directory count
(It should be 171417 instead of 171413)
The volume Macintosh HD needs to be repaired.
Error: Filesystem verify or repair failed.
I tried doing a 'Repair Disk' from the installation CD, but it says it fails because it could not unmount the HD.
what am I doing wrong and how can I fix it and is it really bad?
I've heard some suggest to go buy Disk Warrior. Will this fix it... or.. probably not?

*"Will this fix it... or.. probably not?"*
You won't know until you give it a try. You should own a copy of Disk Warrior anyway for at least some peace of mind in the future.
If it doesn't work, then you'll need to backup your files, erase the drive and start from scratch.

Verify Disk gives message invalid volume file count/invalid directory count

My Powerbook G4 (running Leopard 10.5.5) was running slower and slower. So I ran Disk Utility. When running “Verify Disk”, I received the following message -
Quote
At “checking volume information”, got the following message –
Invalid volume file count
(it should be 608262 instead of 608269)
invalid volume directory count
(it should be 126277 instead of 126270)
The volume Macintosh HD needs to be repaired.
Error: Filesystem verify or repair failed.
Unquote
A friend told me my hard drive was DEAD and needed to be repaired. Is this true or is there some way to fix my drive?

I started up from my latest OS X Installer (Leopard) and opened Disk Utility (although it seems to give me the Disk Utility that's on my Hard Drive, NOT one on the installation disk). Repair Disk was NOT an option (even after running Verify Disk again to see if that helped).
So, now what do I do now? Disk Warrior may help (or it may not) and a new hard disk isn't THAT expensive. Should I just go ahead and bite the bullet and get a new hard drive???
Oh, and while I'm asking questions - my PowerBook G4 is 5 years old. Besides the dodging hard drive everything else is running ok. But after 5 years (mainly run on mains power, not the battery), is it about time for a new battery? Is there a way to tell whether your battery is about to die before it actually dies and you can't start up?
Message was edited by: paswines

Verify Disk results, confusing.. Can they be the cause of system lock ups?

I have been experiencing strange freezes on my Mac Pro 2008 system.
My boot disk is a 50% full 128GB SSD from Crucial and is running beautifully fast however for the past couple of weeks my system often freezes for anything from 3 seconds to 30 seconds and then the Finder restarts.
After the Finder restarts everything continues running smoothly. As if nothing ever happend, no error reports, no apps crashed, nothing.
I have verified disk permissions and verified the disk itself in Disk Utility but I am not quite sure what these results mean and if they could be the cause of these random lock ups.
here are the results:
Verify permissions for “Boot Disk”
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Group differs on "private/etc/hostconfig", should be 0, group is 20.
Permissions verification complete
Verifying volume “Boot Disk”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Missing thread record (id = 5888152)
Incorrect number of thread records
Checking multi-linked files.
Checking catalog hierarchy.
Invalid volume directory count
(It should be 184294 instead of 184295)
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Boot Disk was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
I would really appreciate it if someone that knows their way around this stuff could help me troubleshoot this.
As for the problem of the system locking up it does not happen in the same application consistently.
Often it happens in Firefox but it could equally often happen when working in Photoshop, browsing files in the Finder or trying to access the Spotlight search via the keyboard shortcut.
When the system locks up I get the spinning beach ball and I can still move the mouse and click and even still access CMD+TAB app switcher, switch spaces and all those things, just applications become non responsive.
If you need any more details please let me know.
Thanks for reading,
Jannis

These are innocuous errors that you may safely ignore. However the disk error is a problem. Do the following:
Repairing the Hard Drive
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 and Leopard.) 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, then quit DU and return to the installer. Now restart normally.
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.

Diskutil - Verify disk - error in log

Sorry for the long post.
I have a iMac Late 2012 with 1TB Fusion drive and been running Yosemite for the past several months. Installed Bootcamp to run Windows 7 and after couple of weeks later wanted to also install Mavericks for my development work as the software that I was trying to use doesn't support Yosemite yet. I tried to remove Bootcamp partition from Disk Utility but unable to do so as the "-" sign wasn't enabled.
Launched Terminal and used some Core Storage commands which messed my parititon I think. After doing this, I got kernel panics while rebooting. I booted into the Recovery HD partition and ran VerifyDisk from Disk Utility and one of the lines has this displayed in red:
Invalid Logical volume header @<some number>
The last line says "The drive appears to be OK". I tried to reinstall Yosemite from a bootable flash drive and to my dismay, the installer didn't list my 1TB Fusion drive. I called up support and have an appointment with Apple care next week.
Meanwhile, as a last resort, I checked on other forums and ran these commands from Terminal:
diskutil cs list
diskutil cs delete <core storage partition>
diskutil eraseDisk jhfs+ <label> <disk id1>
diskutil eraseDisk jhfs+ <label> <disk id2>
After this I continued with the Disk Utillity and it gave me a message saying "No Core Storage found...". Do you want to fix it?
I clicked on the Fix button and it did everything successfully. I partitioned the Macintosh HD into two partitions and and was able to install Yosemite 10.10.1 with no issues. I then ran VerifyDisk from within Yosemite and getting this on the Yosemite (first partition):
Verifying volume “Yosemite”Verifying storage system
Checking volume disk1s2:
Scan for Volume Headers disk0s2:
Scan for Volume Headers disk1s2:
Scan for Disk Labels disk0s2:
Scan for Disk Labels
Logical Volume Group E2086E44-46AF-471C-A0F4-AC1449DAC936 spans 2 devices disk0s2+disk1s2:
Scan for Metadata VolumeLogical Volume Group has a 24 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment HeadersLoad and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 7 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify MetadataSuperblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 31867693-AB13-431A-9481-A59D3CA28C31
Load and verify E8580DBC-D603-440A-B461-2A4A4D43BA45
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume E2086E44-46AF-471C-A0F4-AC1449DAC936 appears to be OK
Storage system check exit code is 0.
Verifying file system.Using live mode.
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking catalog hierarchy.
Checking extended attributes file.
The volume Yosemite appears to be OK.
File system check exit code is 0.
Now, my questions are, initially, I got the "Invalid Logical volume header @ <some number>. Is this cause of concern that the Fusion drive is failing and chances of occurring again?
My next question is, based on the log, does it look OK?. Also, what does this mean "Logical Volume Group E2086E44-46AF-471C-A0F4-AC1449DAC936 spans 2 devices disk0s2+disk1s2: Logical Volume Group has a 24 MB Metadata Volume with double redundancy"?. Is this normal or cause of concern?
Surprisingly, I ran VerifyDisk on the 2nd partition (Mavericks) which I haven't installed Mavericks yet and I see this:
Verifying volume “Mavericks”Verifying file system.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Mavericks appears to be OK.
File system check exit code is 0.
Why is the 2nd partition NOT showing the "Logical Volume Group has a 24 MB Metadata Volume with double redundancy" in the log? Also, is the 2nd partition ok?
On an unrelated task, I have to do this for a software that I'm trying to install and issued the following commands from Terminal.
sudo cp ~/Desktop/com.lsreset.plist /Library/LaunchDaemons/<appconfig.plist>
sudo launchctl load -w /Library/LaunchDaemons/<appconfig.plist>
and seeing this:
/Library/LaunchDaemons/appconfig.plist: Operation already in progress
Previously, I didn't see this error (last month or so)? Is this related to the HDD issue that I'm facing?
Thanks.

Anybody please?
even though I'm covered under Apple Care, I would like to be confident enough to know whats going on before I run to the store.
Thanks guys.

Help after using verify disk with MacBook Pro 2009

Hello, I was running verify disk and got this massage:
This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
Verifying volume “Macintosh HD”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Missing thread record (id = 932391)
Missing thread record (id = 1020109)
Missing thread record (id = 2003740)
Missing thread record (id = 2587373)
Incorrect number of thread records
Checking multi-linked files.
Checking catalog hierarchy.
Invalid volume file count
(It should be 806588 instead of 806594)
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Macintosh HD was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
what dose it mean?
I don´t have my Mac OS X installation disc with me and it is also not possible to buy one here. what can i do?
thank you so much

Boot into single-user mode. After startup is completed you will be in command line mode and should see a prompt with a cursor positioned after it. At the prompt enter the following then press RETURN:
/sbin/fsck -fy
If you receive a message that says "***** FILE SYSTEM WAS MODIFIED *****" then re-run the command until you receive a message that says "** The volume (name_of_volume) appears to be OK." If you re-run the command more than seven times and do not get the OK message, then the drive cannot be repaired this way. If you were successful then enter:
reboot
and press RETURN to restart the computer.
There is no guarantee this will fix the problem. Normally you must boot from another drive in order to repair the startup volume. If you can't use a Snow Leopard DVD then you would need to use some other bootable device like a backup drive or another Mac connected via Firewire - Target Disk Mode.

Invalid number of extended attributes during Verify Disk.

Similar Messages

Maybe you are looking for