[BALU] NIC Card or OS issue?

Kris Kirby kris at catonic.us
Fri Nov 16 10:46:55 CST 2007


On Fri, 16 Nov 2007, Nick Hudson wrote:
> drops.  This is resolved by plugging in a keyboard and restarting the 
> network (/etc/init.d/networking restart).  I looked in 
> /var/log/messages and it gives me nothing but the port is "down".  So 
> I figured it was a bad NIC card.  Replaced the NIC card and it's still 
> happening.  Same non error message is given in the messages file, 
> nothing in dmesg either other than its down.  So this leads me to 
> believe it's a OS issue of some sort.  Anyone have any thoughts or 
> ideas.

It's either OS, cable/wire, or the ethernet switch at the far end. 
CCHHEECCKK YYOOUURR DDUUPPLLEEXX. Otherwise, what I've done to solve 
this problem is the following:

1) replace ethernet switch. If problem no longer exists, pitch the 
ethernet switch off the roof. The reason for this is that if you do not 
destroy the switch, someone else will use it again. Cheap people don't 
throw away broken stuff when they should. 

2) replace the cable. If the cable is subject to movement, or you record 
a ton of port errors when you lose connectivity, this may be an 
indicator of trouble.

3) write a script to ping a remote host known to be up. If the host 
doesn't respond, ifconfig the interface down and up. I have an extended 
version of this script that reboots a gateway on failure of remote 
connectivity. Saved my ass a few times when I munged the firewall rules 
remotely. 

>  I would just reload the server but I have a very large LVM 
> partition attached across some USB drives that I am not sure if they 
> would be unharmed by the upgrade or not.

RTFM on LVM. You can export a lot of filesystems these days, you can 
probably ask it to do an lvrescan or so to pick up any additional 
drives. 

--
Kris Kirby, KE4AHR  <kris at catonic.us>
But remember, with no superpowers comes no responsibility. 
		--rly



More information about the Members mailing list