July 18, 200817 yr Hi chaps, Just found this very useful OS and am having a few networking issues. I have a HP Proliant M115 server, and have just stuffed 3 HDs in there. I've followed the install instructions and can boot beautifully from the usb and get a login to 'tower'. My router/adsl modem has assigned an ip address (I believe, my German is poor at best!) as the MAC addresses match from the router config and BIOS of the server. However, I'll be damned if I can actually see the server. I can't ping anything, the network is 'unavailable'. Now I think the motherboard and NIC are supported otherwise the router wouldn't have assigned an IP yeah? The m/b is an nVidia MCP55s (I believe!). I haven't enabled any of the RAID functions on the m/b. Should I, or will unRaid sort that out? I'm guessing this is not related. So is there someway to get some diagnostics from the command prompt on the hardware interfaces, IRQ's etc...? I would get a syslog, but can't telnet in. Or is there someway to copy to the syslog to the usb key? Sorry for all the q's, really looking forward to getting this baby working and then sitting back and enjoying it Any help is much appreciated.
July 18, 200817 yr You may need to connect a keyboard/mouse/monitor. From there you can login and copy syslog to the USB key. There is also commands which can provide some idea of the state on your interface. ethtool eth0 ifconfig eth0
July 18, 200817 yr Specific instructions on how to copy the syslog to the flash drive are here http://lime-technology.com/wiki/index.php?title=Troubleshooting Since you indicated you see a "Login:" prompt, log in as "root" (initially there is no password) then, type the following once you get a root@Tower# prompt: cp /var/log/syslog /boot/syslog.txt chmod a-x /boot/syslog.txt As described, you can type ifconfig eth0 Shutdown the unRAID box by typing poweroff Wait for server to power off Remove the USB stick from your unRAID server and put into your desktop computer Attach the syslog.txt file from your flash drive to your next post Don't worry about shutting down cleanly, you have no disks configured, so there is really nothing there to stop at this point. Once you do get connectivity, and can get to //tower/ on your web-browser, and disks assigned, then you can stop the array and power down by using the buttons on the web-interface. Joe L.
July 18, 200817 yr Author Cheers for the advice guys. Not getting anything back from the ifconfig... just gives me the MAC address and then no packets sent/received. For the life of me, I can't get the syslog off the damn usb key. I know my way around unix, and it copies over fine, but when I do a 'poweroff', it starts shutting everything down and then gives me a 'INIT: no more processes left in this runlevel.' So basically, I have to hard-shut down (i.e. power key in 3 seconds), which I think doesn't unmount the usb key cleanly, and there is no syslog on the usb key when inserted into my windows box... at least that's my reasoning. One thing to note is that on poweroff, it states /boot/config/network.cfg - no such file or directory, and the same for /var/temp/network.cfg Something strange going on here... any ideas. Using the latest version available for download as of today - 4.3.2 I believe Anyways, off to bed, will try again in the morning. Matt.
July 18, 200817 yr OK, time to start with the basics. Log in as root. Type: ls -lR /boot If you see no files... it is a clue. If you see the config folder, and bzroot, and bzimage it is a good sign. Type: mount It should look like this: root@Tower:/tmp# mount proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sda1 on /boot type vfat (rw) <--- my flash drive If you do not see the flash drive mounted at /boot, it is another clue. (I'm guessing you will not see any files, and not see the flash drive mounted at /boot) Since you know your way around unix, you will then realize that /boot is simply a mount point (empty directory) in RAM if the flash drive was not mounted to it. When you copy the syslog to it, you are copying it to a file in an in-memory file system. Type: ls -l /dev/disk/by-label the output should look like this: root@Tower:/tmp# ls -l /dev/disk/by-label total 0 lrwxrwxrwx 1 root root 10 Jul 15 14:16 UNRAID -> ../../sda1 I'm guessing you will not see a volume with the UNRAID label. Type ifconfig eth0 The output should look like this: root@Tower:/tmp# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:11:11:75:FB:7E inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11118422 errors:0 dropped:0 overruns:0 frame:0 TX packets:12246058 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3514349145 (3.2 GiB) TX bytes:1703972345 (1.5 GiB) If there is no inet address, then you did not get a dhpc assignment. type lsmod this will show the loaded modules, including the network driver module. In my case, it is the e1000 driver. I'm guessing you will not see a network card driver. root@Tower:/tmp# lsmod Module Size Used by md_mod 49992 10 fuse 34580 3 ide_disk 11904 20 ata_piix 13700 1 libata 122552 1 ata_piix pdc202xx_new 5248 0 [permanent] piix 6404 0 [permanent] ide_core 88236 3 ide_disk,pdc202xx_new,piix e1000 180800 0 So... here is the series of events that have to take place. The network config is read from the flash drive AFTER it has been mounted. If it is not mounted, you will have no network connectivity. To mount the drive, it must be located by its volume label. UNRAD. If the label does not exist, the flash drive will not be mounted, you will not get a network driver loaded, and no IP address assigned, etc... So... let us know the output of the various commands I gave above. Odds are you just need to set the volume label on the flash drive. If it is already set, and the flash drive mounted, then we will need to know more about your motherboard network chipset. It might have been identified, and a driver loaded, and you have a bad cable, or the cable is plugged into the wrong network controller on the motherboard. Each of the commands give clues. Let us know what you find. Joe L.
July 19, 200817 yr Author Joe, many thanks for your response. Ok, ls -IR /boot gives me nothing. mount, gives me the same as your results, but without the last line, i.e. nothing is mounted at /boot. Should I try another flash drive? - I think I have a sandisk cruzer kicking around here ls -l /dev/disk/by-label gives me a 'no such file or directory', so you're right on that account again! ifconfig eth0 has no IP address, just the MAC address, and obviously no packets sent or received. lsmod gives me tg3 sata_nv libata amd74xx ide_core ... and that's it. Doesn't look like the ethernet driver is being loaded, so you're assumption and explanation is good so far. OK, let me try the other flash drive just to see if I get the same results. I'm almost 100% sure that I set the volume label to UNRAID (case sensitive I guess with linux). I'll post again if there are any differences with the cruzer. Cheers once again, Matt.
July 19, 200817 yr Author Hey great news. Plugged the Sandisk cruzer in, took longer booting - negotiating dhcp I noticed - and voila, ip assigned! Logged straight in and am now formatting the drives. I'm sure I'll be back with more questions once I've had a play around. Cheers once again for the help. Matt.
July 19, 200817 yr ... and that's it. Doesn't look like the ethernet driver is being loaded, so you're assumption and explanation is good so far. OK, let me try the other flash drive just to see if I get the same results. I'm almost 100% sure that I set the volume label to UNRAID (case sensitive I guess with linux). Glad your other flash drive worked, but all of the symptoms indicated that the volume label on your first flash drive was not set. If you get a chance, put the first flash drive in your desktop PC, right click on it, choose "properties" and you can there view and/or set the volume label. (you can set it there and retry booting it on your unRAID server) It must be UNRAID (six characters, all uppercase). Everything indicates it was not set at all. If it had been set, even to lower case, it would have probably shown up in the /dev/disk/by-label link set up by the Linux udev process. I'll bet it is blank, and that is why you did not boot to where the network was configured. Don't feel too bad, I initially had a very hard time getting my flash drive to boot. Glad you are up and running though. It is very easy to set the label, then reformat wiping it out. I know that happened to me once. I did not release I had accidentally erased the volume label on my flash drive when I tried reformatting it a different way using the HP tool. Lots of tips and information exist in the wiki. http://lime-technology.com/wiki/index.php?title=UnRAID_Wiki Both the official documentation (sometimes slightly out of date) http://lime-technology.com/wiki/index.php?title=Official_Documentation and the user-contributed section will answer many questions. http://lime-technology.com/wiki/index.php?title=Unofficial_Documentation Oh yes, version 4.3.3 was released, if you are on 4.3.2, you might upgrade. (You only need to replace the bzroot and bzimage files on the flash drive with those same two files unzipped from the 4.3.3 release.) You do not need to reformat the flash drive, or reload syslinux, those were already done the first time. Your disk configuration will still be in place, and you will just be running the newer version. The changes are not critical for you, but can't hurt. You are probably in the middle of formatting the drives. Let that complete, and the initial parity calc complete, then go for the upgrade when you get a chance. Joe L.
Archived
This topic is now archived and is closed to further replies.