SuudoXR

My server atm is just running a 7th gen intel on a Gigabyte GA-Z170M-D3H. Works fine for the purpose of a NAS but not exactly bleeding edge or server grade

I use intel nics on my server and have no issues same as you, think the general theme I see on the forum is to stick with intel based devices

Taken from https://wiki.unraid.net/Hardware_Compatibility Network Controllers Broadcomm BCM5751 Gigabit PCIe x1 D-Link DGE-528T Gigabit Ethernet (from v4.1) ***NOTE - THIS CARD IS NO LONGER SUPPORTED SINCE 5rc5 DUE TO LINUX DRIVER ISSUES*** Intel 82566DC Gigabit LAN chipset Intel PRO/1000 Gigabit Ethernet Intel PRO/100 Ethernet Linksys LNE100TX Marvell Yukon Gigabit Ethernet Netgear GA311 Gigabit Ethernet - uses Realtek, may have issues noted below Realtek - RTL8169S, RTL8111B, RTL8111C, probably others too ***NOTE - MANY PEOPLE REPORT ISSUES WITH REALTEK, SO CHECK THE FORUMS BEFORE ASSUMING YOUR BOARD WILL WORK*** Others that use the same chipsets as the controllers above Whilst exhaustive lists are implicitly difficult due to the volume of hardware vendors and models around the wiki does make a point to comment on Realtek devices. Cheers, SuudoXR

Same as above thanks to all involved in helping resolve, working as expected now.

I am seeing the same issues as you, I detailed my troubleshooting in this thread under general support:

Hate to keep bumping but no closer to figuring this out, would anyone be will to provide a copy of there sysylog.conf (with personal info redacted) so I can at least compare with a working one? To try and rule something out at this point. Cheers, Danny

I thought that was inside the diagnostic zip config/rsyslog.conf unless i'm wrong but that looks right to me.

Bump Sorry but still not been able to figure this out

Attempting to enable a local syslog server to enable persistent logging. I do not want to mirror the logs to flash so followed the guide in FAQ here: What I am running into is the following error in the system log after enabling the syslog server in the settings panel. Sep 2 13:52:45 Kronk rsyslogd: Could not find template 1 'remote' - action disabled [v8.2002.0 try https://www.rsyslog.com/e/3003 ] Sep 2 13:52:45 Kronk rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 121: errors occured in file '/etc/rsyslog.conf' around line 121 [v8.2002.0 try https://www.rsyslog.com/e/2207 ] Sep 2 13:52:45 Kronk rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="14154" x-info="https://www.rsyslog.com"] start I have reviewed a few error posts on the forum that suggest deleting the flash/config/rsyslog.cfg & rsylog.conf and rebooting. I have done this and the issue persists. I have also booted into safe mode and the error still occurred there. Google search hasn't really helped me identify the error in the file if it exists. Anyone had this before? Thanks, Danny kronk-diagnostics-20200902-1402.zip

OK, i guess since I haven't set up syslog server your correct that there is the chance I missed one, as you say the evidence fits! I will run corrective and setup syslog just so I can review better in future. Thanks for taking the time to help me. Cheers, Danny

@johnnie.black The second non-correcting check has completed, it reported the same 23 sectors as before, I have attached diags as requested. Thanks again, Danny kronk-diagnostics-20200901-1707.zip

Thanks for the reply Johnnie, running now, will report back in 8 hours. Danny

Hello all, Been running Unraid for about 3 months now and been really happy with everything it offers. This morning my scheduled monthly non-corrective parity check came back with 23 errors. Since the previous month I have not had any unplanned power outages but I have had a clean shutdown during a storm to protect against one as I don't have a UPS currently. In terms of other events that may seem a little odd in the logs I do use a 'user-script' to stop and start my docker containers on a daily bases i.e. stop plex, radarr, sonarr and sabnzbd overnight when I'm not using them. I did this originally as I was spinning my drives down overnight but I no longer do this so probably will remove that script once this is sorted. Reading the forums I get the feeling that when a small number of errors occur that I should run a correct parity check and then see what the following month brings. However after reading the horror stories of people making changes before seeking advice I wanted to air on the side of caution and get some feedback I have attached the diagnostics and would appreciate any comments suggestions on my next steps. Apologies in advance if I have missed some information! Cheers, Danny kronk-diagnostics-20200901-0824.zip

Oh that's awesome!! Thank you so much sir

These are really cool! I've held onto a Cooler Master HAF932 for many years and finally putting it back in service Would love to have an icon for it I have the original with the 6 mesh blanking plates for the 5.25 bays but couldn't find a good face on picture, from reading it looks like the 932 advanced was the same case but with the one of the blanking plates as USB3 interface but the rest is the same. If possible I would like it with 6 blanking plates like the original model. Thanks

Thank you for the prompt reply.

Hello, Apologies if this is covered somewhere but i failed to find anything on a quick check :) I am planning on re-using an old mobo/CPU for an unraid project that are in my partners active system currently. I have been reading up on HVM and IOMMU which are features I want for my use case. The CPU supports both features (6600k) and the motherboard in theory does (Gigabyte GA-Z170m-D3H), however I want to validate this before upgrading her PC and taking the old :D I am aware that in the System Information window in Unraid it will show you HVM & IOMMU support is enabled or disabled, my question is can I see this before going as far as registering a trial key? would rather save the trial key in case it doesn't work with this hardware for another attempt in the future. Thanks in advance. SuudoXR