May 21, 201115 yr Ok I'll be as brief as possible while trying to give all the necessary info. Basically I've had a system for the past 4-5 years, that recently crashed due to a motherboard that died (see: http://lime-technology.com/forum/index.php?topic=12745.msg121218#msg121218) Based on the recommendations of folks (especially the Raj prototype list) I bought the following components to upgrade/replace my old system. Mobo: SUPERMICRO MBD-X8SIL-F-O CPU: Intel i3 540 Clarkdale (the i3 530 and i3 550 are fine too, choose based on price and availability) RAM: Kingston 4GB DDR3 1333 SATA: Supermicro-AOC-SASLP-MV8 & SATA2 Serial ATA II PCI-Express RAID Controller Card The system starts up like a charm (and about 4 times faster than my old system) and ends at the "tower logon" prompt. Typically at that point, I can use another computer and open my browser and type-in: "//tower" and then the main homepage pops up so that I can configure the system. The problem is, its not working. My browser just opens up a search for "tower" ie, links to the wikipedia definition of tower just pop up. I've restarted everything several times, I've played with the bios settings (including booting from the USB port first) and its not working. I've got two ethernet cables plugged into my router (one from the dedicated IPMI port and one two the LAN 1 port (the LAN 2 port is empty). Any ideas what I'm doing wrong? Thank you so much in advance for any advice!!
May 21, 201115 yr Author Attach a console and see if it's booting. Do you mean attach a monitor to watch it boot? If so, I am, and its booting just fine
May 21, 201115 yr Logon in to the console and run ifconfig and see what ip address is it using, then try the IP in instead of http://tower Shawn
May 21, 201115 yr Author Logon in to the console and run ifconfig and see what ip address is it using, then try the IP in instead of http://tower Shawn Ok did that - I don't understand exactly what it says, but I'm suscpicious that I'm not getting a real IP address. I seem to remember that all my computers are like 168.x.x.1 etc etc: It says: 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) I noticed on the "building an unraid server page their example looks like this: eth0 Link encap:Ethernet HWaddr 00:1A:4D:27:13:8A inet addr:10.0.1.57 Bcast:10.0.255.255 Mask:255.255.0.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:16261 errors:0 dropped:0 overruns:0 frame:0 TX packets:2850 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1067783 (1.0 MiB) TX bytes:1193253 (1.1 MiB) Interrupt:21 Base address:0xa000 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) That first paragraph after the "eth0" doesn't show up on my screen One other thing I just noticed is that on the back of the MB where I have the two ethernet ports plugged, the IPMI one has one solid green light on the left. The cord plugged into the LAN 1 has a solid orange light on the left and a solid yellow light on the right. Not sure if this means anything? One other thing. My version of Unraid is old, I honestly don't remember which it is, but it has been 1-2 years since I last upgraded. Any chance that would be an issue with the above equipment? So now what? Thanks!
May 21, 201115 yr Author i upgraded to 4.7 and then ran IFCONFIG and was able to connect by using the IP address instead of //tower Thanks!
May 21, 201115 yr Author Yes it does. Thanks! Drives are all working and Parity sync is running. Speed is 38 KB/s. It seems that is about what I was getting on my old system. Based on the system specs I have, should my sync be faster than that?
Archived
This topic is now archived and is closed to further replies.