Jump to content

Installation Help


ashr

Recommended Posts

I've just bought a server especially for UNRAID but I cannot get it set up correctly.

 

I've followed all the instructions on the config page (http://lime-technology.com/wiki/index.php/Configuration_Tutorial), but I am not receiving an IP address when I use ifconfig eth0. So I can't get onto the WebGUI.

 

My router (virgin superhub) is already set to DHCP, but I've tried entering an unused static IP into the mcedit /boot/config/network.cfg too. I've tried doing this on both UNRAID and on the file itself on my PC before putting it in.

 

I've checked the specifications of the motherboard (asus a88xma) and its all fine.

I've changed the port the ethernet goes into in the back of the router, changed the static ip address, turned DHCP off/on, I've installed a different version of UNRAID (used 6.0 first, then 5.0.6). I've checked that the two ports used (listed in ident.cfg) are open. I've tried pinging the static ip on PuTTy (no response)...

 

...and anything else I could think of doing.

 

Any suggestions or help would be appreciated

Thanks,

Link to comment

I don't find anyone else using that board.  It seems to have a "Realtek 8111G", which sounds common, but I have not heard of the G variation before.  It's possible that its PCI ID is not listed yet.  Try the Console networking commands, to find out what (if any) driver is assigned.  Show us one or more of the network.cfg files that you have tried.  And provide a syslog, see Need help? Read me first!

 

Thanks Rob, sorry... I ment the Realtek 8111G chip. I checked a list somewhere which listed a number of motherboards used for UNRAID and a number seemed to have that. It's good spec so I assumed other stuff wasn't important (the problem is it's not finding the network).

 

I've tried a number of the console networking commands and it seems like everything is there (everything has a size when I use "lsmod").

 

There are no RX packets (sending out?) but there are TX packets (coming in?), not sure what that means...

 

It also won't netlook up ("didn't find #20) or ping to google.com ("unknown host")

 

For network.cfg I've used ... 192.168.0.9 and 192.168.0.69 (unused IPs) and 192.168.0.2 (my PCs IP, already registered with router, and my PC was turned off). I've also used 192.168.1.69 (although all other IPs are 0). mask has always been 255.255.255.0, and gateway 192.168.0.1 (same as router).

 

I can't get the syslog on here because it can't find the network so I can't get onto webGUI, but I've used cat /var/logs/syslog to read through it... I can't find anything notable other than...

 

Syslog...

/sbin/ifconfig lo 127.0.0.1

/sbin/route add -net 127.0.0.0 network 255.0.0.0 lo

NX (Execute Disable) protection:active

System Product Name/A88XM-A BIOS 2001 12/05/2014

ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length

ACPI: no dock devices found.

Registered new address record for 192.168.0.2 on eth0.IPv4.

Server setup complete. Host name is Tower.local. Local service cookie is 2683876654.

Service "Tower" (/services/smb.services successfully established.

 

Looks like syslog is confirming that the server is setup and should be working fine, but I can't log onto the webGUI (I've tried uppercase and lowercase, changing the name, using ip, using tower, different browsers, etc...)

 

Please save me haha

 

 

 

Link to comment

It's not until the very last line of the syslog that the network connects though, with the "r8168: eth0: link up".

 

You do not want to use 192.168.0.2 if that's reserved for your PC, because the router knows the MAC of the PC, and your server MAC will not match.  Use 192.168.0.9 or anything else.

Link to comment

It's not until the very last line of the syslog that the network connects though, with the "r8168: eth0: link up".

 

You do not want to use 192.168.0.2 if that's reserved for your PC, because the router knows the MAC of the PC, and your server MAC will not match.  Use 192.168.0.9 or anything else.

 

Thanks Rob / Itimpi,

 

I'd tried 0.9 and 0.69 (one that I definitely knew was free) before 0.2 and they didn't work either. I only used 0.2 because I thought it'd be a recognised address on the router. To be honest I've tried absolutely everything haha.

 

I've attached the ifconfig... Had to take a pic on my phone.

IMG_20150603_204515_Medium.JPG.d4aa7897c48cddeddfb349e25c84a38c.JPG

Link to comment

The picture shows you haven't yet changed your IP, it's still 192.168.0.2.

I only used 0.2 because I thought it'd be a recognised address on the router.

The router would recognize it alright, and know it's not yours!  You really need to change to either DHCP or 192.168.0.9, and reboot.  Setting it to use DHCP would show us what responses you get, if any.  In the picture, you transmitted 19 packets (TX=19), but not one came back (RX=0), so no one at all is talking to you.  What is the network cable connected to on the other end, a switch or a router?  The fact that the eth0 link came up means there's a working ethernet component on the other end of the cable, but so far, there is no evidence at all of a router on the network.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...