Jump to content

Hoopster

Members
  • Content Count

    1843
  • Joined

  • Last visited

  • Days Won

    10

Hoopster last won the day on October 9

Hoopster had the most liked content!

Community Reputation

233 Very Good

2 Followers

About Hoopster

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Utah USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. First, enable the SMB protocol in Settings > SMB (Note: I am running the unRAID 6.8.0 release candidate. The WSD and Enable NetBIOS options will not appear if you are on a prior version of unRAID). For the shares you want to be exported, click on the share name in the Shares tab and select the desired SMB security settings. The exported shares should then show up in Windows. Note, depending on Windows settings, your server may or may not show up by name under Network in the File Explorer. If the server name does not appear (there is an entire thread in this forums dedicated to such problems but it involves enabling SMB v1.0 on the Windows machine), you can always access it via IP address.
  2. If your files are stored on a WIndows computer you export your shares via SMB (or NFS, AFP for linux or MacOS) and they show up in Windows as Network shares. You can just copy files from the computer over to unRAID shares. By the way SMB works better on MacOS than AFP these days. If they are on an external drive, you can mount that drive through the Unassigned Devices plugin and copy the files to unRAID via the command line or a file manager docker container such as Krusader or Dolphin. Where are the files you want on the unRAID server currently stored?
  3. Nope, that's not it. I upgraded my backup server to 6.8.0-RC1, It has virtually the same 'go' file entries. i915 drivers load without issue with no call trace: Oct 15 18:00:28 BackupNAS root: plugin: installed Oct 15 18:00:28 BackupNAS root: Starting go script Oct 15 18:00:28 BackupNAS kernel: Linux agpgart interface v0.103 Oct 15 18:00:28 BackupNAS kernel: i915 0000:00:02.0: enabling device (0000 -> 0003) Oct 15 18:00:28 BackupNAS kernel: [drm] VT-d active for gfx access Oct 15 18:00:28 BackupNAS kernel: [drm] DMAR active, disabling use of stolen memory Oct 15 18:00:28 BackupNAS kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Oct 15 18:00:28 BackupNAS kernel: [drm] Driver supports precise vblank timestamp query. Oct 15 18:00:28 BackupNAS kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none Oct 15 18:00:28 BackupNAS kernel: [drm] Initialized i915 1.6.0 20190619 for 0000:00:02.0 on minor 0 Oct 15 18:00:28 BackupNAS kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) Oct 15 18:00:28 BackupNAS kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 Oct 15 18:00:28 BackupNAS kernel: [drm] Cannot find any crtc or sizes Oct 15 18:00:28 BackupNAS root: Starting emhttpd It also has none of the errors highlighted in this problem report. The backup server boots with a fairly clean syslog. Of course, the hardware and configuration are different. Backup server diagnostics attached for comparison. backupnas-diagnostics-20191016-0005.zip
  4. You could also designate a "remote syslog server" location.
  5. No big deal. I was just seeking confirmation that was the case so I did not start troubleshooting something needlessly.
  6. If your appdata (or domains, iso, system) is on the cache drive, the local syslog can be set to write to appdata. However, no array means no appdata, etc. so if the array does not start you still can't get to the log. The flash drive appears to be the only currently available location outside the array.
  7. Just curious if there are known issues with ControlR and 6.8.0-RC1? I cant access my server through ControlR since updating to the RC. This is true on both the local LAN and via VPN
  8. Are some of my issues a few posts back possibly related to 'go' file entries? #Setup drivers for hardware decoding in Plex modprobe i915 sleep 4 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri # Copy SSH files back to /root/.ssh folder and set permissions for files mkdir -p /root/.ssh cp /boot/config/ssh/medianas_key /root/.ssh/id_rsa cp /boot/config/ssh/known_hosts /root/.ssh/known_hosts cat /boot/config/ssh/backupnas_key.pub > /root/.ssh/authorized_keys chmod g-rwx,o-rwx -R /root/.ssh #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & That is where modprobe i915 is executed. I am also setting up ssh keys for doing an unattended backup via rsync between two unRAID servers. I know the permissions/security on the flash drive have changed. Is this causing problems? Go file is copied to /tmp and executed there, correct? I also see several of these errors in the syslog: Oct 14 23:40:36 MediaNAS kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful As far as I can tell, i915 loads and functions as Plex still claims it is hardware decoding and encoding. I watched a few shows last night after upgrading and forced transcoding and Plex/Tautulli claimed (hw) transcoding was happening. I have not yet tried to execute the unattended backup as a parity sync kicked off at 1am and is about 50% complete. The backup runs on Monday at 1am and executed properly (as it always does) yesterday before the upgrade to 6.8.0-RC1. Again, as far as I can tell, the server appears to be functioning normally, but, I really have not done too much with it yet since the upgrade late last night.
  9. Just upgraded to 6.8.0-RC-1. Syslog contains a bunch of the following errors: Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 7: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Also, I get a call trace that seems to be related to the i915 video module: Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour dummy device 80x25 Oct 14 23:04:52 MediaNAS kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Oct 14 23:04:52 MediaNAS kernel: [drm] Driver supports precise vblank timestamp query. Oct 14 23:04:52 MediaNAS kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 14 23:04:52 MediaNAS kernel: [drm] Disabling framebuffer compression (FBC) to prevent screen flicker with VT-d enabled Oct 14 23:04:52 MediaNAS kernel: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27) Oct 14 23:04:52 MediaNAS kernel: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 48: Can't calculate constants, dotclock = 0! Oct 14 23:04:52 MediaNAS kernel: WARNING: CPU: 2 PID: 7789 at drivers/gpu/drm/drm_vblank.c:638 drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm] Oct 14 23:04:52 MediaNAS kernel: Modules linked in: i915(+) iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid e1000e igb i2c_algo_bit sr_mod cdrom x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd mpt3sas glue_helper raid_class i2c_i801 intel_cstate intel_uncore mxm_wmi i2c_core ahci intel_rapl_perf video wmi scsi_transport_sas backlight libahci acpi_pad button ie31200_edac [last unloaded: e1000e] Oct 14 23:04:52 MediaNAS kernel: CPU: 2 PID: 7789 Comm: modprobe Not tainted 5.3.6-Unraid #1 Oct 14 23:04:52 MediaNAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C236 WSI, BIOS P2.60 03/06/2018 Oct 14 23:04:52 MediaNAS kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm] Oct 14 23:04:52 MediaNAS kernel: Code: 43 20 8b 80 78 01 00 00 23 43 50 a8 10 75 1b 48 8b 83 28 03 00 00 48 85 c0 0f 84 5b ff ff ff 48 83 78 28 00 0f 84 50 ff ff ff <0f> 0b e9 44 01 00 00 48 8b 43 20 48 8d 55 c0 41 57 44 89 f6 52 4c Oct 14 23:04:52 MediaNAS kernel: RSP: 0018:ffffc90003dff7e8 EFLAGS: 00010002 Oct 14 23:04:52 MediaNAS kernel: RAX: 000000000000003f RBX: ffff888815b00000 RCX: ffffc90003dff888 Oct 14 23:04:52 MediaNAS kernel: RDX: 0000000000000000 RSI: ffffffffa0314379 RDI: 0000000000000001 Oct 14 23:04:52 MediaNAS kernel: RBP: ffffc90003dff850 R08: 0000000000000000 R09: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000000002 R11: ffff88884678e000 R12: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff888846789080 Oct 14 23:04:52 MediaNAS kernel: FS: 0000153176da5b80(0000) GS:ffff88884de80000(0000) knlGS:0000000000000000 Oct 14 23:04:52 MediaNAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 14 23:04:52 MediaNAS kernel: CR2: 000000000052a020 CR3: 0000000848700005 CR4: 00000000003606e0 Oct 14 23:04:52 MediaNAS kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Oct 14 23:04:52 MediaNAS kernel: Call Trace: Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc+0x41/0x63 Oct 14 23:04:52 MediaNAS kernel: ? drm_calc_timestamping_constants+0xac/0x12c [drm] Oct 14 23:04:52 MediaNAS kernel: drm_get_last_vbltimestamp+0x54/0x73 [drm] Oct 14 23:04:52 MediaNAS kernel: drm_reset_vblank_timestamp+0x58/0xc2 [drm] Oct 14 23:04:52 MediaNAS kernel: drm_crtc_vblank_on+0x8f/0xcf [drm] Oct 14 23:04:52 MediaNAS kernel: intel_modeset_setup_hw_state+0x786/0x1059 [i915] Oct 14 23:04:52 MediaNAS kernel: intel_modeset_init+0x11a9/0x16e8 [i915] Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915] Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915] Oct 14 23:04:52 MediaNAS kernel: i915_driver_load+0x108b/0x133f [i915] Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc_cyclic+0x53/0xa7 Oct 14 23:04:52 MediaNAS kernel: ? rpm_resume+0x9b/0x409 Oct 14 23:04:52 MediaNAS kernel: i915_pci_probe+0x108/0x12a [i915] Oct 14 23:04:52 MediaNAS kernel: local_pci_probe+0x3c/0x7a Oct 14 23:04:52 MediaNAS kernel: pci_device_probe+0x13c/0x196 Oct 14 23:04:52 MediaNAS kernel: ? sysfs_do_create_link_sd.isra.0+0x80/0xad Oct 14 23:04:52 MediaNAS kernel: really_probe+0x145/0x283 Oct 14 23:04:52 MediaNAS kernel: driver_probe_device+0x9c/0xd1 Oct 14 23:04:52 MediaNAS kernel: device_driver_attach+0x37/0x50 Oct 14 23:04:52 MediaNAS kernel: __driver_attach+0x95/0x9d Oct 14 23:04:52 MediaNAS kernel: ? device_driver_attach+0x50/0x50 Oct 14 23:04:52 MediaNAS kernel: bus_for_each_dev+0x70/0xa6 Oct 14 23:04:52 MediaNAS kernel: bus_add_driver+0xfb/0x1a9 Oct 14 23:04:52 MediaNAS kernel: driver_register+0x99/0xcf Oct 14 23:04:52 MediaNAS kernel: ? 0xffffffffa04c6000 Oct 14 23:04:52 MediaNAS kernel: do_one_initcall+0x71/0x166 Oct 14 23:04:52 MediaNAS kernel: ? __vunmap+0x1c2/0x1e0 Oct 14 23:04:52 MediaNAS kernel: ? _cond_resched+0x1b/0x1e Oct 14 23:04:52 MediaNAS kernel: ? kmem_cache_alloc+0x30/0x128 Oct 14 23:04:52 MediaNAS kernel: do_init_module+0x51/0x1da Oct 14 23:04:52 MediaNAS kernel: load_module+0x19a1/0x1f95 Oct 14 23:04:52 MediaNAS kernel: ? __se_sys_init_module+0xd5/0x116 Oct 14 23:04:52 MediaNAS kernel: __se_sys_init_module+0xd5/0x116 Oct 14 23:04:52 MediaNAS kernel: do_syscall_64+0x57/0xfd Oct 14 23:04:52 MediaNAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 14 23:04:52 MediaNAS kernel: RIP: 0033:0x153176ee013a Oct 14 23:04:52 MediaNAS kernel: Code: 48 8b 0d 59 7d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 26 7d 0c 00 f7 d8 64 89 01 48 Oct 14 23:04:52 MediaNAS kernel: RSP: 002b:00007ffcdf22fde8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Oct 14 23:04:52 MediaNAS kernel: RAX: ffffffffffffffda RBX: 0000000000427e30 RCX: 0000153176ee013a Oct 14 23:04:52 MediaNAS kernel: RDX: 000000000041b400 RSI: 00000000002c38a8 RDI: 0000000000d3f810 Oct 14 23:04:52 MediaNAS kernel: RBP: 000000000041b400 R08: 000000000042501a R09: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000425010 R11: 0000000000000246 R12: 0000000000d3f810 Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000427f40 R14: 0000000000040000 R15: 0000000000427e30 Oct 14 23:04:52 MediaNAS kernel: ---[ end trace c13b68bd66095883 ]--- Oct 14 23:04:52 MediaNAS kernel: [drm] Initialized i915 1.6.0 20190619 for 0000:00:02.0 on minor 0 Oct 14 23:04:52 MediaNAS kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) Oct 14 23:04:52 MediaNAS kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 Oct 14 23:04:52 MediaNAS kernel: fbcon: i915drmfb (fb0) is primary device Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour frame buffer device 128x48 Oct 14 23:04:54 MediaNAS kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device Oct 14 23:04:56 MediaNAS kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Oct 14 23:04:58 MediaNAS root: Starting emhttpd System seems to currently be running OK, but, I have not really tried to do anything other than install the WireGuard plugin (not currently configured or active). Of course, I don't consider these things to be the result of any "bug" but is there something I can look at to track down the cause of these issues that only began with 6.8.0-RC1? Diagnostics attached. medianas-diagnostics-20191015-0512.zip
  10. Sure, I did not think this was a "bug" necessarily so I did not know if it belonged there. I will make the report in that thread for tracking purposes.
  11. Yes, custom networks show up in 6.8.0-RC1. Both of mine are in the list. You must have an issue that prevents custom networks from being available.
  12. I'd like to do something like this to force VPN clients through Pihole - running on a RPi on LAN and set as DNS on my router. unRAID DNS point to Cloudflare. Perhaps I'll give @Xaero 's suggestion a try once I have WireGuard setup tomorrow.
  13. Just upgraded to 6.8.0-RC-1. Syslog is full of the following errors: Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 7: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ] Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Also, I get a call trace that seems to be related to the i915 video module; Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour dummy device 80x25 Oct 14 23:04:52 MediaNAS kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Oct 14 23:04:52 MediaNAS kernel: [drm] Driver supports precise vblank timestamp query. Oct 14 23:04:52 MediaNAS kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 14 23:04:52 MediaNAS kernel: [drm] Disabling framebuffer compression (FBC) to prevent screen flicker with VT-d enabled Oct 14 23:04:52 MediaNAS kernel: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27) Oct 14 23:04:52 MediaNAS kernel: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 48: Can't calculate constants, dotclock = 0! Oct 14 23:04:52 MediaNAS kernel: WARNING: CPU: 2 PID: 7789 at drivers/gpu/drm/drm_vblank.c:638 drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm] Oct 14 23:04:52 MediaNAS kernel: Modules linked in: i915(+) iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid e1000e igb i2c_algo_bit sr_mod cdrom x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd mpt3sas glue_helper raid_class i2c_i801 intel_cstate intel_uncore mxm_wmi i2c_core ahci intel_rapl_perf video wmi scsi_transport_sas backlight libahci acpi_pad button ie31200_edac [last unloaded: e1000e] Oct 14 23:04:52 MediaNAS kernel: CPU: 2 PID: 7789 Comm: modprobe Not tainted 5.3.6-Unraid #1 Oct 14 23:04:52 MediaNAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C236 WSI, BIOS P2.60 03/06/2018 Oct 14 23:04:52 MediaNAS kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm] Oct 14 23:04:52 MediaNAS kernel: Code: 43 20 8b 80 78 01 00 00 23 43 50 a8 10 75 1b 48 8b 83 28 03 00 00 48 85 c0 0f 84 5b ff ff ff 48 83 78 28 00 0f 84 50 ff ff ff <0f> 0b e9 44 01 00 00 48 8b 43 20 48 8d 55 c0 41 57 44 89 f6 52 4c Oct 14 23:04:52 MediaNAS kernel: RSP: 0018:ffffc90003dff7e8 EFLAGS: 00010002 Oct 14 23:04:52 MediaNAS kernel: RAX: 000000000000003f RBX: ffff888815b00000 RCX: ffffc90003dff888 Oct 14 23:04:52 MediaNAS kernel: RDX: 0000000000000000 RSI: ffffffffa0314379 RDI: 0000000000000001 Oct 14 23:04:52 MediaNAS kernel: RBP: ffffc90003dff850 R08: 0000000000000000 R09: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000000002 R11: ffff88884678e000 R12: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff888846789080 Oct 14 23:04:52 MediaNAS kernel: FS: 0000153176da5b80(0000) GS:ffff88884de80000(0000) knlGS:0000000000000000 Oct 14 23:04:52 MediaNAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 14 23:04:52 MediaNAS kernel: CR2: 000000000052a020 CR3: 0000000848700005 CR4: 00000000003606e0 Oct 14 23:04:52 MediaNAS kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Oct 14 23:04:52 MediaNAS kernel: Call Trace: Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc+0x41/0x63 Oct 14 23:04:52 MediaNAS kernel: ? drm_calc_timestamping_constants+0xac/0x12c [drm] Oct 14 23:04:52 MediaNAS kernel: drm_get_last_vbltimestamp+0x54/0x73 [drm] Oct 14 23:04:52 MediaNAS kernel: drm_reset_vblank_timestamp+0x58/0xc2 [drm] Oct 14 23:04:52 MediaNAS kernel: drm_crtc_vblank_on+0x8f/0xcf [drm] Oct 14 23:04:52 MediaNAS kernel: intel_modeset_setup_hw_state+0x786/0x1059 [i915] Oct 14 23:04:52 MediaNAS kernel: intel_modeset_init+0x11a9/0x16e8 [i915] Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915] Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915] Oct 14 23:04:52 MediaNAS kernel: i915_driver_load+0x108b/0x133f [i915] Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc_cyclic+0x53/0xa7 Oct 14 23:04:52 MediaNAS kernel: ? rpm_resume+0x9b/0x409 Oct 14 23:04:52 MediaNAS kernel: i915_pci_probe+0x108/0x12a [i915] Oct 14 23:04:52 MediaNAS kernel: local_pci_probe+0x3c/0x7a Oct 14 23:04:52 MediaNAS kernel: pci_device_probe+0x13c/0x196 Oct 14 23:04:52 MediaNAS kernel: ? sysfs_do_create_link_sd.isra.0+0x80/0xad Oct 14 23:04:52 MediaNAS kernel: really_probe+0x145/0x283 Oct 14 23:04:52 MediaNAS kernel: driver_probe_device+0x9c/0xd1 Oct 14 23:04:52 MediaNAS kernel: device_driver_attach+0x37/0x50 Oct 14 23:04:52 MediaNAS kernel: __driver_attach+0x95/0x9d Oct 14 23:04:52 MediaNAS kernel: ? device_driver_attach+0x50/0x50 Oct 14 23:04:52 MediaNAS kernel: bus_for_each_dev+0x70/0xa6 Oct 14 23:04:52 MediaNAS kernel: bus_add_driver+0xfb/0x1a9 Oct 14 23:04:52 MediaNAS kernel: driver_register+0x99/0xcf Oct 14 23:04:52 MediaNAS kernel: ? 0xffffffffa04c6000 Oct 14 23:04:52 MediaNAS kernel: do_one_initcall+0x71/0x166 Oct 14 23:04:52 MediaNAS kernel: ? __vunmap+0x1c2/0x1e0 Oct 14 23:04:52 MediaNAS kernel: ? _cond_resched+0x1b/0x1e Oct 14 23:04:52 MediaNAS kernel: ? kmem_cache_alloc+0x30/0x128 Oct 14 23:04:52 MediaNAS kernel: do_init_module+0x51/0x1da Oct 14 23:04:52 MediaNAS kernel: load_module+0x19a1/0x1f95 Oct 14 23:04:52 MediaNAS kernel: ? __se_sys_init_module+0xd5/0x116 Oct 14 23:04:52 MediaNAS kernel: __se_sys_init_module+0xd5/0x116 Oct 14 23:04:52 MediaNAS kernel: do_syscall_64+0x57/0xfd Oct 14 23:04:52 MediaNAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 14 23:04:52 MediaNAS kernel: RIP: 0033:0x153176ee013a Oct 14 23:04:52 MediaNAS kernel: Code: 48 8b 0d 59 7d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 26 7d 0c 00 f7 d8 64 89 01 48 Oct 14 23:04:52 MediaNAS kernel: RSP: 002b:00007ffcdf22fde8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Oct 14 23:04:52 MediaNAS kernel: RAX: ffffffffffffffda RBX: 0000000000427e30 RCX: 0000153176ee013a Oct 14 23:04:52 MediaNAS kernel: RDX: 000000000041b400 RSI: 00000000002c38a8 RDI: 0000000000d3f810 Oct 14 23:04:52 MediaNAS kernel: RBP: 000000000041b400 R08: 000000000042501a R09: 0000000000000000 Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000425010 R11: 0000000000000246 R12: 0000000000d3f810 Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000427f40 R14: 0000000000040000 R15: 0000000000427e30 Oct 14 23:04:52 MediaNAS kernel: ---[ end trace c13b68bd66095883 ]--- Oct 14 23:04:52 MediaNAS kernel: [drm] Initialized i915 1.6.0 20190619 for 0000:00:02.0 on minor 0 Oct 14 23:04:52 MediaNAS kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) Oct 14 23:04:52 MediaNAS kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 Oct 14 23:04:52 MediaNAS kernel: fbcon: i915drmfb (fb0) is primary device Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour frame buffer device 128x48 Oct 14 23:04:54 MediaNAS kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device Oct 14 23:04:56 MediaNAS kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Oct 14 23:04:58 MediaNAS root: Starting emhttpd System seems to currently be running OK, but, I have not really tried to do anything other than install the WireGuard plugin (not currently configured or active). Of course, I don't consider these things to be the result of any "bug" but it there something I can look at to track down the cause of these issues that only began with 6.8.0-RC1 Diagnostics attached. medianas-diagnostics-20191015-0512.zip
  14. The issue wasn't unRAID per se, rather it was the Linux kernel (4.19.x) used in prior versions of unRAID. The 6.8.0-RC1 release uses the 5.3.6 Linux kernel in which 9th gen iGPUs should be supported. If you care about this for Plex transcoding purposes, a recent Plex Media Server release now also supports 9th generation iGPUs.
  15. I have created VLANs on the same physical NIC. My server has two NICs but I am using eth1 for something else. @bonienl wrote a very good guide on creating VLANs for docker, VMs, etc. I followed that guide and it works beautifully. I have Ubiquiti UniFi routers and switches which support VLANs very well.