December 17, 201213 yr Hi - any and all help is welcome. As the cryptic title says I am not able to access the tower over emhttp, unmenu (port 8080), telnet, or over the windows network. None of my Samba shares are visible either. But when I hook up the monitor to the tower directly I can see that the system boots up and runs fine and I can login as root. I don't know whether the array is online and whether all the discs are running fine but the server seems to boot up and I do get a inet address when I checked using ifconfig eth0 So don't know why the tower is in accessible using any of the above, not even using telnet. I tried powering down and restarting but no luck. I tried cleaning up all the plugins and renaming the extra folder and rebooting still no luck. Any suggestions as to how to resolve this? syslogs attached - syslog.txt is the file before removing all the plugins, the other one is after plugins were removed. More Details: I have a 15 TB media server running on unRAID 5.0 rc8a. Everything was working fine till I left for a long 6 week vacation out of the country, even after that I used to get daily status updates via e-mail and that was all good till Dec 2nd (when I got the last update saying unRAID is OK). There was a parity check scheduled on the 1st of every month and that ran fine and finished on Dec 1st, and after that the tower was working fine as per the last email I got. But never heard anything after that, when I got back on Dec 13th and checked the server was running (all fans spinning and LED's on), but I could not access the tower over the browser (I have simple features installed), I used putty to telnet to the server before but that was also not working - "Host does not exist". So I thought the server is not booting up, and hooked up a monitor to the server and checked and everything is booting up as it should. I tried to check my router to see if the tower is in the connected devices list and I don't think I found the MAC address for the NIC in there (not a 100% sure about this), but as mentioned earlier I do get an inet address. So no idea what is going on here. I have very limited linux command line knowledge but I'm happy to learn. Please help!
December 17, 201213 yr Both of the files you uploaded are of zero length. (empty) Please post the EXACT contents of the output of ifconfig eth0 Everything you mentioned seems to indicate you did not get an IP address and there is no connection to your router. To get any help, you'll need to remove the add-ons, as some of them will do almost EXACTLY what you described. They will prevent the server from starting. (although unMENU should start) Again, post a copy of your syslog. Joe L.
December 17, 201213 yr Author Sorry about the blank files guys. Will attach the syslog files once I get home today. Appreciate all your help. @ Joe L. - Thanks for the reply Joe, will post the exact results of the ifconfig eth0 command as well along with the actual syslog files. About the add on's I did try removing all of them and rebooting but no luck. Will try that again - just to confirm, all I need to do is empty the contents of the /boot/config/plugins folder and rename the extra folder to something else right? That was what I did before will try doing it again, unless there is something else you would want me to do. @CaptainSpalding - I did check the LAN ports on both the NIC and the router and they seem to be working fine. I can change the LAN port on the router to be sure, I have internet access on my other Windows machines, so I could switch the ports between my desktop and the tower and see if that helps. I am using an Intel NIC rather than the on-board Realtek one. Should I try using the on-board one - any BIOS changes needed? What is baffling is that everything seemed to work fine till Dec 2nd and then all of a sudden it all changed. What could cause that change without any hardware changes or manual tampering to the system? Would a power outage be the culprit? I will post the non-empty syslog files as soon as possible. Thanks again.
December 17, 201213 yr I'm a pro of getting my unraid server to not boot at times. Even when I have not made any hardware changes, the hardware seems to "live" in the case. I would recommend to check that the NIC is not loose and yes please do try the on-board realtek. If that works that makes me think you'll need to update drivers for the new card. But that's just my couple years of trial and error.... Joe L. knows much more of the innerworkings of the unRAID.
December 18, 201213 yr Sounds like your WINS resolution isn't happening properly - *OR* your unraid box isn't getting an IP address via DHCP. Turn off Unraid. Restart Router, wait 4 minutes, restart unraid. Try again. If no go at this point, log onto unraid locally, do a ifconfig and see what the IP address is. If it comes back with one, try that in your browser (http://unraid.ip.address/ ... if no go at that point post more.
December 18, 201213 yr Author Syslog files attached - syslog.txt is the one before disabling plugins. ifconfig eth0 returns the following: Link encap:Ethernet HWaddr 68:05:ca:01:81:5e inet addr: 169.254.202.185 Bcast: 169.254.255.255 Mask: 255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:7168 (7.0 KiB) Interrupt:17 Memory:feac0000-feae0000 syslog-20121217-000526.zip
December 18, 201213 yr This Dec 17 00:51:25 Tower ident.cfg[3319]: COMMENT="Media server"^M Dec 17 00:51:25 Tower ident.cfg[3319]: SECURITY="user"^M Dec 17 00:51:25 Tower ident.cfg[3319]: WORKGROUP="MSHOME"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: localMaster="yes"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN_LOGIN="Administrator"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN_PASSWD=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: winbindDelay="10"^M Dec 17 00:51:25 Tower ident.cfg[3319]: timeZone="America/Chicago"^M Dec 17 00:51:25 Tower ident.cfg[3319]: USE_NTP="no"^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER1="pool.ntp.org"^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER2=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER3=""^M Dec 17 00:51:25 Tower network.cfg[3320]: # Generated settings:^M Dec 17 00:51:25 Tower network.cfg[3320]: USE_DHCP="yes"^M Dec 17 00:51:25 Tower network.cfg[3320]: IPADDR="192.168.2.126"^M Dec 17 00:51:25 Tower network.cfg[3320]: NETMASK="255.255.255.0"^M Dec 17 00:51:25 Tower network.cfg[3320]: GATEWAY="192.168.2.1"^M Dec 17 00:51:25 Tower network.cfg[3320]: DHCP_KEEPRESOLV="yes"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER1="8.8.8.8"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER2="8.8.4.4"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER3=""^M Dec 17 00:51:25 Tower share.cfg[3321]: # Generated settings:^M Is your IP address, 192.168.2.126 Try http://192.168.2.126 If this doesn't work, open up a command prompt and try to 'ping 192.168.2.126' if you can't ping it, something is blocking communications between your desktop and your unraid box. . Syslog files attached - syslog.txt is the one before disabling plugins.
December 18, 201213 yr looking at the network, bot your pc, router & unraid are on the same netmask (/32) and should be able to communicate with each other. If you can't communicate via name, IP will work. If IP works and name doesn't you've got a WINS server not working. This Dec 17 00:51:25 Tower ident.cfg[3319]: COMMENT="Media server"^M Dec 17 00:51:25 Tower ident.cfg[3319]: SECURITY="user"^M Dec 17 00:51:25 Tower ident.cfg[3319]: WORKGROUP="MSHOME"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: localMaster="yes"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN_LOGIN="Administrator"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN_PASSWD=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: winbindDelay="10"^M Dec 17 00:51:25 Tower ident.cfg[3319]: timeZone="America/Chicago"^M Dec 17 00:51:25 Tower ident.cfg[3319]: USE_NTP="no"^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER1="pool.ntp.org"^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER2=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER3=""^M Dec 17 00:51:25 Tower network.cfg[3320]: # Generated settings:^M Dec 17 00:51:25 Tower network.cfg[3320]: USE_DHCP="yes"^M Dec 17 00:51:25 Tower network.cfg[3320]: IPADDR="192.168.2.126"^M Dec 17 00:51:25 Tower network.cfg[3320]: NETMASK="255.255.255.0"^M Dec 17 00:51:25 Tower network.cfg[3320]: GATEWAY="192.168.2.1"^M Dec 17 00:51:25 Tower network.cfg[3320]: DHCP_KEEPRESOLV="yes"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER1="8.8.8.8"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER2="8.8.4.4"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER3=""^M Dec 17 00:51:25 Tower share.cfg[3321]: # Generated settings:^M Is your IP address, 192.168.2.126 Try http://192.168.2.126 If this doesn't work, open up a command prompt and try to 'ping 192.168.2.126' if you can't ping it, something is blocking communications between your desktop and your unraid box. . Syslog files attached - syslog.txt is the one before disabling plugins.
December 18, 201213 yr Author This Dec 17 00:51:25 Tower ident.cfg[3319]: COMMENT="Media server"^M Dec 17 00:51:25 Tower ident.cfg[3319]: SECURITY="user"^M Dec 17 00:51:25 Tower ident.cfg[3319]: WORKGROUP="MSHOME"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: localMaster="yes"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN_LOGIN="Administrator"^M Dec 17 00:51:25 Tower ident.cfg[3319]: DOMAIN_PASSWD=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: winbindDelay="10"^M Dec 17 00:51:25 Tower ident.cfg[3319]: timeZone="America/Chicago"^M Dec 17 00:51:25 Tower ident.cfg[3319]: USE_NTP="no"^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER1="pool.ntp.org"^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER2=""^M Dec 17 00:51:25 Tower ident.cfg[3319]: NTP_SERVER3=""^M Dec 17 00:51:25 Tower network.cfg[3320]: # Generated settings:^M Dec 17 00:51:25 Tower network.cfg[3320]: USE_DHCP="yes"^M Dec 17 00:51:25 Tower network.cfg[3320]: IPADDR="192.168.2.126"^M Dec 17 00:51:25 Tower network.cfg[3320]: NETMASK="255.255.255.0"^M Dec 17 00:51:25 Tower network.cfg[3320]: GATEWAY="192.168.2.1"^M Dec 17 00:51:25 Tower network.cfg[3320]: DHCP_KEEPRESOLV="yes"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER1="8.8.8.8"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER2="8.8.4.4"^M Dec 17 00:51:25 Tower network.cfg[3320]: DNS_SERVER3=""^M Dec 17 00:51:25 Tower share.cfg[3321]: # Generated settings:^M Is your IP address, 192.168.2.126 Try http://192.168.2.126 If this doesn't work, open up a command prompt and try to 'ping 192.168.2.126' if you can't ping it, something is blocking communications between your desktop and your unraid box. . Syslog files attached - syslog.txt is the one before disabling plugins. Yes that is the IP but that IP does not show up anywhere on my connected devices list on the router - any idea why? Also neither IP address nor name works. Pinging also did not work.
December 18, 201213 yr So you've tried: Try http://192.168.2.126 via web browser on your desktop and tried 'ping 192.168.2.126' on your desktop, both failed? Couple of things we can do at this point. (This assumes your desktop & unraid both get DHCP from your router). A:) Reboot router and wait 5 minutes. If the router is messed up, it could block comms from either machines. B:) on desktop (assuming it's a windows box) ipconfig /flushdns and then a arp -D (clears dns entries from machine, deletes all arp cached entries)... doing a arp -A will show you the network connections of everything broadcasting on your network. (including broadcast addresses) C:) on unraid box, remove network cable for 60 seconds. you could also accomplish by a (local command, not over network) ifconfig eth0 down then 60 seconds later ifconfig eth0 up (this command causes the network interface to stop then start (requesting a dhcp allocation). However, pulling the cable often accomplishes this with far less typing. D:) ping 8.8.8.8 from the unraid box, if you can do this, you've got a good network connection, and can communicate with the outside world (aka go through router). If at this point you can't reach the ip (from ifconfig) of the unraid box on your desktop, something is blocking the communications from your desktop to unraid. at this point I'd blame your Antivirus/firewall or stock windows firewall. Something is blocking those communications. *** Also, to see the variety in network failures on the ping makes me think - unreachable & timed out.. that's unusual... it's possible (unlikely but possible) that you've got bad cabling or switches in between. Exactly what is your network layout? Do you have a single router with cables spidering out? Or do you have a switch in the middle? *** You know, considering this is your home network, bring everything down. Bring router up, then switch, then unraid, then everything else. I've had to do this once or twice when my d-link switch had corrupted switching tables. A pain, but it's only happened twice (both times I'm sure due to my 30.00 d-link gigabit switch)
December 18, 201213 yr According to ifconfig, your IP address is 169.254.202.185 Yet, you are set to use DHCP=yes. That is not a "real" private IP address. (AFAIK) It is a dummy one assigned when no DHCP server can be found. Your router's DHCP server is not handing out a private address. Is it enabled? Do you have a DHCP server on your LAN? Joe L.
December 18, 201213 yr Crap, I can't believe I missed that. According to ifconfig, your IP address is 169.254.202.185 Yet, you are set to use DHCP=yes. That is not a "real" private IP address. (AFAIK) It is a dummy one assigned when no DHCP server can be found. Your router's DHCP server is not handing out a private address. Is it enabled? Do you have a DHCP server on your LAN? Joe L.
December 18, 201213 yr If youv'e got a home router, unplug it for 10/15 seconds, plug it back in, wait a couple/three minutes, then unplug/reinsert network cable on your unraid box. Crap, I can't believe I missed that. According to ifconfig, your IP address is 169.254.202.185 Yet, you are set to use DHCP=yes. That is not a "real" private IP address. (AFAIK) It is a dummy one assigned when no DHCP server can be found. Your router's DHCP server is not handing out a private address. Is it enabled? Do you have a DHCP server on your LAN? Joe L.
December 18, 201213 yr Author Thank You all - especially dimaestero and Joe L. for all the help. I just rebooted everything (tower, router and desktop) and now everything is working as it should. No idea what changed or what caused this issue, hopefully this fix would work if this issue ever occurs again. Sorry for wasting your time, wasn't my intention. Sometimes the simplest of fixes are the last ones your try .
December 18, 201213 yr Crap, I can't believe I missed that. According to ifconfig, your IP address is 169.254.202.185 Yet, you are set to use DHCP=yes. That is not a "real" private IP address. (AFAIK) It is a dummy one assigned when no DHCP server can be found. Your router's DHCP server is not handing out a private address. Is it enabled? Do you have a DHCP server on your LAN? Joe L. If it makes you feel any better, I was impressed with your networking knowledge.
Archived
This topic is now archived and is closed to further replies.