Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] Cannot Obtain IP Address

Featured Replies

Problem has been solved :) 

 

After spending most of my work day searching every nook and cranny of the world wide web researching this issue

I hit pay dirt  the culprit  WOL features have to be turned off 

 

I fired the flash drive up there she as beautiful as I ever could have imagined  the elusive IP address

 

Thanks for all that offered their help I really appreciate it. 

 

 

 

 

 

Good Day

 

I'm trying to fire up a unRAID server for the first time and before I get the Tower login it says Cannot obtain IP address

 

reading through some posts on the matter I have tried setting a static IP  and it could not be seen on the network 

if I boot the machine into Windows I have no network issues at all 

 

I have the USB labeled UNRAID

my network card is a Intel I217-V  driver 12.15.22.3

 

Any insight would be great I'm foaming at the mouth to get this up and running :)

 

Added log file

log.txt

  • Community Expert

From your post, it not super clear how far along you are in the boot process.  Did you get to the login prompt?  If you did and you are still setup to use a static address, try entering that IP address on a address line of your browser.  Below is the one that I use to get to one of my two unRAID servers:

 

      http://192.168.1.242/

 

(Obviously, you will have to use the IP address that you assigned!)

 

Since it appears you are using a plugin card, did you disable the onboard NIC?  If not do that in the BIOS.

 

If that does not work and you are getting to the login screen, login into the server.  Then type      diagnostics

 

Shut the server down by typing    powerdown

 

Remove the flash drive and plug it into your windows machine.  Inside of the 'logs' folder, you will find the 'diagnostics' zip file.  Attach it to your next post.

  • Author

Thank you for the reply

 

I tried setting a static IP  and the machine could not be seen on the network or logged into via a browser from another machine

the LAN connection is via the motherboard the addon card is a SATA card

 

I am attaching the diagnostics.zip as requested

 

again thank you

tower-diagnostics-20160311-0017.zip

  • Community Expert

I am no real Linux Guru and I don't know what anyone else is seeing in the diagnostics file but it looks like your NIC is working and it is at 1Gb.  This indicates that it is seeing something on the other end of the connection but (and this is where I am a bit confused) the DHCP process apparently is not getting back an IP address. 

 

I would try a new Cat5E or Cat6 cable between the server and the switch.  You might also try another port on the switch.

 

Anyone else with some thoughts?

  • Author

tried different cable and port on router that I use for a different machine still no dice

 

The router is an asus rt-ac66u  the motherboard for the machine is an asus gryphon z87 not sure if there are any settings I should be looking at

 

 

Thank you

  • Community Expert

tried different cable and port on router that I use for a different machine still no dice

 

The router is an asus rt-ac66u  the motherboard for the machine is an asus gryphon z87 not sure if there are any settings I should be looking at

 

 

Thank you

 

I looked up the manual for your router and have a suggestion of something to try.  On your flash drive in the  'config'  folder, rename the  network.cfg file to network.cfg.old

Then copy the attached file into that folder.  Eject the Flash Drive and reboot the server.  Your IP will now be      192.168.1.242   

 

Now try to access the server with          http://192.168.1.242

network.cfg

  • Author

Thanks Franks and I wish I had good news 

 

followed your instructions renamed the old file and added the new    navigated to 192.168.1.242 and I get a webpage not available  ERR_Connection_Timed_Out  I logged into the router and it doesn't see it either

Post a diagnostics with that network.cfg file in use.

 

Your first diagnostics indicates the NIC on the server is working ok.

 

Mar 11 00:16:39 Tower dhcpcd[1415]: dhcpcd-6.8.1 starting
Mar 11 00:16:39 Tower dhcpcd[1415]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Mar 11 00:16:39 Tower dhcpcd[1415]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
Mar 11 00:16:39 Tower dhcpcd[1415]: eth0: waiting for carrier
Mar 11 00:16:42 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 11 00:16:42 Tower dhcpcd[1415]: eth0: carrier acquired
Mar 11 00:16:42 Tower dhcpcd[1415]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Mar 11 00:16:42 Tower dhcpcd[1415]: eth0: delaying IPv4 for 0.4 seconds
Mar 11 00:16:43 Tower dhcpcd[1415]: eth0: using ClientID 01:40:16:7e:78:33:8a
Mar 11 00:16:43 Tower dhcpcd[1415]: eth0: soliciting a DHCP lease
Mar 11 00:16:43 Tower dhcpcd[1415]: eth0: sending DISCOVER (xid 0x427259fd), next in 4.6 seconds
Mar 11 00:16:47 Tower dhcpcd[1415]: eth0: sending DISCOVER (xid 0x427259fd), next in 7.4 seconds
Mar 11 00:16:55 Tower dhcpcd[1415]: eth0: sending DISCOVER (xid 0x427259fd), next in 16.2 seconds
Mar 11 00:17:11 Tower dhcpcd[1415]: eth0: sending DISCOVER (xid 0x427259fd), next in 31.5 seconds
Mar 11 00:17:39 Tower dhcpcd[1415]: received SIGTERM, stopping
Mar 11 00:17:39 Tower dhcpcd[1415]: eth0: removing interface
Mar 11 00:17:39 Tower dhcpcd[1415]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' STOP
Mar 11 00:17:39 Tower dhcpcd[1415]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' STOPPED
Mar 11 00:17:39 Tower dhcpcd[1415]: dhcpcd exited
Mar 11 00:17:39 Tower logger: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -b -t 10 -h Tower -d -L eth0
Mar 11 00:17:39 Tower dhcpcd[1445]: dhcpcd-6.8.1 starting
Mar 11 00:17:39 Tower dhcpcd[1445]: forking to background
Mar 11 00:17:39 Tower dhcpcd[1448]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Mar 11 00:17:39 Tower dhcpcd[1445]: forked to background, child pid 1448
Mar 11 00:17:39 Tower dhcpcd[1448]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Mar 11 00:17:39 Tower dhcpcd[1448]: eth0: delaying IPv4 for 0.3 seconds

 

Basically, it starts up and asks for an IP and receives no response. After a few attempts if gives up and shuts down the dhcpcd program.

  • Author

The plot thickens

 

I have an old laptop that has a LAN  port but it's 32 bit  I downloaded the 32bit version of unraid and put it on the flashdrive  booted up the old laptop using the cable that I was using in the machine and  it  was assigned an IP  without issue

  • Community Expert

The plot thickens

 

I have an old laptop that has a LAN  port but it's 32 bit  I downloaded the 32bit version of unraid and put it on the flashdrive  booted up the old laptop using the cable that I was using in the machine and  it  was assigned an IP  without issue

 

I say it does!!!  You say this Asus MB and its NIC worked with Windows but not with unRAID?  Otherwise I would suspect that this Port is dead.  Have a good look into the CAT5 socket on the MB and be sure that everything looks OK--- no bend or deformed contact springs.  Make sure that something weird did not happen when you were installing the MB into the case with regard to that backplate the MB connectors pass through. 

  • Author

 

no equipment has been moved  if and when I can get this working I'm going to reformat the drives that have windows on it 

 

all is fine and clear on the port and connection there is just some sort of ghost in the machine 

 

If I didn't have such a good head of hair I would start pulling it out :)

  • Community Expert

You might try sending a request for help to    [email protected] 

 

Be sure that you reference this thread.  Maybe they will something that is escaping us. 

Have you tried rebooting the router? I wonder if its pool of DHCP addresses is used up. If it has none spare it can't allocate one to a new request.

 

Trying to use a specific static address will only work if the computer running the web browser has a compatible address, which is assumed in the discussion above but not tested and proved. What address do you use to ping the router?

  • Author

John

 

 

I reboot the router a few times  about 30 minutes ago I did a full reset cleared nvram factory default settings

 

same thing cannot obtain IP address

 

thank you for the suggestion 

 

192.168.1.1 is what use to get to the router interface

 

  • Author

reset router & motherboard to factory defaults  still cannot obtain an IP and when I  assign one manually it can not be accessed via another machine  :-X

I don't have anything that uses the Intel I217-V. Is it integrated into the motherboard? Perhaps someone has experience of that particular chipset.

  • Author

Hi John

 

yes it is a part of the motherboard

 

I have a couple of pictures  one is a screenshot  of an ipconfig  when I boot into windows  the 2nd is an ifconfig -a when I boot from the flash drive

ipconfig.zip

  • Community Expert

I see that you got it solved.  WONDERFUL!!! 

 

Turning off the WOL feature in the BIOS????  It sounds like you used the combination-of-permutations method to achieve a solution.

 

If you actually need the WOL feature, you might check to see if there is an update to the MB BIOS which might fix this.  (I would not even attempt to update any BIOS UNLESS the update was absolutely required to fix some problem that I had!  I can remember when flashing a BIOS could easily result in a brick!  But, perhaps, that situation has changed for the better but I, personally, would rather not chance it.)

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.