Bizarro

That did the trick, just had to delete the Plex docker entirely. Re-downloaded via Community Applications vs the templates, and had to set up all the paths again. Hopefully it doesn't need to rescan all my media, I have kept the path to the existing config file. Thanks for your help

Thank you will give it a try

Hi there, I just went to Settings -> Docker and can't see anywhere to delete docker.img? Or is this done via the command line/console? I am having issues updating Plex. Docker storage location: /mnt/cache/Docker Appdata storage: /mnt/user/appdata/ Are these paths correct? I'm running the latest version of Unraid.

Thanks Rob, something must have changed overnight, 6.2.1 was presented via the built-in updater plugin just then, but it wasn't yesterday. Maybe someone was playing around with the hosting

I'm running 6.1.9 with no issues, however when I go to the plugins page I don't get an option to upgrade to 6.2.2? Only 6.2.0, which has an error I later found to be the website denying access to the .plg download? Is there a 6.2.2 .plg URL I can use to update? There doesn't seem to be any update instructions included with the website download either, is it just a matter of replacing bzimage and bzroot on the USB stick with the newer versions?

Installed a different motherboard and upgraded the TX650 to a TX850 Corsair power supply, parity check completed without issue. Not sure which of them was at fault, probably leaky caps or something else failing in the old motherboard I suspect.

Anyone? Otherwise I'll need to find a way to capture the screen somehow, as I reckon whatever the fault is is not being logged.

OK I ran the Memtest and attached a diagnostics log, I can't see anything that stands out though? Syslog: http://ribfeast.no-ip.com/syslog.txt

When running Memtest I noticed a stick of RAM was a different brand to all the others, I've swapped it out and am re-running a parity check. Also had Disk 3 disappear when I rebooted from doing this, re-seated the SATA cable (seemed snug, but just in case), and it's reappeared. Given that it is another one of the dodgy Seagates I'm copying the data across to another drive just in case. Parity sync at 10% and progressing well, see if it crashes again with the new RAM.

It just went down, but nothing really useful: Aug 15 11:20:54 NAS logger: plugin: running: /boot/config/plugins/fix.common.problems/fix.common.problems-2016.08.06-x86_64-1.txz Aug 15 11:20:54 NAS logger: plugin: running: anonymous Aug 15 11:21:05 NAS logger: Fix Common Problems Version 2016.08.06 Aug 15 11:21:11 NAS logger: Fix Common Problems: Error: Plugin Update Check not enabled Aug 15 11:21:11 NAS logger: Fix Common Problems: Warning: Docker Update Check not enabled Aug 15 11:21:11 NAS logger: Fix Common Problems: Warning: Community Applications not installed Aug 15 11:21:11 NAS logger: Fix Common Problems: Error: Powerdown plugin not installed Aug 15 11:21:13 NAS logger: Fix Common Problems: Warning: PlexMediaServer docker application has its /config folder set to /mnt/user/appdata/PlexMediaServer Aug 15 11:25:05 NAS in.telnetd[26616]: connect from 10.1.1.4 (10.1.1.4) Aug 15 11:25:07 NAS login[26617]: ROOT LOGIN on '/dev/pts/0' from '10.1.1.4' Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:38:11 NAS php: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Aug 15 11:39:23 NAS emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://github.com/dlandon/powerdown/raw/master/powerdown-x86_64.plg Aug 15 11:39:26 NAS logger: plugin: creating: /boot/config/plugins/powerdown/powerdown-2016.04.23.tgz - downloading from URL https://github.com/dlandon/powerdown/raw/master/powerdown-2016.04.23.tgz Aug 15 11:39:28 NAS logger: plugin: checking: /boot/config/plugins/powerdown/powerdown-2016.04.23.tgz - MD5 Aug 15 11:39:28 NAS logger: plugin: creating: /boot/config/plugins/powerdown/powerdown-2.20-noarch-unRAID.txz - downloading from URL https://github.com/dlandon/powerdown/raw/master/powerdown-2.20-noarch-unRAID.txz Aug 15 11:39:30 NAS logger: plugin: checking: /boot/config/plugins/powerdown/powerdown-2.20-noarch-unRAID.txz - MD5 Aug 15 11:39:30 NAS logger: plugin: running: /boot/config/plugins/powerdown/powerdown-2.20-noarch-unRAID.txz Aug 15 11:39:31 NAS init: Re-reading inittab Aug 15 11:39:31 NAS logger: plugin: running: anonymous Aug 15 11:39:31 NAS logger: plugin: creating: /boot/config/plugins/powerdown/powerdown.conf - from INLINE content Aug 15 11:41:43 NAS emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg Aug 15 11:41:45 NAS logger: plugin: running: anonymous Aug 15 11:41:45 NAS logger: plugin: running: anonymous Aug 15 11:41:45 NAS logger: plugin: creating: /boot/config/plugins/community.applications/community.applications-2016.08.13.txz - downloading from URL https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2016.08.13.txz Aug 15 11:41:51 NAS logger: plugin: checking: /boot/config/plugins/community.applications/community.applications-2016.08.13.txz - MD5 Aug 15 11:41:51 NAS logger: plugin: running: /boot/config/plugins/community.applications/community.applications-2016.08.13.txz Aug 15 11:41:51 NAS logger: plugin: running: anonymous Might run a Memtest when I get home.

Shall do, good tip! I've added a few plugins and notifications as recommended by the "Fix common problems" plugin, rescanning now. I'ts been up for around 150 minutes and is 7.2% parity sync, waiting for it to crash so I get some logs.

Thanks guys, great plugin! It's been scanning for a few minutes now and the web GUI is now unresponsive, hopefully it finds something. I've telnetted in and kicked off that syslog dump to the flash drive. Either way hopefully we'll get something logged The server has ECC RAM so I'd assume it isn't a memory issue? I have a bag of spare sticks I can pop in if needed though.

Hi all, I've just upgraded my parity drive from 3TB to 4TB, and am trying to generate parity for the new drive. A few hours into the parity check, the server appears to reboot itself, as when I log in to check on it, I get the prompt to start the array. Is there a way to get Unraid to automatically save the syslog to the cache drive as it generates it, or some other non-volatile location, so that I can troubleshoot this? The logs are cleared on reboot when it crashes. Can anyone think of a reason why it would be crashing? I completed a full parity sync on the 3TB drive fine, so maybe there is an issue with the new 4TB drive?

You will also need to fill in the device field. Mine is /dev/ttyS0 Kevin. Thanks Kevin that was the missing item! Now being detected Thank you everybody for your help!

OK you were right, serial ports were disabled in BIOS and I have now enabled them. No effect though. So for UPS cable I choose "Smart" and for UPS type I choose "APCsmart". Is that the only 2 fields I need to use?