Symptom
Server Assistant stops responding during server configuration.
Solution
Enable TCP/IP on the built-in Ethernet port while setting up Mac OS X Server 10.2. It is not required that an Ethernet cable actually be connected to the port, so long as TCP/IP is enabled on it.
If your server is currently not responding, follow these steps:
1. Restart the computer using the power or interrupt button.
2. Start up into single user mode by holding the Command-S key combination during startup.
3. Execute fsck at the command line (see below for more information).
4. If fsck repairs anything, run it again until it reports no "problems" were found.
5. After that, restart normally; and Server Assistant will start up again. This time, be sure to enable TCP/IP on the built-in Ethernet port while setting up the server.
How to Use fsck From the Command Line
Once you have reached a command line, follow these steps to use fsck:
1. At the prompt, type: fsck -fy
2. Press Return.
The fsck utility will go through five "phases" and then return information about the disk's utilization and fragmentation. If fsck alters, repairs, or fixes anything, it will display the message:
***** FILE SYSTEM WAS MODIFIED *****
Important: If this message appears, repeat the "fsck -fy" command until this message no longer appears (as in Step 4 of the section above). It is normal for your computer to require several "passes" of fsck, because first-pass repairs may uncover additional issues.
3. When fsck reports that no problems were found, type: reboot
4. Press Return.
The computer should start up normally and allow you to log in.