May 1, 200818 yr i just got my drive in the mail. i plugged it in, got it to boot, got to the point where i type root, typed in ifconfig and all looks good there, now it says root@Tower:~# what does that mean and what do i do now? i tried typing in http:tower in my browser and tower records page came up. that is obviously not what i thought was going to happen. thanks for the help
May 1, 200818 yr Same happens to me when I type in http:tower . The correct url to type in is http://tower . That should just work, but just in case it doesn't, here's another way. When you run ifconfig, what does it say? Specifically look at what it says for "inet addr". For example, here's mine: eth0 Link encap:Ethernet HWaddr 00:50:8D:9D:B7:F8 inet addr:192.168.1.18 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:52734018 errors:0 dropped:0 overruns:0 frame:0 TX packets:47385655 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2373164301 (2.2 GiB) TX bytes:1666234323 (1.5 GiB) Interrupt:16 Base address:0xa000 The inet addr is 192.168.1.18, so that's the ip of the server. If http://tower does not work then type the ip. In my example, it'd be http://192.168.1.18 , it will be different for you though.
May 1, 200818 yr Author Nope. Neither one worked. Right now the server is plugged directly into my computer with a cat5 so could that have something to do with it? My ipconfig looks the same except I dont have the bcast part. just inet addr and mask
May 1, 200818 yr How exactly is it connected? Is it connected via one cable directly from the server to another PC? If so then you may need a crossover cable. Or is it connected to a switch/router instead? Ok, let's just make sure one PC can see the other. What is the ip address of your unRAID server (as reported by ifconfig)? Can you successfully ping that ip from your other PC?
May 1, 200818 yr Author the ip is 127.0.0.1 i dont know how to ping it. im sorry. i suck at this stuff.
May 1, 200818 yr The address 127.0.0.1 is a standard (built-in) address known as "localhost" that allows a computer to refer back to itself. When you typed that address into the other (non-unRAID) computer's browser, that (non-unRAID) computer was actually looking for a webpage on itself. That is, this is not an address that can be accessed by another computer. There is something incorrect in your actual network setup. Please describe it. Do have just the two computers connected together with a single cable, or do you have other devices in your network? What are the manufacturer names and models of the other devices?
May 1, 200818 yr Author The computer and unraid box are connected with a single cat5 cable. the computer itself is connected to the home network with a linksus usb wireless adapter. The router is a linksys wrt300n i believe. besides that there are a hand full of other things on the network. 4 laptops, 1 xbox, a nas usb thing which has nothing attached to it and 2 desktops. 1 wireless and 1 wired.
May 1, 200818 yr i just got my drive in the mail. i plugged it in, got it to boot, got to the point where i type root, typed in ifconfig and all looks good there, now it says root@Tower:~# what does that mean and what do i do now? This is normal. This is the Linux prompt, similar to a "C:\>" proimpt you might see on a Windows command line. Right now the server is plugged directly into my computer with a cat5 so could that have something to do with it? My ipconfig looks the same except I dont have the bcast part. just inet addr and mask This won't work. As described, your 127.0.0.1 IP is a problem. You should be seeing an IP like 192.168.0.3. There are two ways to connect your unRAID server to your workstation. 1. One is by having a local area network in your home. Most people that have cable modems or other high-speed internet stuff already in their house already have some form of LAN. If you have something called a "router" or a "swtch" or a "hub", you have such a beast. If you do, your computer (the one you connect to the internet with) should have a CAT5 cable running from it into the router, switch, or hub. If this is you, you need to run a CAT5 cable from your unRAID server and plug it in to the same thing your workstation is plugged into. unRAID really likes to have a Gigabit network to perform well. Most people do NOT already have a Gigabit LAN, but upgrading to one is pretty inexpensive. You just need to buy a "Gigabit Switch". 2. The other way to network two computers is by using a special cable called a "crossover cable". A crossover cable will create a two computer network. One end plugs into one comoputer, the other into the other computer. It sounds easy but sometimes getting the crossover cable to work requires some fiddling with settings and IP addresses, and to be honest it has been many moons since I've tried to use one so couldn't help you much. But I'm sure you could find good instructions on the Internet. This is NOT a good long term option! Post back more info about your setup, as musicmann asks, and people here can help further.
May 1, 200818 yr Author ok. im gonna go plug it directly to the router. ill try some stuff and get back to you. by the way i really appreciate all the help. you guys are awesome.
May 1, 200818 yr Author i plugged it into the router. let it boot, typed "root" , then i did ifconfig again and it still says 127.0.0.1 not what? i dont get it. if it is plugged into the router it should get its own ip right?
May 1, 200818 yr Author also i dont know if it is relevant or not but when i do the ifconfig i get two sections: etho and lo the inet addr pops up under the lo section.
May 1, 200818 yr i plugged it into the router. let it boot, typed "root" , then i did ifconfig again and it still says 127.0.0.1 not what? i dont get it. if it is plugged into the router it should get its own ip right? There are many possibilities... cabling is one, but there are a few others that could also cause the network card to not work. Type the following command after you log in as root. ls /boot It should show you a listing of the files on your flash drive. If it does not, then your flash drive was not mounted as /boot. The usual cause of that is that you did not set the volume label of the flash drive to UNRAID To confirm, type ls -l /dev/disk/by-label It should show you something like this root@Tower:~# ls -l /dev/disk/by-label /dev/disk/by-label: total 0 lrwxrwxrwx 1 root root 10 Apr 10 17:50 UNRAID -> ../../sda1 If the label is there, and you see files on the flash drive at /boot, then try typing lsmod It will show you the driver modules currently loaded. It will look like this: root@Tower:~# lsmod Module Size Used by md_mod 50248 10 fuse 36116 3 ata_piix 13700 0 libata 122552 1 ata_piix ide_disk 11904 22 piix 6404 0 [permanent] pdc202xx_new 5248 0 [permanent] ide_core 88236 3 ide_disk,piix,pdc202xx_new e1000 180800 0 In my case, the e1000 module is my ntwork card driver. Your driver will depend on your motherboard/network card. Let us know what it says. If the flash drive is not found, and not mounted at /boot, then the networking configuration is not read from it, and the network driver will not start. So... start by checking a few things. If the disk/by-label is correct, then attach a copy of your syslog and we can figure out what is happening with its help. Joe L.
May 1, 200818 yr Author ok i did the ls /boot and got a list bzimage* config/ license.txt* menu.c32* syslinux.cfg* bzroot* ldlinux.sys* memtest* readme.txt* all where green except config/, which was blue. when i tried to confirm i get -bash: ls/: No such file or directory
May 1, 200818 yr Since there were files listed at /boot, your flash drive was identified by its volume label and was mounted. That is a very big first step. typing ifconfig will tell us more about how your network card was identified. And, lastly, to see what driver module was loaded for it, as I first described, type lsmod If the network card/chipset was detected (you will see an eth0 section in the ifconfig output) then the remaining possibility is that the cabling or router/switch port could be the issue. Joe L.
May 2, 200818 yr Author ok everything looks good except the ifconfig. here is what i get. eth0 link encap:ethernet hwaddr oo:17:31:c4:4f:fa up 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.0 b) tx bytes:0 (0.0 b) interrupt:10 base address:0x6000 lo link encap:local loopback inet addr:127.0.0.1 mask:255.0.0.0 up loopback running mtu:16436 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:0 rx bytes:0 (0.0 b) tx bytes:0 (0.0 b) does that make sence to anyone. im stuck
May 2, 200818 yr most people use a router as the dhcp server. If set up that way, the router automatically gives out IP numbers to each computer that you have plugged into the network, or that connect to your network wirelessly.
May 2, 200818 yr Author so theoretically when i type ifconfig and hit enter it should come up with an ip right?
May 2, 200818 yr so theoretically when i type ifconfig and hit enter it should come up with an ip right? right. It will show an IP address IF you have a DHCP server on your LAN giving out IP addresses and if the cable from your unRAID server to the network switch is good. If you do not have a DHCP server, then you will need to assign one yourself. (If you do not have a properly wired LAN cable, you will need to get one) To assign an IP yourself you will need to edit the network.cfg file in the config folder on the flash drive. It looks like this when a DHCP server is expected to supply the IP address: # Generated network settings USE_DHCP=yes IPADDR=192.168.2.4 NETMASK=255.255.255.0 GATEWAY=192.168.2.1 You would need to change it to have an IPADDR that is valid on your LAN, you would also change it to say USE_DHCP=no, and you would need to set the GATEWAY (typically the IP address of your router) you would leave the NETMASK as it is. The IP address should be one in the same subnet (first 9 digits are the same as other PCs on your LAN) with the final 3 digits unique on your LAN. In my case, all my machines are 192.168.2.xxx where xxx is unique per machine. 192.168.2.1 is the IP address of my router that in turn is plugged into my cable modem to get to the internet. After you edit network.cfg, reboot your unRAID server. Joe L.
May 2, 200818 yr Author got it.Thank you all so much. now i just gotta figure out how to use this thing so im sure ill be talking to you soon. thanks again everyone
May 2, 200818 yr first clear out if you indeed use a DHCP (most probably your router) or not - if not, I wonder how you've set up your other computers in the LAN (as you had to have done it manually in that case)... if you do use a DHCP you probably don't need to do anything but find the real problem (for example check if while unRAID boots, it posts any error about finding the LAN - I had that problem and needed to add some parameter in the boot sequence, search the forum)
May 2, 200818 yr Author ok i am able to connect to the tower thru my browser, i activated three drives in the devices tab, then pushed start array. i have two 750's and . it has one 500 in there with one of the 750's set to parity. after i pressed start array it started doing its thing and says mounting under the 500 and the non parity 750. it does not say anything under the parity drive. is this normal and about how long does it take? im assuming this is like formating the drives or something close. is this correct?
Archived
This topic is now archived and is closed to further replies.