Munce31

Same thing for me after upgrading. Could anyone shine a light on why these IPv6 routes were created?

Is this still a current issue? I've been looking for backup solution for my server and was thinking that Duplicati was it, however after reading posts on this forum, I am having my doubts...

I've just updated to 6.8 but I cannot access my GUI. The server is definitely working as my pfsense VM is working, otherwise I wouldn't have internet. Am I missing something with this release? I usually access my server via ip address - also tried <servername>.local - but that's not working either. EDIT: I now have access to my unraid server, but only after I deleted the static ip address assignment I had for it in pfsense and rebooted server. Is there an issue with static ipaddress assignment and 6.8?

Hi BRiT My log still remains at 1% of capacity, which is good. However, I did run the command you specified: -[0000:00]-+-00.0 Intel Corporation 8th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] +-02.0 Intel Corporation UHD Graphics 630 (Desktop 9 Series) +-12.0 Intel Corporation Cannon Lake PCH Thermal Controller +-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller +-14.2 Intel Corporation Cannon Lake PCH Shared SRAM +-14.3 Intel Corporation Wireless-AC 9560 [Jefferson Peak] +-16.0 Intel Corporation Cannon Lake PCH HECI Controller +-17.0 Intel Corporation Cannon Lake PCH SATA AHCI Controller +-1b.0-[01]-- +-1b.4-[02]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 +-1c.0-[03]-- +-1d.0-[04]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 +-1f.0 Intel Corporation Z390 Chipset LPC/eSPI Controller +-1f.3 Intel Corporation Cannon Lake PCH cAVS +-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller +-1f.5 Intel Corporation Cannon Lake PCH SPI Controller \-1f.6 Intel Corporation Ethernet Connection (7) I219-V Appears to be one of my NVme SSD's. As the log hasn't gone crazy, i'll continue to monitor and report back here if the log starts to go crazy again. Thanks

I rebooted the server. This has appeared to fix it. It has been at least 24 hours and the log file remains at 1% of capacity. Hopefully it stays that way for a while. Thanks👍

Hi My log on my dashboard is showing at 79% full. I ran the diagnostics (I've attached this) and have found that a PCIE bus error is spamming my syslog. Jul 3 07:25:35 Hawkie kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Jul 3 07:25:35 Hawkie kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Jul 3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Jul 3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Jul 3 07:25:36 Hawkie kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Jul 3 07:25:39 Hawkie kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Jul 3 07:25:39 Hawkie kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Device [8086:a32c] is in reference to the following: IOMMU group 7:[8086:a32c] 00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0) My question is: How can I find out what is plugged into port #21 and stop it from spamming my syslog files? Thanks in advance, Munce31 hawkie-diagnostics-20190703-1057.zip

Ahh that may be the difference - dedicated GPU. What happens with me, is that i can see everything on the console up until it gets to the desktop. At the desktop it appears to download a 350 mb update and at the conclusion of the update it reboots and is never seen again. Just a blank screen with an enlarged mouse cursor. However, steamos specifically states that it supports intel gpu.. so theoretically it should work,

I'm having this same issue. Doesn't seems like a common to be installed via VM on unraid though, hence the lack of support...

Hi, Thanks. That recommendation worked for me as well.. Will have to use this version until the latest is fixed. Btw the error I was receiving in the log is as follows: Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support. Hope that helps. Regards.