Squid

Not necessarily your problem, but all systems are far more stable when using the same memory sticks. If you can't do that, then you really have to ensure that the CAS timing is identical between the two sets. Either way, you want to run a memtest for at least a pass if only to rule out a bad stick (won't rule out the above though) Now, if it actually shuts itself off then you're at either a power problem or an overheating problem.

You wound up hitting apply on the Blank Template. Within Previous Apps, remove it from Previous Apps (Actions). Then you can reinstall it fresh from a search and set stuff accordingly Easier (and less work on your part) to enable "Allow 2nd instance" from within CA's settings and then you can install second instances (and have the name and appdata automatically adjusted so as to not interfere with the original) No easy way to recover from the deletion (and subsequent Are you sure dialog) unless you've got a backup of the file somewhere. (MyServer's flash backup won't help you since it would have also been updated and doesn't currently support history)

Not particularly recommended. Disable VT-d in the BIOS if it causes problems Boot into the non-GUI mode. Then after logging in, enter in diagnostics and then post the resulting file (logs folder on the flash drive) here after the network drops off.

You're going to want to add a cron job via crontab or by placing an application .cron file within /config/dynamix on the flash drive. User scripts will eventually disallow a cron entry like this (when I get to it)

That particular question is probably best suited to Plex's own forums. (But, having a particular part of Plex segfault on a semi-regular basis is pretty common)

It means the the author of the container did not include nano in it. Are you trying to edit a file within appdata? Navigate via Krusader to /UNRAID/appdata/....

Nov 14 03:05:23 Homeserver kernel: BTRFS warning (device dm-7): csum failed root 5 ino 8891848 off 495853568 csum 0x53264c22 expected csum 0x265b60b1 mirror 1 Nov 14 03:05:23 Homeserver kernel: BTRFS error (device dm-7): bdev /dev/mapper/sdl1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 Nov 14 03:05:23 Homeserver kernel: BTRFS info (device dm-7): read error corrected: ino 8891848 off 495853568 (dev /dev/mapper/sdl1 sector 286184976) You've got some corruption on your cache pool (ssd-cache) Not sure how much that would affect it though. Do you have a whack of containers that are displaying the question mark for the icon?

Not the Plex expert, but whenever I see that (and a google) means that the movie you downloaded is Dolby Vision without a fallback compatibility and your TV does not support Dolby Vision. I bought a new TV to work around it.

How long has it been? Check your spam folder. Otherwise, contact @SpencerJ

Works for me (Chrome) both signed in and signed out

The link you posted returned a 404. Try again posting to the forum. Many users including myself do not particularly like clicking random links

Yup. Fairly common with plugins. Just means that a last minute bug was found that I didn't want to wait until the next release for one reason or another.

1 Double check the boot order in the BIOS 2 Put the flash drive into a regular windows box, and run the file system checks on it. 3 Make a backup of the flash drive 4 Re-run MAKE_BOOTABLE.BAT as administrator 5 Try it again. 6 If no dice, then set up a new flash drive copy over the contents of /config from your backup and boot with it.

You would need to enable the syslog server so that the logs become persistent after the crash

Q. Are you guys perchance leaving the dashboard open on a browser tab and never closing it?

The syslog will detail all the failed attempts, and is what is parsed by FCP to come up with the error

Try deleting (or renaming) /config/network.cfg and network-rules.cfg on the flash drive and reboot (this will set your system back to DHCP) and see if that makes a difference

A DNS server is what translates something like http://google.com to instead be http://142.251.32.78 which is how the entire internet works. By not specifying a DNS server, the system defaulting to using whatever DNS addresses are set in your router (or modem) which are usually handled by your ISP. Most ISP's DNS servers are terrible and don't resolve correctly all the time. Those 2 addresses are for the OpenDNS servers. There are many available via a google search. EG: If you would like Google to know and use in their analytics that you've installed an app from docker or a plugin from GitHub you would use instead 8.8.8.8 / 8.8.4.4 (Google's servers - Incredibly awesome, always resolve, but they do track you)

You didn't type it in correctly. 2 separate entries (one on each line) 208.67.222.222 208.67.220.220

Even if you manage to get it to work, I can 100% guarantee that you will never be able to update the OS automatically, and will always have to update it manually Quality flash drives are cheap, and you'll get more support here doing things "proper"

Failed password for invalid user ftpuser from 13.94.255.171 port 53232 ssh2 Are you directly forwarding the port for FTP and/or have the server in your router's DMZ? Not the greatest idea as eventually a brute force attack (which is currently happening) will eventually succeed. Use a VPN or reverse proxy or the like. By and large drive failures are exceedingly rare This Nov 12 16:08:23 unRaid-DINO kernel: ata3.00: failed command: READ DMA EXT implies that you've got poor cabling (loose sata and/or power -> SATA connections are (pardon my French) shit, especially if you ever add in splitters etc into the equation) Now, seeing as how the drive in question is returning no SMART data at all it is either The above problem (that code snip however was from your parity drive) The drive actually is completely dead #1 is far far more likely. Reseat all the cabling (both ends), and after you've done one drive, make sure you don't touch it (and hold your breath) when doing the next drive. Additionally, if you problems seem to be always on Disk 2, then do NOT use locking SATA cables. Most of them actually do not meet spec on the requirements and hold worse on WD drives than the non-locking type (which by definition ARE spec)

Far easier (and far far faster) to simply delete the docker folder via Settings -> Docker, then change where the folder is stored followed by Apps -> Previous apps and check the stuff off

Try setting static DNS addresses in Settings - Network (208.67.222.222 / 208.67.220.220) Won't hurt.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-713741

Post your diagnostics