Following up on the problems addressed earlier, I just installed a D-Link DGE-530T.  Now the console works fine but I can't access or ping the server at all.

 

*I disabled the onboard NIC

*I moved the cable into the PCI NIC's port

*I do get green lights on the NIC

*My server was previously configured to pull DHCP from my router.  I did not change any config at first, just *installed hardware, swapped cable and booted

*I can't access the webGUI via the previously configured server name ("UNRAID") or various IPs I've tried.

*Looking in the router's DHCP table, I don't see anything new showing up

 

*I tried using ifconfig to manually set an IP/netmask/gateway--no change in behavior, except browser took longer to time out and after repeated attempts the server locked up (presumably because the syslog overran it's buffer)

 

Troubleshooting info:

lsmod lists

md_mod

xor

ide_gd_mod

atiixp

ahci

sata_mv

 

ifconfig:

lo (only listing)

Link encap: Local Loopback

inet addr:127.0.01 Mask 255.0.0.0 [no idea why this isn't pulling from network.cfg properly]

 

ethtool lo:

Link detected: yes

 

ethtool -i:

Cannot get driver information: Operation not supported

 

 

* I backed up network.cfg and disabled DHCP.  I set the static IP to the server's previously reserved (in router DHCP config) address.

 

Two syslogs attached: 07-14 is last captured before install of PCI NIC, 07-16 is latest one, with edited network.cfg. Also attached config files.

mkunraid.zip

According to the second syslog, the system doesn't recognize the NIC. Since you're running unmenu, you could use it to install pciutils which will give you the lspci command you can use to see if it shows up at all (probably not). This could mean a number of things, possibly badly seated, defective, incompatible mainboard or slot. First to try would be to remove it from the slot and put in a different one.

I'd try a fresh stick with 5.0b, or at least 4.71. Just long enough to see if the card is recognized.

 

From what I've seen reported here, the sky/skg (Marvell) drivers included with mid-4.x unRAID often have this problem. I'd think it could be worked around with the right BIOS settings but don't know your board.

Good tips, I will try both.  I was planning to upgrade to v5 anyway, I just was hoping to get all my issues straightened out before I introduced new complications