TechnoBabble28

Members
  • Posts

    40
  • Joined

  • Last visited

Everything posted by TechnoBabble28

  1. After trying several things to get some sort of output from the server I decided to just nuke the flash drive. It was not giving me any output past the post screen nor was I given the normal blue unraid boot options screen to pick how i'd like to boot. Somehow, when I uninstalled the qbittorrent docker last night it must have just completely corrupted the files on my drive. Don't know how or why but I don't have any other explanation at this point. I have spent the last little while thoroughly testing the flash drive and that seems to be just fine so I am confident I can reuse it. My config folder, however, is completely missing from the flash drive and several other files/folders appear to be seriously corrupted. I just reformatted the flash drive and did a fresh install of unraid. It booted right up no problem. Now I just need to figure out how to get a replacement key since I was unable to copy over the key file. I can't register for a trial key because the GUID is already attached to my original key, but there is no option for me to request a replacement anywhere that I can find. Anyone know the proper way to go about this? EDIT: Found my registration email and was successfully able to reapply the key file.
  2. Ive run chkdsk but it did not return any errors or indicate that any corrections needed to be made. I am in the process of pulling the server out of the closet now so i can get a monitor hooked up. Is there anything that can be done from the CL that may help to shed some light on this? Am I able to reformat the USB and reinstall unraid while still preserving the data? It appears the issue is OS related and not data drive related so is there any chance of fixing this issue without losing my data?
  3. Hey all, I am low-key panicking at the moment. I just finished removing a qbittorrent docker container from UnRaid since it was giving me problems (downloads weren't starting). I replaced it with the binhex delugevpn container and was in the middle of testing out my configuration. I had added a movie and a tv show to download and was just waiting for them to be done so I could make sure the post-processing was working. About halfway through though, I got a warning from UnRaid saying that my docker img was at 75% capacity, and then 76%, and then 77%. I stopped both downloads and then stopped the deluge container so i could double check my downloads path. However, when I attempted to go into the deulge container to edit the settings, i was instead redirected to the docker settings page. There was a warning displayed and an orange triangle next to one of the settings but I did not get a chance to comprehend any of it because my entire server subsequently shut off for some, as of yet, unknown reason. After confirming the power shut off wasn't some sort of weird power issue, I powered the server back on. This is when I started to panic. As of right now, I am unable to get to the web UI of the server. I let the server run for about 30 minutes just to make sure it was fully booted but there was no difference. In a bit of a heightened panic, I did a hard reboot of the server. No change. I then logged in to my Unifi controller and verified that the link to the server is up so it is not a connectivity issue. This is where I have just about lost my s***. I am not able to SSH in to the server at all BUT I am able to connect via sftp (Filezilla). The server runs headless but does have a cheapo graphics card in it for emergencies, however, I can't plug a monitor in right now because the server is conveniently located in the closet of my 1yr old sons room and my wife would probably castrate me if I woke him up. Anyway, using Filezilla, I attempted to navigate to my cache drive and, well.....it doesn't exist. As a matter of fact, NONE of my shares exist. What the hell happened?! Who knows?! Someone please tell me everything is going to be alright so I don't have to rock myself to sleep tonight whilst sucking on my wife's thumb... Also, no, I do not have a back up of my flash drive, because I am a dumb dumb. The last log that I could pull off of the flash drive just shows this repeating continuously... "Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/Downloads.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/Movies.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/Pictures.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/TV Shows.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Feb 9 21:42:33 MediaServer emhttpd: Starting services... Feb 9 21:42:33 MediaServer emhttpd: shcmd (40513): /etc/rc.d/rc.samba restart Feb 9 21:42:35 MediaServer root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: Not a directory Feb 9 21:42:35 MediaServer root: cp: cannot stat '/boot/config/machine-id': Not a directory Feb 9 21:42:35 MediaServer root: Starting Samba: /usr/sbin/smbd -D Feb 9 21:42:35 MediaServer root: /usr/sbin/nmbd -D Feb 9 21:42:35 MediaServer root: /usr/sbin/winbindd -D Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/Downloads.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/Movies.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/Pictures.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/TV Shows.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/appdata.cfg Feb 9 21:42:36 MediaServer emhttpd: Starting services..." Anyone have any idea of where I can even start? OR If the config is totally jacked up, am I still able to read from the drives if I plug them into a windows machine? TIA
  4. I kept trying each RC until I found a stable one. RC4 had been the most stable with an uptime of about 2 weeks which usually means I am in the clear. I just upgraded to RC5 a couple days ago and that has been solid as well so far.
  5. I had been running on 6.5.3 for many months without issue and without any sort of zenstates or c-states modifications. I never had any issues with my Ryzen build other than some bad RAM sticks early on. I updated to the F23 gigabyte BIOS a few months back but never looked through it until the other day. After disabling global c-states and adjusting the power supply power to "typical", 6.7 rc1 was stable for several days. It only started crashing again once I updated to rc2. I am using FCP to gather logs so when it inevitably crashes in the next 16 hours or so I can hopefully see what's going on. I also see that gigabyte released a F25 BIOS a little while ago but I am hesitant to change to the new BIOS until I figure out why the system is crashing. From what I can see, the biggest change is some tweaks for athalon based systems and an AGESA update from 1.0.0.4 to 1.0.0.6. It also mentions a requirememt to update the chipset driver which I cannot do. I know one of you mentioned a mellanox card and having some problems. I am also running a mellanox card but haven't encountered any issues. However, I do not have any VMs running and I am not using the mellanox card for internet, only direct file transfers between my desktop and server.
  6. I was stable on 6.7rc1 for a couple days then went to rc2. RC2 has crashed twice now all within 24 hours of uptime. I am now running FCP in troubleshooting mode to capture logs and will upload once it happens again.
  7. Server has been up and running for almost 18 hours as of now. That's the longest it's stayed on thus far. So far so good. Nothing unusual in the logs.
  8. I saw that while I was looking for the global c-states setting and set mine to typical also. Figured it was worth a shot. It's still up so far, fingers crossed.
  9. Will do. Just rebooted into 6.7. I think my longest up-time previously was about 12.5 hours so we will see if we make it that far.
  10. You sir were correct. It was buried in the overclocking settings under "advanced cpu core settings". Have just disabled it and will re-update to 6.7.
  11. I have no such option anywhere in the Bios for global c-states. These are my only c-states settings.
  12. Nope, that just hard locks the system every 20 minutes lol. I think ill just go back to 6.5.3. That's a bummer since the new dashboard is pretty nice. I'll close this thread.
  13. C6 was set to auto in this new Bios version so i have reset it to disabled. Will see if that fixes the problem.
  14. Bios was updated to lasted at the beginning of December and i haven't had any issues with it. I am running a zenstates script to fix the turbo boost issue and had previously disabled c-states in bios when i first set the system up. However, I have not checked the c-states since this bios update to see if they have been changed, mainly because everything was stable in 5.6.3 even after the bios update. I will check that now.
  15. I don't run any VM's, this is purely just a media server running Plex and a couple supporting dockers.
  16. I just upgraded from 5.6.3 to 6.7 rc1 yesterday afternoon. It initially locked after about 4 hours, no ssh or browser access, and required a hard reset. I then ran TS mode from the FCP plugin, left the dashboard window open on my screen, and went to bed. When i woke up this morning it had locked up again around 12.5 hours in. I am not running any VM's, this is purely a media server with minimal dockers. The logs are attached below. FCPsyslog_tail.txt mediaserver-diagnostics-20190122-0245.zip
  17. My system is hard locking anywhere from 4 hours to ~12 after startup. I am unable to reach it via ssh or a browser so my only recourse is to do a hard restart. I have attached the log files below as well as a screen shot of the dashboard when it locked overnight. I left the dashboard up before i went to bed so i could see what was happening and when everything locked. I came from 6.5.3 and had no issues previously. FCPsyslog_tail.txt mediaserver-diagnostics-20190122-0245.zip
  18. I have attempted to migrate over to sickchill but I have been unsuccessful thus far. Installing sickchill is not a problem. I can get that up and running without issue. The problem i am running into is rolling back Sickrage to 10.06-1-01. I have edited the repository as posted above but sickrage fails to launch at that point. When i look at the logs i get this line: 17:50:37 ERROR::MAIN :: Your config version (11) has been incremented past what this version of SickRage supports (8). I really dont care about copying over config files as that doesnt take long to set up. I really just want to move the database over. I originally tried restore a sickrage backup from 10-28 into sickchill and it said it completed successfully, however, nothing actually happened. Neither my config or my library info transferred. I even tried manually copying the database files over to sickchill without success. Does anyone have any ideas?? EDIT: After taking a break and starting with a fresh install of Sickchill, i found that the only thing i needed to do was use my most recent database file from sickrage (sickrage.db), rename it to sickbeard.db, and move it into the sickchill appdata directory, overwriting the existing db. This does NOT keep any config settings, but for me that was acceptable.
  19. I have been running on 6.5 for a while now but have had no issues with the new system other than a stick of RAM that went bad on me. I do not use the Zen state options but I also don't use any VMs so it's not really an issue. The system has never locked up on me since switching to the new components and has only been down when I am messing with something or doing an update. I've been very happy with everything!
  20. I will give the memtest a try. I tried a scrub once already and it came back with 20 uncorrectable errors from what i remember. But I will try it again after a memtest. As for the cstates/zenstates thing, i definately have cstates disabled in the MB BIOS and when i tried the zenstates code it made the system very unstable so i havent been using it.
  21. Sorry, forgot about that. Here you go! mediaserver-diagnostics-20180412-1129.zip
  22. Hey guys, Long story short, one of my drives had a corrupted filesystem. I did not have a backup of the data and it wasn't that big of a deal because it was all replaceable. I formatted the drive and reinstalled. Everything was fine for a day or so, then I started having all sorts of random errors. To further aggravate things, in my carelessness I deleted my appdata folder (i did have a backup of this) and decided to use the opportunity to just reformat my cache drives since I was getting some csum errors from btrfs. Now I have a brand new cache pool and a brand new drive. The problem is the errors I am still getting and the server is locking up. Here is a snippet of all the crap going on.... Apr 12 11:11:03 MediaServer root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Apr 12 11:11:15 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 217452544 csum 0x9883fc4e expected csum 0x9a9ee9e3 mirror 1 Apr 12 11:11:15 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 263610368 csum 0x54ed82f1 expected csum 0x58eef065 mirror 1 Apr 12 11:11:19 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 1244962816 csum 0xa8f2f821 expected csum 0x9bee6e99 mirror 1 Apr 12 11:11:19 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 1365680128 csum 0x9e50867b expected csum 0xc91194b2 mirror 2 Apr 12 11:11:20 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 1482903552 csum 0xdba4a14a expected csum 0x866ac217 mirror 1 Apr 12 11:11:20 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 1482903552 csum 0xdba4a14a expected csum 0x866ac217 mirror 1 Apr 12 11:11:21 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 1482903552 csum 0xdba4a14a expected csum 0x866ac217 mirror 2 Apr 12 11:11:22 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 1482903552 csum 0xdba4a14a expected csum 0x866ac217 mirror 1 Apr 12 11:11:22 MediaServer root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 12 11:11:22 MediaServer kernel: BTRFS warning (device sde1): csum failed root 5 ino 1020051 off 1482903552 csum 0xdba4a14a expected csum 0x866ac217 mirror 2 Apr 12 11:11:22 MediaServer root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 12 11:11:29 MediaServer root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Apr 12 11:11:40 MediaServer kernel: general protection fault: 0000 [#2] PREEMPT SMP NOPTI Apr 12 11:11:40 MediaServer kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod it87 hwmon_vid mlx4_en mlx4_core igb ptp pps_core i2c_algo_bit hid_logitech_hidpp edac_mce_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc mpt3sas aesni_intel aes_x86_64 crypto_simd glue_helper ahci libahci i2c_piix4 i2c_core raid_class cryptd scsi_transport_sas hid_logitech_dj mxm_wmi wmi_bmof ccp wmi button acpi_cpufreq [last unloaded: mlx4_core] Apr 12 11:11:40 MediaServer kernel: CPU: 6 PID: 6426 Comm: kworker/u32:11 Tainted: G D 4.14.26-unRAID #1 Apr 12 11:11:40 MediaServer kernel: Hardware name: Gigabyte Technology Co., Ltd. AX370-Gaming K5/AX370-Gaming K5-CF, BIOS F22 03/15/2018 Apr 12 11:11:40 MediaServer kernel: Workqueue: btrfs-worker btrfs_worker_helper Apr 12 11:11:40 MediaServer kernel: task: ffff8803c5686200 task.stack: ffffc90009c58000 Apr 12 11:11:40 MediaServer kernel: RIP: 0010:prefetch_freepointer.isra.11+0x8/0x10 Apr 12 11:11:40 MediaServer kernel: RSP: 0018:ffffc90009c5bd98 EFLAGS: 00010286 Apr 12 11:11:40 MediaServer kernel: RAX: 0000000000000000 RBX: fff78803baef8c00 RCX: 00000000023e5b06 Apr 12 11:11:40 MediaServer kernel: RDX: 00000000023e5a06 RSI: fff78803baef8c00 RDI: ffff88041e807620 Apr 12 11:11:40 MediaServer kernel: RBP: ffff88041e807600 R08: 00000000457cf000 R09: 0000000000000000 Apr 12 11:11:40 MediaServer kernel: R10: 0000000000000003 R11: ffff88041eda09e8 R12: ffff8803baef8ba0 Apr 12 11:11:40 MediaServer kernel: R13: 0000000001408040 R14: ffffffff811d33da R15: 0000000000000000 Apr 12 11:11:40 MediaServer kernel: FS: 0000000000000000(0000) GS:ffff88041ed80000(0000) knlGS:0000000000000000 Apr 12 11:11:40 MediaServer kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 12 11:11:40 MediaServer kernel: CR2: 00001456e50f7ff8 CR3: 00000003c213e000 CR4: 00000000003406e0 Apr 12 11:11:40 MediaServer kernel: Call Trace: Apr 12 11:11:40 MediaServer kernel: __kmalloc+0xd6/0x121 Apr 12 11:11:40 MediaServer kernel: ? btrfs_async_submit_limit+0x1c/0x1c Apr 12 11:11:40 MediaServer kernel: btrfs_csum_one_bio+0x51/0x3cd Apr 12 11:11:40 MediaServer kernel: ? __accumulate_pelt_segments+0x1d/0x2a Apr 12 11:11:40 MediaServer kernel: ? native_apic_wait_icr_idle+0x18/0x23 Apr 12 11:11:40 MediaServer kernel: ? irq_work_queue+0x47/0x7c Apr 12 11:11:40 MediaServer kernel: ? dequeue_entity+0x49d/0x4c2 Apr 12 11:11:40 MediaServer kernel: ? btrfs_async_submit_limit+0x1c/0x1c Apr 12 11:11:40 MediaServer kernel: __btrfs_submit_bio_start+0x9/0x12 Apr 12 11:11:40 MediaServer kernel: run_one_async_start+0x20/0x29 Apr 12 11:11:40 MediaServer kernel: btrfs_worker_helper+0xc2/0x185 Apr 12 11:11:40 MediaServer kernel: process_one_work+0x14c/0x23f Apr 12 11:11:40 MediaServer kernel: ? rescuer_thread+0x258/0x258 Apr 12 11:11:40 MediaServer kernel: worker_thread+0x1c3/0x292 Apr 12 11:11:40 MediaServer kernel: kthread+0x111/0x119 Apr 12 11:11:40 MediaServer kernel: ? kthread_create_on_node+0x3a/0x3a Apr 12 11:11:40 MediaServer kernel: ? SyS_exit_group+0xb/0xb Apr 12 11:11:40 MediaServer kernel: ret_from_fork+0x22/0x40 Apr 12 11:11:40 MediaServer kernel: Code: 44 06 ff a5 41 f6 40 09 04 74 17 49 63 40 1c 41 8b 48 50 48 01 c6 29 c1 48 89 f7 88 d0 48 63 c9 f3 aa c3 48 85 f6 74 0a 48 63 07 <48> 8b 04 06 0f 18 08 c3 31 c0 c3 55 48 89 fd 53 48 63 47 20 48 Apr 12 11:11:40 MediaServer kernel: RIP: prefetch_freepointer.isra.11+0x8/0x10 RSP: ffffc90009c5bd98 Apr 12 11:11:40 MediaServer kernel: ---[ end trace 35dac60ee19e4866 ]--- Apr 12 11:11:40 MediaServer kernel: general protection fault: 0000 [#3] PREEMPT SMP NOPTI Apr 12 11:11:40 MediaServer kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod it87 hwmon_vid mlx4_en mlx4_core igb ptp pps_core i2c_algo_bit hid_logitech_hidpp edac_mce_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc mpt3sas aesni_intel aes_x86_64 crypto_simd glue_helper ahci libahci i2c_piix4 i2c_core raid_class cryptd scsi_transport_sas hid_logitech_dj mxm_wmi wmi_bmof ccp wmi button acpi_cpufreq [last unloaded: mlx4_core] Apr 12 11:11:40 MediaServer kernel: CPU: 6 PID: 6560 Comm: kworker/u32:12 Tainted: G D 4.14.26-unRAID #1 Apr 12 11:11:40 MediaServer kernel: Hardware name: Gigabyte Technology Co., Ltd. AX370-Gaming K5/AX370-Gaming K5-CF, BIOS F22 03/15/2018 Apr 12 11:11:40 MediaServer kernel: Workqueue: btrfs-worker btrfs_worker_helper Apr 12 11:11:40 MediaServer kernel: task: ffff88033b442a00 task.stack: ffffc90009e30000 Apr 12 11:11:40 MediaServer kernel: RIP: 0010:__kmalloc+0xb7/0x121 Apr 12 11:11:40 MediaServer kernel: RSP: 0018:ffffc90009e33da0 EFLAGS: 00010286 Apr 12 11:11:40 MediaServer kernel: RAX: 0000000000000000 RBX: ffff88033b712040 RCX: 00000000023e5c06 Apr 12 11:11:40 MediaServer kernel: RDX: 00000000023e5b06 RSI: 00000000023e5b06 RDI: 0000000000024060 Apr 12 11:11:40 MediaServer kernel: RBP: ffff88041e807600 R08: 0000000047def000 R09: 0000000000000000 Apr 12 11:11:40 MediaServer kernel: R10: 0000000000000001 R11: ffff88041eda09e8 R12: fff78803baef8c00 Apr 12 11:11:40 MediaServer kernel: R13: 0000000001408040 R14: ffffffff811d33da R15: 0000000000000000 Apr 12 11:11:40 MediaServer kernel: FS: 0000000000000000(0000) GS:ffff88041ed80000(0000) knlGS:0000000000000000 Apr 12 11:11:40 MediaServer kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 12 11:11:40 MediaServer kernel: CR2: 00001456e50f7ff8 CR3: 00000003c213e000 CR4: 00000000003406e0 Apr 12 11:11:40 MediaServer kernel: Call Trace: Apr 12 11:11:40 MediaServer kernel: ? btrfs_async_submit_limit+0x1c/0x1c Apr 12 11:11:40 MediaServer kernel: btrfs_csum_one_bio+0x51/0x3cd Apr 12 11:11:40 MediaServer kernel: ? __accumulate_pelt_segments+0x1d/0x2a Apr 12 11:11:40 MediaServer kernel: ? native_apic_wait_icr_idle+0x18/0x23 Apr 12 11:11:40 MediaServer kernel: ? irq_work_queue+0x47/0x7c Apr 12 11:11:40 MediaServer kernel: ? dequeue_entity+0x49d/0x4c2 Apr 12 11:11:40 MediaServer kernel: ? btrfs_async_submit_limit+0x1c/0x1c Apr 12 11:11:40 MediaServer kernel: __btrfs_submit_bio_start+0x9/0x12 Apr 12 11:11:40 MediaServer kernel: run_one_async_start+0x20/0x29 Apr 12 11:11:40 MediaServer kernel: btrfs_worker_helper+0xc2/0x185 Apr 12 11:11:40 MediaServer kernel: process_one_work+0x14c/0x23f Apr 12 11:11:40 MediaServer kernel: ? rescuer_thread+0x258/0x258 Apr 12 11:11:40 MediaServer kernel: worker_thread+0x1c3/0x292 Apr 12 11:11:40 MediaServer kernel: kthread+0x111/0x119 Apr 12 11:11:40 MediaServer kernel: ? kthread_create_on_node+0x3a/0x3a Apr 12 11:11:40 MediaServer kernel: ret_from_fork+0x22/0x40 Apr 12 11:11:40 MediaServer kernel: Code: 34 01 f0 7e 48 8b 70 08 48 39 f2 75 e7 48 83 78 10 00 4c 8b 20 74 35 4d 85 e4 74 30 48 63 45 20 48 8d 8a 00 01 00 00 48 8b 7d 00 <49> 8b 1c 04 4c 89 e0 65 48 0f c7 0f 0f 94 c0 84 c0 74 b2 48 8d Apr 12 11:11:40 MediaServer kernel: RIP: __kmalloc+0xb7/0x121 RSP: ffffc90009e33da0 Apr 12 11:11:40 MediaServer kernel: ---[ end trace 35dac60ee19e4867 ]--- Apr 12 11:11:40 MediaServer kernel: general protection fault: 0000 [#4] PREEMPT SMP NOPTI Apr 12 11:11:40 MediaServer kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod it87 hwmon_vid mlx4_en mlx4_core igb ptp pps_core i2c_algo_bit hid_logitech_hidpp edac_mce_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc mpt3sas aesni_intel aes_x86_64 crypto_simd glue_helper ahci libahci i2c_piix4 i2c_core raid_class cryptd scsi_transport_sas hid_logitech_dj mxm_wmi wmi_bmof ccp wmi button acpi_cpufreq [last unloaded: mlx4_core] Apr 12 11:18:38 MediaServer nginx: 2018/04/12 11:18:38 [error] 9461#9461: *17726 connect() to unix:/var/run/php5-fpm.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.28.1, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.28.2", referrer: "http://192.168.28.2/Main" Apr 12 11:06:22 MediaServer root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Apr 12 11:06:37 MediaServer root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Any ideas???
  23. UPDATE: After spending a few hours diggings around the forums this fixed it for me.