Invalid Block Count

Hi Everyone,
I seem to be getting an error message when i run Disk Utility, it says "Invalid Block Count, your disk is corrupt and needs to be repaired".
I then repair it using the Lion recovery disk and it repairs it. Maybe a month or so down the line it appears again I then do the same and the end result is the same, can anyone help with this as it is worrying me.
Also is there any way you can get rid of the bad sectors in the HDD when problems appear?
Thank you in advance.

Yes, you can take it to a genius bar and they should be able to give you a definitive diagnosis. They will charge you for a replacement if necessary, but you will know the cost and be able to decide if you want to do it yourself.
Ciao.

Similar Messages

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

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.

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.

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

.OAM file in Muse - invalid block type (type==3)

Every time I try to insert an Edge .OAM file in muse and try to publish I keep getting an "invalid block type (type==3)" error, over and over... it doesn't matter even if the OAM file is empty, it still displays this problem... could someone please point me if this is a bug or if I'm just doing something wrong?
Regards

Hi,
I have the same issue but it's not an OS issue (i think) : I'm working on SnowLeopard and I have the same error message. All the http://www.adobekb.com/inserting_edge_content.html steps are correctly followed.
I cannot use the preview mode and cannot preview in a browser as well.
Any idea ?
Cheers,
Pierre

"Invalid Block Type" exception message

I got "Invalid Block Type" exception message in my program. I'm not sure what this is. Could somebody please advice?
Thanks
GZIPInputStream gzip_in_stream = null;
BufferedOutputStream destination_out_stream = new BufferedOutputStream(
   new FileOutputStream(weatherFile), BUF_SIZE);
   byte[] input_buffer = new byte[BUF_SIZE];
int byteLength = 0;
while ( (byteLength = gzip_in_stream.read(input_buffer, 0, BUF_SIZE)) > 0 )
destination_out_stream.write(input_buffer, 0, byteLength);
destination_out_stream.flush(); // Ensure all the data is written to the output.
destination_out_stream.close();
gzip_in_stream.close();

ZipException, and it only says "Signals that a Zip exception of some sort has occurred."
I forgot to include this.
InputStream tempStream = ftpClient.retrieveFileStream(zippedFile);
gzip_in_stream = new GZIPInputStream(
new BufferedInputStream(tempStream));

Imac G5 will not start up correctly? invalid directory count 52 instead of 53

Hi, i have a Imac G5. it had been working fine for many years untill a year or 2 ago when it stopped all of a sudden and just would not start up as it should. instead, it went to this grey screen with horizontal lines. eventually after trying just about every combination of keys held down on startup, the only way i could get the mac to restart was by starting it in safe mode. (at this point i rescued all my photos and music and moved them onto my macbook pro) i thought it was working fine in safe mode untill i realised that it could not connect to the internet, the sound would not work at all, and when i went to preferances it could not find any output device for the sound. it also keeps coming up with a message saying that my internet communication device does not exist. allot of the programs worked fine, such as word, or photoshop, whereas others would not. i verified the disk, and discored that it would not let me repair it.
Invalid directory count
it should be 53 instead of 52)
checking attributes file
checking volume bitmap
checking volume information
repaired.",1)
macintosh hd
error: the underlying task reported failure on exit
HSF volume checked
volume needs repair
it then came up with a message saying that he disk utility stopped verifying the macintosh hd because of it reporting the failure on exit.
i have tried doing this a few times but the exact same result is gained
i tryed using disk repair whilst starting up from the original install disk, but this also did not fix the problem. eventually, i decided to reinstall the os x 10.4.11. this had absolutely no effect, and i am at the same point. i would be very gratefull if anybody would be able to come up with any ideas of how i could fix this problem?
additional details: i have tried using the proxy reset
i have also tried running a apple hardware test
i have tried repairing the macintosh hd disk using the original install disks
also: all of the sockets at the back work fine, e.g. usb, but the microphone and headphone sockets do not work.
it will read disks fine

but this also did not fix the problem. eventually, i decided to reinstall the os x 10.4.11. this had absolutely no effect,
I'd have guess you reformated at that time. The file system is messed up. You need to reformat.
Format a disk using the installation DVD
To format the startup drive, you will need to run disk utility from your installation DVD.
This article will tell you how to get to disk utility. Once in a disk utility, you can go and format the disk.
http://support.apple.com/kb/TS1417
To format your startup drive, you will need to run disk utility from your startup DVD.
Mac OS X 10.4: About the utilities available on the Mac OS X 10.4 Install DVD
http://support.apple.com/kb/HT2055
How to run disk utility from your startup DVD.
Insert your startup DVD into your reader. Power down your machine. Hold down to the c key. Power on your machine. This will bootup your startup DVD. ( Alternatively, you may hold down the control key, this brings up the startup manager. Click on the desired volume. Click on the right arrow. )
This will bring you to a panel asking you for your language. Pick your language.
You you come to the Install Mac OS panel. Do not install.
Click on Utilities menu item. This will give you a pulldown list of utilities.
Click on the disk utility.
Start up disk utility.
On the left pane view, you will see a list of all your disks. Click on the external disk.
Click on the partition tab.
You will now see how your external disk is currently set up. Fill in the information as appropriate. You should pick Mac OS Extended (Journaled).
More details on formatting.
http://www.kenstone.net/fcp_homepage/partitioning_tiger.html

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.

Can't update to 10.6.8 kernel panic and pcscd.pub wrong block count

Hi there, as the title said, I cannot update to the recent 10.6.8 v1.1 (nor v1 for what it matters). All seems going fine till the iMac reboots, then a kernel panic is generated. Only way out is to reinstall 10.6.7 COMBO.
Both Disk Utility and Disk Warrior agree on the issue, they both say they have repaired and the iMac goes into kernel panic with again pcscd.pub block count error (should be 16 instead of 17). Re-installing 10.6.7 everything is happy again.
Any idea? Hard disk tests with Disk Warriors show nothing and the HD is journaled.

See
What is a kernel panic,
Technical Note TN2063: Understanding and Debugging Kernel Panics,
Mac OS X Kernel Panic FAQ,
Resolving Kernel Panics, and
Tutorial: Avoiding and eliminating Kernel panics for more details.

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.

Help for "Invalid Object Count"

Hi
I got a Schema in my Database, i added a couple of tables with a script, dropped them again and did so 3 times because of some errors. Now i get the Error "Owner's Invalid Object Count" in the Category "Invalid Objects by Schema" and Oracle Enterprise Manager says i have invalid objects in my schema. How can i clean the schema and delete those invalid objects? i can't seen them in my tables, views or synonyms.
greets

May be some script error
u should drop old table
then create new table.
ok
good luck

Invalid Block Count

Similar Messages

Maybe you are looking for