Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[SOLVED]: can't see second NIC in v6.2

Featured Replies

I'm running v6.2 and trying to add a second NIC to allow network bonding but all I'm seeing is one NIC in unraid.  I've searched the forum but am not finding anything conclusive.  Will v6.2 automatically recognize a 2nd, 3rd NIC?  Is there a command or some other setup step to allow the addition NIC to show up under the GUI?  I deleted my network.cfg file and rebooted, no change.

 

I have 3 NICs installed, 2 NICs on the X9SCM-F motherboard and 1 PCIe add-on card.  (2) on-board NICs are: (1) Intel 82574L and (1) Intel 82579LM and the (1) PCIe add-on is a Intel 82574L.

  • Community Expert

They should be detected unless you're stubbing them, if you're not try deleting network-rules.cfg from the config folder on your flash drive and reboot.

They should be detected unless you're stubbing them, if you're not try deleting network-rules.cfg from the config folder on your flash drive and reboot.

 

In 6.2 stable deleting the network-rules.cfg file shouldn't be necessary anymore, a smarter detection in interface changes is in place now. :)

 

Telnet/ssh into the system and type

 

ifconfig -s -a

 

 

  • Author

here's the output of the command:

root@Artoo-Detoo:~# ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0      1500    53784      0    315 0         44311      0      0      0 BMRU
gre0      1476        0      0      0 0             0      0      0      0 O
gretap0   1462        0      0      0 0             0      0      0      0 BM
ip_vti0   1364        0      0      0 0             0      0      0      0 O
lo       65536       40      0      0 0            40      0      0      0 LRU
tunl0     1480        0      0      0 0             0      0      0      0 O

 

but here's another thought:

 

Previously I was running v6.1.9 and had a pfSense VM which I believe I passed through/stubbed NIC2 and NIC3.  A few weeks ago I build a dedicated pfSense box and turned off the pfSense VM in unRAID, but left the pfSense VM on disk.  After upgrading to v6.2 I decided I no longer needed that pfSense VM so I deleted it from disk via the GUI.  I wonder if NIC2 and NIC3 are still stubbed or reserved so that unRAID can't see them after a reboot.  (I also deleted network.cfg and rebooted but that didn't make any difference as you indicated bonienl.)

 

Goto Main -> Boot Device -> Flash -> Syslinux Configuration

 

Check if any command was added for stubbing these interfaces

  • Author

could it be the "...pci-stub..." line below?

 

default /syslinux/menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pci-stub.ids=8086:10d3 initrd=/bzroot
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest

When you go to Tools ->System Devices -> PCI Devices

 

You can see which component is "8086:10d3" (likely your ethernet card)

 

  • Author

Yes, there it is.  I believe the "8086:10d3" encompases both Ethernet NICs that the pfSense VM was using.

 

Is the correction to go back to: Main -> Boot Device -> Flash -> Syslinux Configuration and remove "pci-stub.ids=8086:10d3 " from the "append pci-stub.ids=8086:10d3 initrd=/bzroot" line, save changes and reboot?

 

PCI Devices

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller [8086:0108] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0105] (rev 09)
00:06.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:010d] (rev 09)
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 05)
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b5)
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation C204 Chipset Family LPC Controller [8086:1c54] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 05)
01:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)
02:00.0 RAID bus controller [0104]: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller [1b4b:9485] (rev 03)
03:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
05:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
06:03.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)

Is the correction to go back to: Main -> Boot Device -> Flash -> Syslinux Configuration and remove "pci-stub.ids=8086:10d3 " from the "append pci-stub.ids=8086:10d3 initrd=/bzroot" line, save changes and reboot?

 

Correct.

 

  • Author

That fixed it!  I see all 3 Ethernet adapters now available in "Network Settings"!

 

You are awesome!  Thank you bonienl and johnnie.black!  8)

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.