Welcome to the MacNN Forums.

shockme17 · Apr 16, 2005, 03:11 PM

after installing the 10.3.9 upgrade, my computer shut off during the optimization process.. i restarted, and after the login window shouldve appeared, i got a black terminal screen, saying darwin/bsd and my computer name, and a log in prompt.. after logging in with my user name, i was given a bash prompt...

how can i get osx back? thanks

asdasd · Apr 16, 2005, 04:33 PM

well now seems like a bug there.

After you log in can you see if there is anything in /Library/Logs/CrashReporter?

There may be a windowserver crash log or a loginwindow crash log.

Also try ~( homedirectory)/Library/Library/CrashReporter, but try the first one first. Report back here .....

asdasd · Apr 16, 2005, 04:55 PM

The bug may also be in the application called SecurityAgent.

shockme17 · Apr 16, 2005, 05:55 PM

im not familiar with using the terminal functions.. how do i go to that directory?
im only familiar with using dos ie : cd\ and such..

Big Mac · Apr 16, 2005, 06:02 PM

Dropping into a shell upon login would freak me the hell out. Not something I have ever seen. Can you restart and try logging in as a different user? If you want to restart, you can issue the "shutdown -r now" command.

theolein · Apr 16, 2005, 06:03 PM

You should try booting into single user mode (Command-s on start), and then trying a "fsck -fy" at the prompt and repeating that command until there are no more error messages and the issuing the "reboot" command

asdasd · Apr 16, 2005, 07:22 PM

Lets not get offtrack, permissions wont fix much. And once he is in the position he is in he is like he is in single user mode

At the bash prompt

1) login
2) cd /Library/Logs/CrashReporter
3) ls -al

report the logs you see here first.

shockme17 · Apr 16, 2005, 09:16 PM

yeah i only have one user account on the machine.. ill try the crash reporter nd post the details in a bit
thanks for the help

shockme17 · Apr 17, 2005, 03:15 AM

bad news.. theres no crash reporter directory...
the only directories listed in the library/logs are : apple file service, console, directoryservice, and a log for the software update..

help help!

jamil5454 · Apr 17, 2005, 03:23 AM

Try fixing permissions. I know many people say it like it's a miracle worker, but in this case I think it may actually do some good.

Chuckit · Apr 17, 2005, 04:34 AM

I doubt it. Since LoginWindow runs as root, and permissions are irrelevevant to root, I don't see how permissions could be hurting LoginWindow.

theolein · Apr 17, 2005, 06:34 AM

Originally Posted by asdasd

Lets not get offtrack, permissions wont fix much. And once he is in the position he is in he is like he is in single user mode

At the bash prompt

1) login
2) cd /Library/Logs/CrashReporter
3) ls -al

report the logs you see here first.

fsck -fy is not reparing permissions. it's checking the filesystem, which could just be ****ed, thereby causing loginwindow to crash

chabig · Apr 17, 2005, 07:04 AM

Out of curiousity, how did your computer magically "shut off" during optimization? Macs don't just shut down on their own. I suspect there is more going on here than you're telling us.

Chris

shockme17 · Apr 17, 2005, 06:41 PM

hey calm down.. whats with the suspicious tone of your post? i shut off the computer. ve donethis before when doing software updates, not consistantly, but ive never received these results..

if anyone has any idea how to reolve this, id gladly appreciate it.

asdasd · Apr 17, 2005, 06:49 PM

shockme,

You need to give us the info we asked for, or else noone can help you. Even Apple could not help you. Your problem seems unique.

( I suspect that you may have run out of power, maybe?)

Chuckit · Apr 17, 2005, 07:08 PM

He didn't run out of power. He says he shut it down. The question is why that would kill LoginWindow permanently.

Since the "Optimizing" phase, to my knowledge, is just a fancy way of saying "I'm running update_prebinding," I'd try doing this:

Code:
sudo update_prebinding -root /

shockme17 · 08:43 PM

thanks asdasd, but if you checked my post shortly following yours concerning the crash reporter, you'd see that such directory exists..

ill try that command Chuckit, and post the results. thanks.

edit: ok well just as i was preparted to try that last sudo command.. it booted up properly.. very odd. but im no complaining! hopefully there won't be any further problems.. thanks for the help.

edit 2: so i restarted and i got the same error, so i updated the prebindings, and everything appears to be working fine now..- since im using it now

. also, ive read somewhere a while ago there was a script or a setting somewhere to turn off the optimization rocess folling installs.. does anyone know what that is?

thanks again.