August 13, 200718 yr OK, I'm getting somewhere. I'm now able to boot from a kicker-floppy and load unRAID (or so I think) from my sandisk cruzer micro. It completes with: Welcome to Linux 2.6.22.1 (ttyl) Tower login: But it's not network accessible. If I login as root locally and type ifconfig eth0, I get: eth0 Link encap:Ethernet HWaddr 00:19:5B:39:0B:D2 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0b) INterrupt:3 Base address:0x2c00 A look at the DHCP server shows no new addresses leased. I tried editing the network.cfg file on the USB key to set a fixed IP, mask, gateway, but that doesn't seem to work either. Is it likely that the NIC in this box simply isn't compatible with unraid? It's probably an old Netgear 10/100 card (not an onboard port, there are no onboard ports on this box). I know the NIC itself is in working order as I've used it with other OS's in the last couple of days. The box is just an old PIII 1 ghz and 512 MB RAM. I'm just trying to get unraid running for some testing before buying specific equipment (assuming that I like unraid). Any help at this point? How fussy is unraid about network adaptors? Thanks.
August 13, 200718 yr Unraid is picky about network chips and USB keys, though 4.x is FAR better about network support than 3.x was. Check out the hardware compability section. http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility Bill
August 13, 200718 yr unraid's nic support depends on Linux's nic support. If you have an old intel nic around, those definitely work.
August 13, 200718 yr Author Thanks. I've got a few old NIC's laying around, but most are probably old 3com cards or Linksys cards. All 10/100. They seem unlikey to work but I'll try them. Anyone know of a specific PCI NIC (make/model) that is known to work that I can pick up for testing purposes?
August 13, 200718 yr OK, I'm getting somewhere. I'm now able to boot from a kicker-floppy and load unRAID (or so I think) from my sandisk cruzer micro. It completes with: Welcome to Linux 2.6.22.1 (ttyl) Tower login: But it's not network accessible. If I login as root locally and type ifconfig eth0, I get: eth0 Link encap:Ethernet HWaddr 00:19:5B:39:0B:D2 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0b) INterrupt:3 Base address:0x2c00 A look at the DHCP server shows no new addresses leased. I tried editing the network.cfg file on the USB key to set a fixed IP, mask, gateway, but that doesn't seem to work either. Is it likely that the NIC in this box simply isn't compatible with unraid? It's probably an old Netgear 10/100 card (not an onboard port, there are no onboard ports on this box). I know the NIC itself is in working order as I've used it with other OS's in the last couple of days. The box is just an old PIII 1 ghz and 512 MB RAM. I'm just trying to get unraid running for some testing before buying specific equipment (assuming that I like unraid). Any help at this point? How fussy is unraid about network adaptors? Thanks. The progress is encouraging news. Before you go crazy checking network drivers, did the flash drive get mounted at /boot as expected? If you did not set the volume label on it to "UNRAID" the network would not be established as it would not have been able to read the network.cfg file as it would not have found the drive. If you type mount do you see something like this: root@Tower:~# mount /dev/sda1 on /boot type vfat (rw) /dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime) /dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime) /dev/md8 on /mnt/disk8 type reiserfs (rw,noatime,nodiratime) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime) /dev/md6 on /mnt/disk6 type reiserfs (rw,noatime,nodiratime) /dev/md7 on /mnt/disk7 type reiserfs (rw,noatime,nodiratime) Of course, you will not have as many disks as I do, but you should see /boot. Next, type cat /proc/modules Its output should look something like this: root@Tower:/proc# cat /proc/modules md_mod 52200 8 - Live 0xe0872000 ata_piix 11524 0 - Live 0xe0814000 libata 85796 1 ata_piix, Live 0xe0828000 e1000 181632 0 - Live 0xe0844000 The last line is the driver module for my motherboard. Yours will be different. Post your output, it will allow us to see if your network card was found and the driver module loaded. Again, if the volume label is not set, the module will not be loaded. It appears as if you have a MAC address, to me that seems to indicate something is working to get to your network card. As described earlier, Tom does not include all the network card drivers possible as part of the 2.6 kernnel. He supports many of the gigabyte cards and some 100MB cards using popular chipsets. Good news is that the network driver is a module and easily added to any distribution and most chipsets are supported under Linux. Last, attach a copy of /var/log/syslog to your next post. You can type cp /var/log/syslog /boot/syslog.txt to copy it to your flash drive, then move the flash drive to your PC to attach it to the forum post. It gives all the detail needed to figure out how to proceed. By the way... what did you do differently this time to get the kicker disk to work? (Others following this thread might benefit from your experience) Joe L.
August 13, 200718 yr Author Thanks Joe. In response to your last question first, I formatted the USB key with the HP utility rather than Windows. And that worked, sort of, until I realized that when doing it this way I neglected to give it the label UNRAID. Doing that seems to make it boot. the MOUNT command gives me the /boot line, and nothing else. Attached is my syslog.txt. FYI, I changed the TOWER name to UNRAID in the cfg file, so the server name is unraid. Regarding the cat /proc/modules command, it gives several lines of output that I don't have time to type at this moment as I'm literally walking out the door, but I can post those later if they're essential. Thanks to anyone that sees anything worth noting in the syslog...
August 13, 200718 yr Looks pretty decent actually. You might want to re-enable DHCP in your config file and reboot. That is about the only piece that seems different to me from my syslog (other than your ethernet card)
August 13, 200718 yr Author OK, it's up. For now, anyway. I replaced the NIC (a DLink DFE-530TX+ 10/100 card) with a DLink Gigabit card (DGE-530T 10/100/1000 for those interested in a compatible PCI card) that I pulled from one of my other working PC's. Pulled an IP address from DHCP and I can connect to the UnRAID Server's web interface and view the available drives. (Of course, I've got to put that card back where I got it now...I need my SageTV after all. But that specific card is readily available locally so I'll pick another one up tonight.) Thanks to all who assisted me. Now I can start toying with this thing.
Archived
This topic is now archived and is closed to further replies.