What is an invalid leaf count?

My computer wasn't starting up and it was just going to the page with the apple and clock thing that kept spinning. I ran disk utility. It repaired one volume, but it said that when it checked my extended attributes file, I had an invalid leaf record count and that it couldn't be repaired. Does anyone know if that's serious? If a volume can't be repaired, what should I do? Wipe out my hard drive and start over? I just installed Leopard and my computer has been running really slow since then. Could that have anything to do with it?
I'm really confused...if anyone can help me, I'd really appreciate it! Thanks!

It means that a node for a B-tree structure on the HFS Extended (Plus) volume has been changed for some reason. Thus, the leaf node no longer refers to other nodes or records in the proper manner.
Disk Utility may not able to repair this type of error on the bottom level (exclusively for leaf nodes) of a B-tree structure for the HFS Extended format volume. In a similar disk logical error, there is "Keys Out of Order" that indicates a key record/s on a B-tree structure is damaged.
It is essential to run Disk Utility to repair the issue via starting up from Leopard install disc because B-tree structures are complex. If it cannot fix the issue, try Disk Utility built in Tiger's Install disc. The second option is a third-party utility called DiskWarrior 4.0. The last option is to perform "Erase and Install."
Best wishes

Similar Messages

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!

Invalid leaf count

Hi everybody,
First that all, my English is not very good, sorry for my grammar mistakes.
In the School i work have a Power Mac G5, about two months i could not empty the trash, get error -1. I start the machine with the original Install CD (Mac OS X 10.3.2 AHT 2.1.1) start up the machine and I verify the disk with Disk Utility and get an error: Invalid leaf record count (It should be 1 instead of 211) The volume Macintosh HD need to be repaired, when I try to repair it get 1 volume could not be repaired. The volume is Journaled HFS+
I was looking on the web and found three possible solutions:
1.- Run '/sbin/fsck -fy'
2.- Diskwarrior 4 (I HAVE TO BUY IT)
3.- reformat hard drive (PLEASE NO!!! I have a lot root configurations and bash opctions, ssh, etc.)
Plase someone can give me an advice, suggestion, which will be the best option, and we want to upgrade it to Leopard, but I stop because this error.
I will appreciate any help
Ivan

Clone your drive with SuperDuper - makes an exact image.
Then never ever rely on just Apple First Aid, the best time to buy Disk Warrior of course is BEFORE you need to.
I'd als throw a new WD Cavair Black in your shopping cart.
Never use Disk Utility or any utility that is older than what you are using, that it supports your current system. And instead of using any CD or DVD, even Disk WArrior,
Setup an emergency boot drive with just fully updated Apple OS plus your utilities and used for nothing else;
A clone / backup from SuperDuper that is for just the system and updated before any update;
A backup of your data to another drive (might want more than one backup set so you don't lose or write over anything).

Invalid leaf count. Help!!

Turned on my macbook pro, logged in, tried to get online but the computer froze and I had to force shut down. When I turned it back on it never left the gray apple screen. Never had this before! I searched online and found a few things to try and I when I tried repairing it it said "invalid lead count. Should be 483 instead of 478" then it said "the volume mac hd could bot be repaired" and finally " error: disk utility can't repair this disk..." And then told me told me to back up as many files as I can.
Question 1: is my computer fried with no fix!? If yes then..
Question 2: how can I back up all of my pictures, music, etc? I'm kinda freaking out
Please help!

No your computer is not fried. the problem is the directory for the disk is corrupt.
So back it up. I would suggest trying to create a bootable clone with either SuperDuper or CCC.
Once you have done that boot from the clone.
From the clone you can reformat the disk thereby create a new directory.
You can then clone the external back to to the interal.
Allan

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 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.

Invalid leaf record count (it should be 175 of 5069)

Hi guys,
Long time Mac user and desperately wanting to bring my old Sunflower IMac back to full life.
I was having a few problems with it, sometimes had the question mark on boot up, lots of crashing. Decided to do an archive and reinstall. I had been running Snow Leopard.
Seemed to go okay, but then it would accept my password. (I chose to reinstall importing old usernames/settings. Hope that wasn't a bit of time save that caused this.)
Managed to google around and reset the password. But then it booted into Darwin when it accepted my new password.
More googling, and checking these boards, and I ran disk utility repair and the "Invalid leaf record count (it should be 175 of 5069)" came up. Ram repairs and so on, and it seemed to clear, but the disc wouldn't mount when I tried to verify again.
Booted with S-command and tried fsck -fy which I'd come across earlier in the day. (Logged in with my username and new password.) At **Checking Extended Attributes file the same error came up as I found with disk utility. Then I had,
**Checking volume bitmap
**Checking volume information
**Repairing volume
*++++ FILE SYSTEM WAS MODIFIED *****
sh-2.05a# 0
I've been reinstalling and trying things all day but I know I've gone as far as I can without your help now. Hope there's some way to fix this.
Thanks for reading all that.

Thank you, baltwo. I've done that a few times and it shows the same message. But I'll keep at it for a while.
I'm thinking maybe I'll need Diskwarrior which I saw mentioned in some threads here.
*In my OP I meant 'it wouldn't accept my password' in the third paragraph.

Invalid block count and poor performance

Hi - Can anyone help?
Running an early 2011 13' MBP on ML. For a year - 18 months I've noticed poor performance at times, consistently slow boot (sometimes 5 minutes to usable), occasional lockups and spotlight often reindexes itself and slows the system (much more than my previous MBP), I can't see anything that triggers it. I'm also getting recurring errors in Disk Utility of 'Invalid block count', every time I'll repair the disk (booting into recovery), but after a month of use the error will reappear. About three months ago I erased and reinstalled ML, some of my data was moved over in Time Machine but I didn't restore from it. The erase and reinstall hasn't made any difference and I'm still seeing the same issues. Hard disk SMART status appears to be fine.
Can anyone recommend any troubleshooting steps? I'm not sure what else to do, still under Applecare and was thinking maybe the HD isn't working correctly?
Cheers!

Performance.
Activity Monitor – Monitor Performance Problems
Performance Guide
Why is my computer slow
Why your Mac runs slower than it should
Slow boot.
Startup - Slow Boot
Startup - Slow Boot (2)
Startup - Slow Boot (3)
Startup Issues - Resolve
Startup Issues - Resolve (2)

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.

Java.sql.SQLException: Invalid column count. Cannot be less or equal to zer

Hi,
update method working but java.sql.SQLException: Invalid column count. Cannot be less or equal to zero is thorwn...
value's are updating...how can i handle this exception...pls anybody help me
related java file(IDE) generated file
public void setColumnCount(int columnCount) throws SQLException {
if (columnCount <= 0) {
throw new SQLException("Invalid column count. Cannot be less " +
"or equal to zero");
}

The idea behind drag'n'drop visual editors and code-generators is nice. But they are not intented to be used by developers who don't understand what they do.
With other words, keep away from those visual editors and code generators as long as you're unexperienced with Java. Write code at your own. You will learn and grow gratefully.

Frequent 'Filesystem Corrupt', Invalid File count

I have been getting this message every a couple of days in my MBP or iMac running 10.6.2. It happens/visible only when I runs Disk Utility and Verify Disk. Of course, this brings unsettling point to me when it comes now and then. Not to mention I have to boot from DVD to run disk utility to fix this
Error Message: Invalid file count (It should be xxxxx instead of xxx+1) AND
Error Message: Invalid volume directory count (It should be xxxxx instead of xxxx-1)
Any idea what causes this and what's the impact i.e. do I lose any files?
Thanks!!

Leonard Ong wrote:
Hi Tim,
By default, it is HFS+ Journaled (non-case sensitive). So I have also the same understanding that journalled filesystem should be robust as you wrote it. But the fact that this comes now and then, It created some doubts.
Is this a harmless error message or should I be worried about it. That basically my questions. I do repair when I see this.
It can't be because of disk is failing for a number of reason:
1) I have the same behavior both in my iMac and MBP
2) Both HDD has been replaced with new one recently
3) Both HDD has passed through surface scan from TechTool Deluxe 5.0.6, so no bad blocks
Still a puzzle...
Are you sure that the errors are showing up on both computers when performing either a "Verify Disk" or "Repair Disk" and NOT just a "Verify Disk Permissions" or "Repair Disk Permissions"? Permissions errors are mostly harmless. Filesystem errors (the sort you see when you ask for "Verify Disk" or "Repair Disk" in Disk Utility are not harmless and you should be worried about those.
If so, then either both drives are failing or your drives are being exposed to a strong enough magnetic field to damage their data (and that would have be pretty strong -- a common refrigerator magnet wouldn't do the trick.) In all of my years of working with journaled filesystems (or operating systems with "filesystem logging" which is the same thing) I have NEVER seen a journaled volume have filesystem errors unless it was physically failing.
Journaling will prevent filesystem errors if it's enabled for pretty much every cause except for a physically defective or damaged disk. Here's the short version of how journaling works...
Journaling (aka "filesystem logging") is intended to prevent filesystem corruption... and it's pretty rock-solid.
1) A "journal" (or "log") area is added.
2) A hard rule is established that, under no circumstances may the OS be performing writes to both the journal and the regular filesystem at the same time. One must be flushed before it can work on the other and vice versa.
3) When a write operation is about to happen, the OS writes information to the journal indicating which blocks on the filesystem are about to be changed and what it's about to change. This information is flushed to disk.
4) The OS can then perform the write on the actual filesystem areas it intended to change. These must then be flushed to disk.
5) The journal can now be cleared.
That's pretty much it (simplified). But think about what this does. Normally if something interrupts a write operation (something crashes, a kernel panic, a power loss, etc.) there is something that will still have integrity because the OS will not write to both the journal and the regular filesystem at the same time.
If a failure occurs while writing to the filesystem it's no big deal. When the system boots back up, it notices the journal wasn't cleared so it "replays" the journal. This re-writes any blocks that might only have been partially written thus clearing any chance of corruption on the volume.
If a failure occurs while writing to the journal it's still no big deal. When the system boots back up it notices a corrupt journal, but that means the regular filesystem itself wasn't being touched so the filesystem is guaranteed to not have errors on it (although it does mean the last file you were about to save probably didn't get saved -- and that file wouldn't have written successfully even if journaling were off. At least this way there is no filesystem corruption.)
While it sounds pretty solid (and it is) there's still a potential for corruption, but it's rare. If a drive swings the access arms to a specific track and starts writing data, the assumption is that the write head is above the correct track. If the head is "sloppy" due to wear, then the head may be slightly mis-aligned and bleeding writes into the adjacent track. This will cause filesystem corruption even with journaling enabled.
If these drives came with the computers then the only warranty would be via Apple. If you purchased these drives on your own then they probably came with a pretty good manufacturer warranty -- most drives I've purchased in recent years had at least a 3 year warranty.

Leaf Count Record

After backing up my hard drive and booting from my freshly made eDrive, I ran TechTool Pro 6's "Volume Rebuild" and after that ran it showed me the results, as usual. There were a few green items but one red. The "Leaf Count Record" went from 1777 to 625. I tried to find out what a Leaf Count Record is by googling it but only count find things on the error associated with this.
So my first question is: What is a Leaf Count Record?
Secondly, is there any problem with my Leaf Count going down, and should i be worried about it?
Note: i went ahead with the rebuild since all the information i could find on Leaf Count Record is mostly about the Leaf Count going up and not down.

After backing up my hard drive and booting from my freshly made eDrive, I ran TechTool Pro 6's "Volume Rebuild" and after that ran it showed me the results, as usual. There were a few green items but one red. The "Leaf Count Record" went from 1777 to 625. I tried to find out what a Leaf Count Record is by googling it but only count find things on the error associated with this.
So my first question is: What is a Leaf Count Record?
Secondly, is there any problem with my Leaf Count going down, and should i be worried about it?
Note: i went ahead with the rebuild since all the information i could find on Leaf Count Record is mostly about the Leaf Count going up and not down.

[SOLVED] makepkg gives "grep: invalid max count"

[thiderman@justitia dunst-git]$ makepkg
==> Making package: dunst-git 1.0.0.554.92cda43-1 (Sat Dec 28 16:52:48 CET 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating dunst git repo...
Fetching origin
==> Validating source files with md5sums...
dunst ... Skipped
==> Validating source files with sha256sums...
dunst ... Skipped
==> Extracting sources...
-> Creating working copy of dunst git repo...
Cloning into 'dunst'...
done.
==> Starting pkgver()...
==> Starting prepare()...
==> Removing existing pkg/ directory...
==> Starting build()...
dunst build options:
CFLAGS = -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -g --std=c99 -pedantic -Wall -Wno-overlength-strings -Os -D_FORTIFY_SOURCE=2 -D_BSD_SOURCE -DVERSION="v1.0.0-30-g92cda43" -DXINERAMA -pthread -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng16
LDFLAGS = -Wl,-O1,--sort-common,--as-needed,-z,relro -lm -L/usr/lib/X11 -lXss -lXinerama -ldbus-1 -lX11 -lfreetype -lXext -lXft -lXss -lgio-2.0 -lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo -lxdg-basedir
CC = cc
creating config.h from config.def.h
CC -c x.c
grep: invalid max count
Makefile:31: recipe for target 'x.o' failed
make: *** [x.o] Error 2
==> ERROR: A failure occurred in build().
Aborting...
[thiderman@justitia dunst-git]$
This has happened to me for a while. I've tried building st-git and dunst-git from the AUR, and they both die with similar stacktraces. The output shown above is run in a bash with stock configuration, so no aliases or other shell trickery is going on. I've searched both source trees, but can't even find any mention of "grep" in any of them.
Googling suggested that a file with a name starting with "-m" has been found, but I can't find any of these either.
wat do?
Last edited by Daethorian (2013-12-28 17:16:25)

Trilby wrote:See my edit above - but also I'd suggest removing all the "@" signs from the makefile to see what the actual command is that is failing.
It looks pretty much exactly the same:
dunst build options:
CFLAGS = -g --std=c99 -pedantic -Wall -Wno-overlength-strings -Os -D_BSD_SOURCE -DVERSION="v1.0.0-30-g92cda43" -DXINERAMA -pthread -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng16
LDFLAGS = -lm -L -lXss -lXinerama -ldbus-1 -lX11 -lfreetype -lXext -lXft -lXss -lgio-2.0 -lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo -lxdg-basedir
CC = cc
cc -g --std=c99 -pedantic -Wall -Wno-overlength-strings -Os -D_BSD_SOURCE -DVERSION="v1.0.0-30-g92cda43" -DXINERAMA -pthread -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng16
CC -c x.c
grep: invalid option -- 'g'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
Makefile:31: recipe for target 'x.o' failed
make: *** [x.o] Error 2

TechTool 4 Volume test and "invalid leaf node"

Just a "heads up". I just installed TechTool 4 and ran the usual diagnostics as a level-set. I was surprised to discover that I had two volumes with invalid leaf nodes. To make a long story short, the discussion with TT support revealed that there's apparently nothing wrong with my drives. They've both been re-formatted, surface scanned, repaired, etc. I've never had any errors from either of them. One is a Seagate 250GB and the other is a WD 160GB. TT support asked to borrow one of my drives for a couple weeks(!) because they think it's a bug and can't reproduce it. Disk Utility says there's nothing wrong. Take Volume Scan leaf node errors reported by TT4 with about a pound of salt, since the bug is still there (and will be, since I can't live without the drive for weeks and they won't buy it). I'm reporting it here, because they suppressed the majority of our discussion on their forum and I don't particularly approve of them hiding a known bug from customers. I have the TT logs and anyone who wants to see them can just ask, BTW. This isn't a vendetta against them so much as an attempt to spare others the 2 days of lost work I experienced while running various things for TT support, all to find out that I'm not the one with the problem.
Mac Pro Mac OS X (10.4.9) 3GHz, 4GB

Oh Yeah, that I know. I run two intermediate backups and a full clone daily. The awkward thing is that one of the drives is my "snapshot backup" drive, naturally. They swear that they've only had one other report of this and it went away with a reformat. Mine did not. You'd think that a reformat and surface scan would reveal a hard, repeatable, drive error - which TT4 implies I have. What are the odds that I have two drives with a totally unique problem (such as they described it), made by different manufacturers, with hard and repeatable errors that only their program can detect? SMART says they're OK, Disk Utility says they're OK, no errors are logged, their temperatures are the same. If this error is so rare, how is it that I just happen to have it on 50% of my drives? It's been a Royal Pain to re-jigger my drives so that the backups go to a drive that doesn't have the "error", just in case.

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.

What is an invalid leaf count?

Similar Messages

Maybe you are looking for