What is "invalid volume directory count"?

I get it when I run Disk Utility on my iMac (OS 10.5.8) My Safari was acting wonky (not correctly loading web pages, or not loading them at all)
It says to run disk utility off the installer disk. Will this wipe out all the stuff on my computer? Thanks

No, it won't wipe the disk. Just run Repair Disk. You need to run from the installer disk because the boot volume needs to dismount for repair and it can't if you're booted from it.
However, as with any operation you do have a backup of your drive, right?
OT

Similar Messages

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 Directory Count

I have had my MacBook Pro for nearly three years (Oct 07). I also have Apple Care but they have been unable to help and hence i am posting here.
About 18months ago 'parallels' sent out an update which caused 'parallels' not to load properly and set off a string of events that has been a marathon of faults and repairs. My Macbook has spent two separate periods of one week in an apple repair shop and ended up with a completely new hard drive under Apple Care. The last problem has not been fixed (the repair shops have said this is a software problem and nothing they can help me with) and i am at a loss what to do.
Problem: Every time i shut my laptop down, the hard drive becomes corrupted and randomly crashes programs and the whole system. When i do disk check, i am told that i have an 'invalid volume directory count' and it will list at least two separate count problems. I will repair this with my installation disk and the next time i shut down my laptop. The problem reappears. If i leave my laptop on, then i usually have no problems for at least a few days.
Please help.

I've been having the same problem for the last 4 months or so. The problem even migrated to my MBP from my MP workstation. I've never had these kinds of file count errors and have had a rock solid Mac system for years, hardly ever a freeze. I can tell when the count goes off because my apps start acting weird, like slowing down, the spinning beach ball and failure to quit an app.
The DU app keeps it repaired for a few days, maybe a week at the most and then the error comes back. I've even rebuilt the directory using Drive Genius 3 only to have it go bad again a week later. Then, I followed advise and replaced the HD with a more expensive commercial grade server class drive, thinking it must be bad sectors, but the new drive shows the same error after a week and the replaced drive tested perfect with no bad sectors. I've considered it a 10.6.4 bug but then, more people would be having problems with it (there are a lot of us), so I decided to look elsewhere, since I have no desire to reinstall the main OS and 100G of applications and updates.
Since the problem migrated to my MBP when I used SuperDuper to clone my main apps over from the MP workstation, I figured there must be a 3rd party SW corrupting drives on both machines. Since there's no pattern to the errors from my main apps, I decided to look elsewhere, where apps could launched without my knowledge. This led me to the startup items in the OSX's main library folder. There I found apps that are tied to older virus scan software and drive utility software. I remember one fellow saying the "Drivepulse" auto scan feature in Drive Genius 3 was corrupting his drive in such a manner, so I turned it off, but not realizing this was executed from the StartupItems folder. I removed just about everything that was 3rd party; I don't want anything launching that is unnecessary. It's been a week and so far, so good. Given the nature of the cycle of past events, this is not sufficient time to say "gotcha" but I think it may be the cause from what I've read.
Go to the main library folder (not the user one) and look in the " StartupItems" folder and see what's there. I think you will be surprised how many apps put stuff there that you do not want running, especially from old software you may have already dumped but didn't know it left behind a few stragglers causing havoc while scanning your system. Get rid of everything you don't need. Those apps you use that do need this folder will rebuild there unix execution apps the next time you launch them.
I'll post an update after a month or so to let you know if my attempts have been successful.

"invalid volume directory count" troubleshooting help sought

Yep, I'm still on 10.5.8. I am about to go to Snow Leopard (since I know my machine can handle that) and was sorting thru files before the upgrade. I came across mds-crash-state file that prompted me to 'verify disk' (in DU) and then got the "invalid volume directory count" error message.
I think I realize that a repair disk from the install disk is perhaps a best option, but am wondering if I can do this, or even fix original issue, from the install disk on upgrade?
I do already have full backup and secondary backup of all files on this disk (main HD).
I feel another option to fix things, that seems like good time to consider this, is to move all my data on my main HD to new internal drive when I do the upgrade to 10.6.x.
Anyway, besides looking for input on my current options (a - fix this upon upgrade and/or b) move to new main HD during upgrade), I'm wondering if I need to consider doing the 'respair disk' option immediately. I'm no more than a week from upgrading, and other than slow acting computer at times, I haven't experienced any worrisome issues with this computer in recent days.

Do not attempt to "Upgrade in Place" without repairing the Hard Drive. The new install brings in over 250,000 new files. That will NOT make things better.
To ( Repair Disk) from the Installer/Utilities DVD:
Boot from the Installer/Utilities DVD, but do not Install. Answer only the "what language" question, if presented, and wait a quarter minute for the MenuBar to be drawn. Choose Disk Utility from the Utilities menu or the Installer Menu.
At this point, your are using the DVD as your System, so the internal Hard drive is fully available for a deep repair.

Invalid volume directory count/unable to repair

My computer (iMac G5, OS 10.5.5) has been running slowly. When I run Disk Utility, I get an "invalid volume file count" and "invalid volume directory count" message, and an error message that the volume HD needs to be repaired. I can run Verify Disk Permissions, Repair Disk Permissions, and Verify Disk, but the Repair Disk button isn't available. Therefore, I followed instructions to start up from the install disk, then go to Disk Utility, all with the same outcome. In other words, I'm stuck, with Repair Disk never being available. What can I do? Many thanks for any helpful suggestions!

Disk Warrior fixes this.

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

INVALID VOLUME FILE COUNT and INVALID VOLUME DIRECTORY COUNT

Every few days, something on my machine is causing an invalid volume file count and an invalid volume directory count. Error message will read something like:
Invalid volume file count
(it should be 520176 instead of 520178)
Invalid volume directory count
(it should be 152750 instead of 152748)
This causes the machine to lock up.
This is my SECOND machine (same set up on the previous machine) that is experiencing these issues. Once I run the disk utility off of the original OS disk everything is fine.

This is my SECOND machine (same set up on the previous machine) that is experiencing these issues. Once I run the disk utility off of the original OS disk everything is fine.
Invest in a couple things - backup drive, Disk Warrior, and SuperDuper
Install OS X to part of your external (small and just big enough for an emergency system and minimal programs).
Booting off DVD is fine, but no Finder and you are limited to the (older) version of Disk Utility on there (and it does get updated and changed).
Clone your system for boot backup, especially before updates and changes.
Disk Warrior recognizes and repairs more issues, some of which Apple First Aid doesn't even look for.
So even though it appears okay afterward...
Next would be to run Apple Hardware Test, and along with that check your RAM with MEMTEST (REMBER is handy and is just GUI wrapper to memtest program) or run Memtest yourself from the Terminal.

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?

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

Disk Utility: invalid volume file count & directory count

My MacBook OS X version 10.5.8 has ran quite slowly occasionally but I think that's due to the fact I've had it for almost 5 years. But then yesterday it kept on freezing every few seconds so that it was impossible to do anything. I then left it overnight and in the morning cleared the safari cache and kept rebooting it which eventually stopped it freezing so often. But now certain applications such as iTunes keep quitting before they even open properly and applications that do work still freeze every so often. So then I ran disk utility and verified the disk which came up with this:
"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)
The volume Macintosh HD needs to be repaired.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Error: Filesystem verify or repair failed."
However the 'repair disk' button is dimmed so I can't click on it. Then when I typed in my problem on the help bar it said I need to use the installation disk to be able to repair this but I don't know where this disc is, so was wondering if there are any ways of fixing this without needing a disc?

was wondering if there are any ways of fixing this without needing a disc?
No.
You cannot do this from the same start-up disk. Reboot from your install disk (holding down the C key). Once it opens, select your language, and then go to Disk Utility from the Utilities menu. Select your hard disk as before and click Repair:
http://support.apple.com/kb/HT1782?viewlocale=en_US
Once that is complete reboot again from your usual start-up disk.
Call Apple Customer Support 1-800-767-2775, provide the Serial Number and specifications of the Mac, and for a reasonable fee, they will supply a replacement set of system discs (if available).
The discs will be for the original version of the OS that was pre-installed when the Mac was manufactured.

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

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?

Invalid volume file count/volume directory count - how to fix?

a run of the disk utility app gave this message:
when I attempt to load my Leopard Install Disk 1, all I get is a hardware check. What else can I try?

If your Macbook is running Snow Leopard do not use a previous OS version to repair a newer system.
Boot from the Snow Leopard installer disc (hold down C key) and use Disk Utility there to repair the drive. If it cannot repair it then you will need to buy a stronger utility such as Diskwarrior.

Invalid volume file count

My system gets stuck on gray screen at start-up. I boot as target drive and use disk utility from my laptop to repair the invalid file count. It starts up fine for a few starts, them hangs on gray screen again. Any fixes?
Once I've repaired the drive remotely from my laptop using the disk utility with the mac pro booted in target mode it starts up ok 2 or 3 times... then gets stuck again and disk utility reports the same invalid count message.

You may be getting that notice from a drive that is having problems.
Do you have current backups? If not, put everything aside and make backups as soon as possible, as the drive may be about to fail catastrophically.
There is a lot you can do to restore your faith in that drive. But several steps in the process take all afternoon. I suggest you buy a new drive and replace the one that is being unreliable, then work on the unreliable drive at your leisure.
One thing that makes a drive unreliable is blocks that are Bad, or that require many retries to get good data. The classic way of dealing with this problem is to security Erase and write Zeroes into every data Block. It takes Hours, but can be done in the background IF this were not your Boot Drive.
When completed without error, the drive has substituted spares from its private stash to replace any Blocks found bad after Zeroing. If too many blocks were spared out, the Zeroing can be repeated, but the drive should be assigned lighter-duty use, such as periodic Backups. Sometimes the drive never passes, and must be retired.

What is "invalid volume directory count"?

Similar Messages

Maybe you are looking for