Invalid record count - grey screen- Target Mode Cures

Hi there,
I have a common problem: I was doing nothing particular that I remember: No fancy file uploads, doanloads, creation, erasing - nothing special:
Anyway after a customary week, or few days of leaving the macbook permanently on, I think "let's give it a rest".
Then switch back on:
- Grey screen, spinning grey progress wheel fine.
- Takes a while. Strange. After say a minute - it just switches off wordlessly.
- Reset PRAM: No solution. Take a look with single-user startup in console: Files are all there, OK. Disk not dead.
- Start up from OS X 10.5 disk:
Permissions repair fine. Good.
Verify disk: FAIL! +*Invalid Record Count.Volume check failed.*+
Next: *Try target disk mode to back up essentials* - that works fine: I now have Time Machine AND a smaller important essentials backup.
But finally, here's the surprise: Just for kicks, I *shut the macbook down, try a reboot - and it works!*
But I note that root system files are unchanged since the problem occurred: ".hotfiles.btree" for example (I don't know what that is but suspect it's relevant).
Then: I tried restarting again - and back to square one, it won't boot.
Do the "Target disk" firewire mode trick again, and browse a few folders: And it boots (slowly).
If I just leave the Macbook on permanently - everything seems fine. Not even sluggish.
So:
- Why can connecting a disk with an incorrect file system in target disk make the system forget about these problems when booting?
- Why does the problem return on a successive reboot?
- Is it related to some system files being ignored if booting straight after a target mode session?
- What is ".hotfiles.btree", and should it not exist ?
And the big one:
- +Can extended Applecare, wot cost me loads of money, help me?+

Hi Cornelius:
Having been a faithful Apple-groupie for a while, and despite some problems over the years (hard drive failing, screen going, etc.) this is the first time I'm disappointed with them, because theor Micromat Applecare deal is a ripoff:
You fork out for Applecare extension: All you get is something that say "Yep, you've got a problem. Now go and buy techtoolpro".
That is, the TechTool Deluxe is practically useless. Argh.
Worse: They keep that rather quiet. If you run TechTool deluxe, and it fails: It points you to the Techtool site to
"download the TechTool Deluxe software with diagnostic and repair capabilities".
You think "Aha, right, I need an update, or a DMG rather than just the executable".
Download another 1.25Gb.
So you try again: Same thing.
The chiselling little crooks, to quote Ken Livingstone, won't even come out and say "Buy TechTool Pro to fix it". The website as reported above is wrong.
Result: I'm not happy with them. And I'll never buy anything off Micromat.
In the meantime, I've got a bootable backup thanks to CC-Cloner (excellent, I'll send him some money), and I'm waiting until I don't have any critical deadlines to allow myself time to restore a daily bootable backup.
The dodgy files seem to be the Sun Developper Java suite according to CC Cloner.

Similar Messages

MINUS operator fetches invalid record count

Hi,
One of the application team complained that oracle MINUS operator fetches an invalid record count after data load.
Here are the details of the data load:
They are using source as PROD and target as UAT.
They are replicating the data on UAT environment in schema A from fetching the data in PROD from the same schema.
After load when we query the count of records in UAT it shows more records in target, that is in UAT, than PROD.
When they use MINUS operator to fetch the extra records in UAT, it shows no rows selected.
SQL> select 'A' count(1) from A.UAT union all select 'A' count(1) from A.PROD@BISLSPD1;
A COUNT(1)
A.UAT 19105022
A.PROD 19104995
SQL> select distinct count(*) from (select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.UAT minus select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.PROD@BISLSPD1);
COUNT(*)
0
SQL> select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.UAT minus select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.PROD@BISLSPD1
no rows selected
Please note that both are partitioned tables and they are using Informatica Data Replication 9.5 tool to populate the data from source to target.
Not sure if this could be a bug or an issue.
PROD DB Version: 10.2.0.5
UAT DB Version: 10.2.0.5
Both are in Linux 2.6
Please throw some light on this.

974065 wrote:
SQL> select 'A' count(1) from A.UAT union all select 'A' count(1) from A.PROD@BISLSPD1;
A                  COUNT(1)
A.UAT                     19105022
A.PROD                   19104995
SQL> select distinct count(*) from (select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.UAT minus select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.PROD@BISLSPD1);
COUNT(*)
0
SQL> select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.UAT minus select distinct DW_DISCOUNT_KEY, DW_DISCOUNT_MODIFIER_KEY from A.PROD@BISLSPD1
no rows selected
Given that you've go "distinct" in your query, you're eliminating duplicates from each table (and MINUS implicitly means distinct anyway). Check for duplicates (of dw_discount_key, dw_discount_modifier_key) in both tables.
If the combination is actually unique, I would check that you actually had the raw results the right way round - MINUS is not symmetrical, and for a complete picture you need to look at (select from uat minus select from prod) union all (select from prod minus select from uat)
Regards
Jonathan Lewis

Please help! Invalid node structure and invalid record count

My MacBook Pro is about 6.5 years old. I upgraded to Snow Leopard 2 years ago and added RAM at the same time. My first problem ever occurred three days ago when my computer got super sluggish, I restarted and got the gray screen with apple and spinning wheel...no boot up. I ran disk utility from the snow leopard install disk and found "invalid node structure" and "invalid record count". After reading on here what to do...try to repair the disk and so on with no success I went out and bought Disk Warrior. Got home expecting to fix everything and Disc Warrior won't boot...I just get a file with a question mark and the disc is ejected. I tried erasing the hard drive but was only able to use the "don't erase data" option. Then I tried to reinstall Snow Leopard with no luck. Now I am stuck. Any ideas?
One thing to note is I am to the point of not caring about the files on the hard drive, I was a dummy and never backed them up...lesson learned! I just want my computer back without having to spend $1000+ for a new one. Then again I am always willing to do that too as a last resort.
PLEASE HELP!

When you contact Alsoft, make sure you let them know that you are using Snow Leopard (10.6.8).
Try the following in the meantime -
Disconnect all peripherals from your computer.
Boot from your install disc & run Repair Disk from the utility menu. To use the Install Mac OS X disc, insert the disc, and restart your computer while holding down the C key as it starts up.
Select your language.
Once on the desktop, select Utility in the menu bar.
Select Disk Utility.
Select the disk or volume in the list of disks and volumes, and then click First Aid.
Click Repair Disk.
Restart your computer when done.
Repair permissions after you reach the desktop-http://support.apple.com/kb/HT2963 and restart your computer.
Try DiskWarrarior again if it's combatible with the os system.
YOu cannot reformat until you get your issue corrected.

HD crash. Disk utility says invalid node structure, invalid record count. Disk utility cannot repair. Now what?

My hard drive crashed. The disk utility says it can not repair. I tried to boot in safe mode but I stopped after 10 minutes. Is that impatient or how long can it take?
I have the installation disk but doesn't that erase everything?

I have never bought a new computer from Apple so I don't know the details of what is covered by the warranty. You can try taking it to the Apple Store and they may have a copy of DW they can run. Or maybe not and they will just wipe the drive and reinstall the OS for you and if you haven't made a backup before they do that then tough luck. I'd check first!
If you buy Diskwarrior on DVD it will boot the computer. I think Apple Stores carry it, but you can also buy it directly from the vendor. I also don't use Lion OS so I don't know the details. You may be able to get their download version and boot from your recovery partition, then run it without a DVD.

Reloading everything back onto laptop after a disc erase due to grey screen - steps

1) I have had grey screen problem & have done start jo sox re install. Now I want to reload all my files from time capsule back onto my 17inch pro.
What are the steps
The mac17 has had full backup just before it stopped. Last piece of software loaded was a flash player update for YouTube videos .
But worked ok after that . But had an coloured spinning wheel later when tried to close program's. then after a power restart could only get a grey screen. Tried disc repair & got messages to say invalid record count & invalid node structure . Worker my way through recommended grey screen restarts & now doing re install of OS X
2) I have since bought a Mac Pro 13 with retina display - due to the 17 mac pros weight.
I want to reload all my files onto this from time capsule. Link both via iCloud .

sabeque wrote:
4) make a new time machine backup with the fresh os and no data
This step is superfluous.
If reinstalling the OSX will allow you to make a Time Machine backup, do so.
Remember that the first thing you must do with a new HDD is to format it in Disk Utility>Erase to Mac OS Extended (Journaled). Only then can you install the OSX and the data from Time Machine.
5) restore from the first time machine backup on the old disk. If this works, great, but im worried that if I had corrupt data on the old drive then when I restore from the old disk, it will bring all that corrupt data onto the new disk. In this case, I would restore again from time machine but this time from the one I did in step 4 when the disk was fresh and clean. I will have lost my apps and have to count my losses. Is this a good plan or will this taint the new disk if the old data is corrupt?
What makes you believe that you have corrupt data? Is the issue not the HDD? Step four only copies the OSX and NO user data. That has no benefit for you. All of you applications should be on the first Time Machine backup, assuming it is successful.
Ciao.

I think my HDD is dead - stuck at the grey screen, with the apple logo ..

Hi all,
I think my Mbp's HDD has partially failed. It is the original 100gig drive , which was 95% full.
It started getting incredibly slow so I decided to reboot it. It has not been possible to boot.
I have managed to connect the internal drive to another mac using FireWire and T on startup.
The drive shows up and the data can be accessed albeit slowly.
I tried to repair the drive in disk utility and it came up with a lot of " invalid node structures" and " invalid record counts".
The disk utility seemed to not complete the process so I had to quit it.
I can't boot from the cd , but I may be doing it wrong.
Can anyone help me with the next thing to try?
Thanks.

Slow access even with Target Disk Mode (TDM) can indicate a failing drive, but it's possible that drive can be rehabilitated by continuing to off-load files and keep trying with Disk Utility. Sometimes, enough DU runs can restore sanity.
I'd check the SMART status first (try: SMART Utility at Apple OSX Downloads ). This can be done from the other Mac while the MBP is in TDM. If the drive passes and you can off-load some of the load, then a directory repair utility like DiskWarrior might be worth a try.
However DiskWarrior is US$100 and you can get a new 500GB SATA 2.5" hard drive for less than that. The advantage to disk Warrior is that it's easier to install in an MBP than a new hard drive.

Disk utility gets "invaild record count"

Hello, Using Macbook pro running OSX 10.9.2
Yesterday, i was using my computer searching internet, plugged it in and walked away for about 5 mins. Came back and tried to open iTunes. I 1st choose iTunes using the button w/ the 6 squares on it on the top row of keyboard. Nothing happen and iTunes did not open. 2nd I tried to open iTunes using the dashboard. Again nothing happen. I used the power button to shut down the computer. Then restarted, it came up with a window asking which language I would like to use. I choose English and then a new window opens with 4 choices; "Restore using Time machine", "Reinstall OSX", "Get online help" (which is how I am here now), and "use disk utility". I picked disk utlity and verified the disk which popped up a window say it "stopped and needed to be repaired. I hit the "repair buttom" and got a "Invaild record count" in red. It then stopped and said it could not be repaired.
Tried to restore using the back-up/restore with Time machine. It found time machine, but on about the 4th screen it asks which volume I would like torestore to. Nothing comes up and just says "searching for disks" None ever come up. I quit disk utility and then choose "Start up disk" under the apple menu. It doesn't find anything. I tried the "command + option + P + R" nothing is different.
So here I am. each new screen that comes up flickers a lot before clearing.
Dead hard drive?
Just can't find it?
What's next?
Thank you for being here to help
Jody

Thank you dominic23.
I tried the instructions listed by Chris Watts1 and after running the /sbin/fsck_hfs -yprd /dev/disk0s2
it never asked for a password just said "starting". After waiting a couple mintues it came back with the following: (which I have no idea what any of it means)
journal_reply (/dev/disk0s2) returned 22
using cacheBlockSize = 32K cacheTotalBlock = 16384 cacheSize = 524288K.
Executing fsck_hfs (version hfs-226.1.1).
**Checking journaled HFS Plus volume.
hfs_swap_BTNode: invalid forward link (0xA9812964)
hfs_swap_BTNode: invalid backward link (0x0B69B6DB)
hfs_swap_BTNode: invalid node kind (-124)
hfs_swap_BTNode: invalid node height (42)
hfs_swap_BTNode: invalid record count (0x3E6B)
Invalid record count
(3, 3)
**The volume could not be verified completely.
volume check failed with error 2
volume type is pure HFS+
Primary MDB is at Block 0 0x00
Alternate MDB is at Block 0 0x00
Primary VHB is at Block 2 0x02
Alternate VHB is at Block 975093950 0x3a1ec0be
Sector size = 512 0x200
VolumeObject flags = 0x07
total sectors for volume = 975093952 0x3a1ec0c0
total sectors for embedded volume = 0x00
CheckHFS returned -1317 , fsmodified = 0
Does any of this mean anything to you?
thank you again,
Jody

Sequence - Record count is double

Hi Experts,
I have requirement to move the data from from one table to another in Oracle.
I have created a sequence for autonumber and the same attribute has been defined as primary key as well and using IKM sql Control append.
When the data is being transfered to target table actually count is double or 3 times of origianl count.
Please suggest me how to resove this.
Regards,
Preet

Hi ,
Can you please check the operator log :- number of inserts for I$ table and main table.
And find which step is giving issue.
please copy that query here.
Other details needed :-
Source record count.
Target record count before execution
Target record count after execution
I$ record count
Any joins ?
Regards,
Rathish A M

Grey screen every time with MBP Retina

Hi,
I got a strange behaviour of my MBP Retina. After upgrading to Mountain Lion it may not start. I have a grey screen, Safe Mode doesn't pass. Restore works, MBP boots OK then, can even restart and shutdown OK few times. But if the shut down period is long (more than 3-4h) I got a grey screen again.
I tried all the tricks with premissions restore, resetting PRAM, uninstalled Parallels and Little snitch, run Onyx for Mountai Lion and cleaned everything, everything from startup apps list. Nothing happens. I got a grey screen again, almost every day, then re-install the OS, and it works OK until next shutdown. SSD is OK, MBP has no hangs/freezes, works great after OSX reinstall, then again - grey screen. Verbose Mode hangs after a list of "FIPS USER Space Post" - all success, no mistakes. Before there is a message "Kernel is LP64", and the a string "/dev/rdisk0s2 (NO WRITE)"
Please, give some advise!

Sorry to bring this topic again, i have the same exact symptoms in here, and i suspect that its a third party aswell bugging me around doign this grey screens. ( had this for 3 days now after shutting down it gets back to grey screen but after i do a couple of stuff i can get it back to work. )
I already have the latest firmwares etc and updates i would say.
heres the etrecheck scan. ( ignore wow open )
Hardware Information:
    iMac (27-inch, Late 2012)
    iMac - model: iMac13,2
    1 2.9 GHz Intel Core i5 CPU: 4 cores
    16 GB RAM
Video Information:
    NVIDIA GeForce GTX 660M - VRAM: 512 MB
System Software:
    OS X 10.9.1 (13B42) - Uptime: 0 days 2:12:19
Disk Information:
    APPLE HDD WDC WD10EALX-408EA0 disk1 : (1 TB)
        EFI (disk1s1) <not mounted>: 209,7 MB
        disk1s2 (disk1s2) <not mounted>: 937,52 GB
        Recovery HD (disk1s3) <not mounted>: 650 MB
        BOOTCAMP (disk1s4) /Volumes/BOOTCAMP: 61,83 GB (16,99 GB free)
    APPLE SSD SM128E disk0 : (121,33 GB)
        EFI (disk0s1) <not mounted>: 209,7 MB
        disk0s2 (disk0s2) <not mounted>: 120,99 GB
        Boot OS X (disk0s3) <not mounted>: 134,2 MB
USB Information:
    Razer Razer Lachesis
    C-Media Electronics Inc.       USB PnP Sound Device
    Apple Inc. FaceTime HD Camera (Built-in)
    Apple Inc. BRCM20702 Hub
        Apple Inc. Bluetooth USB Host Controller
FireWire Information:
Thunderbolt Information:
    Apple Inc. thunderbolt_bus
Kernel Extensions:
    com.steelseries.BoardListener    (8.39 - SDK 10.6)
    com.tuxera.filesystems.tufsfs.fusefs_txantfs    (2012.4.17)
Problem System Launch Daemons:
Problem System Launch Agents:
Launch Daemons:
    [System]    at.obdev.littlesnitchd.plist 3rd-Party support link
    [System]    com.adobe.fpsaud.plist 3rd-Party support link
    [System]    com.adobe.SwitchBoard.plist 3rd-Party support link
    [System]    com.oracle.java.Helper-Tool.plist 3rd-Party support link
Launch Agents:
    [System]    at.obdev.LittleSnitchNetworkMonitor.plist 3rd-Party support link
    [System]    at.obdev.LittleSnitchUIAgent.plist 3rd-Party support link
    [System]    com.adobe.AAM.Updater-1.0.plist 3rd-Party support link
    [System]    com.oracle.java.Java-Updater.plist 3rd-Party support link
User Launch Agents:
    [not loaded]    com.adobe.AAM.Updater-1.0.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
    [not loaded]    com.valvesoftware.steamclean.plist 3rd-Party support link
User Login Items:
    None
Internet Plug-ins:
    FlashPlayer-10.6: Version: 12.0.0.38 - SDK 10.6 3rd-Party support link
    AdobePDFViewer: Version: 10.1.1 3rd-Party support link
    Flash Player: Version: 12.0.0.38 - SDK 10.6 3rd-Party support link
    JavaAppletPlugin: Version: Java 7 Update 51 3rd-Party support link
    QuickTime Plugin: Version: 7.7.3
    Default Browser: Version: 537 - SDK 10.9
Audio Plug-ins:
    BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
    AirPlay: Version: 1.9 - SDK 10.9
    AppleAVBAudio: Version: 2.0.0 - SDK 10.9
    iSightAudio: Version: 7.7.3 - SDK 10.9
3rd Party Preference Panes:
    Flash Player 3rd-Party support link
    Java 3rd-Party support link
Bad Fonts:
    None
Old Applications:
    Install Spotify:    Version: 1.0 - SDK 10.5 3rd-Party support link
        /Users/[redacted]/Downloads/Install Spotify.app
    SA Color Finesse 3 UI:    Version: 3.0.6(275) - SDK 10.5 3rd-Party support link
        /Applications/Adobe After Effects CS6/Plug-ins/Effects/Synthetic Aperture/(CF3 Support)/SA Color Finesse 3 UI.app
    dynamiclinkmanager:    Version: 6.0.0 - SDK 10.5 3rd-Party support link
        /Library/Application Support/Adobe/Common/dynamiclink/CS6/dynamiclinkmanager.app
    dynamiclinkmediaserver:    Version: 6.0.0 - SDK 10.5 3rd-Party support link
        /Library/Application Support/Adobe/Common/dynamiclinkmediaserver/1.0/dynamiclinkmediaserver.app
Time Machine:
    Time Machine not configured!
Top Processes by CPU:
       116%    installd
        38%    World of Warcraft
        10%    WindowServer
         7%    firefox
         3%    storeagent
Top Processes by Memory:
    1.28 GB    World of Warcraft
    770 MB    firefox
    239 MB    installd
    164 MB    mds_stores
    164 MB    com.apple.IconServicesAgent
Virtual Memory Information:
    4.18 GB    Free RAM
    5.21 GB    Active RAM
    5.03 GB    Inactive RAM
    1.58 GB    Wired RAM
    656 MB    Page-ins
    0 B    Page-outs

Grey screen on Target Disk mode boot up

I have a home iMac, Late 2012, OSX 10.9.1, 32GB, and a corp MBP, Late 2011, 8GB. I would really like to use Target Disk Mode to boot the MBP on the faster iMac - it worked once or twice and was fabulous, but that was when both were on Lion.
Now after upgrading both to Mavericks, Target Disk mode bootup isn't working anymore. I get to the Login Screen on the MBP bootup, but after logging in i just get a grey screen. Nothing else.
Pretty sure i'm doing everything right. Connect both, boot target with cmd-T, boot host with "alt", select startup disk, login ..... then nothing.
Fix is probably simple - any help would be great.

Ok this is a guess.
Are you trying to use the system files etc on the iMac to run the MBP?
If so I am surprised it worked in Mountain Lion, the Video cards probably have different drivers and that could be why you cannot login but the login screen with standard resolution works.
You could try and match the resolution on the iMac with one that suits both machines but running it that way is not something I would do.
Perhaps I understand your question incorectly, if so apologies and disregard my post.

Invalid leaf record count, keys out of order?

Yesterday I returned home from a month long trip which I did not bring my 13 inch 2011MacBook Pro on.
I plugged it in and turned it on, and connected my phone to it so i could retrieve some photos. I looked away and looked back to see the grey "You must hard shut down your computer" error message. Possibly because i think the phone may have been disconnected without being properly ejected? So i turned it off and then later the next day, when I try to turn it on it is stuck on the white apple loading screen forever. When I startup with Command+R and enter disk utility, it tells me:
Invalid Leaf record count, keys out of order, volume could not be repaired. When I startup in single user mode and use fsck -fy it tells me the same.
I got it used less than a year ago. I have some pretty heavy applications like MS Office, Photoshop and a few other adobe applications, and The Sims 3.
Help!

When Disk Utility can't repair a hard drive, with an error like that, many buy Disk Warrior to do the repair. You can see an answer on the Disk Warrior site here.
Or, if you have a system backup, erase the hard drive (I would probably do a secure erase and write zero's to the hard drive) and restore it.

Grey Screen w/ logo on startup, crashes in disk utility and FW disc mode

So yesterday I woke my computer from sleep and launched firefox. After a few minutes it crashed and the froze. I restarted and got the grey screen with apple logo. Restarted many more times and would either get the grey screen with logo or if it managed to startup it would again freeze after a few minutes.
Tried starting up from install disc to launch disc utility to check the permissions and verify disk. This also froze several times put i managed to repair permissions and repair disc. Now I am not able to get it to start up unless from the install disk. I have a bootable backup drive with I tried to connect and use as a startup disc. I just got a black screen when I tried that, I also connected the G5 to my
Powerbook G4 in firewire disk mode. It connected and I was going to attempt to copy the Bootable external drive back to the Drive in the tower and try starting from that, but the G5 then froze in Firewire disk mode and had to be restarted.
I'm out of options here, and desperate....any ideas. I thought that grey screens many times meant software or hardware conflicts. could this just be something horribly wrong with my hardware?
Help!
Thanks in Advance!

I've read several response to problems with target disc mode. I'm trying to connect my old computer, G3 tower with OS 8.6, to my new computer, mac book pro. I've called tech support twice and they have no clue as to why it won't work. They suggested this discussion page. I tried what one fella did, which worked for him, but didn't for me. I rebooted with shift button down, then ran verify and repair, then shut down, unplugged for a minute or two, restarted zapping pram (optioncommand(apple) P & R keys. Then restarted with the T key down. Attached firewire to both target computer and disc computer, (did this first), but no jumping firewire icon ever appeared.
One fella out there said it took his computer 5 minutes for the icon to appear. Did he hold the T key down all that time? I let go after my normal desktop icons were up and the computer stopped wiring.
I am calling tech support back...who knows maybe I'll get someone who knows something.
Any ideas?
Thanks Little Champ

Invalid Leaf Record Count??

After Software Update installed new versions of QuickTime and iTunes, my computer hung while doing the required restart. It got stuck at the point where the spinning clock thing appears. I had to force a shutdown by pressing and holding the power button. Now when I run Disk Utility (from an OS X install CD) to repair the disk, I get the following error message:
Invalid leaf record count.
It should be 7, instead of 66.
The repair ends with a message that the disk could not be repaired. However, when I start-up in single-user mode and do a disk repair by typing in “fsck –yf”, I get no error messages, and it says the hard disk appears to be OK. I also ran DiskWarrior, but that did not fix the “invalid leaf record count” problem.
I would be interested to know what “invalid leaf record count” means and if I should be concerned.
Thanks.
Lou

You can get this error if you use an older Panther CD instead of the Tiger DVD on your 10.4 as per this article.
http://docs.info.apple.com/article.html?artnum=301266

Invalid Leaf Count Record

When I repaired my startup disk with Disk Utility, an invalid leaf count record error was reported. From looking at other posts, it appears that one of the recommended things to do for this is trying to repair the issue with Disk Utility. I tried this using Disk Utility 4.1. I replaced my directory with the rebuilt directory. Unfortunately, when I started back up from my install CD and ran Repair Disk, the invalid leaf count record error was reported again.
Any advice would be much appreciated... maybe I did something wrong.
Thanks

First, I realized that I had the error message wrong. I should have wrote "Invalid Leaf Record Count" originally instead of "Invalid Leaf Count Record". I doubt this makes a difference, but just in case there it is.
Secondly, I am running 10.3.9 and have been doing so for quite some time. My understanding based on this is that DiskWarrior 4.1 should work. I took your advice and tried running DiskWarrior again. As I did previously, I simply booted from DiskWarrior because the disk I am trying to fix is my startup disk. I rebuilt and replaced the directory with DiskWarrior 4.1 again. As a matter of fact, I ran it multiple times while I had it going. I even ran it under the scavenge mode.
After doing this, I restarted the computer, ejected the DiskWarrior disc, and put in my install disc that came with my iMac. I booted from this CD and reran "Repair Disk" with Disk Utility. The error stills shows up. One thing to note is that my install disc came with 10.3.5 on it. Could this somehow cause a problem? My understanding is that you should always use an install disc for the major OS version you are running to run the "Repair Disk" function of Disk Utility. For example use an install disc for 10.3 if you are trying to repair a disk running 10.3.x or use an install disc for 10.4 if you are trying to repair a disk running 10.4.x.
Prior to ever running DiskWarrior, I used the fsck command from single-user mode. Interestingly, the error did not show up here. I thought the "Repair Disk" function with Disk Utility was similar to this command, but maybe there is enough variation to cause the difference. Do you guys have any idea, which one I should trust?
Let me know if any of this is incorrect. Any other suggestions regarding this error would be welcomed. I don't really understand what the error itself means. For now, I guess I will just leave it since I don't really know what else to do. Maybe in the future it will get worse and DiskWarrior will recognize it... I know that's asking for a problem!

Hello my Mac Air is frozen on the grey screen (with the apple symbol, sleeping mode, restart-and off button), once you turn it on.

hello my Mac Air is frozen on the grey screen (with the apple symbol, sleeping mode, restart-and off button), once you turn it on. I Can`t press any button.My Mouse still works. Battery is charged. Alt-cmd-escape doesn`t work It even after a forced shutting off, the problem is the same.   what should i do? Thank you for your help.

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
     a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Step 3
Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 5.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 4
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 5
Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
Step 6
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 7
Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
Step 8
This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. The battery is distinct from the main battery of a portable. A dead logic-board battery can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions.
Step 9
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

Invalid record count - grey screen- Target Mode Cures

Similar Messages

Maybe you are looking for