single-user mode gone - help

zold · #1 October 23rd, 2003, 07:15 PM

Hi.
For you power-users ...
I have relied on single user mode for fsck-ing for a while now. Twice, when doing freelance work on-site I have run into OS 10.2+ machines that refuse to boot in single-user mode. Now I'm having this problem on my home machine, and it is really bugging me (running 10.2.6). When I try command-s on startup, the machine just hangs forever very early in the boot process with a black screen. I haven't been able to find any information about this problem. How do I best diagnose it? Is there a file or a group of files in the system that I should look at? Has anyone else found this problem and, hopefully, fixed it?
Any help is GREATLY appreciated
thanks in advance
Chris G

Arden · #2 October 25th, 2003, 07:21 AM

Can you bear the weight of downloading 10.2.8? I suggest you upgrade to the latest version of 10.2 and see if the problem persists.

iscaro · #3 October 25th, 2003, 07:36 AM

Like he said, upgrade... then check your system for permissions and fix disk errors before you try again... then we'll see.

zold · #4 October 25th, 2003, 11:21 AM

Hi and thanks for the replies. I found out (thanks to macfixit forum) that one of my video cards - the one I'm using normally - does not initialize early enough in the boot process, which means that I actually am in single user mode, but the monitor is dead. This means I have to switch to the original video card whenever I restart in s.u.m.
Thanks for the replies. It may be time soon to upgrade to 10.2.8 soon, anyway ...

Cheers

Chris G

Quote:

Originally Posted by zold

Hi.
For you power-users ...
I have relied on single user mode for fsck-ing for a while now. Twice, when doing freelance work on-site I have run into OS 10.2+ machines that refuse to boot in single-user mode. Now I'm having this problem on my home machine, and it is really bugging me (running 10.2.6). When I try command-s on startup, the machine just hangs forever very early in the boot process with a black screen. I haven't been able to find any information about this problem. How do I best diagnose it? Is there a file or a group of files in the system that I should look at? Has anyone else found this problem and, hopefully, fixed it?
Any help is GREATLY appreciated
thanks in advance
Chris G

[i]

**Jason** · #5 October 26th, 2003, 01:05 AM

or you can boot into single user mode, wait a few seconds, enter your fsck, wait a couple mins, do it again maybe, etc, then hit exit and have fun