irishjd

I have identified that plugin as the cause of the error as well. Thanks!

So I talked to the company that I bought the drive from, and their tech folks says its a firmware incompatibility between the drive and the disk controller. I guess it could be, but I have never run across that before.

I just started seeing the error “no such column: smart_reallocated_sector_count”. It is in red text just below the top menu bar.

That is the only thing I have not tried. I will go ahead and shut down the server, remove the drive, clean the contacts on the drive, re-insert, and then re-seat it. If that doesn’t work, it looks like I probably got a lemon.

I think the disk might be bad. I ran the blkdiscard command on it and didnt have any errors. However when I go to MAIN-UD i see the drive listed (sdm), but it says its size is 0. If I try to add it to my Cache Pool Devices, it is not listed as available.

Good point… Instead I am going try to “clear” the disk by wiping the MBR via a dd command. If it works, I will post the actual dd command here in case someone else ever has an issue like this.

I just purchased a "used" Samsung SSD for use on my Dell R820. When I plug it in, the server sees it, Preclear states "Cannot Preclear". The logs show this: { "sdm": { "ID_SCSI_SERIAL": "P0NA0H912234", "ID_SERIAL": "35002538a069d5590", "ID_SERIAL_SHORT": "5002538a069d5590", "ID_VENDOR": "SAMSUNG", "SERIAL_SHORT": "P0NA0H912234", "SERIAL": "35002538a069d5590", "BUS": "scsi", "FSTYPE": "", "SMART": "-d auto", "FAMILY": "SAMSUNG P1633N19 EMC1920", "MODEL": "SAMSUNG P1633N19 EMC1920 - Rev. EQPC", "FIRMWARE": "n\/a", "SIZE": 0, "SIZE_H": "0 B", "DEVICE": "\/dev\/sdm", "PARTS": [], "NAME": "sdm", "NAME_H": "sdm", "RUNNING": false, "TIMESTAMP": 0, "TEMP": "*", "SSD": true, "PRECLEAR": false } } Unraid is showing this: Feb 21 14:48:57 Unraid-1 kernel: sd 1:0:13:0: [sdm] Synchronizing SCSI cache Feb 21 14:48:57 Unraid-1 kernel: sd 1:0:13:0: [sdm] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 21 14:49:02 Unraid-1 kernel: sd 1:0:14:0: [sdm] Spinning up disk... Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Unsupported sector size 520. Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] 0 512-byte logical blocks: (0 B/0 B) Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] 4160-byte physical blocks Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Write Protect is off Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Mode Sense: b7 00 10 08 Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Write cache: enabled, read cache: enabled, supports DPO and FUA Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Preferred minimum I/O size 8192 bytes Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Optimal transfer size 8192 bytes Feb 21 14:49:29 Unraid-1 kernel: sd 1:0:14:0: [sdm] Attached SCSI disk Feb 21 14:49:32 Unraid-1 emhttpd: device /dev/sdm has size zero I stopped the array, and still no joy. Did I happen to get a bad drive, or is there a way to "wipe" the drive and make Unraid look at it again? v/r Jon

Thanks @JorgeB... when I get back in town, I will take another stab at this. At least now, I know that the NIC, the GBIC, and the fiber are all good.

So there is definitely something going on with the network config. The only way I could get access back to my server was to shut it down, remove the flash drive, remove all the settings for the fiber interface from the network.cfg file, and reboot. I am about to go out of town awhile for work, so I am not going to mess with this any more until I get back. @JorgeBdo you guys have any tools for parsing the diagnostics dumps that can be shared? I would like to be able to do some of the detective work myself without having to bother everyone, but there are a lot of files created and when I am not exactly sure what I am looking for, it makes it difficult to look at the right file.

Once I get the 10GB link working, I plan on disabling the copper 1GB link.

The switch is directly connected to the DHCP router. This being the fact, it sounds like I might have a UniFi issue. I will check with them. Any idea how I can reset the GBIC to auto negotiate? I tried using: root@Unraid-1:~# sudo ethtool –s eth4 autoneg on netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device netlink error: no device matches name (offset 24) netlink error: No such device No data available

So, I just received the Intel SFP+'s that Intel states are compatible with the NIC. I replaced the Dell SFP+'s with the Intel, and plugged the fiber in. Both the NIC and the switch show a link, but the interface (eth4) is still not pulling an IP address.According to ethtool, the SFP+ has autonegotiate turned off, so I configured the switch to set the connection at 10GBPS FDX. This has not corrected the issue. According to the switch, 854 MB have been transfered over the link, but only 86 kb have been received. I am puzzeled as to what the issue is. I will drop the latest diag dump here in hopes that someone can tell me what I am doing wrong. unraid-1-diagnostics-20240131-1454.zip

I did... it appears at this time UNRAID only supports up to 2 instances of a Docker App.

So is there any chance that this option can be extended to more than just a 2nd instance? I am playing with WindowsinDocker and would like to try and setup an entire AD domain. To do so, I will need a lot more than just 2 instances.

@JorgeB thanks for the suggestion. I have tried these as well, but with no luck. I'll keep trying.

Will do... is there a best practices document for joining an UNRAID server to a Microsoft Active Directory Domain? I have not had any luck in doing so.

Thanks @JorgeB. I let it sit all night and this morning I was able to get the array to stop. I made my change (tried to join it to my MS AD test domain (didn't work)), and then tried to start the array. Now, it appears to be stuck at "starting services". It has been this way for several hours now. If it helps, I have attached a new diagnostics dump. unraid-1-diagnostics-20240123-1040.zip

Recently, I had a need to stop my unraid array to make some settings changes. After a couple of hours, it was still saying that it was trying to stop the array. I noticed in the lower left-hand corner, the status kept saying " Array Stopping•Retry unmounting disk share(s)". I rebooted the system, but I am having the same issue as i can't stop the array. I have attached a diagnostics dump and would appreciate any help. v/r Jon unraid-1-diagnostics-20240122-1419.zip

I looked up an Intel doc that listed compatible SFP+'s. I'll order a couple and see what happens. Thanks for the help!

Bummer... I assume that it is referring to a supported SFP+ module for the NIC in the server, or does it have to be a SFP+ that UnRAID supports?

Here is the latest Diagnostics dump... unraid-1-diagnostics-20240119-1042.zip

It appears that a driver is not being loaded: 00:00.0 0600: 8086:3c00 (rev 07) Subsystem: 1028:04fe 00:01.0 0604: 8086:3c02 (rev 07) Subsystem: 1028:04fe Kernel driver in use: pcieport 00:01.1 0604: 8086:3c03 (rev 07) Subsystem: 1028:04fe Kernel driver in use: pcieport 00:02.0 0604: 8086:3c04 (rev 07) DeviceName: SLOT 7 Subsystem: 1028:04fe Kernel driver in use: pcieport 00:02.2 0604: 8086:3c06 (rev 07) DeviceName: SLOT 3 Subsystem: 1028:04fe Kernel driver in use: pcieport 00:03.0 0604: 8086:3c08 (rev 07) DeviceName: SLOT 6 Subsystem: 1028:04fe Kernel driver in use: pcieport 00:04.0 0880: 8086:3c20 (rev 07) Subsystem: 1028:04fe 00:04.1 0880: 8086:3c21 (rev 07) Subsystem: 1028:04fe 00:04.2 0880: 8086:3c22 (rev 07) Subsystem: 1028:04fe 00:04.3 0880: 8086:3c23 (rev 07) Subsystem: 1028:04fe 00:04.4 0880: 8086:3c24 (rev 07) Subsystem: 1028:04fe 00:04.5 0880: 8086:3c25 (rev 07) Subsystem: 1028:04fe 00:04.6 0880: 8086:3c26 (rev 07) Subsystem: 1028:04fe 00:04.7 0880: 8086:3c27 (rev 07) Subsystem: 1028:04fe 00:05.0 0880: 8086:3c28 (rev 07) Subsystem: 1028:04fe 00:05.2 0880: 8086:3c2a (rev 07) Subsystem: 1028:04fe 00:11.0 0604: 8086:1d3e (rev 05) Subsystem: 1028:04fe Kernel driver in use: pcieport 00:16.0 0780: 8086:1d3a (rev 05) Subsystem: 1028:04fe Kernel modules: mei_me 00:16.1 0780: 8086:1d3b (rev 05) Subsystem: 1028:04fe 00:1a.0 0c03: 8086:1d2d (rev 05) Subsystem: 1028:04fe Kernel driver in use: ehci-pci 00:1c.0 0604: 8086:1d10 (rev b5) Subsystem: 1028:04fe Kernel driver in use: pcieport 00:1c.7 0604: 8086:1d1e (rev b5) Subsystem: 1028:04fe Kernel driver in use: pcieport 00:1d.0 0c03: 8086:1d26 (rev 05) Subsystem: 1028:04fe Kernel driver in use: ehci-pci 00:1e.0 0604: 8086:244e (rev a5) Subsystem: 1028:04fe 00:1f.0 0601: 8086:1d41 (rev 05) Subsystem: 1028:04fe 00:1f.2 0106: 8086:1d02 (rev 05) Subsystem: 1028:04fe Kernel driver in use: ahci Kernel modules: ahci 01:00.0 0200: 14e4:165f DeviceName: NIC1 Subsystem: 1028:1f5b Kernel driver in use: tg3 Kernel modules: tg3 01:00.1 0200: 14e4:165f DeviceName: NIC2 Subsystem: 1028:1f5b Kernel driver in use: tg3 Kernel modules: tg3 02:00.0 0200: 14e4:165f DeviceName: NIC3 Subsystem: 1028:1f5b Kernel driver in use: tg3 Kernel modules: tg3 02:00.1 0200: 14e4:165f DeviceName: NIC4 Subsystem: 1028:1f5b Kernel driver in use: tg3 Kernel modules: tg3 03:00.0 0107: 1000:0087 (rev 05) Subsystem: 1028:1f35 Kernel driver in use: mpt3sas Kernel modules: mpt3sas 08:00.0 0604: 1912:0013 Subsystem: 1912:0013 Kernel driver in use: pcieport 09:00.0 0604: 1912:0013 Subsystem: 1912:0013 Kernel driver in use: pcieport 09:01.0 0604: 1912:0013 Subsystem: 1912:0013 Kernel driver in use: pcieport 0a:00.0 0604: 1912:0012 Subsystem: 1912:0012 0b:00.0 0300: 102b:0534 DeviceName: Embedded Video Subsystem: 1028:04fe Kernel driver in use: mgag200 Kernel modules: mgag200 3f:08.0 0880: 8086:3c80 (rev 07) Subsystem: 8086:0000 3f:09.0 0880: 8086:3c90 (rev 07) Subsystem: 8086:0000 3f:0a.0 0880: 8086:3cc0 (rev 07) Subsystem: 8086:0000 3f:0a.1 0880: 8086:3cc1 (rev 07) Subsystem: 8086:0000 3f:0a.2 0880: 8086:3cc2 (rev 07) Subsystem: 8086:0000 3f:0a.3 0880: 8086:3cd0 (rev 07) Subsystem: 8086:0000 3f:0b.0 0880: 8086:3ce0 (rev 07) Subsystem: 8086:0000 3f:0b.3 0880: 8086:3ce3 (rev 07) Subsystem: 8086:0000 3f:0c.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0c.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0c.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0c.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0c.6 0880: 8086:3cf4 (rev 07) Subsystem: 8086:0000 3f:0c.7 0880: 8086:3cf6 (rev 07) Subsystem: 8086:0000 3f:0d.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0d.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0d.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0d.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 3f:0d.6 0880: 8086:3cf5 (rev 07) Subsystem: 8086:0000 3f:0e.0 0880: 8086:3ca0 (rev 07) Subsystem: 1028:04fe 3f:0e.1 1101: 8086:3c46 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 3f:0f.0 0880: 8086:3ca8 (rev 07) Subsystem: 8086:0000 3f:0f.1 0880: 8086:3c71 (rev 07) Subsystem: 8086:0000 3f:0f.2 0880: 8086:3caa (rev 07) Subsystem: 8086:0000 3f:0f.3 0880: 8086:3cab (rev 07) Subsystem: 8086:0000 3f:0f.4 0880: 8086:3cac (rev 07) Subsystem: 8086:0000 3f:0f.5 0880: 8086:3cad (rev 07) Subsystem: 8086:0000 3f:0f.6 0880: 8086:3cae (rev 07) Subsystem: 8086:0000 3f:10.0 0880: 8086:3cb0 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 3f:10.1 0880: 8086:3cb1 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 3f:10.2 0880: 8086:3cb2 (rev 07) Subsystem: 8086:0000 3f:10.3 0880: 8086:3cb3 (rev 07) Subsystem: 8086:0000 3f:10.4 0880: 8086:3cb4 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 3f:10.5 0880: 8086:3cb5 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 3f:10.6 0880: 8086:3cb6 (rev 07) Subsystem: 8086:0000 3f:10.7 0880: 8086:3cb7 (rev 07) Subsystem: 8086:0000 3f:11.0 0880: 8086:3cb8 (rev 07) Subsystem: 8086:0000 3f:13.0 0880: 8086:3ce4 (rev 07) Subsystem: 8086:0000 3f:13.1 1101: 8086:3c43 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 3f:13.4 1101: 8086:3ce6 (rev 07) Subsystem: 1028:04fe 3f:13.5 1101: 8086:3c44 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 3f:13.6 0880: 8086:3c45 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 40:01.0 0604: 8086:3c02 (rev 07) DeviceName: SLOT 5 Subsystem: 1028:04fe Kernel driver in use: pcieport 40:02.0 0604: 8086:3c04 (rev 07) DeviceName: SLOT 4 Subsystem: 1028:04fe Kernel driver in use: pcieport 40:02.2 0604: 8086:3c06 (rev 07) DeviceName: SLOT 2 Subsystem: 1028:04fe Kernel driver in use: pcieport 40:03.0 0604: 8086:3c08 (rev 07) DeviceName: SLOT 1 Subsystem: 1028:04fe Kernel driver in use: pcieport 40:04.0 0880: 8086:3c20 (rev 07) Subsystem: 8086:0000 40:04.1 0880: 8086:3c21 (rev 07) Subsystem: 8086:0000 40:04.2 0880: 8086:3c22 (rev 07) Subsystem: 8086:0000 40:04.3 0880: 8086:3c23 (rev 07) Subsystem: 8086:0000 40:04.4 0880: 8086:3c24 (rev 07) Subsystem: 8086:0000 40:04.5 0880: 8086:3c25 (rev 07) Subsystem: 8086:0000 40:04.6 0880: 8086:3c26 (rev 07) Subsystem: 8086:0000 40:04.7 0880: 8086:3c27 (rev 07) Subsystem: 8086:0000 40:05.0 0880: 8086:3c28 (rev 07) Subsystem: 1028:04fe 40:05.2 0880: 8086:3c2a (rev 07) Subsystem: 1028:04fe 42:00.0 0200: 8086:10fb (rev 01) Subsystem: 8086:000c Kernel driver in use: ixgbe Kernel modules: ixgbe 42:00.1 0200: 8086:10fb (rev 01) Subsystem: 8086:000c Kernel modules: ixgbe 44:00.0 0300: 10de:1c30 (rev a1) Subsystem: 103c:11b3 Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia 44:00.1 0403: 10de:10f1 (rev a1) Subsystem: 103c:11b3 7f:08.0 0880: 8086:3c80 (rev 07) Subsystem: 8086:0000 7f:09.0 0880: 8086:3c90 (rev 07) Subsystem: 8086:0000 7f:0a.0 0880: 8086:3cc0 (rev 07) Subsystem: 8086:0000 7f:0a.1 0880: 8086:3cc1 (rev 07) Subsystem: 8086:0000 7f:0a.2 0880: 8086:3cc2 (rev 07) Subsystem: 8086:0000 7f:0a.3 0880: 8086:3cd0 (rev 07) Subsystem: 8086:0000 7f:0b.0 0880: 8086:3ce0 (rev 07) Subsystem: 8086:0000 7f:0b.3 0880: 8086:3ce3 (rev 07) Subsystem: 8086:0000 7f:0c.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0c.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0c.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0c.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0c.6 0880: 8086:3cf4 (rev 07) Subsystem: 8086:0000 7f:0c.7 0880: 8086:3cf6 (rev 07) Subsystem: 8086:0000 7f:0d.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0d.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0d.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0d.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 7f:0d.6 0880: 8086:3cf5 (rev 07) Subsystem: 8086:0000 7f:0e.0 0880: 8086:3ca0 (rev 07) Subsystem: 1028:04fe 7f:0e.1 1101: 8086:3c46 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 7f:0f.0 0880: 8086:3ca8 (rev 07) Subsystem: 8086:0000 7f:0f.1 0880: 8086:3c71 (rev 07) Subsystem: 8086:0000 7f:0f.2 0880: 8086:3caa (rev 07) Subsystem: 8086:0000 7f:0f.3 0880: 8086:3cab (rev 07) Subsystem: 8086:0000 7f:0f.4 0880: 8086:3cac (rev 07) Subsystem: 8086:0000 7f:0f.5 0880: 8086:3cad (rev 07) Subsystem: 8086:0000 7f:0f.6 0880: 8086:3cae (rev 07) Subsystem: 8086:0000 7f:10.0 0880: 8086:3cb0 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 7f:10.1 0880: 8086:3cb1 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 7f:10.2 0880: 8086:3cb2 (rev 07) Subsystem: 8086:0000 7f:10.3 0880: 8086:3cb3 (rev 07) Subsystem: 8086:0000 7f:10.4 0880: 8086:3cb4 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 7f:10.5 0880: 8086:3cb5 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore 7f:10.6 0880: 8086:3cb6 (rev 07) Subsystem: 8086:0000 7f:10.7 0880: 8086:3cb7 (rev 07) Subsystem: 8086:0000 7f:11.0 0880: 8086:3cb8 (rev 07) Subsystem: 8086:0000 7f:13.0 0880: 8086:3ce4 (rev 07) Subsystem: 8086:0000 7f:13.1 1101: 8086:3c43 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 7f:13.4 1101: 8086:3ce6 (rev 07) Subsystem: 1028:04fe 7f:13.5 1101: 8086:3c44 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 7f:13.6 0880: 8086:3c45 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore 80:05.0 0880: 8086:3c28 (rev 07) Subsystem: 1028:04fe bf:08.0 0880: 8086:3c80 (rev 07) Subsystem: 8086:0000 bf:09.0 0880: 8086:3c90 (rev 07) Subsystem: 8086:0000 bf:0a.0 0880: 8086:3cc0 (rev 07) Subsystem: 8086:0000 bf:0a.1 0880: 8086:3cc1 (rev 07) Subsystem: 8086:0000 bf:0a.2 0880: 8086:3cc2 (rev 07) Subsystem: 8086:0000 bf:0a.3 0880: 8086:3cd0 (rev 07) Subsystem: 8086:0000 bf:0b.0 0880: 8086:3ce0 (rev 07) Subsystem: 8086:0000 bf:0b.3 0880: 8086:3ce3 (rev 07) Subsystem: 8086:0000 bf:0c.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0c.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0c.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0c.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0c.6 0880: 8086:3cf4 (rev 07) Subsystem: 8086:0000 bf:0c.7 0880: 8086:3cf6 (rev 07) Subsystem: 8086:0000 bf:0d.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0d.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0d.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0d.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 bf:0d.6 0880: 8086:3cf5 (rev 07) Subsystem: 8086:0000 bf:0e.0 0880: 8086:3ca0 (rev 07) Subsystem: 1028:04fe bf:0e.1 1101: 8086:3c46 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore bf:0f.0 0880: 8086:3ca8 (rev 07) Subsystem: 8086:0000 bf:0f.1 0880: 8086:3c71 (rev 07) Subsystem: 8086:0000 bf:0f.2 0880: 8086:3caa (rev 07) Subsystem: 8086:0000 bf:0f.3 0880: 8086:3cab (rev 07) Subsystem: 8086:0000 bf:0f.4 0880: 8086:3cac (rev 07) Subsystem: 8086:0000 bf:0f.5 0880: 8086:3cad (rev 07) Subsystem: 8086:0000 bf:0f.6 0880: 8086:3cae (rev 07) Subsystem: 8086:0000 bf:10.0 0880: 8086:3cb0 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore bf:10.1 0880: 8086:3cb1 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore bf:10.2 0880: 8086:3cb2 (rev 07) Subsystem: 8086:0000 bf:10.3 0880: 8086:3cb3 (rev 07) Subsystem: 8086:0000 bf:10.4 0880: 8086:3cb4 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore bf:10.5 0880: 8086:3cb5 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore bf:10.6 0880: 8086:3cb6 (rev 07) Subsystem: 8086:0000 bf:10.7 0880: 8086:3cb7 (rev 07) Subsystem: 8086:0000 bf:11.0 0880: 8086:3cb8 (rev 07) Subsystem: 8086:0000 bf:13.0 0880: 8086:3ce4 (rev 07) Subsystem: 8086:0000 bf:13.1 1101: 8086:3c43 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore bf:13.4 1101: 8086:3ce6 (rev 07) Subsystem: 1028:04fe bf:13.5 1101: 8086:3c44 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore bf:13.6 0880: 8086:3c45 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore c0:05.0 0880: 8086:3c28 (rev 07) Subsystem: 1028:04fe ff:08.0 0880: 8086:3c80 (rev 07) Subsystem: 8086:0000 ff:09.0 0880: 8086:3c90 (rev 07) Subsystem: 8086:0000 ff:0a.0 0880: 8086:3cc0 (rev 07) Subsystem: 8086:0000 ff:0a.1 0880: 8086:3cc1 (rev 07) Subsystem: 8086:0000 ff:0a.2 0880: 8086:3cc2 (rev 07) Subsystem: 8086:0000 ff:0a.3 0880: 8086:3cd0 (rev 07) Subsystem: 8086:0000 ff:0b.0 0880: 8086:3ce0 (rev 07) Subsystem: 8086:0000 ff:0b.3 0880: 8086:3ce3 (rev 07) Subsystem: 8086:0000 ff:0c.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0c.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0c.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0c.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0c.6 0880: 8086:3cf4 (rev 07) Subsystem: 8086:0000 ff:0c.7 0880: 8086:3cf6 (rev 07) Subsystem: 8086:0000 ff:0d.0 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0d.1 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0d.2 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0d.3 0880: 8086:3ce8 (rev 07) Subsystem: 8086:0000 ff:0d.6 0880: 8086:3cf5 (rev 07) Subsystem: 8086:0000 ff:0e.0 0880: 8086:3ca0 (rev 07) Subsystem: 1028:04fe ff:0e.1 1101: 8086:3c46 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore ff:0f.0 0880: 8086:3ca8 (rev 07) Subsystem: 8086:0000 ff:0f.1 0880: 8086:3c71 (rev 07) Subsystem: 8086:0000 ff:0f.2 0880: 8086:3caa (rev 07) Subsystem: 8086:0000 ff:0f.3 0880: 8086:3cab (rev 07) Subsystem: 8086:0000 ff:0f.4 0880: 8086:3cac (rev 07) Subsystem: 8086:0000 ff:0f.5 0880: 8086:3cad (rev 07) Subsystem: 8086:0000 ff:0f.6 0880: 8086:3cae (rev 07) Subsystem: 8086:0000 ff:10.0 0880: 8086:3cb0 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore ff:10.1 0880: 8086:3cb1 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore ff:10.2 0880: 8086:3cb2 (rev 07) Subsystem: 8086:0000 ff:10.3 0880: 8086:3cb3 (rev 07) Subsystem: 8086:0000 ff:10.4 0880: 8086:3cb4 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore ff:10.5 0880: 8086:3cb5 (rev 07) Subsystem: 8086:0000 Kernel driver in use: snbep_uncore ff:10.6 0880: 8086:3cb6 (rev 07) Subsystem: 8086:0000 ff:10.7 0880: 8086:3cb7 (rev 07) Subsystem: 8086:0000 ff:11.0 0880: 8086:3cb8 (rev 07) Subsystem: 8086:0000 ff:13.0 0880: 8086:3ce4 (rev 07) Subsystem: 8086:0000 ff:13.1 1101: 8086:3c43 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore ff:13.4 1101: 8086:3ce6 (rev 07) Subsystem: 1028:04fe ff:13.5 1101: 8086:3c44 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore ff:13.6 0880: 8086:3c45 (rev 07) Subsystem: 1028:04fe Kernel driver in use: snbep_uncore

I am running UnRAID on a Dell R820. Currently, I am bonding the 4 1GB NICs into a 4GB channel, and it is working fine. I recently purchased a DELL Intel X520-DA2 X520 10Gb SFP+ Network Adapter 0942V6 0XYT17 E10G42BTDAPG1P5 NIC. I have installed it and UnRAID appears to "see" it, but I cannot get network connectivity over it. Is there anything "special" I need to do to UnRAID in order for it to use this NIC? I have gone into Network Settings, and configured it, but then I loose all network connectivity and I have to pull the Flash drive and remove the settings for the 10GB NIC in order for it to have connectivity again. Here are the settings that I have in network.cfg: # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="no" DHCP6_KEEPRESOLV="no" BONDNAME[0]="bond0" BONDNICS[0]="eth0 eth1 eth2 eth3" BONDING_MODE[0]="4" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRNICS[0]="bond0" BRSTP[0]="no" BRFD[0]="0" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" USE_DHCP6[0]="yes" IFNAME[1]="br4" BRNAME[1]="br4" BRSTP[1]="no" BRFD[1]="0" BRNICS[1]="eth4" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.100.70" NETMASK[1]="255.255.255.0" GATEWAY[1]="192.168.100.1" USE_DHCP6[1]="yes" SYSNICS="2"

@sircompoThanks!

This is really odd... I got a window to reboot my UnRAID box and was able to delete all 3 of the ZFS datasets that were giving me issues.