04-30-2009, 09:04 AM

hi.. I'm starting a new thread because I need specific instruction for my problem I'm really very worried that one wrong move could jeopardize the data in my HD..

yesterday I tried to adjust permissions in my system. I'm using a MacBook running leopard.. I changed permissions for the entire "macintosh HD" for "everyone" to no access. then I tried to log out of the admin account and then the problem started..

the screen stays at the blue screen where the gear spins in the foreground. after a few seconds the screen refreshes but the same thing repeats itself forever. I believe the problem is with the permissions issue. I'm typing on my iPhone now..

I have tried booting from my mac os x installation disk and ran "disk utilities" from "utilities". but both "verify permissions" and "repair permissions" gave the same error that is, it reported failure on exit. so the first aid operation failed. what can I do from here? should I try using terminal? but I have no idea of the commands. scary too.. I ran "verify disk" and it reported the disk appears to be OK.

any help is greatly appreciated.. I'm desperate.. thanks!!

04-30-2009, 12:51 PM

hi, i would recommend a fresh leopard install, try to backup your home, and reinstall OS.
Be carefull with permissions!

04-30-2009, 12:53 PM

Before you consider a reinstall, read this sticky thread:

Basic OS X/Mac Troubleshooting

05-01-2009, 08:24 AM

hi thank you for the replies!

a re-installation will be my very very last resort because i left out 2 folders of my video editing files in my time machine backups.. i will also check out the link you provided me with devilboy.

but i still have a hunch that this problem could be solved without a re-installion because verifying my disk shows my macintosh HD is OK and the S.M.A.R.T is verified. the drive and its contents are perfectly intact. just the permissions. when i click "verify permissions" or "repair permissions", an error shows up which is "The underlying task reported failure on exit".

Anyone knows how to go around this error? how about using terminal? i merely changed permissions for everyone to no access but i kept read/write for admin and system...