June 30, 201115 yr Hi there, Got a new build together /CPU/MOBO/RAM/ with previous disks (no changes in array) and USB flash drive. Before I built it - I tested this build to make sure it was compatible (via the UNRAID FAQ tutorial) and it worked (I was able to resolve to the tower via browser) This build is using the on-board NIC. This USB currently has unRAID Server Release 5.0-beta6a and was running nicely before the new build. What its doing: It receives an IP from the router. It responds to a ping and I can telnet to it. It looks like its trying to run a parity check (as all the lights on my icydock trays are orange; previously did this during parity checks) What its not doing. It will not resolve via web browser or allow me to access SMB shares. I ran the following commands (from another post) but not sure if the results are in the syslog or not mount ifconfig eth0 ethtool eth0 ls -l /boot ls -l /dev/disk/by-id I have also attached the syslog - any help would be appreciated. I am afraid to keep it running through a parity check overnight in case the array is not configured properly. Could it affect the files currently on the array if I leave it up and running? Thanks Mark syslog.zip
June 30, 201115 yr Author I tried using a static IP on my network and still no go. I also found some commands from a previous thread for troubleshooting and they seem to come back fine - results below Tower2 login: root Linux 2.6.36.2-unRAID. root@Tower2:~# net lookup google.com 74.125.224.52 root@Tower2:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 1c:6f:65:71:fd:55 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:204 errors:0 dropped:0 overruns:0 frame:0 TX packets:122 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16051 (15.6 KiB) TX bytes:7069 (6.9 KiB) Interrupt:40 Base address:0x2000 root@Tower2:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes root@Tower2:~#
June 30, 201115 yr Have you tried just browsing to the system's IP address? (http://192.168.1.52/) Not sure if that's what you meant by "static".
June 30, 201115 yr Author Yup - I tried that. I had it previously set (old build) as static in the network.cfg, so part of my trouble shooting was to get it back to DHCP=yes and try it that way Same results both DHCP and Static = Not resolving via IP or name..
June 30, 201115 yr Author I can ping both the router (x.x.1.1) and my room PC (x.x.1.2) - but the latency is abysmal. I'm not sure if thats normal? Samples to each below (edited ping responses to 5 lines each) Linux 2.6.36.2-unRAID. root@Tower2:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.583 ms 64 bytes from 192.168.1.1: icmp_req=10 ttl=64 time=0.490 ms 64 bytes from 192.168.1.1: icmp_req=11 ttl=64 time=0.519 ms 64 bytes from 192.168.1.1: icmp_req=12 ttl=64 time=0.547 ms 64 bytes from 192.168.1.1: icmp_req=13 ttl=64 time=0.546 ms ^C --- 192.168.1.1 ping statistics --- 15 packets transmitted, 15 received, 0% packet loss, time 14099ms rtt min/avg/max/mdev = 0.490/0.541/0.583/0.029 ms root@Tower2:~# ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=128 time=0.704 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=128 time=0.670 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=128 time=0.674 ms 64 bytes from 192.168.1.2: icmp_req=4 ttl=128 time=0.427 ms 64 bytes from 192.168.1.2: icmp_req=5 ttl=128 time=0.408 ms ^C --- 192.168.1.2 ping statistics --- 12 packets transmitted, 12 received, 0% packet loss, time 11006ms rtt min/avg/max/mdev = 0.312/0.603/0.704/0.133 ms root@Tower2:~# PS - I was thinking of copying a fresh GO Script to my boot flash drive - Or.. or a fresh install of Unraid Basic on a different flash drive - will either of these affect my configuration at all (assuming I dont start the array)? Thanks Mark
June 30, 201115 yr Author OK thats weird.... I started it up this morning (after a full night of being off)- just to try Flibblebot's suggestion - and its working... Maybe it just needed a nap? Im not going to [sOLVE] until I can regularly boot it up w/o incident. Strange.
June 30, 201115 yr Author Im not sure. Once it was up and running - I turned it off and went to work... I'll check back in later.
July 1, 201115 yr Author OK - I think this is Solved. It may have had to do with a hard shutdown when I brought it down the first time... I recall that being a problem sometimes (corrupted something or other) I've stopped (console) and started 3 or 4 times now and it seems to be ok. Thanks All!
Archived
This topic is now archived and is closed to further replies.