Did USB Key Mount properly? / ETH0 not working

[tr0910]

I have tried 2 keys and keep getting the same issues, and am wondering if it usb key related?

 

MB is Asus M4A785-M with AMD Semphron 140 and 1 gig of DDR2 ram.  Unraid 4.6 installed on Kingston Data Traveller 1gb via syslinux.

 

I just had one of these MB laying around and tried to use it for an unraid test box.  I created the usb boot key and successfully booted into unraid, but at the tower prompt, entering ifconfig eth0 didn't get me an ip address, nor can I access tower.  I didn't have my key named UNRAID first time but I later changed the volume label to UNRAID and still can't get eth0 to show up with an ip addy.

 

I get

 

eth0    Link encap:Ethernet HWaddr 90:e6:ba:a2:52:xx

          UP BROADCAST MULTICAST MTU:1500 Metric:1

          RX etc...

          TX ...

          collisions ....

          RX ....

          Interrupt:26 Base Address:0xa000

 

Just before giving the login prompt, I see it doing the following:

 

Starting Network Interface Plugging Daemon eth0

Starting RPC portmapper /sbin/rpc.portmap

Starting RPC NSM /sbin/rpc.statd

Starting Internet super-server daemon /usr/sbin/inetd

Starting ACPI daemon: /usr/sbin/acpid

Starting Samba /usr/sbin/nmbd -D

                    /usr/sbin/smbd -D

 

Welcome to Linux 2.6.32.9-unraid tty1

 

Did it properly mount the USB, or do I have some other problem?

 

[Joe L.]

Type the command

mount

and you can see if it was mounted.

 

Type the command

ls -l /dev/disk/by-label

and you can see if you set the disk label correctly..

[tr0910]

Type the command

mount

and you can see if it was mounted.

 

I get

 

fusectl.....

usbfs on .....

/dev/sdb1 on /boot type vfat .....

 

 

Type the command

ls -l /dev/disk/by-label

and you can see if you set the disk label correctly..

 

I get

 

lrwxr....... 1 root root 10 Dec 24 19:36 UNRAID -> ../../sdb1

 

Is that what I should see?  (Linux noob here)

 

 

[Joe L.]

The label exists, and this line shows it was mounted:

/dev/sdb1 on /boot type vfat .....

 

Type

ethtool eth0

to learn more about the LAN connection

[tr0910]

Type

ethtool eth0

to learn more about the LAN connection

 

Lots of stuff about ports, link modes, and speed duplex etc, but the one thing that looks strange is

 

Link detected: no

 

This computer works fine with Win7 Ult, and accesses the network beautifully.  Yet it doesn't find a link when I put the unraid key into it???

 

There is a WRT 54g router running dd-wrt firmware and 2 dlink 2208 gig switches between this computer and the router.

[Kaygee]

Link Detected = no indicates the NIC isnt seeing the switch port. Is the link light on?

Your MAC address is also funky, 90:e6:ba:a2:52:xx have you got some sort of MAC address spoofing enabled?

 

Please post up your syslog.

 

Realtek 8112L = R8169 driver.

Syslog snip from R8169 enabled board with DHCP being used.

 

kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded

kernel: r8169 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18

kernel: r8169 0000:02:00.0: setting latency timer to 64

kernel: r8169 0000:02:00.0: irq 26 for MSI/MSI-X

kernel: eth0: RTL8168d/8111d at 0xf8276000, 48:5b:39:78:8b:6b, XID 083000c0 IRQ 26

...

logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1

logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo

ifplugd(eth0)[1237]: ifplugd 0.28 initializing.

ifplugd(eth0)[1237]: Using interface eth0/48:5B:39:78:8B:6B with driver <r8169> (version: 2.3LK-NAPI)

ifplugd(eth0)[1237]: Using detection mode: SIOCETHTOOL

ifplugd(eth0)[1237]: Initialization complete, link beat detected.

kernel: r8169: eth0: link up

kernel: r8169: eth0: link up

ifplugd(eth0)[1237]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

ifplugd(eth0)[1237]: client: Polling for DHCP server on interface eth0:

logger: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -d -t 30 -h Babel eth0

dhcpcd[1265]: broadcasting DHCP_DISCOVER

dhcpcd[1265]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255

dhcpcd[1265]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

dhcpcd[1265]: DHCP_OFFER received from  (192.168.1.1)

dhcpcd[1265]: broadcasting DHCP_REQUEST for 192.168.1.100

kernel: r8169: eth0: link up

dhcpcd[1265]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

dhcpcd[1265]: DHCP_ACK received from  (192.168.1.1)

ifplugd(eth0)[1237]: client: dhcpcd: MAC address = 48:5b:39:78:8b:6b

ifplugd(eth0)[1237]: client: dhcpcd: your IP address = 192.168.1.100

ifplugd(eth0)[1237]: client: dhcpcd: MAC address = 48:5b:39:78:8b:6b

ifplugd(eth0)[1237]: client: dhcpcd: your IP address = 192.168.1.100

 

[tr0910]

I got rid of one gigabit dlink 2208 between me and the router, but still no joy.  Link doesn't  seem to be alive.  When running Win7 Ult we have no problems with this exact same network.

 

There is lights on the switch, but only randomly do the lights show up on the computer network port when unraid is running.

 

MAC address is standard, I just replaced the last 2 char with xx.  Do you want it?

 

syslog attached.....

 

Is is possible that the dlink switch is somehow the problem? 

syslog.txt

[Joe L.]

MAC address is standard, I just replaced the last 2 char with xx.  Do you want it?

syslog attached.....

 

Is is possible that the dlink switch is somehow the problem? 

no need to mess with mac address, unless it is a duplicate of another  on your lan. Have you tried a  different port on the router, a different cable?  Could be win7 was connecting at slower rate.

[tr0910]

Well it's working.  I had pulled one of the 1gb mem sticks because I wanted unraid to run with 1gb of memory.  I tested by booting into win7 and it still worked and accessed the internet properly, but it wasn't until I added the mem stick back in that unraid was happy to find the ip address.  Array is building with 2 gig of mem presently.

 

go figure.......

[Joe L.]

Well it's working.  I had pulled one of the 1gb mem sticks because I wanted unraid to run with 1gb of memory.  I tested by booting into win7 and it still worked and accessed the internet properly, but it wasn't until I added the mem stick back in that unraid was happy to find the ip address.  Array is building with 2 gig of mem presently.

 

go figure.......

The memory should not have made any difference whatsoever.... unless the memory used was not configured in the BIOS to have the correct clock speed timing, and voltage.  Most modern BIOS get it right with standard RAM, but often get it wrong with premium RAM. 

[BRiT]

I suspect you had a loose network cable and thus in process of your re-adding the memory the cable was reseated properly.

[tr0910]

Joe L and Brit, thanks for the healthy skepticism.

 

It appears that the server will in fact run with only 1 gb and still connect the network.  I pulled the 2nd 1 gb stick again, and the server continues to run fine.

 

Now I am really puzzled about what was really wrong.  I reseated the network cable multiple times in testing with no change.

 

When reinstalling the 2nd memory stick I also changed from a DVI monitor cable to a VGA analog cable.  Is it possible that unraid doesn't like DVI?

[BRiT]

Nope. unRAID doesn't care about what sort of output your video uses. I've used unRAID with VGA, DVI, HDMI, and no video output.