Hey all,
So, this is probably a stupid question... but I have a Mac Pro 2008 that when I verify disk, I get an error saying I need to start up from the OS X install disc and run disk utility on it to fix errors. I've done that, it says it fixes errors, but back in the OS, it will give me same error again and say I need to run disk utility from the install disc.
So, my question is, I can reinstall the OS from my Snow Leopard disc, but I really don't want to... it's my freelance machine and I don't want to have to reinstall all of my applications (that can take years to install all discs, updates and media), scripts, plug-ins, media archives, etc.
Any advice on a way to fix disk errors like this without having to go back to all your install discs?
I'm at work now so I can't remember the exact disk error, but I can post tonight if this can better direct me to a specific program/procedure that might help.
I also haven't tried verifying disk from another admin account... which I can also try... just figured it seemed like a system-wide problem.
Thanks!
Brad
So, this is probably a stupid question... but I have a Mac Pro 2008 that when I verify disk, I get an error saying I need to start up from the OS X install disc and run disk utility on it to fix errors. I've done that, it says it fixes errors, but back in the OS, it will give me same error again and say I need to run disk utility from the install disc.
So, my question is, I can reinstall the OS from my Snow Leopard disc, but I really don't want to... it's my freelance machine and I don't want to have to reinstall all of my applications (that can take years to install all discs, updates and media), scripts, plug-ins, media archives, etc.
Any advice on a way to fix disk errors like this without having to go back to all your install discs?
I'm at work now so I can't remember the exact disk error, but I can post tonight if this can better direct me to a specific program/procedure that might help.
I also haven't tried verifying disk from another admin account... which I can also try... just figured it seemed like a system-wide problem.
Thanks!
Brad