Invalid volume free block count

I have witnessed this insight from the disk repair report
persistently , lately every day . I have noticed among other
things that the bluetooth is , although active , unrecognised
by any system feature designed for that purpose . The list
of actions I have taken from plist removal , restart with USB
leads removed along with all the other leads , to permission
repair , fsck , disk utility and disk warrior have had some
effect but of little duration . The bluetooth was similarly
affected before the latest OSX system wide update and
recovered system wide recognition before this latest step
back . I am interested in some idea's perhaps indicating
the substance of a persistent invalid volume free block
count referral , and a related or not bluetooth recognition
problem with availability but the system blind to it .
Thanks Frederick
G5 Dual 2 GHz PPC G5 Mac OS X (10.4.4) Seagate 160 G and Seagate 300 G

invalid volume free block count referral
This from a 10.3.9 kb article: (perhaps not updated).
"The volume free block count is a type of cache of the real information stored in the volume bitmap, and the count being off does not mean your volume is damaged in any way. An incorrect volume block count message (block count changed from X to Y) is an example of this type of message."
-mj
[email protected]

Similar Messages

Invalid Volume Free Block Count Error In Disk Utility

My Ti-Book has been acting very strange lately so I decided to run the Verify Disk Option in the Disk Utility program. When I ran it, I got a series of messages in red that were:
Volume Bit Map Needs Minor Repair
Invalid volume free block count
Error: The Underlying Task reported failure on exit
When the verify disk function completed, I was asked to enter my administrator password. When I entered it and clicked on Okay, the Disk Utility program froze up and I had to restart.
What do the two error messages mean? How do I repair my disk?

Hi, WTM. The Verify Disk routine in Disk Utility is almost never worth running. It does the same error-detection tasks as the Repair Disk routine, but then it doesn't repair any errors that it finds.
Start up from your Tiger installer DVD, open Disk Utility, select your hard drive, and run the Repair Disk routine. If you get the same "task reported failure on exit" message, you'll need a stronger directory-repair utility like DiskWarrior, or you'll need to erase your hard drive completely and reinstall everything on it.

Volume needs repair..Invalid volume Free block count..

When I did a scan on the HD through Disk Utilty I got this error..."Volume needs repair...Invalid volume Free block count,,,Should be 65607....instead od 65606."
Is there any application that I can get to fix that error..so that I don't have to Reinstall with the start up disks.. I don't feel like reinstalling everything all over again. Please help or if you can direct me to the area so that I can change the numbers myself...Thank you

Hi Nvrdan1de, and a warm welcome to the forums!
You cannot repair the HD you're booted from, "Try Disk Utility
1. Insert the Tiger Mac OS X Install disc , then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, *you must select your language first.)*
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk."
Then Safe Boot , (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it finishes.
Safe Boot... holding Shift key down at bootup. Safe Boot is a special way to start Mac OS X 10.2 or later when troubleshooting.
http://docs.info.apple.com/article.html?artnum=107392
Though this seems like a simple one for DU to fix, unfortunately DU can't fix all that much,So, if it fails your best bet is DiskWarrior, you need the CD though.
http://www.alsoft.com/DiskWarrior/

Invalid free block count

Hi,
Earlier today I wanted to use the boot camp utility to install WinXP on my MBP. I decided to set the partition to about 60 Gb of space for Windows, but the utility crashed from some reason. (The screen went slightly dim grey and the message "please restart your computer now" appeared).
So I restarted the computer, but now, the 60 Gb I allocated for the new partition has been interpreted by the OS as used space on the Mac HD. I tried running Disk Utility to verify what was going on, and I get the message "Disk repair failed, invalid free block count".
How can I get my free space back? Do I really need to use the Leopard dvd to run disk utility again? I hope not, because I left the dvd at my other house, that's pretty far away from where I am right now. Any help would be appreciated! Thanks.

I don't know that Disk Utility can help since it will not repair the corrupted Boot Camp partition. You can run Boot Camp Assistant and see if it will remove the partition. If it cannot, then the next steps can be a gamble so you should backup your OS X partition in case you may need to repartition the drive.
If you cannot remove the partition with Boot Camp, then you can try this:
Open Disk Utility, select the drive entry (mfgr.'s ID and drive size) from the left side bar, then click on the Partition tab in the DU main window. You should now see the partition sizing graphic. Hopefully you should see two partitions. The top partition will be your OS X system volume. The bottom partition should be the one Boot Camp tried to create. Click in the bottom partition to select it (you will see it will be outlined in blue) and click on the "-" button in the lower left corner. The partition should then be removed. Click on the Apply button and wait for the process to complete. If the process fails then you will have to start from scratch and repartition the entire drive. Your OS X installation will be lost. This is why you need to make the backup in advance. If it does work then select the sizing gadget in the lower right corner of the remaining partition and drag it down to the bottom of the sizing window, then click on the Apply button again. Wait for the repartitioning to complete.
Just to be on the safe side I would repair the drive:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must 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 or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

IMac/Tiger kernel panic and incorrect block count

Hi,
First time here, and I am not super computer-savvy, so please bear with me as I stumble through this.
I have an iMac running 10.4.11. The other day, my screen suddenly showed a message telling me I had to immediately restart my computer. (I have since learned this was due to "kernel panic.") I ran Disk Utility, received the following message via the log:
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect block count for file .journalHistoryLog
(It should be 34187 instead of 0)
0 %)
Incorrect number of thread records
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking Extended Attributes file.
ng volume bitmap.",0)
Volume Bit Map needs minor repair
Checking volume information.
Invalid volume free block count
(It should be 19184890 instead of 19177718)
The volume Macintosh HD needs to be repaired.
I then found that to repair this, I have to boot and run DU from my original startup (Tiger 10.4) disk.
But (here's the problem): I cannot find my 10.4 disks, and I understand it's almost impossible to purchase Tiger anymore. Also, I'm planning to get a new computer soon, so would hate to spend a lot of money to just get through a few weeks (OTOH, would hate to crash and have no computer for a few weeks!).
So here's the questions:
1. Is it possible to boot some other way (for example, in Safe Mode) and run DU that way to fix the problem? If so, what are the steps in the process?
2. If not, then what are my chances if I don't repair (that is, how serious a problem is this)? Would I be okay using the computer for another several weeks until I get my new computer (going for a Mac Book Pro)?
I should note that since this happened, the computer has been fine. (Though of course, I back up to an external hard drive every night, just in case.) So I'm hoping the computer will survive for a few weeks.
Sorry for the long post. Thank you all in advance for any help you can offer!
- Linda

"Is this something a reinstall of OS X would fix or would it be more of a bad HDD that I should replace? The iMac is still under the 1 year warranty until February 5th."
Sounds like Disk Utility cannot fix the hard disk.
If getting your iMac in for service is difficult, you could get DiskWarrior which repair a directory available here: http://www.alsoft.com/
If it were me with an iMac still under warranty, I'd take it in for service and make sure Apple repairs it. You shouldn't have to rely on 3rd party software to repair the hard disk when it's still under warranty. If you do this, when you pick the iMac up, make sure and boot it before you take it home to make sure it's functioning as it should.
Carolyn
Message was edited by: Carolyn Samit

Has a fix been posted for OSX Lion causing Invalid Volume counts? Post installing OS Lion the new Recovery volume disabled my ExFAT volume shared with Bootcamp

I'm running a dual boot environment with OSX and Win 7. Before upgrading to OS Lion I had three partitions setup, one for OS SL, WIn7 and a shared ExFAT volume for multual file sharing between the OSs(Worked great!). After upgrading to OS Lion my shared volume was blocked out from Windows but remained visible to Lion. The Partition boundaries appear to be currupted by the newly added "Recovery HD" Partition that comes along with the Lion installation. This inserted volume has also started a chain of error in Disk Untility indicating "Invalid Volume File Counts". This can be cleaned up by Disk Utility using the installation CD or ironically the Recovery HD partition. The repair is only good for one reboot than the invalid Volume error returns. Windows seems fine outside of the lost shared volume but if you try to format the free space left behind by the partition issue major issues happen. Formatted actually creats a Dynamic disk switch and toasts all three volumes. OS Lion seems to be a wounded animal as I now have to reboot twice to get Lion to load up after setting up bootcamp. The problem is the partitions and OS Lion new Recovery HD. What I need is a fix to stabilize the OS Lion partition and restore the shared volume.
Pete

There are hundreds of postings describing your error and how to resolve it so I won't rehash those here. Use the search at the top right of this page to search for your error.
But I will advise you that Windows 7 32bit will not work satisfactorily for you. You said you have 8GB ram. 32 bit Windows will not address more than about 2.5GB to 3GB of your ram. You need to install the 64 bit Windows 7 in order for Windows to use all your ram.
When you bought the retail Windows 7 operating system it should have had two disks in the package, one being 32 bit and the other being the 64 bit version of Windows 7.

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)

Recurring "Invalid volume directory count" error

Hi everyone!
I'm hoping that someone can shed some light on this issue, because I'm just about to lose my mind trying to figure it out!
I manage a small companies' network of approximately 35 Apple Macintosh computers. All the computers are newer 2009 or later MacBook Pros and 2009 or later iMac running Mac OS 10.5.8 or 10.6.6.
A small number of computers persistently report one or more "Invalid Volume Directory Count" errors whenever I perform a Verify Disk check in Disk Utility roughly once per month. The errors are always easily corrected by booting the computers from their system CDs and then performing a Repair Disk and/or executing an fsck command in single user mode. Unfortunately, the problem recurs the very next time I check the affected computers' disks.
One particular user whose computer had always exhibited this problem recently received a new 2010 MacBook Pro 15, and now THIS computer exhibits the problem as well! Even more baffling, and just to be certain I avoided copying any damaged Library component from the old computer's drive, I didn't use the Apple Migration Assistant to migrate this user's hard drive to the new computer; rather, I performed a clean installation of all the applications and then copied his data to the new user account. Once again, Disk Utility reported the same error the very next time I performed a Verify Disk scan on the new computer's drive.
All staff use the same applications, and most of the other computers do not exhibit this problem.
I'm completely stumped by this problem! HELP
Message was edited by: psiciliano

Hi Thomas!
Thanks for your advice!
I doubt that the drives are dying for the following reasons:
1. The computers are fairly new
2. I do check the SMART status every time I perform monthly diagnostics, and the affected units' drives always report back ok
As for backing them up, I will certainly attempt do so more frequently.
I have to believe that the problem must be caused by the way in which the affected users handle their computers; although when I ask them, they always assure me that they properly shut down and/or restart their computers.
As for the possibility that a program may be causing the issue, since everyone in this company uses the same software, I would expect this problem to affect considerably more systems than it presently does.
I will continue to troubleshoot this problem and (hopefully) discover its cause once and for all.
It's these sorts of problems that will one day do me in...career-wise, anyways.
Pietro

Disk utility invalid free block found

I ran Disk Utility because my computer seemed slow. DU said that I needed to restart and repair, but when I did that, DU said that the disc was fine. After re-starting, DU again said that it needed repair. The exact message was: "Invalid free block found (it should be 48071714 instead of 47831211) File system check exit code is 8"
Still running pretty slow. Don't know what the deal is.
Thanks!

A disk that has been "repaired" by Disk Utility has already failed and will fail again, probably in a very short period of time.
Back up your Mac if you have not done so already. To learn how to use Time Machine read Mac Basics: Time Machine backs up your Mac - Apple Support.
Replace the hard disk drive, or take this as an opportunity to upgrade to a SSD.

It takes 5 minutes to startup and i have "invalid volume directory count"

I have tried 'restore disk' with install disk, does not work.
Now it takes 5 minutes to start leopard.....
Please help....
This is when i startup:
12-04-09 21:05:59 com.apple.launchd[107] (0x109840.Locum[197]) Exited: Terminated
12-04-09 21:06:04 com.apple.loginwindow[24] Shutdown NOW!
12-04-09 21:06:04 com.apple.loginwindow[24] System shutdown time has arrived
12-04-09 21:06:05 com.apple.SystemStarter[17] Stopping HP Trap Monitor
12-04-09 21:06:05 com.apple.SystemStarter[17] Stopping HP IO Monitor
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:18 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
12-04-09 21:11:18 com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
12-04-09 21:11:18 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
12-04-09 21:11:18 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
12-04-09 21:11:40 org.ntp.ntpd[14] Error : nodename nor servname provided, or not known
12-04-09 21:11:43 com.apple.SystemStarter[17] Starting HP IO Monitor
12-04-09 21:11:43 com.apple.SystemStarter[17] Starting HP Trap Monitor
12-04-09 21:12:12 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[101]) Exited: Terminated
12-04-09 21:12:12 com.apple.launchd[110] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions

kennmoo wrote:
I have tried 'restore disk' with install disk, does not work.
what exactly doesn't work?
boot from the leopard install DVD and repair the startup disk (repair disk, not permissions) using disk utility.
Now it takes 5 minutes to start leopard.....
Please help....
This is when i startup:
12-04-09 21:05:59 com.apple.launchd[107] (0x109840.Locum[197]) Exited: Terminated
12-04-09 21:06:04 com.apple.loginwindow[24] Shutdown NOW!
12-04-09 21:06:04 com.apple.loginwindow[24] System shutdown time has arrived
12-04-09 21:06:05 com.apple.SystemStarter[17] Stopping HP Trap Monitor
12-04-09 21:06:05 com.apple.SystemStarter[17] Stopping HP IO Monitor
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:16 com.apple.launchctl.System[2] Missing thread record (id = 7726336)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume directory count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 62222 instead of 62224)
12-04-09 21:11:16 com.apple.launchctl.System[2] Invalid volume file count
12-04-09 21:11:16 com.apple.launchctl.System[2] (It should be 269114 instead of 269128)
12-04-09 21:11:18 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
12-04-09 21:11:18 com.apple.launchd[1] (com.apple.blued) Unknown key for boolean: EnableTransactions
12-04-09 21:11:18 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
12-04-09 21:11:18 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
12-04-09 21:11:40 org.ntp.ntpd[14] Error : nodename nor servname provided, or not known
12-04-09 21:11:43 com.apple.SystemStarter[17] Starting HP IO Monitor
12-04-09 21:11:43 com.apple.SystemStarter[17] Starting HP Trap Monitor
12-04-09 21:12:12 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[101]) Exited: Terminated
12-04-09 21:12:12 com.apple.launchd[110] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions

Invalid volume file count and directory count

My wife's macbook pro started shutting down by itself randomly, so i performed Disk Utility Verify Disk and found these errors:
Invalid volume file count
(It should be 800651 instead of 800653)
Invalid volume directory count
(It should be 191005 instead of 191003)
The volume Macintosh HD needs to be repaired.
Error: Filesystem verify or repair failed.
As i do not have the Mac OS Leopard disks physically with me, I target-disk started her mac on my mac, and use my mac to run Disk Utility on her hard-disk, and repaired the disk without problems.
However, this is the 3rd or 4th time this has happened. After the 1st time, i figured something is causing it, so i checked this forum, and found that for some, the Blackberry Messenger app causes programs, so i promptly uninstalled it fully (including associated system files) and this problem didnt come back for a while.
Or could this be a sign the hard disk is physically failing soon? It is out of warranty now. We have regular TimeMachine backups. We are actually kinda waiting out until the new line of macbook pro's come out.. (hopefully in June at WWDC)
Any suggestions as to how else to address this? Thanks!
Laptop stats: MacBook Pro 15"
2.4 GHZ Intel Core 2 Duo
2 GB RAM
HDD: 250GB
Graphics: NVDIA GeForce 9400M VRAM 256MB
OS: Mac OS Leopard

Well, the disk errors are due to corruption caused by the random power downs, so focus on getting that issue solved first. What's the stats on the battery?

First Aid Services reports Errow "Invalid Volume File Count"

In attempt to deleate a small Windows psrtition and creating a larger new Windows partition, Boot Camp directed to First Aid where the resulting error messages are "Invalid Volume File Count" and Invalid File Count", Directions to reboot with program disks failed to work. What next??

What failed to work? Booting to your OS installer disk or running Repair Disk from Disk Utility when you were booted to the installer disk?

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.

Recurring invalid volume file count (I repair, it comes back)

On my desktop system (10.6.8), every once in a while Disk Utility says there is an invalid volume file count (off by 2) and an invalid volume directory count (also off by 2). I boot off the DVD, use Disk Utility to repair the file system, and a couple of weeks later, it recurs. Any way to figure out what's causing this and put an end to it?

A Cortez wrote:
I generally don't post here unless a problems has become a REAL problem. I upgraded a few months back to MacOS10.6.8 and have experienced some pretty strange behavior. It starts with horizontal lines across the screen and these can appear for several hours and then hang or within 10-15 minutes of starting up. The obvious check for me is to run disk utility because it looks to me like something is getting overwritten - virtual memory maybe. When I run disk verify I get:
Performing live verification.
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.
Invalid volume file count
(It should be 759557 instead of 759584)
Invalid volume directory count
(It should be 157930 instead of 157903)
I then have to repair the disk by starting up from original install disks...
I'm getting the horizontal lines right now and I just ran disk repair!
I can't run/find/access Apple Hardware test - seems to have disappeared from this release!
Any ideas as to how to fix/stop it from happening. It seems to be happening daily, today it has happened at least 3 times....
making me nuts!
Appears you have directory damage & need a stronger 3rd party utility to fix. You should not use your computer until the damage has been repaired to avoid damaging your directory any further.
Utilities are best run from the CDs to avoid system interference & false readings/reports. You must use the versions that are compatible w/your OS system & keep the utilities updated to avoid damaging/harming/trashing your system.
You need to make your own decision on which to purchase. Read up on them on their websites because each do something a little different.
DiskWarrior (Highly Recommended for Directory Damage Repair)
Techtool Pro
Drive Genius
================
Check out:
Apple Hardware Test

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

Invalid volume free block count

Similar Messages

Maybe you are looking for