sureguy

I've eliminated eth1 but the problem persists. New output of ifconfig: root@Phatstore:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 9000 inet6 fe80::21b:21ff:fe4c:233 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 3530 bytes 1707911 (1.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3555 bytes 2419328 (2.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 192.168.3.5 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::7831:80ff:fea8:b412 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 2885 bytes 958663 (936.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1870 bytes 2247105 (2.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::42:68ff:fea2:b842 prefixlen 64 scopeid 0x20<link> ether 02:42:68:a2:b8:42 txqueuelen 0 (Ethernet) RX packets 43 bytes 16594 (16.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 111 bytes 28321 (27.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000 ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 4944 bytes 2927792 (2.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5107 bytes 3036116 (2.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xf79c0000-f79e0000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 46 bytes 24013 (23.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 46 bytes 24013 (23.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth4fd73ef: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::249e:55ff:fe4f:132d prefixlen 64 scopeid 0x20<link> ether 26:9e:55:4f:13:2d txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24 bytes 4513 (4.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth72c2b6f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::ec85:7aff:feb7:6885 prefixlen 64 scopeid 0x20<link> ether ee:85:7a:b7:68:85 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 59 bytes 9497 (9.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethcb9657f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::c42b:abff:fe8c:6cc5 prefixlen 64 scopeid 0x20<link> ether c6:2b:ab:8c:6c:c5 txqueuelen 0 (Ethernet) RX packets 23 bytes 14920 (14.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 118 bytes 19053 (18.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethe7a24c8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::7cd5:8eff:fe9c:deeb prefixlen 64 scopeid 0x20<link> ether 7e:d5:8e:9c:de:eb txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 74 bytes 12197 (11.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethf02c911: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::4033:2dff:fea8:9db4 prefixlen 64 scopeid 0x20<link> ether 42:33:2d:a8:9d:b4 txqueuelen 0 (Ethernet) RX packets 20 bytes 2276 (2.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 84 bytes 24661 (24.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethf45dbe2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::2829:20ff:fe20:40ad prefixlen 64 scopeid 0x20<link> ether 2a:29:20:20:40:ad txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 63 bytes 9813 (9.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:cd:a2:9b txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:feb1:f956 prefixlen 64 scopeid 0x20<link> ether fe:54:00:b1:f9:56 txqueuelen 1000 (Ethernet) RX packets 182 bytes 26149 (25.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 548 bytes 270968 (264.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fee2:4e5f prefixlen 64 scopeid 0x20<link> ether fe:54:00:e2:4e:5f txqueuelen 1000 (Ethernet) RX packets 219 bytes 33064 (32.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 576 bytes 280055 (273.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fe44:dd23 prefixlen 64 scopeid 0x20<link> ether fe:54:00:44:dd:23 txqueuelen 1000 (Ethernet) RX packets 255 bytes 24056 (23.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 622 bytes 311214 (303.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0 is my onboard nic - which I disabled in the bios as part of my troubleshooting. I'm not sure why unraid decided to assign my NIC to eth1. Attached is my network.cfg: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="1" BONDNICS[0]="eth0 eth1" BRNICS[0]="bond0" DESCRIPTION[0]="" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.3.5" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.3.254" METRIC[0]="" DNS_SERVER1="192.168.3.250" DNS_SERVER2="192.168.3.198" DNS_SERVER3="" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" MTU[0]="9000" SYSNICS="1"

Yes Jumbo Frames are enabled on my router, and my switch supports 15K jumbo frames. I booted a live linux distro from my unraid server, and ran ping -s 9000 to both my router and workstation without issue. So it's not a problem with any of the hardware being used. Below is the output of me pinging from my router: unraid (192.168.3.5) with 1504 bytes, unraid (192.168.3.5) with 1505 bytes, a ubuntu VM (192.168.3.198) hosted on unraid with 9000 bytes: root@unknown:/tmp/home/root# ping 192.168.3.5 -c 4 -s 1504 PING 192.168.3.5 (192.168.3.5): 1504 data bytes 1512 bytes from 192.168.3.5: seq=0 ttl=64 time=0.870 ms 1512 bytes from 192.168.3.5: seq=1 ttl=64 time=0.470 ms 1512 bytes from 192.168.3.5: seq=2 ttl=64 time=1.977 ms 1512 bytes from 192.168.3.5: seq=3 ttl=64 time=0.615 ms --- 192.168.3.5 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 0.470/0.983/1.977 ms root@unknown:/tmp/home/root# ping 192.168.3.5 -c 4 -s 1505 PING 192.168.3.5 (192.168.3.5): 1505 data bytes --- 192.168.3.5 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss root@unknown:/tmp/home/root# ping 192.168.3.198 -c 4 -s 9000 PING 192.168.3.198 (192.168.3.198): 9000 data bytes 9008 bytes from 192.168.3.198: seq=0 ttl=64 time=5.254 ms 9008 bytes from 192.168.3.198: seq=1 ttl=64 time=1.241 ms 9008 bytes from 192.168.3.198: seq=2 ttl=64 time=1.034 ms 9008 bytes from 192.168.3.198: seq=3 ttl=64 time=1.063 ms --- 192.168.3.198 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.034/2.148/5.254 ms

I've tried in 6.3.5 and 6.4.0_rc18f. I"ve booted ubuntu 16.04.3 Desktop live from usb on the same hardware and the issue doesn't exist. Basically if I ping (my workstation or router) with a size greater than 1504 from unraid the ping fails. The same thing happens if I ping unraid from these devices. I've disabled my onboard NIC as it's not being used. The NIC is an "Intel Corporation 82574L Gigabit Network Connection PCIE card. I can even use jumbo frames from within VMs hosted on unRAID and ping my router or workstation with 9000 byte packets. Any suggestions on how to resolve this issue would be appreciated. Currently running 6.4.0_rc18f the output of ifconfig and ethtool follow: root@Phatstore:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 9000 inet6 fe80::21b:21ff:fe4c:233 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 42682 bytes 59851034 (57.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24282 bytes 2824528 (2.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 192.168.3.5 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::b0ce:3bff:fe18:71e8 prefixlen 64 scopeid 0x20<link> ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 41635 bytes 58363303 (55.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22821 bytes 2550997 (2.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::42:b5ff:fefe:4cbe prefixlen 64 scopeid 0x20<link> ether 02:42:b5:fe:4c:be txqueuelen 0 (Ethernet) RX packets 18414 bytes 1294607 (1.2 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 33881 bytes 49590312 (47.2 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000 ether 00:1b:21:4c:02:33 txqueuelen 1000 (Ethernet) RX packets 42682 bytes 59851034 (57.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24282 bytes 2824528 (2.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xf79c0000-f79e0000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2205 bytes 1039524 (1015.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2205 bytes 1039524 (1015.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth38984e9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::5440:dfff:fea6:31c2 prefixlen 64 scopeid 0x20<link> ether 56:40:df:a6:31:c2 txqueuelen 0 (Ethernet) RX packets 17204 bytes 1145249 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 32662 bytes 49118877 (46.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth62466e9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::1452:88ff:feca:98ef prefixlen 64 scopeid 0x20<link> ether 16:52:88:ca:98:ef txqueuelen 0 (Ethernet) RX packets 3 bytes 138 (138.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 267 bytes 30010 (29.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth67b76ef: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc3c:9cff:fef3:59e1 prefixlen 64 scopeid 0x20<link> ether fe:3c:9c:f3:59:e1 txqueuelen 0 (Ethernet) RX packets 509 bytes 333141 (325.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 811 bytes 91753 (89.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth6871e2b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::78e3:eff:fe65:9b80 prefixlen 64 scopeid 0x20<link> ether 7a:e3:0e:65:9b:80 txqueuelen 0 (Ethernet) RX packets 360 bytes 39419 (38.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 632 bytes 271505 (265.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth6b5b5fa: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::54c1:13ff:feac:7a17 prefixlen 64 scopeid 0x20<link> ether 56:c1:13:ac:7a:17 txqueuelen 0 (Ethernet) RX packets 189 bytes 18172 (17.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 430 bytes 107104 (104.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vetha3e3d5a: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::8833:24ff:fec0:b352 prefixlen 64 scopeid 0x20<link> ether 8a:33:24:c0:b3:52 txqueuelen 0 (Ethernet) RX packets 149 bytes 16284 (15.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 418 bytes 123108 (120.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:cd:a2:9b txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fee2:4e5f prefixlen 64 scopeid 0x20<link> ether fe:54:00:e2:4e:5f txqueuelen 1000 (Ethernet) RX packets 359 bytes 55360 (54.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1386 bytes 518894 (506.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:feb1:f956 prefixlen 64 scopeid 0x20<link> ether fe:54:00:b1:f9:56 txqueuelen 1000 (Ethernet) RX packets 232 bytes 31416 (30.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1290 bytes 494438 (482.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet6 fe80::fc54:ff:fe44:dd23 prefixlen 64 scopeid 0x20<link> ether fe:54:00:44:dd:23 txqueuelen 1000 (Ethernet) RX packets 477 bytes 43040 (42.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1511 bytes 546422 (533.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@Phatstore:~# ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: on (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes root@Phatstore:~# ethtool bond0 Settings for bond0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 1000Mb/s Duplex: Full Port: Other PHYAD: 0 Transceiver: internal Auto-negotiation: off Link detected: yes

Just in case anyone runs into this error, the solution is pretty simple. In the official Plex docker there is a host path for the transcode folder. I set mine to a location in mnt/user (on the cache drive) and also tried pointing it directly to the same folder using /mnt/cache but still got these errors. Setting the host path for transcode to /tmp (which is in RAM) resolved this issue. I have direct IO enabled, so it's possible that's causing an issue as well.

Did you recently enable direct IO by any chance? If so put the docker in privileged mode or point the config to /mnt/cache/Docker/appdata/whatever rather than /mnt/user/Docker/appdata/whatever

The URL should be safe to post.

Do it via the web gui.

I believe you can assign all drives as data drives and the one that is unformatted is your parity drive. And then if you have a cash drive I'm not sure how you're going to deal with that, sorry.

LimeTech has stated they only support unRAID running directly on the hardware. People have posted work arounds for the issue on this thread. I recommend trying one of those.

I must be missing something as I have two USB devices passed through to my unraid 6.1.3 (booted via plop) running on ESXi 5.5.0.3116895. The log file is full of errors from both usb drives :-( Nov 2 18:04:25 unraid kernel: usb 1-2: reset high-speed USB device number 3 using ehci-pci Nov 2 18:04:26 unraid kernel: sd 4:0:0:0: [sdj] 7975296 512-byte logical blocks: (4.08 GB/3.80 GiB) Nov 2 18:05:01 unraid kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci Nov 2 18:05:01 unraid kernel: sd 3:0:0:0: [sdi] 30529536 512-byte logical blocks: (15.6 GB/14.5 GiB) I can't recall anyone mentioning plop with the dual USB solution. You might want to try the vmdk method to see if it makes a difference.

I'd update to the latest version of unraid, support on a beta is going to be tough as most people are running the official release at this point

Well the reason I'm asking is that the two drives I have attached to my on board SATA ports don't show up in my unRAID VM though I did confirm the are detected in the BIOS. Sorry, missed the fact that you're running under esxi You missed it in the Virtualizing unRAID forum? It's ok I'll give you a pass . Tapatalk on mobile, doesn't show the forum name, at least not the version I am running

Well the reason I'm asking is that the two drives I have attached to my on board SATA ports don't show up in my unRAID VM though I did confirm the are detected in the BIOS. Sorry, missed the fact that you're running under esxi

That should work fine

Why not just download and run preclear against the drives? Wipes them and ensures they're good, although it's slower.

Unraid under ESXi isn't supported. I run it though. This is apparently a kernel issue, so until its fixed and unraid moves to that kernel you're out of luck unless you use one of the previously mentioned work arounds.

Agreed on the roku, for a better experience use ethernet rather than WiFi if possible ...or if stuck with WiFi, should be 5GHz. 2.4GHz just doesn't have the bandwidth needed. I have a FireStick on 5GHz and no buffering issues, 20Mbit cable. 5GHz has penetration/range issues, 2.4GHz has bandwidth/crowded channel issues. Pick your poison. At least you can throw money at 5GHz to fix it.

Agreed on the roku, for a better experience use ethernet rather than WiFi if possible

Once you remove the two drives and restart the array you will need to do new config to rebuild parity.

Yes

You cannot restart emhttp on unraid 5+. I'm mobile, so you'll need to search for unraid 5 manual shut down

I can't remember what files are responsible for the credentials off hand, but if you delete them they should be recreated on a reboot. Have you run check disk on the flash drive?

Sonarr should move the show to the folder you specified for the show or the folder that was found when you scanned your TV library. I don't use sonarr as a docker though.

I believe that the docker site was down earlier today.