July 6, 200916 yr Hi, I am testing out the free version of Unraid (4.2) before buying the full version. I am having a problem with accessing my server (telnet, web or IP). Indeed, I am unable to access my Unraid server whenever it is plugged in my Gigabit switch. My network looks like this: internet -> wrt54gl running tomato DHCP (100 mbit) -> Trendnet TEG-S80G 8 port unmanaged gigabit switch -> Clients and server I can access the server from a client ONLY when it is directly plugged in the linksys router. Whenever I connect the server to the switch, I lose connectivity. However, I have built this server to stream multiple HD movies and music. Hence, I need gigabit speeds. I have tried setting a static IP to the server but it does not help. I know the switch works so I dont think it is the problem. Please help me! Thanks, Guigz ---------------edit------------ Further information; router ip address: 192.168.1.1 Client address: 192.168.1.75 Server ip : 192.168.1.76
July 6, 200916 yr Hi, I am testing out the free version of Unraid (4.2) before buying the full version. I am having a problem with accessing my server (telnet, web or IP). Indeed, I am unable to access my Unraid server whenever it is plugged in my Gigabit switch. My network looks like this: internet -> wrt54gl running tomato DHCP (100 mbit) -> Trendnet TEG-S80G 8 port unmanaged gigabit switch -> Clients and server I can access the server from a client ONLY when it is directly plugged in the linksys router. Whenever I connect the server to the switch, I lose connectivity. However, I have built this server to stream multiple HD movies and music. Hence, I need gigabit speeds. I have tried setting a static IP to the server but it does not help. I know the switch works so I dont think it is the problem. Please help me! Thanks, Guigz ---------------edit------------ Further information; router ip address: 192.168.1.1 Client address: 192.168.1.75 Server ip : 192.168.1.76 First, version 4.2 of unRAID is 24 versions old. See here: http://lime-technology.com/wiki/index.php/Release_Notes Please use 4.5beta6. You will be much better off. Do not worry about the beta6 label. It is stable. Second, post a syslog. (instructions under troubleshooting in the wiki) At the least, post the output of the following commands (after you log in via telnet to the unRAID server): ifconfig eth0 ethtool eth0 ping -c 5 google.com Next, what security do you have enabled in the router? how do you have the networking settings configured on the unRAID server? What do you have for Netmask? Gateway? DNS Server? Workgroup Name? When you say you lose connectivity, can you ping by IP address? or does it just not respond by the name "tower"? Have you tried pinging at all? Or is it just not showing up in the network neighborhood? In order to help you, we need you to supply the clues... Joe L.
July 6, 200916 yr Author First, version 4.2 of unRAID is 24 versions old. See here: http://lime-technology.com/wiki/index.php/Release_Notes Please use 4.5beta6. You will be much better off. Do not worry about the beta6 label. It is stable. Can you explain to me how to upgrade to the new version without losing all my data? Second, post a syslog. (instructions under troubleshooting in the wiki) Please find the syslog at the following url. Keep in mind that the log was created while the server was hooked to my router, not the switch. http://www.mediafire.com/download.php?0trdhnodfzd At the least, post the output of the following commands (after you log in via telnet to the unRAID server): ifconfig eth0 ethtool eth0 ping -c 5 google.com eth0 Link encap:Ethernet HWaddr 00:19:66:28:f6:13 inet addr:192.168.1.76 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:593 errors:0 dropped:0 overruns:0 frame:1 TX packets:632 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:70060 (68.4 KiB) TX bytes:228386 (223.0 KiB) Interrupt:23 Base address:0x6c00 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000001 (1) Link detected: yes --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4049ms rtt min/avg/max/mdev = 49.093/49.604/50.308/0.417 ms root@Tower:~# Next, what security do you have enabled in the router? Do you mean DMZ and access restriction? If so, none that I know of. how do you have the networking settings configured on the unRAID server? I have tried both assigning a static ip address and having the router do it. Right now it is at "Obtain ip address automatically" What do you have for Netmask? Gateway? DNS Server? Workgroup Name?255.255.255.0 , 192.168.1.1 and AMI_DES_BONBONS respectively When you say you lose connectivity, can you ping by IP address? or does it just not respond by the name "tower"? Have you tried pinging at all? Or is it just not showing up in the network neighborhood? I mean that I am unable to contact the server. I have tried using "tower" in a browser, telneting the IP seeing in network neighborhood. I have tried pinging and it does not work I really appreciate the help.
July 7, 200916 yr eth0 Link encap:Ethernet HWaddr 00:19:66:28:f6:13 inet addr:192.168.1.76 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:593 errors:0 dropped:0 overruns:0 frame:1 TX packets:632 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:70060 (68.4 KiB) TX bytes:228386 (223.0 KiB) Interrupt:23 Base address:0x6c00 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000001 (1) Link detected: yes --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4049ms rtt min/avg/max/mdev = 49.093/49.604/50.308/0.417 ms root@Tower:~# Please perform those same commands while the unRAID server is connected to the switch? You'll need to log in to the console of the unRAID server of course, since you can't telnet to it in that configuration. To save the output to your flash drive, use the following syntax: [pre]ifconfig eth0 >/boot/diag.txt ethtool eth0 >>/boot/diag.txt ping -c 5 google.com >>/boot/diag.txt [/pre](Note two >'s on the second and third command) You can then reconnect it to your router and retrieve the contents of /boot/diag.txt via telnet or by mapping a drive to \\tower\flash, and post the results here so we can see what the server sees when it's unreachable.
July 7, 200916 yr Author I have no easy way of logging in to the console ( I assume that means plugging a screen in the server (it is running headless) and a mouse/keyboard and inputing the commands). Is there some way I can put that in my go script and have it done automatically (perhaps I should also include a command to tell the computer to wait 30 secs after booting to perform the tasks). Thanks,
July 7, 200916 yr I have no easy way of logging in to the console ( I assume that means plugging a screen in the server (it is running headless) and a mouse/keyboard and inputing the commands). Is there some way I can put that in my go script and have it done automatically (perhaps I should also include a command to tell the computer to wait 30 secs after booting to perform the tasks). Thanks, You should be able to add this to your go script to get the commands to run after a certain period of time: echo "ifconfig eth0 >/boot/diag1.txt" | at now + 10 minutes echo "ethtool eth0 >>/boot/diag2.txt" | at now + 12 minutes echo "ping -c 5 google.com >>/boot/diag3.txt" | at now + 14 minutes Then after the computer has booted up just wait about fifteen minutes and go shut it down. From there you can take the flash drive out and get the files.
July 7, 200916 yr I have no easy way of logging in to the console ( I assume that means plugging a screen in the server (it is running headless) and a mouse/keyboard and inputing the commands). Is there some way I can put that in my go script and have it done automatically (perhaps I should also include a command to tell the computer to wait 30 secs after booting to perform the tasks). Thanks, I highly recommend that you have a way to hook up a keyboard and monitor to your unRAID server. There will be times (and this seems a good example) when having physical access to the console will be extremely convenient or outright necessary. When everything is running fine, pull the video card. But have it handy just in case.
July 7, 200916 yr I see no reason why you shouldn't be able to put them in your go script. If you change the single > to double >> in the first command, then all three will append to diag.txt so you wouldn't even need to worry about retrieving the file before booting it a second time to regain connectivity. But that may not even be necessary. From your description, the setup with the most direct path - with everything plugged directly into the gigabit switch - is the one that doesn't work, which suggests to me that this is a hardware issue rather than a networking problem. First things first - give unRAID a static IP address. Then at least it'll always have an address whether the router is available or not, and best practice dictates that servers of any sort should always be static anyway. Next, are you getting link LED's at both the switch and the unRAID NIC when you connect the two? Are you using a Cat5e or Cat6 cable? Gigabit ethernet requires all four pairs in the cable, whereas 10/100 ethernet only uses two pairs - a cable that may work just fine for a 10/100 connection may not work at all for gigabit. Have you tried different ports on the switch? Have you connected another - known good - gigabit device to the switch using the same cable and port that fails for the unRAID server? Does it connect? At gigabit speed? Please don't take offense if any of these questions seem simplistic, it's just that having worked in support for years, I know that it's often the simplest things that get overlooked.
July 7, 200916 yr Oh, and one other thing... are you sure you're running unRAID 4.2, not 4.4.2? 4.4.2 is the latest "production" release, so unless you got the code from a third-party site, it's unlikely that you would have downloaded 4.2.
July 7, 200916 yr Author Whoops, indeed, I am running version 4.4.2, NOT 4.2... I will post the results of these commands later when I get back from work. Couple of clarifications. I know that the cable is good, it is a CAT6 cable and I tested it with another computer. I know that the switch works at gigabit speed AND at 100 mbps speeds (tested with another computer). So in theory, even though my onboard NIC is NOT gigabit (will replace it with a gigabit card later on), it should connect at 100 mbps. I did try different ports on the switch (confirmed to be working with another computer). My switch's LEDs flash whenever I plug the server into it. The pattern indicates that it is connecting at 100 mbps. Your help is really appreciated. Thanks
July 7, 200916 yr Author Here are the results of the 3 commands. eth0 Link encap:Ethernet HWaddr 00:19:66:28:f6:13 inet addr:192.168.1.76 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:3770 (3.6 KiB) Interrupt:23 Base address:0x6c00 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000001 (1) Link detected: yes PING google.com (74.125.67.100) 56(84) bytes of data. 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=1 ttl=54 time=49.9 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=2 ttl=54 time=49.3 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=3 ttl=54 time=49.7 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=4 ttl=54 time=49.9 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=5 ttl=54 time=48.5 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4034ms rtt min/avg/max/mdev = 48.535/49.499/49.918/0.592 ms
July 7, 200916 yr OK, just double-checking... did you change that first > to >> so it appended to the output file instead of overwriting it? If not, and you subsequently rebooted with it connected to your router so you could retrieve the file, then it will have overwritten the diags with good data when it rebooted. The reason I ask is that that output shows a NIC in perfect health with full connectivity to its DNS and the outside world. Can you add a [pre]ping 192.168.1.75 >> /boot/diag.txt[/pre] command, to demonstrate connectivity on the LAN segment? If it can ping out (and receive the reply packets) then the routing, etc, is fine and I'm at a loss. My only other thought was that the switch is somehow failing to refresh its arp cache to reflect the fact that your unRAID's MAC is now on a different port, but if it can ping out then that blows that idea out of the water.
July 8, 200916 yr Author Ok I will try that too. I did not need to reboot to retrieve the data. What I did was to boot it while it is plugged on the switch, let it do its thing and, after its done, plud it back in the router to access it via the lan. -------------edit--------------- Here it is: PING 192.168.1.75 (192.168.1.75) 56(84) bytes of data. From 192.168.1.76 icmp_seq=1 Destination Host Unreachable -----same thing is repeated 897 times---------------------------- From 192.168.1.76 icmp_seq=898 Destination Host Unreachable From 192.168.1.76 icmp_seq=899 Destination Host Unreachable From 192.168.1.76 icmp_seq=900 Destination Host Unreachable From 192.168.1.76 icmp_seq=901 Destination Host Unreachable From 192.168.1.76 icmp_seq=902 Destination Host Unreachable From 192.168.1.76 icmp_seq=903 Destination Host Unreachable 64 bytes from 192.168.1.75: icmp_seq=904 ttl=128 time=2010 ms 64 bytes from 192.168.1.75: icmp_seq=905 ttl=128 time=1008 ms 64 bytes from 192.168.1.75: icmp_seq=906 ttl=128 time=8.45 ms 64 bytes from 192.168.1.75: icmp_seq=907 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=908 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=909 ttl=128 time=0.183 ms 64 bytes from 192.168.1.75: icmp_seq=910 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=911 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=912 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=913 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=914 ttl=128 time=0.181 ms 64 bytes from 192.168.1.75: icmp_seq=915 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=916 ttl=128 time=0.183 ms 64 bytes from 192.168.1.75: icmp_seq=917 ttl=128 time=0.184 ms 64 bytes from 192.168.1.75: icmp_seq=918 ttl=128 time=0.188 ms 64 bytes from 192.168.1.75: icmp_seq=919 ttl=128 time=0.177 ms 64 bytes from 192.168.1.75: icmp_seq=920 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=921 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=922 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=923 ttl=128 time=0.198 ms 64 bytes from 192.168.1.75: icmp_seq=924 ttl=128 time=0.182 ms 64 bytes from 192.168.1.75: icmp_seq=925 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=926 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=927 ttl=128 time=0.195 ms 64 bytes from 192.168.1.75: icmp_seq=928 ttl=128 time=0.187 ms 64 bytes from 192.168.1.75: icmp_seq=929 ttl=128 time=0.303 ms 64 bytes from 192.168.1.75: icmp_seq=930 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=931 ttl=128 time=0.188 ms 64 bytes from 192.168.1.75: icmp_seq=932 ttl=128 time=0.188 ms 64 bytes from 192.168.1.75: icmp_seq=933 ttl=128 time=0.194 ms 64 bytes from 192.168.1.75: icmp_seq=934 ttl=128 time=0.249 ms 64 bytes from 192.168.1.75: icmp_seq=935 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=936 ttl=128 time=0.193 ms 64 bytes from 192.168.1.75: icmp_seq=937 ttl=128 time=0.179 ms 64 bytes from 192.168.1.75: icmp_seq=938 ttl=128 time=0.190 ms 64 bytes from 192.168.1.75: icmp_seq=939 ttl=128 time=0.192 ms 64 bytes from 192.168.1.75: icmp_seq=940 ttl=128 time=0.181 ms 64 bytes from 192.168.1.75: icmp_seq=941 ttl=128 time=0.190 ms 64 bytes from 192.168.1.75: icmp_seq=942 ttl=128 time=0.184 ms 64 bytes from 192.168.1.75: icmp_seq=943 ttl=128 time=0.191 ms 64 bytes from 192.168.1.75: icmp_seq=944 ttl=128 time=0.192 ms 64 bytes from 192.168.1.75: icmp_seq=945 ttl=128 time=0.212 ms 64 bytes from 192.168.1.75: icmp_seq=946 ttl=128 time=1.38 ms 64 bytes from 192.168.1.75: icmp_seq=947 ttl=128 time=0.175 ms 64 bytes from 192.168.1.75: icmp_seq=948 ttl=128 time=0.172 ms 64 bytes from 192.168.1.75: icmp_seq=949 ttl=128 time=0.185 ms I dont know if I am reading this right, but it seems that after many tries, it eventually is able to ping the computer.....
July 8, 200916 yr Assuming that the change from unreachable to replying did not coincide with when you unplugged it from the switch and plugged it into the router, then I suspect that your switch is simply not updating its MAC address table in a timely manner, and is continuing to send packets destined for your unRAID's NIC out the port which is connected to the router instead of out whichever port the unRAID is now connected to, until such time as its arp cache finally expires. Have you tried power-cycling the switch after plugging the unRAID directly into it? Once you can ping the client from the server, you should be able to access (and ping) the server from the client.
July 8, 200916 yr Ok I will try that too. I did not need to reboot to retrieve the data. What I did was to boot it while it is plugged on the switch, let it do its thing and, after its done, plud it back in the router to access it via the lan. -------------edit--------------- Here it is: PING 192.168.1.75 (192.168.1.75) 56(84) bytes of data. From 192.168.1.76 icmp_seq=1 Destination Host Unreachable -----same thing is repeated 897 times---------------------------- From 192.168.1.76 icmp_seq=898 Destination Host Unreachable From 192.168.1.76 icmp_seq=899 Destination Host Unreachable From 192.168.1.76 icmp_seq=900 Destination Host Unreachable From 192.168.1.76 icmp_seq=901 Destination Host Unreachable From 192.168.1.76 icmp_seq=902 Destination Host Unreachable From 192.168.1.76 icmp_seq=903 Destination Host Unreachable 64 bytes from 192.168.1.75: icmp_seq=904 ttl=128 time=2010 ms 64 bytes from 192.168.1.75: icmp_seq=905 ttl=128 time=1008 ms 64 bytes from 192.168.1.75: icmp_seq=906 ttl=128 time=8.45 ms 64 bytes from 192.168.1.75: icmp_seq=907 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=908 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=909 ttl=128 time=0.183 ms 64 bytes from 192.168.1.75: icmp_seq=910 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=911 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=912 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=913 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=914 ttl=128 time=0.181 ms 64 bytes from 192.168.1.75: icmp_seq=915 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=916 ttl=128 time=0.183 ms 64 bytes from 192.168.1.75: icmp_seq=917 ttl=128 time=0.184 ms 64 bytes from 192.168.1.75: icmp_seq=918 ttl=128 time=0.188 ms 64 bytes from 192.168.1.75: icmp_seq=919 ttl=128 time=0.177 ms 64 bytes from 192.168.1.75: icmp_seq=920 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=921 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=922 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=923 ttl=128 time=0.198 ms 64 bytes from 192.168.1.75: icmp_seq=924 ttl=128 time=0.182 ms 64 bytes from 192.168.1.75: icmp_seq=925 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=926 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=927 ttl=128 time=0.195 ms 64 bytes from 192.168.1.75: icmp_seq=928 ttl=128 time=0.187 ms 64 bytes from 192.168.1.75: icmp_seq=929 ttl=128 time=0.303 ms 64 bytes from 192.168.1.75: icmp_seq=930 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=931 ttl=128 time=0.188 ms 64 bytes from 192.168.1.75: icmp_seq=932 ttl=128 time=0.188 ms 64 bytes from 192.168.1.75: icmp_seq=933 ttl=128 time=0.194 ms 64 bytes from 192.168.1.75: icmp_seq=934 ttl=128 time=0.249 ms 64 bytes from 192.168.1.75: icmp_seq=935 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=936 ttl=128 time=0.193 ms 64 bytes from 192.168.1.75: icmp_seq=937 ttl=128 time=0.179 ms 64 bytes from 192.168.1.75: icmp_seq=938 ttl=128 time=0.190 ms 64 bytes from 192.168.1.75: icmp_seq=939 ttl=128 time=0.192 ms 64 bytes from 192.168.1.75: icmp_seq=940 ttl=128 time=0.181 ms 64 bytes from 192.168.1.75: icmp_seq=941 ttl=128 time=0.190 ms 64 bytes from 192.168.1.75: icmp_seq=942 ttl=128 time=0.184 ms 64 bytes from 192.168.1.75: icmp_seq=943 ttl=128 time=0.191 ms 64 bytes from 192.168.1.75: icmp_seq=944 ttl=128 time=0.192 ms 64 bytes from 192.168.1.75: icmp_seq=945 ttl=128 time=0.212 ms 64 bytes from 192.168.1.75: icmp_seq=946 ttl=128 time=1.38 ms 64 bytes from 192.168.1.75: icmp_seq=947 ttl=128 time=0.175 ms 64 bytes from 192.168.1.75: icmp_seq=948 ttl=128 time=0.172 ms 64 bytes from 192.168.1.75: icmp_seq=949 ttl=128 time=0.185 ms I dont know if I am reading this right, but it seems that after many tries, it eventually is able to ping the computer..... You are reading it wrong. The first 5 pings indicate it could NOT contact google.com... you do not have a nameserver defined. Or, if you do, it does not know how to route the connection. The remainder is because you did not include a "-c count" option to the ping command... It is able to ping your PC by IP address.
July 8, 200916 yr Author Joe : Are you referring to an earlier message? Because I am trying to ping my other computer on the LAN, not goggle.com. Can you tell me how to set up those things you are suggesting? How does having a nameserver help? What will a -c count do? Jetkins: I will try power cycling to see if that helps. Is there any way I can accelerate the speed at which the cache is updated? thank you,
July 8, 200916 yr Normally you set the name server (DNS Server) and network Gateway on the "Settings" page in the unRAID interface. Those settings for the network are stored in config/network.cfg Post the contents of your config/network.cfg file Joe L.
July 8, 200916 yr PING 192.168.1.75 (192.168.1.75) 56(84) bytes of data. From 192.168.1.76 icmp_seq=1 Destination Host Unreachable -----same thing is repeated 897 times---------------------------- From 192.168.1.76 icmp_seq=898 Destination Host Unreachable From 192.168.1.76 icmp_seq=899 Destination Host Unreachable From 192.168.1.76 icmp_seq=900 Destination Host Unreachable From 192.168.1.76 icmp_seq=901 Destination Host Unreachable From 192.168.1.76 icmp_seq=902 Destination Host Unreachable From 192.168.1.76 icmp_seq=903 Destination Host Unreachable 64 bytes from 192.168.1.75: icmp_seq=904 ttl=128 time=2010 ms 64 bytes from 192.168.1.75: icmp_seq=905 ttl=128 time=1008 ms 64 bytes from 192.168.1.75: icmp_seq=906 ttl=128 time=8.45 ms 64 bytes from 192.168.1.75: icmp_seq=907 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=908 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=909 ttl=128 time=0.183 ms 64 bytes from 192.168.1.75: icmp_seq=910 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=911 ttl=128 time=0.186 ms 64 bytes from 192.168.1.75: icmp_seq=912 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=913 ttl=128 time=0.189 ms 64 bytes from 192.168.1.75: icmp_seq=914 ttl=128 time=0.181 ms 64 bytes from 192.168.1.75: icmp_seq=915 ttl=128 time=0.185 ms 64 bytes from 192.168.1.75: icmp_seq=916 ttl=128 time=0.183 ms 64 bytes from 192.168.1.75: icmp_seq=917 ttl=128 time=0.184 ms 64 bytes from 192.168.1.75: icmp_seq=918 ttl=128 time=0.188 ms 64 bytes from 192.168.1.75: icmp_seq=919 ttl=128 time=0.177 ms [snip] I dont know if I am reading this right, but it seems that after many tries, it eventually is able to ping the computer..... You are reading it wrong. The first 5 pings indicate it could NOT contact google.com... you do not have a nameserver defined. Or, if you do, it does not know how to route the connection. With respect, Joe, I think you're reading it wrong. That output was the result of pinging the client machine on the same LAN segment, by IP address. No DNS was involved, and the fact that it was unable to connect for the first 900 attempts (approximately 15 minutes) and then suddenly started getting responses, suggests suggests a switch or intermittent hardware problem to me. However guigz, Joe is correct that if you are going to set the IP address manually, then you should also set your DNS manually because some other functions do use DNS. I expect your router is acting as a DNS forwarder for your LAN, so your DNS address would be 192.168.1.1. And as for how to force your switch to refresh its arp cache more quickly, I have no better suggestion than to power cycle it. A well-designed switch should detect such a change and update its tables pretty much immediately; if yours is indeed not doing that then that's something you'd need to take up with the manufacturer, or just live with it. If it was a managed switch you may have been able to update its firmware, but I don't believe that's an option for an unmanaged switch such as yours.
July 8, 200916 yr Author here is my Network.cfg: # Generated settings: USE_DHCP=no IPADDR=192.168.1.76 NETMASK=255.255.255.0 GATEWAY=192.168.1.1 HWADDR=00:19:66:28:F6:13 DHCP_KEEPRESOLV=no DNS_SERVER1=192.168.1.1 DNS_SERVER2= DNS_SERVER3= Is there anything missing? Also, I tried powercycling the switch and the router. It does not seem to do anything....
July 8, 200916 yr That looks fine. OK, next thought: perhaps auto negotiation is failing - wouldn't be the first time that two supposedly-compatible devices have failed to "play nice" with each other. Try adding the following go your go script: [pre]ethtool -s eth0 speed 100 duplex full autoneg off[/pre]However, I'll admit that at this point I'm really clutching at straws. My sole remaining suggestion if disabling autoneg doesn't work would be to try another NIC, because based on the information you've provided I can see no logical reason why it doesn't work. The output of the three commands that you posted yesterday showed that it had connectivity, had access to your DNS, and could ping out to google.com. If all of those were true and it still could not ping or be pinged by the local subnet, I'm totally mystified.
July 8, 200916 yr Author I have replaced the NIC with an Intel Pro 1000/GT card. It seems that the problem was the onboard NIC because now, the connectivity is there. However, I am unable to get gigabit speeds.... Any clues? here are my reports: eth0 Link encap:Ethernet HWaddr 00:19:66:28:f6:13 inet addr:192.168.1.76 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2408 errors:0 dropped:0 overruns:0 frame:0 TX packets:2326 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:327161 (319.4 KiB) TX bytes:335237 (327.3 KiB) Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes PING google.com (74.125.67.100) 56(84) bytes of data. 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=1 ttl=55 time=48.9 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=2 ttl=55 time=49.3 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=3 ttl=55 time=48.9 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=4 ttl=55 time=49.4 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=5 ttl=55 time=49.6 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4044ms rtt min/avg/max/mdev = 48.920/49.256/49.609/0.386 ms
July 9, 200916 yr I have replaced the NIC with an Intel Pro 1000/GT card. It seems that the problem was the onboard NIC because now, the connectivity is there. However, I am unable to get gigabit speeds.... Any clues? The two devices - your NIC and the switch - will (should) negotiate the fastest reliable connection possible given each of their capabilities. If 100/Full is the best they can agree upon, that suggests either an incompatibility or a hardware (cable?) problem. Simplest things first; try another cable. You could also try forcing gigabit with [pre]ethtool -s eth0 speed 1000 duplex full autoneg off[/pre]but if there is a genuine reason why they only negotiated 100/Full, you may see a bunch of network errors such as dropped packets, etc, if you get a connection at all. Are your other machines gigabit, and do they get 1000/Full connections? I'll admit that my tendency at this point is to suspect that there may be a reason why the Trendnet switch is so affordable.
July 9, 200916 yr Author Hi Guys! I got feed up with my switch and replaced it with a D-link 8 port Gigabit one. Now I am getting full connectivity at 1000 mbps! Yay! Thanks for the help, it was really appreciated. Do you guys think that upgrading to the latest beta version would be better? If so, is there a tutorial on how to upgrade the software? Thanks, Guigz
July 9, 200916 yr FAQ: How do I upgrade the unRAID software? Do you guys think that upgrading to the latest beta version would be better? If so, is there a tutorial on how to upgrade the software? Almost all users that have upgraded to v4.5-beta6 have been happy with it.
July 9, 200916 yr I got feed up with my switch and replaced it with a D-link 8 port Gigabit one. Now I am getting full connectivity at 1000 mbps! I've had a nagging suspicion all along that the switch was at the root of all this, since there was no logical reason for the problems you were encountering. Glad you got it resolved. Do you guys think that upgrading to the latest beta version would be better? If so, is there a tutorial on how to upgrade the software? Although 4.5b6 is officially a beta, it appears that it's very stable and the known problems (such as not actually supporting 20 drives) are not show-stoppers for most people. I've been using it for a while now with no problems; as long as you don't get nervous running betas, I'd say "go for it." Upgrade instructions are included in the first post of the announcement thread - basically you just replace two files. Thanks You're welcome; glad to see another happy user.
Archived
This topic is now archived and is closed to further replies.