I'm trying to setup unRaid for the first time (4.4.2, but also tried 4.3.3). Everything seems to be ok so far except the network isn't working. When I type 'ifconfig', only lo shows (loopback?). eth0 does not display. If I do a 'ethtool eth0', it gives me a bunch of info about my TrendNet TEG-PCITXR. All the specs look accurate... and it says it's detected link. So I don't get why it's not showing up in 'ifconfig' and doesn't appear to have attempted to grab an address via DHCP. I've disabled my onboard nic as well. If I do a 'ifconfig eth0 start' it tells me it's busy?

 

In case it matters, I'm using an Asus P4SDX motherboard.

 

Thx in advance,

Brian

The syslog may supply hints as to why your network was not detected or connected.

 

Follow the Troubleshooting link in my sig for instructions on capturing and posting a syslog.

The syslog may supply hints as to why your network was not detected or connected.

 

Follow the Troubleshooting link in my sig for instructions on capturing and posting a syslog.

 

Appreciate the help! All I'm able to decipher is that it finds the eth0, tries to start it but it says it's busy... Here's my log:

The kernel could not setup an IRQ for the networking, so it does not work.  I'm afraid your motherboard may be too old, or may not be compatible with unRAID.  Here are some of the relevant lines:

Mar 15 12:28:54 Tower kernel: ACPI: BIOS age (2000) fails cutoff (2001), acpi=force is required to enable ACPI

Mar 15 12:28:54 Tower kernel: ACPI: Disabling ACPI support

 

So no ACPI support.  ACPI normally controls the setup of the PCI resources and the IRQ's.  You can *try* the boot option mentioned above, but I think it is VERY unlikely to help, or create a stable system.

 

Mar 15 12:28:54 Tower kernel: Enabling SiS 96x SMBus.

 

I don't know enough to say for sure, if this means it is a SIS based motherboard, or just a SIS SMBus chipset, sensors perhaps.  But I don't believe there is support for SIS chipsets in the kernels released with unRAID.  This may possibly explain why it could not setup the IRQ for the networking.

 

Mar 15 12:28:54 Tower kernel: r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded

Mar 15 12:28:54 Tower kernel: PCI: Enabling device 0000:00:08.0 (0014 -> 0017)

Mar 15 12:28:54 Tower kernel: PCI: No IRQ known for interrupt pin A of device 0000:00:08.0. Please try using pci=biosirq.

Mar 15 12:28:54 Tower kernel: eth0: RTL8169sb/8110sb at 0xf080c000, 00:14:d1:16:ef:54, XID 10000000 IRQ 0

 

It identified an r8169 compatible networking chipset, but could not setup an IRQ.  "IRQ 0" is not valid.  There is another tip about a possible boot option, which you can try, but I'm not optimistic.  If you are unfamiliar with boot options, see the Boot Codes wiki page.

Thanks for the tips. My motherboard does have ACPI support. I've added the boot code and am crossing my fingers that's all it takes.

IT WORKED!!!    At least I'm pretty sure I'm OK now. I now see eth0 when I do an ifconfig. It has an IP address and I'm able to ping yahoo.com successfully. I can also now browse to http://tower/. Going to attempt to set everything up now. Thanks again for pointing me to the boot options.

Disk status

  Model / Serial No. Temperature Size Free Reads Writes Errors

parity ata-WDC_WD10EADS-00L5B1_WD-WCAU45360344 35°C 976,762,552 - - - -

disk1 ata-WDC_WD10EADS-00L5B1_WD-WCAU46812581 35°C 976,762,552 Mounting - - -

disk2 ata-WDC_WD10EADS-00L5B1_WD-WCAU45488471 35°C 976,762,552 Mounting - - -

 

Lookin good. Thx again!

IT WORKED!!!    At least I'm pretty sure I'm OK now. I now see eth0 when I do an ifconfig. It has an IP address and I'm able to ping yahoo.com successfully. I can also now browse to http://tower/. Going to attempt to set everything up now. Thanks again for pointing me to the boot options.

To help the next person with your motherboard, what boot code did you add that allowed your network chipset to work?

IT WORKED!!!    At least I'm pretty sure I'm OK now. I now see eth0 when I do an ifconfig. It has an IP address and I'm able to ping yahoo.com successfully. I can also now browse to http://tower/. Going to attempt to set everything up now. Thanks again for pointing me to the boot options.

To help the next person with your motherboard, what boot code did you add that allowed your network chipset to work?

 

Also, what board is it?  I would like to at least get it added to the list of boards that seem to work.

IT WORKED!!!    At least I'm pretty sure I'm OK now. I now see eth0 when I do an ifconfig. It has an IP address and I'm able to ping yahoo.com successfully. I can also now browse to http://tower/. Going to attempt to set everything up now. Thanks again for pointing me to the boot options.

To help the next person with your motherboard, what boot code did you add that allowed your network chipset to work?

 

acpi=force. It seems that unRAID was simply not trying acpi based on the date of the bios.

IT WORKED!!!    At least I'm pretty sure I'm OK now. I now see eth0 when I do an ifconfig. It has an IP address and I'm able to ping yahoo.com successfully. I can also now browse to http://tower/. Going to attempt to set everything up now. Thanks again for pointing me to the boot options.

To help the next person with your motherboard, what boot code did you add that allowed your network chipset to work?

 

Also, what board is it?  I would like to at least get it added to the list of boards that seem to work.

 

Asus P4SDX

IT WORKED!!!    At least I'm pretty sure I'm OK now. I now see eth0 when I do an ifconfig. It has an IP address and I'm able to ping yahoo.com successfully. I can also now browse to http://tower/. Going to attempt to set everything up now. Thanks again for pointing me to the boot options.

To help the next person with your motherboard, what boot code did you add that allowed your network chipset to work?

 

Also, what board is it?  I would like to at least get it added to the list of boards that seem to work.

 

Asus P4SDX

 

Thanks much.  I will get this added later (have a college final in about 20 minutes or so).  If you could also look at this thread and get your board to level one that would be great!!

Sure, no problem. I computed parity last night. Moving a lot of media over now. Should be done this evening. Will run a parity check overnight.

Ok, I've gotten to level 1. I've had a few parity checks now without issue. I've also moved ~ 300GB of movies onto the server and they play fine via Media Center and my extenders. I guess my only remaining issue at this point is how long it takes to boot into unRAID on my system. It's taking more than 10 minutes. I see about a half a screen-full of dots for the second item (I'm at work now, but I think it's loading bzimage? or maybe bzroot). My motherboard specs indicate USB 2.0 is supported, but is there any way for me to confirm this w/in unRAID? Everything I've read on the Wiki points to this being symptomatic of USB1.0.

 

Thanks

Ok, I've gotten to level 1. I've had a few parity checks now without issue. I've also moved ~ 300GB of movies onto the server and they play fine via Media Center and my extenders. I guess my only remaining issue at this point is how long it takes to boot into unRAID on my system. It's taking more than 10 minutes. I see about a half a screen-full of dots for the second item (I'm at work now, but I think it's loading bzimage? or maybe bzroot). My motherboard specs indicate USB 2.0 is supported, but is there any way for me to confirm this w/in unRAID? Everything I've read on the Wiki points to this being symptomatic of USB1.0.

 

Thanks

You are correct... it does seem to indicate you are booting at USB 1.0 speeds.  (fortunately, we don't boot often)

On many BIOS there is a setting for "Legacy" USB devices...(you don't want this, as it is usually slower) or to adjust the speed from 1.0 to 2.0.  I'd look there first.

 

Edit:I looked in your MB manual. You do have a "Legacy USB" setting enabled by default (unless you changed it) and you also have a "USB Speed" setting to select 1.0 or 2.0 speeds.  One or both may need to be changed in your BIOS.   

 

Glad to hear you are up and running. 

 

Joe L.

Thanks Joe. Will check into that this evening.

Mar 15 12:28:54 Tower kernel: PCI: Enabling device 0000:00:03.3 (0004 -> 0006)

Mar 15 12:28:54 Tower kernel: PCI: No IRQ known for interrupt pin D of device 0000:00:03.3. Please try using pci=biosirq.

Mar 15 12:28:54 Tower kernel: ehci_hcd 0000:00:03.3: Found HC with no IRQ.  Check BIOS/PCI 0000:00:03.3 setup!

Mar 15 12:28:54 Tower kernel: ehci_hcd 0000:00:03.3: init 0000:00:03.3 fail, -19

  ...

Mar 15 12:28:54 Tower kernel: usb 2-1: new full speed USB device using ohci_hcd and address 2

Mar 15 12:28:54 Tower kernel: usb 2-1: configuration #1 chosen from 1 choice

Mar 15 12:28:54 Tower kernel: scsi0 : SCSI emulation for USB Mass Storage devices

 

This is from your earlier syslog, so it may have changed after you enabled ACPI.

 

The same IRQ issue you had before also blocked the initialization of EHCI above, which is the USB 2.0 support.  So your flash drive was recognized as a "full speed" device, using OHCI, which provides USB 1.1 support only.  You might try adding the boot option suggested above (pci=biosirq), to see if that will enable the EHCI support.

Did not work.. but that's OK really. How often do you reboot your storage anyways right?? Everything seems to be working fine for my needs (I'm able to stream DVDs/.DVR-MS w/o issue.). I'm content leaving it as-is until I need to upgrade.  I guess I'll continue adding PCI SATA cards and upgrade when things don't work anymore . Appreciate all your help in getting me going.