yenko said:
i didn't see that option - i wonder if it's on disc 2
can't hurt to try again, i think i've calmed down enough that the poor powerbook is in no physical danger.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Log in window hung (won't boot)
- Thread starter iBlue
- Start date
- Sort by reaction score
i didn't see that option - i wonder if it's on disc 2
can't hurt to try again, i think i've calmed down enough that the poor powerbook is in no physical danger.
mad jew said:I think Disk Utility is in the Installer menu ad it should be on the first disk.
ah thank you! learn something every day, i didn't even notice the option. i ran the repair permissions, still stuck on the newest annoyance "waiting for update settings" man all i wish is that i could tell it to stop looking/waiting and just friggin BOOT already. <tears hair out>
it's probably my fault for stupidly trying to re-install the OS when there was a log in issue. i'm not that experienced in this, what can i say?
it's a genuine tragedy when something happens to my mac, it's like waiting to hear back from a doctor about a sick family member or something. stressful.
all the help is sure appreciated
I really hope that you get this fixed T_T *hugs* don't get too stressed out just remember to never use gmail status ><!
ok, i ran the repair disk and it says this:
repair attepted on 2 volumes
1 HFS volume repaired
1 volume could not be repaired
and the volume it couldn't repair is "Volume Bit Map"
whatever that means.
so i tried after that to reboot and it is again still stuck on "waiting for update settings" - what is that? bloody hell, this looked so promising too.
repair attepted on 2 volumes
1 HFS volume repaired
1 volume could not be repaired
and the volume it couldn't repair is "Volume Bit Map"
whatever that means.
so i tried after that to reboot and it is again still stuck on "waiting for update settings" - what is that? bloody hell, this looked so promising too.
Okay, try running fsck then. I seem to have more luck with fsck than Disk Utility.
This sucks, hopefully it'll get fixed soon.
This sucks, hopefully it'll get fixed soon.
i love how changing one letter of that word [fsck] seems a fitting name.
i am reading the article and about to do it as soon as i understand what i am doing
thanks again, you're awesome!
i am reading the article and about to do it as soon as i understand what i am doing
thanks again, you're awesome!
done. same crap. it came back with "the volume appears to be ok" well apparently not. still stuck at the "waiting for update settings" part of log in (or lack thereof)
i googled that phrase and someone had the exact same problem but i have no idea what they are talking about with the solution.
i want to cry
still stuck at the "waiting for update settings" part of log in (or lack thereof) i googled that phrase and someone had the exact same problem but i have no idea what they are talking about with the solution.
link
i want to cry
well Empty Cache in XPF refers to XpostoFacto
So that has nothing to do with you. and reformatting is well yes
So that has nothing to do with you. and reformatting is well yes
eva01 said:
ok, thanks
i'm totally baffled as to what i should do now with it, but i can tell you that it sure sucks to be on a mac site using windows.
poor me
Are you backed up or do you have another Mac to try Target Disk Mode? If we can get in using Target Disk Mode, then we may be able to either repair some of the errors or more ideally get your files off the drive, ready for a format and install.
Before attempting Target Disk Mode, reset your PMU. I've seen it not work sometimes on faulty systems (like yours) until the PMU is reset. I don't understand the relationship, but it seems to work.
Before attempting Target Disk Mode, reset your PMU. I've seen it not work sometimes on faulty systems (like yours) until the PMU is reset. I don't understand the relationship, but it seems to work.
what update settings means
When you install a system update that requires a reboot (as so many do), there will be a settings update thing that has to run during that reboot, and it needs to finish before the update is complete.
If you see the system hanging on this, let it sit for up to 5 minutes or so to see if it can finish. After it completes, it should remove itself (until the next software update adds a new one).
If the "update settings" thing never completes, you can try rebooting into single user mode and removing the script that runs that part. (but try giving the wait 5 minutes thing a shot first).
In single user mode,
mount -uw /
rm -rf /System/Library/StartupItems/UpdateSettings/UpdateSettings
exit
See if that gets you a little further along.... it should at least eliminate the pesky message.
When you install a system update that requires a reboot (as so many do), there will be a settings update thing that has to run during that reboot, and it needs to finish before the update is complete.
If you see the system hanging on this, let it sit for up to 5 minutes or so to see if it can finish. After it completes, it should remove itself (until the next software update adds a new one).
If the "update settings" thing never completes, you can try rebooting into single user mode and removing the script that runs that part. (but try giving the wait 5 minutes thing a shot first).
In single user mode,
mount -uw /
rm -rf /System/Library/StartupItems/UpdateSettings/UpdateSettings
exit
See if that gets you a little further along.... it should at least eliminate the pesky message.
mad jew said:Are you backed up or do you have another Mac to try Target Disk Mode? If we can get in using Target Disk Mode, then we may be able to either repair some of the errors or more ideally get your files off the drive, ready for a format and install.
Before attempting Target Disk Mode, reset your PMU. I've seen it not work sometimes on faulty systems (like yours) until the PMU is reset. I don't understand the relationship, but it seems to work.
scary stuff - and i'm not totally backed up but i would not lose my mind if everything were wiped clean. i would lose a profound amount of photos in iPhoto but it's not the end of the world... but of course i would rather not lose all that.
i wish i had another mac
but you know i am about ticked enough to go buy another one if it meant i could crack in and solve this issue. <shrugs> i'm just really happy there are people out there that know more than i do about this, i'd be totally screwed without you all. <insert mushy affectionate phrases here>
now....
iMeowbot said:
it did!
[phew, getting somewhere] it got me back to the log in window starting thing, where it proceeds to stick. at least it got there though. maybe i will try a couple of the previous tips again since the 'update settings' thing is not in my face right now.
THANK YOU!!!
Okay, well it's promising that we're getting somewhere but is there any chance of borrowing a Mac just to start from to back things up before we go too much further?
mad jew said:Okay, well it's promising that we're getting somewhere but is there any chance of borrowing a Mac just to start from to back things up before we go too much further?
yes, actually as rare luck would have it (i normally have horrible luck) my neighbors across the street have a G4 desktop; they are actually friends of ours from before we moved here (total coincidence they moved across the street from us) and i am sure they'd be fine with me using their mac for this. of course they are asleep right now but there's always tomorrow
- it's 9:30pm here i hope you're still so willing to help tomorrow. <crosses fingers> thanks again, you guys are seriously awesome. such patience!
Winner! Nice find.
Do you have the appropriate Firewire cable? You'll need one that'll fit into both machines (6 pin). Also, no guaranties that this'll work but I think it's your best bet at the moment. Fingers crossed.
Do you have the appropriate Firewire cable? You'll need one that'll fit into both machines (6 pin). Also, no guaranties that this'll work but I think it's your best bet at the moment. Fingers crossed.
mad jew said:Winner! Nice find.
Do you have the appropriate Firewire cable? You'll need one that'll fit into both machines (6 pin). Also, no guaranties that this'll work but I think it's your best bet at the moment. Fingers crossed.
i'll have to buy one but that shouldn't be a problem. (famous last words)
i agree, i think this is a wise step too. if no other quick ideas come up in the meantime, i will go with this plan.
Log in window hung
And stockings by the mantle stacked
In hopes that St. Nicholas
through the chimney had backed...
This bit of randomness brought to you by the CCAPL
Christmas Carol Anti-Proliferation League
And stockings by the mantle stacked
In hopes that St. Nicholas
through the chimney had backed...
This bit of randomness brought to you by the CCAPL
Christmas Carol Anti-Proliferation League
I have one last idea, related to a quick fix people had used in the past to deal with slow Panther boot times.iBlue said:if no other quick ideas come up in the meantime, i will go with this plan.
Once again in single user mode,
mount -uw /
mv /usr/sbin/BootCacheControl /usr/sbin/BootCacheControl.arrgh
reboot
This might get you up and running again, depending on which of various Panther ills you have run up against. If it doesn't help, you can safely rename it back again with
mv /usr/sbin/BootCacheControl.arrgh /usr/sbin/BootCacheControl
(should mention that this probably won't help if you did get updated back to the latest Panther updates after your earlier problems.)
iMeowbot said:
haha, yeah i tried it but no cigar. i imagine i better change that name back now.
Yeah, might as welliBlue said:haha, yeah i tried it but no cigar. i imagine i better change that name back now.
Your best bet as this point, given that OS X isn't telling you much about what is happening, would be to get those files backed up tomorrow and do and archive and install. It will be quicker and easier than fumbling with individual files and settings by trial end error.
iMeowbot said:
I think you may as well do a format and install. Since you'll be backed up (hopefully), you may as well make it as clean as possible. Plus, a reformat should fix that disk error.