May 24, 201115 yr Ok so I've tried everything I can find and can't get either the onboard nic or a Netgear GA311 addon bought just for the project. The onboard nic has no lights when booted into unraid and lsmod shows no driver loaded. The onboard works fine when booted into Ubuntu 11.04, as does the addon. I disabled the onboard in bios and installed the addon ga311 which lights up. lsmod still shows no driver loaded and the syslog shows "no link beat detected." I tried: modprobe r8169 ifconfig and lsmod then shows the driver loaded, but ifconfig still shows only lo. I tried adding modprobe r8169 to the go script as a stab in the dark, but obviously that didn't work either. Here's a link to the motherboard (ASRock 890GX Pro3): http://www.asrock.com/mb/overview.asp?Model=890GX%20Pro3 and a copy of the syslog: http://pastebin.com/Z2vk4gk0 Please help! EDIT: Also, same behavior on Unraid 4.7 and 5.0b6a, incase it makes a difference
May 24, 201115 yr After you modprobe try this: /etc/ifplugd/ifplugd.action eth0 down then /etc/ifplugd/ifplugd.action eth0 up
May 24, 201115 yr Author Thanks for your help prostuff1, I'm pulling my hair out = \ up and down looks successful (no errors), but ifconfig still don't see anything Output from lsmod: Module Size Used by md_mod 44249 0 xor 12849 1 md_mod r8169 26900 0 atiixp 1788 0 ahci 16605 0 libahci 13307 1 ahci and ethtool eth0: Settings for eth0: No data available
May 25, 201115 yr Probably by flashing the BIOS to the latest one, loading the "default" and then disabling any unused hardware feature from this "premium" board - floppy, serial and parallel ports, audio. firewire, the IDE controller if you are not going to use any older PATA drive, even the USB3 controller if needed. If you have choice you can even disable some of the existing USB2 ports. And the onboad LAN is shown as Atheros® AR8151 on the specification page.
May 25, 201115 yr Author Ok, not sure where I got the 8111E, updated title to reflect. I tried disabling everything but the USB ports earlier, but I'll got hack those off too and see what happens. With your new piece of information, I also found this: http://www.linuxquestions.org/questions/linux-networking-3/atheros-ar8151-gigabit-ethernet-on-slackware-linux-862555/ but I'm not sure this is for me. As a little bit of back ground, I'm trying to convince my work place that this is a viable alternative to expensive and proprietary solutions with said solutions' vendors flooding us with their propaganda.... If I can get this going, we'll be ready to move up to a pro license and open the door to other OSS =) Thanks again for the help! I'll post back after turning everything else off.
May 25, 201115 yr Ok, not sure where I got the 8111E, updated title to reflect. I tried disabling everything but the USB ports earlier, but I'll got hack those off too and see what happens. With your new piece of information, I also found this: http://www.linuxquestions.org/questions/linux-networking-3/atheros-ar8151-gigabit-ethernet-on-slackware-linux-862555/ but I'm not sure this is for me. As a little bit of back ground, I'm trying to convince my work place that this is a viable alternative to expensive and proprietary solutions with said solutions' vendors flooding us with their propaganda.... If I can get this going, we'll be ready to move up to a pro license and open the door to other OSS =) Thanks again for the help! I'll post back after turning everything else off. Ok, so you happened to pick a board that has an Atheros NIC... that is just bad luck. The newegg site has the wrong NIC listed, hence where you probably got the Realtek from. For unRAID the Atheros NICS are usually always avoided. Intel and Realtek seem to work the best. It it were me and I was trying to sell this to my company I would grab this JetWay board. It is pretty cheap to get and has been used for unRAID before, so compatibility is known working.
May 25, 201115 yr As a little bit of back ground, I'm trying to convince my work place that this is a viable alternative to expensive and proprietary solutions with said solutions' vendors flooding us with their propaganda.... If I can get this going, we'll be ready to move up to a pro license and open the door to other OSS =) If we are talking about a company then: 1. You must pick a board that uses ECC memory and even better has "chipkill" functionality. - http://arstechnica.com/business/news/2009/10/dram-study-turns-assumptions-about-errors-upside-down.ars 2. You must use a good UPS. 3. You may stick with 7200 rpm drives only to provide that little bit extra performance (write) - but make sure the case will keep the hard drives cooled below 40 deg C at all time.
May 25, 201115 yr Author Ok, I've disabled everything I can find in the bios and still the same symptoms. Here's the output from dmesg: http://pastebin.com/t57D0NLL Unfortunately my limited Linux knowledge as come to an end so I really hope someone can help. I feel like it has to be something simple since the link lights are up and this nic has been used successfully. These are the drives we went with so I think they'll be sufficient: http://www.newegg.com/Product/Product.aspx?item=N82E16822145475
May 25, 201115 yr Atheros NICs are know to be problematic in unRAID. Data corruption is the most common issue with these NICs so even if it seems to start working there will likely still be a problem. The easiest fix is to add a cheap Intel PCI Gig-e NIC.
May 25, 201115 yr The easiest fix is to add a cheap Intel PCI Gig-e NIC. .... but he's already added a GA311, which should be working fine.
May 25, 201115 yr Author .... but he's already added a GA311, which should be working fine. This =) For what it's worth, while trying to make sense of the dmesg output, I saw something about an Intel Pro, is that normal?
May 25, 201115 yr .... but he's already added a GA311, which should be working fine. This =) For what it's worth, while trying to make sense of the dmesg output, I saw something about an Intel Pro, is that normal? That is the driver being loaded if I remember correctly
May 25, 201115 yr Author That is the driver being loaded if I remember correctly But since neither or the NICs are Intel, could that be the problem?
May 25, 201115 yr That is the driver being loaded if I remember correctly But since neither or the NICs are Intel, could that be the problem? should not be. That is stuff that is logged in everyones syslog. If I was to look in mine right now it would have the Intel Pro line in it just like yours.
May 25, 201115 yr Have you tried basic troubleshooting yet? I didn't see any mention of the obvious steps to take. Some PCI slots are master and others are slave. Your MB has three slots. Which are master? Which are slave? Have you tried the card in all three slots? Next, have you checked your PSU's output voltage? Is the 3.3V and 5V outputs to spec? Other devices might work if the PSU is slightly out of spec. The GA311 might not. When you ran the card in Ubuntu, was it in this machine in the exact same configuration? Did you add/remove any devices that could change the PSU loading? Have you disabled any overclocking or core unlocking? Either can cause operational problems with the PCI Bus in some cases.
May 25, 201115 yr Author Ok great. Is there any other information I can provide that might give a clue?
May 25, 201115 yr Author Haven't tried the other slots bc we'd have to punch out the slots and I'd like to avoid any non-fanned holes if possible. Ubuntu was the exact same config, just unplugged the unRAID drive and plugged in a Ubuntu usb drive. Physically it seems fine since I can get gigabit connections with both in Ubuntu. Here's the PSU, but I'm pretty sure it should be fine: http://www.newegg.com/Product/Product.aspx?item=N82E16817152043
May 25, 201115 yr Have you also searched the forums? If you had you would have found these posts where the 8169 driver was not working with unRAID: http://lime-technology.com/forum/index.php?topic=587.msg3769#msg3769 http://lime-technology.com/forum/index.php?topic=7644.0 http://lime-technology.com/forum/index.php?topic=12534.0 http://lime-technology.com/forum/index.php?topic=9863.msg94416#msg94416 http://lime-technology.com/forum/index.php?topic=12420.msg118059#msg118059 Looks like 3 pages of posts where the 8169 comes into play. And it may have been working in the past, on older versions with different drivers. From reading through some of the search results, it looks like Lime monkeyed with the 8169 in the 4.X releases. So it's possible that is on the approved Wiki list because it worked in the past, but may not be working now. unRAID has serious issues with the Realtek 8111 NIC, and the 8111 and 8169 share the same driver. So I'm going to go out on a limb and say that the 8169 will have all the same problems as the 8111. So my best guess at this point is that your motherboard has an Atheros NIC, which isn't supported by unRAID, and you installed an add-on card with a 8169, which is also looking like it isn't supported by unRAID (actually, unRAID supports it, it just has a crappy driver from Realtek).
May 25, 201115 yr Haven't tried the other slots bc we'd have to punch out the slots and I'd like to avoid any non-fanned holes if possible. Ubuntu was the exact same config, just unplugged the unRAID drive and plugged in a Ubuntu usb drive. Physically it seems fine since I can get gigabit connections with both in Ubuntu. Here's the PSU, but I'm pretty sure it should be fine: http://www.newegg.com/Product/Product.aspx?item=N82E16817152043 I'm saying have you actually tested the PSU with a meter to make sure it actually outputs what it says it should output. At the very least, your BIOS may have an screen where it shows you the +3.3,+5,+12,-12, etc. voltages. You can then compare these to the spec on the PSU (and preferably to the readings from a good meter, in case you MB is malfunctioning). But that is probably pointless, since a quick search indicates the 8169 just isn't compatible with unRAID. IF I had to guess, slots 1 &2 are probably master and 3 is slave, but it could also be 1&3 master, with two slave. You should be safe if it is in slot 1 (nearest the CPU). 50/50 if it is in two or three.
May 25, 201115 yr Have you updated the BIOS as I asked in a previous post. You have this and until it is fixed you probably wont move ahead: pnp 00:03: disabling [io 0x0000-0x000f] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:03: disabling [io 0x0060-0x005f disabled] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:03: disabling [io 0x0064-0x0063 disabled] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0010-0x001f] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0022-0x003f] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0044-0x005f] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0062-0x0063] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0065-0x006f] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0072-0x007f] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0080] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0084-0x0086] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0088] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x008c-0x008e] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x0090-0x009f] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x00a2-0x00bf] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] pnp 00:08: disabling [io 0x00e0-0x00ef] because it overlaps 0000:02:05.0 BAR 0 [io 0x0000-0x00ff] Also make sure the option ACPI HPET is enabled in the BIOS
May 25, 201115 yr Have you also searched the forums? If you had you would have found these posts where the 8169 driver was not working with unRAID: http://lime-technology.com/forum/index.php?topic=587.msg3769#msg3769 http://lime-technology.com/forum/index.php?topic=7644.0 http://lime-technology.com/forum/index.php?topic=12534.0 http://lime-technology.com/forum/index.php?topic=9863.msg94416#msg94416 http://lime-technology.com/forum/index.php?topic=12420.msg118059#msg118059 Looks like 3 pages of posts where the 8169 comes into play. And it may have working in the past, on older versions with different drives. From reading through some of the search results, it looks like Lime monkeyed with the 8169 in the 4.X releases. So it's possible that is on the approved Wiki list because it worked in the past, but may not be working now. unRAID has serious issues with the Realtek 8111 NIC, and the 8111 and 8169 share the same driver. So I'm going to go out on a limb and say that the 8169 will have all the same problems as the 8111. The Realtek "issue" you mention has, as far as I am concerned, been blown out of proportion. I have built several servers with Realtek NIC's in them (I run a Gigabyte board, with a Realtek NIC) and have never had a problem. I have messed with almost every version of unRAID since about 4.3 and the hiccups related to Realtek NIC's has been few if any. I don't doubt that some are having problems, and maybe a driver update is needed. That would come from a newer kernel, as Lime Tech usually goes with the driver that is included with the kernel. I think what might be happening is that there is some sort of conflict between everything and the UEFI firmware. So my best guess at this point is that your motherboard has an Atheros NIC, which isn't supported by unRAID, and you installed an add-on card with a 8169, which is also looking like it isn't supported by unRAID (actually, unRAID supports it, it just has a crappy driver from Realtek). It is the kernel that is not supporting it. unRAID uses what it has been given from the kernel and if the kernel has problems with it, then unRAID is out of luck.
May 25, 201115 yr Author HPET (whatever that is) is enabled in bios, flashed to version 30 from the ASRock site. The GA311 is in slot 1 and works fine in Ubuntu. If I hadn't searched the forums, I wouldn't be posting in them as I'd much rather grab an existing solution than play guessing games with random people on the internet. None of the threads you linked are the same symptoms and my apparently poor searching turns up that full slackware distros are able to run the GA311 and other r8169 and r1000 chipsets. Also, as previously posted modprobe loads the driver just fine, it's just what ever setup normally occurs after that doesn't seem to be happening. I think Prostuff1 and bcbgboy are on the right track, I don't know what any of that means but disabled anything doesn't sound good.
May 25, 201115 yr Have you also searched the forums? If you had you would have found these posts where the 8169 driver was not working with unRAID: http://lime-technology.com/forum/index.php?topic=587.msg3769#msg3769 http://lime-technology.com/forum/index.php?topic=7644.0 http://lime-technology.com/forum/index.php?topic=12534.0 http://lime-technology.com/forum/index.php?topic=9863.msg94416#msg94416 http://lime-technology.com/forum/index.php?topic=12420.msg118059#msg118059 Looks like 3 pages of posts where the 8169 comes into play. And it may have working in the past, on older versions with different drives. From reading through some of the search results, it looks like Lime monkeyed with the 8169 in the 4.X releases. So it's possible that is on the approved Wiki list because it worked in the past, but may not be working now. unRAID has serious issues with the Realtek 8111 NIC, and the 8111 and 8169 share the same driver. So I'm going to go out on a limb and say that the 8169 will have all the same problems as the 8111. The Realtek "issue" you mention has, as far as I am concerned, been blown out of proportion. I have built several servers with Realtek NIC's in them (I run a Gigabyte board, with a Realtek NIC) and have never had a problem. I have messed with almost every version of unRAID since about 4.3 and the hiccups related to Realtek NIC's has been few if any. I don't doubt that some are having problems, and maybe a driver update is needed. That would come from a newer kernel, as Lime Tech usually goes with the driver that is included with the kernel. I think what might be happening is that there is some sort of conflict between everything and the UEFI firmware. So my best guess at this point is that your motherboard has an Atheros NIC, which isn't supported by unRAID, and you installed an add-on card with a 8169, which is also looking like it isn't supported by unRAID (actually, unRAID supports it, it just has a crappy driver from Realtek). It is the kernel that is not supporting it. unRAID uses what it has been given from the kernel and if the kernel has problems with it, then unRAID is out of luck. I run a Realtek NIC on two unRAIDs. I'm not saying that all of them are a problem. But there are numerous problems reported with the 8111,8168, and 8169 realtek chipsets, all which use the same driver. And obviously Lime can add or remove drivers as needed when building a kernel, since they removed the original 8169 driver and monkeyed around with other 8169 drivers during the 4.X betas. These are known buggy chipsets in unRAID. Attempt to use them at your own risk.
May 25, 201115 yr HPET (whatever that is) is enabled in bios, flashed to version 30 from the ASRock site. The GA311 is in slot 1 and works fine in Ubuntu. If I hadn't searched the forums, I wouldn't be posting in them as I'd much rather grab an existing solution than play guessing games with random people on the internet. None of the threads you linked are the same symptoms and my apparently poor searching turns up that full slackware distros are able to run the GA311 and other r8169 and r1000 chipsets. Also, as previously posted modprobe loads the driver just fine, it's just what ever setup normally occurs after that doesn't seem to be happening. I think Prostuff1 and bcbgboy are on the right track, I don't know what any of that means but disabled anything doesn't sound good. Really. This isn't the same symptom? http://lime-technology.com/forum/index.php?topic=7644.0 They install a 8169 NIC. UnRaid detects it and correctly loads the driver. They can't transmit/receive any data. Sounds to me exactly like the problem you are having. They continued looking for help here: http://lime-technology.com/forum/index.php?topic=7644.msg73909#msg73909 And their problem doesn't appear to have been solved. They did not go into a great deal of troubleshooting, but they had many of the same symptoms. Both were 8169's. Theirs lit up. Yours lights up. Theirs loads the driver. Yours loads the driver. Theirs worked in Windows. Yours works in Ubuntu. Theirs wouldn't communicate in unRAID. Yours won't communicate in unRAID. Their problem was never solved. Yours... How much time do you really want to invest in this vs buying another $20 NIC based on a chipset that doesn't have widely reported problems?
Archived
This topic is now archived and is closed to further replies.