OK, here's the situation. We've got a server that's connected/powered to a UPS. Over the weekend, the battery went bad and the server lost power abruptly. This morning we came in a booted it up and it can't bring up the eth0 interface eventhough it's connected to the network. Any idea why this would happen? Should I run a manual fschk on /, is it possible some config files were corrupted? The NIC info is assigned via DHCP. I can't think of why losing power would cause the network interface not to come up and I need to get this server up ASAP, I'd appreciate some help.

Thanks,
Aaron

It is possible your NIC went bad. You could try swappin it out with another NIC, if the problem persists, it's elsewhere.

Yes, it's a good idea to run a manual fsck from a boot disk/cd. (fsck doesn't like to fix stuff on a mounted file system)

Can you manually assign and IP address to eth0 and have it ping out? Do you have a link light? Clean the contacts, reseat the card.

There's a start.

Where are the config files for manually setting up Networking/DNS in Red Hat 9? Are there any other diagnostic things I could try to see if the NIC's bad?

man ifconfig

quick and dirty, (not a replacement for man ifconfig) to set an ip address and bring an interface up:

ifconfig eth0 192.168.0.25 netmask 255.255.255.0 up

try pinging something on that collision domain.

howzit

try stop and starting service to see if errors r given (service network restart). Look at /var/log/messages and see if any errors come up. Config files r found in /etc/sysconfig/networking/devices/ or try and see /etc/sysconfig/network-scripts/ there should be a file that says ifcfg-eth0. Try this cmd to see if NIC appears lspci. Check and see if modules is inserted and running lsmod or /etc/modules.conf.

I know i mnetioned a few things but take it one step at a time and if u need any clatification BUZZ us.

chow

Thanks alot everyone, it was the network card that had gone bad. I found is by doing a "service network restart", it gave me an erroring stating that the device eth0 was in a error state. I appreciate all your help!