May 22, 201016 yr I'm brand new to unRAID, so be gentle. I just installed the latest release on a USB key and booted to it fine. I got the login prompt and logged in as root, but I'm not sure where to go from here. I tried accessing the web-based management utility with "//tower" and by what should be the server's ip, but neither works. ifconfig returns nothing. Any ideas? Or can anyone point me in the right direction? edit: My motherboard is an MSI K9N Platinum.
May 22, 201016 yr I'm brand new to unRAID, so be gentle. I just installed the latest release on a USB key and booted to it fine. I got the login prompt and logged in as root, but I'm not sure where to go from here. I tried accessing the web-based management utility with "//tower" and by what should be the server's ip, but neither works. ifconfig returns nothing. Any ideas? Or can anyone point me in the right direction? edit: My motherboard is an MSI K9N Platinum. Best bet is to capture and post a copy of your syslog. Instructions are in the wiki here: http://lime-technology.com/wiki/index.php?title=Troubleshooting#How_to_get_help What did you get when you typed? ifconfig eth0 What do you get when you type: ethtool eth0 What do you see when you type ls -l /boot What do you see when you type ls -l /dev/disk/by-label
May 24, 201016 yr I got the same problem with 4.5.4. It seems to be a network problem and I don't know how to resolve it. The syslog is attached. I appreciate your helps. Thanks. syslog.txt
May 24, 201016 yr I got the same problem with 4.5.4. It seems to be a network problem and I don't know how to resolve it. The syslog is attached. I appreciate your helps. Thanks. I posted the solution to your issue in the other thread. 4.5.4 now supports the on-board ethernet controller on your motherboard. You apparently did not disable it in your BIOS, so it is being assigned as eth0, and it is the one used in 4.5.4. The additional Intel ethernet controller is now eth1. I'm guessing the on-board port was not supported in the older unRAID release. Very likely everything will work just fine if you either move the LAN cable to the on-board port and not use the additional Intel LAN controller at all, or, disable the on-board port in your BIOS.
May 24, 201016 yr Joe, it works perfectly now. I disabled the on-board LAN in the BIOS. Thank you. You are simply amazing.
May 24, 201016 yr Author Best bet is to capture and post a copy of your syslog. Instructions are in the wiki here: http://lime-technology.com/wiki/index.php?title=Troubleshooting#How_to_get_help What did you get when you typed? ifconfig eth0 eth0 Link encap: Ethernet HWaddr 00:19:db:f3:23:e8 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0B) TX bytes:0 (0.0B) Interrupt: 20 Base address:0xc000 What do you get when you type: ethtool eth0 Settings for eth0: Supported ports: [ MII ] 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: MII PHYAD: 1 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes What do you see when you type ls -l /boot total 48 -rw-r--r-- 1 root root 46164 May 24 17:30 syslog What do you see when you type ls -l /dev/disk/by-label total 0 lrwxrwxrwx 1 root root 10 May 24 17:29 DATA -> ../../hda2 lrwxrwxrwx 1 root root 10 May 24 17:29 SYS -> ../../hda1 I haven't been successful in getting a syslog yet, but I'm still trying. When I use the "poweroff" command, my server doesn't actually poweroff. It hangs at "INIT: no more processes left in this runlevel" When I attempt to ping something, I get "connect: Network is unreachable." The server doesn't show up in my DHCP list on my router either. My motherboard has dual gigabit ports, but I've disabled one of them (and yes, I'm sure I have it plugged in to the one that's turned on).
May 24, 201016 yr Best bet is to capture and post a copy of your syslog. Instructions are in the wiki here: http://lime-technology.com/wiki/index.php?title=Troubleshooting#How_to_get_help What did you get when you typed? ifconfig eth0 eth0 Link encap: Ethernet HWaddr 00:19:db:f3:23:e8 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0B) TX bytes:0 (0.0B) Interrupt: 20 Base address:0xc000 What do you get when you type: ethtool eth0 Settings for eth0: Supported ports: [ MII ] 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: MII PHYAD: 1 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes What do you see when you type ls -l /boot total 48 -rw-r--r-- 1 root root 46164 May 24 17:30 syslog What do you see when you type ls -l /dev/disk/by-label total 0 lrwxrwxrwx 1 root root 10 May 24 17:29 DATA -> ../../hda2 lrwxrwxrwx 1 root root 10 May 24 17:29 SYS -> ../../hda1 I haven't been successful in getting a syslog yet, but I'm still trying. When I use the "poweroff" command, my server doesn't actually poweroff. It hangs at "INIT: no more processes left in this runlevel" When I attempt to ping something, I get "connect: Network is unreachable." The server doesn't show up in my DHCP list on my router either. My motherboard has dual gigabit ports, but I've disabled one of them (and yes, I'm sure I have it plugged in to the one that's turned on). Your flash drive was not mounted at /boot It was not mounted at /boot because you did not set the volume label to UNRAID. If you had, you would have seen it in when you typed ls -l /dev/disk/by-label. Because the flash rive was not mounted, the network configuration could not be set up and you did not get a network connection. Put the flash drive in your PC, set the volume label to UNRAID (6 characters, all upper-case) and them move it back to the unRAID server and reboot. It should all work then. You do not need to re-format the drive, or re-load it, or run syslinux on it again, you just need to set the volume label to UNRAID Joe L.
May 24, 201016 yr Author Well, don't I feel stupid. Sorry for the bother; your help is much appreciated.
Archived
This topic is now archived and is closed to further replies.