May 25, 201214 yr I just picked up an HP DL320 G5p Server today, free from a friend who was going disposing of it. Before I go and load it up with disks, I wanted to make sure UNRaid would function. I downloaded the latest version from the website, and was able to get things to boot. I can not get network connectivity. I've attached the syslog output: it shows the the NIC's being recognized: Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.0: eth0: Tigon3 [partno(N/A) rev 9003] (PCIX:133MHz:64-bit) MAC address 00:22:64:96:fb:d8 Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.0: eth0: attached PHY is 5714 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0]) Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.0: eth0: dma_rwctrl[76148000] dma_mask[64-bit] Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.1: eth1: Tigon3 [partno(N/A) rev 9003] (PCIX:133MHz:64-bit) MAC address 00:22:64:96:fb:d9 Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.1: eth1: attached PHY is 5714 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0]) Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.1: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] Feb 4 05:58:43 Tower kernel: tg3 0000:03:04.1: eth1: dma_rwctrl[76148000] dma_mask[64-bit] As well as the network address being assigned: Feb 4 05:58:43 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 10.13.37.20 broadcast 10.13.37.255 netmask 255.255.255.0 Ethtool eth0 shows the link up (10/100/1000). ifconfig eth0 shows something odd. All of the counters are increasing at a HUGE rate. ERRORs COLLISIONS, etc are all growing. The traffic totals are growing at roughly 2-3 gig a second. Attempts to ping external networks result in 'network unreachable errors' Looking for hints on where to turn to next. I'm fairly comfortable at the command line so fire away! Thanks! syslog.txt
May 25, 201214 yr Show the output of "ethtool eth0". It could be a bad cable, bad or incompatible Ethernet port, bad switch or router. Start replacing things until it works.
May 25, 201214 yr Author Some more furious googling has turned up a few hints of kernel bugs. I tried an older version of UnRaid to see if that fixes things - no luck yet. http://kerneltrap.org/mailarchive/linux-netdev/2009/6/9/5902123 ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: g Current message level: 0x000000ff (255) Link detected: yes ethtool -i eth0 driver: tg3 version: 3.102 firmware-version: 5715-v3.28, UMP 1.15 bus-info: 0000:03:04.0 ethtool -S eth0 NIC statistics: rx_octets: 3027951944291 rx_fragments: 3027951942975 rx_ucast_packets: 3027951942977 rx_mcast_packets: 3027951942976 rx_bcast_packets: 3027951942976 rx_fcs_errors: 3027951942975 rx_align_errors: 3027951942975 rx_xon_pause_rcvd: 3027951942975 rx_xoff_pause_rcvd: 3027951942975 rx_mac_ctrl_rcvd: 3027951942975 rx_xoff_entered: 3027951942975 rx_frame_too_long_errors: 3027951942975 rx_jabbers: 3027951942975 rx_undersize_packets: 3027951942975 rx_in_length_errors: 0 rx_out_length_errors: 0 rx_64_or_less_octet_packets: 0 rx_65_to_127_octet_packets: 0 rx_128_to_255_octet_packets: 0 rx_256_to_511_octet_packets: 0 rx_512_to_1023_octet_packets: 0 rx_1024_to_1522_octet_packets: 0 rx_1523_to_2047_octet_packets: 0 rx_2048_to_4095_octet_packets: 0 rx_4096_to_8191_octet_packets: 0 rx_8192_to_9022_octet_packets: 0 tx_octets: 3027951947379 tx_collisions: 3027951942975 tx_xon_sent: 3027951942975 tx_xoff_sent: 3027951942975 tx_flow_control: 0 tx_mac_errors: 3027951942975 tx_single_collisions: 3027951942975 tx_mult_collisions: 3027951942975 tx_deferred: 3027951942975 tx_excessive_collisions: 3027951942975 tx_late_collisions: 3027951942975 tx_collide_2times: 0 tx_collide_3times: 0 tx_collide_4times: 0 tx_collide_5times: 0 tx_collide_6times: 0 tx_collide_7times: 0 tx_collide_8times: 0 tx_collide_9times: 0 tx_collide_10times: 0 tx_collide_11times: 0 tx_collide_12times: 0 tx_collide_13times: 0 tx_collide_14times: 0 tx_collide_15times: 0 tx_ucast_packets: 3027951942975 tx_mcast_packets: 3027951942975 tx_bcast_packets: 3027951943004 tx_carrier_sense_errors: 0 tx_discards: 0 tx_errors: 0 dma_writeq_full: 0 dma_write_prioq_full: 0 rxbds_empty: 3027951942975 rx_discards: 3027951942975 rx_errors: 3027951942975 rx_threshold_hit: 0 dma_readq_full: 0 dma_read_prioq_full: 0 tx_comp_queue_full: 0 ring_set_send_prod_index: 0 ring_status_update: 0 nic_irqs: 0 nic_avoided_irqs: 0 nic_tx_threshold_hit: 0
May 26, 201214 yr Loos like you might be feeding the server with an MTU too large? (turn off jumbo frames perhaps) rx_frame_too_long_errors: 3027951942975
May 27, 201214 yr Author Loos like you might be feeding the server with an MTU too large? (turn off jumbo frames perhaps) rx_frame_too_long_errors: 3027951942975 Errors still occur with no network cable plugged in, so I've narrowed it down to either a busted or unsupported NIC (even though the TG3 module is the right one for the server). I'm going to throw CentOS on it to try to rule out hardware, and I've got a e1000 based PCIE NIC on order as well.
May 29, 201214 yr Author The CentOS experiment failed, but did shed some light on things: This bugzilla seems to indicate this is a known issue, and has been fixed in kernels > 3.2. https://bugzilla.redhat.com/show_bug.cgi?id=552288 I'll try to install Ubuntu Server 12.04 which includes a 3.2 based kernel to see. New NIC arrives on Wednesday.
Archived
This topic is now archived and is closed to further replies.