Currently Being ModeratedJun 5, 2011 6:39 AM (in response to StirFry_2112)
I have seen Disk Utility claim to successfully repair disks with those errors but in actual fact not real fix them.
You could try DiskWarrior. It will totally rebuild the directory structure on your disk and will be able to repair those errors.
If the error persist even after repair with DiskWarrior it has usually been my experience that the disk is about to fail.
No matter what you do I would first back up any important data on that disk.
Currently Being ModeratedJun 5, 2011 6:43 AM (in response to StirFry_2112)
That drive is about to fail. Replace it.
Currently Being ModeratedJun 5, 2011 6:54 AM (in response to Allan Eckert)
Thanks for the quick responses Allan and Linc! Luckily, I have many time machine backups and have been spending the last few days restoring from different backups from different days to see if maybe some software conflict was the problem. All of them worked for about 3 hours before causing some sort of chaos again. I would like to zero the drive, reinstall everything from scratch and move on with my life, but I don't want to waste 2 work days reinstalling and authorizing (many audio plugins and software instruments) only to have more failures a few days later. Is there any way to find out for certain if this is a hardware issue?
Currently Being ModeratedJun 19, 2011 6:01 PM (in response to StirFry_2112)
UPDATE: So, I ended up buying a brand new drive on June 6th (Seagate Barracuda), re-installed everything and all seemed well. Yesterday, I went to screen share (a normal process for us as another MacPro houses all audio instruments) and it would not connect. Suspecing the worse, I checked Disk Uitility and sure enough, the exact same error message poped up again!
Invalid volume file count
Invalid volume directory count
It is now in the hands of the Apple store geniuses as of a few hours ago, the tech said they will run all their diagnostic tools but made it clear that they will probably not find anything wrong with the machine, suggesting the 8 GB RAM modules are causing the problem or some other 3rd party issue is at fault. Could this be true? Why does this hard drive error continue to show up even with a brand new drive and why does it seem to cause so many problems? I'm a long time Mac user and am completely in the dark on how to diagnose this problem, any help is greatly appreciated!!!!
Currently Being ModeratedJun 19, 2011 7:48 PM (in response to StirFry_2112)
Since the data from the disk is read into RAM, it is possible for the data from the disk to be corrupted in RAM and making it appears as if the disk is in error. This is an unusual circumstance hence the reason we are all pointing our fingers at the disk. Since you are having the same error with a brand new disk that does pint the guilty finger toward RAM now. It they are are saying they think it is RAM, I would trust them seeing as how they probably have more powerful test software then anything we have.
AllanMacBook Pro, Mac Pro,, Mac OS X (10.6.7), 12 GB RAM, 3.5 TB, iPhone 4, Nikon N80, D70 and D300 Nikon Cools
Currently Being ModeratedJun 20, 2011 1:40 PM (in response to Allan Eckert)
Totally agree Allan, just waiting to hear back from apple. In theory, this makes sense but the only problem is this is a recent problem and the computer ran fine for a solid 4 months prior with no changes to any hardware. I guess something could have easily shorted out or something, but just seems odd I can't pinpoint what is wrong (memtest said everything was okay). Very frustrating. Will post back as soon as I get word from Apple. Thanks again Allan!
Currently Being ModeratedJun 20, 2011 1:43 PM (in response to StirFry_2112)
RAM does have limited life expectancy. It does go bad. It doesn't have to short or anything of the sort.
Currently Being ModeratedJun 20, 2011 2:12 PM (in response to StirFry_2112)
..snip: this makes sense but the only problem is this is a recent problem and the computer ran fine for a solid 4 months prior with no changes to any hardware. I guess something could have easily shorted out or something, but just seems odd ..snip:
It's tempting (even to me) to bring out that "but it was fine yesterday" until I remember something my physics lecturer told me, to quote him
"in the history of all broken things is the day before it broke"
Doesn't help you but ......
Currently Being ModeratedJun 24, 2011 1:15 PM (in response to Csound1)
Big update: Talked to the Genius when getting computer back, computer was thoroughly tested for 72 hours or so, no problems found with any hardware. The only thing the guy thought was strange was the 3 8GB chips of RAM installed since they are not officially supported by Apple, however he did admit the RAM showed no errors when tested. Told to put back original RAM and see if the problem persists.
Got the computer home and all set up again with the origional 6GB chips installed (6 1GB chips). Wiped the hard drive and reinstalled the OS again from the OS disk, updated all software and restored from Time Machine backup. Tried running our Logic project again and found the computer running worse than it was before! Tried screen sharing with other MacPro and it worked very sluggishly, disconnected, restarted both computers and tried again - could not connect via screen share at all. So, something told me this may be an ethernet problem.
Just for fun, we decided to connect the 2 MacPros together directly, bypassing our ethernet hub (one ethernet cable connected to each other). In both computers, I disabled all other network connections so the only active service was the single ethernet port. Viola, like magic, everything was running much smoother! No more glitches in audio performance, no more screen sharing issues! So, I think we are now on the right path to finding a solution. Now, how do I test the hub for problems? Could it not also be one of the other computers on the ethernet network causing the problem as well? We have a MacMini (10.6.7) that has been acting strange lately (random beach balls all the time in safari and iWork, which I'm trying to fix when I find the time) that is connected to the hub and on all the time. It's nice that we seem to have a workaround for now and we can complete our project, but I would still like to get to the bottom of this as having all the computers on one ethernet network is very important for us. Again, I truly appreciate all the continued help from you guys and all the input as this has been a very positive experience. I'm glad I decided to come here for help as I don't feel alone in solving this and am not being scripted through solutions that don't make sense. Great discussion!
Currently Being ModeratedJun 30, 2011 5:56 PM (in response to StirFry_2112)
Okay, scratch that last update: just ran Apple Disk Utility today and the error is back again! Is there anything else I should try? Why does the directory keep writing errors? I thought for sure it could have been the RAM and the ethernet seemed slightly logical. I'm at a loss, any fresh ideas?
Currently Being ModeratedJun 30, 2011 9:29 PM (in response to StirFry_2112)
If you have the same problem again that is starting to sound like the disk is dying.
I suggest you back up your data and prepare to replace it.
Currently Being ModeratedJul 1, 2011 1:09 AM (in response to Allan Eckert)
The boot drive has been replaced with 2 brand new drives over the course of 2 months now, and all the drives test as fine drives. I just put in a new Western Digital 1 TB black 1 week ago when I received the computer back from Apple. I do have a good backup so no worries there.
Currently Being ModeratedAug 15, 2011 2:28 PM (in response to StirFry_2112)
Have you found any other plausible solutions to your problem? I've been having the same Invalid Volume Errors for the past two years. Been buying new harddrives, but after watching videos online - Vimeo, Comedy Central, etc. the problem always comes back. Can't seem to find any solution online either.