And the wget log is just this over and over again:

 

--2013-09-27 03:07:58--  (try:20)  http://dl.dropboxusercontent.com/s/wmpj4bi3nmio8fo/control_panel-ikosa.plg
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|184.72.246.204|:80... connected.
HTTP request sent, awaiting response... Read error (Connection timed out) in headers.
Giving up.

Also I went poking around with vi and had a look at network.cfg. For the IPADDR it was '192.168.1.108' even though via the webgui it was set to DHCP and the IP address listed there was 192.168.1.2

 

I tried changing to IPADDR to 192.168.1.2 but wget still hangs...

Networking is seriously the bane of *nix, I swear.  It's easier to get congress to pass a budget.

 

If you want to run DHCP, do the following:

 

Ensure network.cfg is set to DHCP thusly

 

# Generated network settings
USE_DHCP=yes
IPADDR=
NETMASK=
GATEWAY=
MTU=1500

 

note not specifying an IP address above.

 

Ensure you are not specifying a particular IP address in ANY setting on your unraid box.

 

Check your router's management page for the DHCP lease assigned to your box, and make a note of the address.  Also check what address you're assigning to it by MAC and change it to whatever it is assigned now (192.168.1.2, I'm guessing).

 

Reboot.

 

When the box comes back, check the syslog and run an ifconfig to see what happened.  Ideally, without specifying an address you want it to run, it should come back up and be granted the same leased IP address it had before.

 

Try that and let us know what happened.  You may, depending on several factors, have to do some more tweaking, such as trashing the lease from the router and manually restarting dhcpcd, but let's hope it doesn't come to that...

 

EDIT:  If this doesn't immediately work, reboot your router and check the syslog again.  This should result in the following:

 

Unraid set to vanilla DHCP

Router set to give unraid a static lease

 

Which is what you need.

Okie dokie, done that. The syslog is attached and below is ifconfig

eth0      Link encap:Ethernet  HWaddr 00:0a:e4:87:97:96  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:67 errors:0 dropped:0 overruns:0 frame:0
          TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7406 (7.2 KiB)  TX bytes:13919 (13.5 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

 

The settings in the webgui match up. The settings in network.cfg are still the follwing:

 

# Generated network settings
USE_DHCP=yes
IPADDR=
NETMASK=
GATEWAY=
MTU=1500

 

Shouldn't the above be changed upon reboot when the unraid box receives it's IP address?

syslog2.txt

I'm getting tempted to format the USB stick and start over. Not sure if that will help, I guess it would kill any messed up config files which could be potentially causing this hassle?

 

Is there any down side to doing so? I guess I don't need to preclear the hdd again or anything since that side of things has been working great. Just reformat the USB stick, install unRAID again, boot and reassign the hdd's?

 

Or is that a dumb idea and I should persevere with trying to solve this problem (though I'm at a loss!) ?

OK, reinstalled unRAID which made zero difference... then I had a brain fart and sure enough it proved to be true. I realized the unRAID box along with my PC and Mac are sitting behind a switch... specifically this one: http://www.zyxel.com/uk/en/products_services/gs_108b.shtml

 

So I moved the unRAID box from connecting to the switch then onto the router to being directly connected to the router and bingo! wget works fine.

 

Question is can I have my unRAID box back behind my switch or does it need to be connected directly to the router?

Unless there are other items on the network that you haven't told us about, I'd say that 8 port switch is bad. Try connecting ONLY the router, switch, and unraid plugged into the switch, power cycle the switch, then try to connect. If it works, start adding machines until things break. If it doesn't, return or trash that switch. It should work fine plugged into the switch.

Unless there are other items on the network that you haven't told us about, I'd say that 8 port switch is bad. Try connecting ONLY the router, switch, and unraid plugged into the switch, power cycle the switch, then try to connect. If it works, start adding machines until things break. If it doesn't, return or trash that switch. It should work fine plugged into the switch.

 

Nope just the switch and suspect you are right that the switch is bad. For now I'm going to leave the unRAID box connected directly to the router. Power cycling the switch did nothing and resulted in the same problems...

 

So unRAID was fine all along, it was the (busted) switch that was throwing everything out. I'm marking this as solved and binning this damn switch.