Boot Problem on Ultra 10 (still)

I am still having a boot problem with my Ultra 10 running Solaris 8. The computer was running normally until I performed a shutdown. Now it boots, but does not allow any networking or remote access. Also, I cannot login to a normal graphical session. The error message that shows when it boots is "ifconfig cannot find /usr/lib/ld.so.1"

I have posted a prior question to this forum and was told to run "dtconfig -e" then reboot. I did this, but it did not fix the problem. The next suggestion was to check the run level to see if it is 3 (it was). I then tried to start the X server with "xinit", but this command would not run. Finally, I was told to check the .xsession-errors file for errors. I could not find an .xsession-errors file anywhere, so either I don't know where to look or one does not exist. The only evidence that it might be an X server problem that I can see comes when you try to log into a normal X session. It takes forever and finally an error box comes up that says that the "dt messaging system cannot be started" and that I should start a failsafe session and check /etc/src.sh, /etc/hosts, and /usr/adm/inetd.sec to make sure that the hostname is correct (only the hosts file exists on the system).

Because of these (and other) tests, I am beginning to believe it is a problem related to the network configuration or hardware, not the X server. Specifically, when I try to run "ifconfig -a", it does nothing (simply returns back to the # prompt with no output). Likewise, "arp -a" also does nothing. Because of some troubleshooting I have done, I believe I have isolated the problem to the S30sysid.net startup script in the rc2.d directory. For some reason, none of the commands in that script will execute. Is there any key tests I should be doing to further isolate the problem? Thanks for your help.

[1857 byte] By [jmlight0] at [2007-11-25 23:21:25]
# 1
What does watch-net show you at the ok prompt?ok setenv auto-boot? falseok resetok watch-netIf you have a problem with lo0 and hme0 then this could explain the inability to start CDE.
jds2n at 2007-7-5 18:09:07 > top of Java-index,General,Talk to the Sysop...
# 2

It may be that the /usr slice is corrupted, or/and that your hard disk has some bad sectors... I'd boot up to a cd, run an fsck on the raw /usr, and see what you get.

You can also try to boot up on single user mode, then manually bring the networking up, and see what you get. Ifa everything works well in single user mode, and everything comes up as it is supposed to, then you may look into the xserver.

Chaac at 2007-7-5 18:09:07 > top of Java-index,General,Talk to the Sysop...
# 3
Thanks for the help. Turns out that the ifconfig file was corrupt. Once I had replaced it, it worked.
jmlight0 at 2007-7-5 18:09:07 > top of Java-index,General,Talk to the Sysop...