Squid

Try using the IP again.

Did you ever try starting 6.3.5 in safe mode?

Limit display to 6.4RC8Q's limit of 1920 pixels (previously CA and unRaid supported any arbitrary maximum window width) Only display Legacy mode option in case of an appfeed download error Under certain circumstances, random app of the day could actually be blacklisted or incompatible Minor CSS changes. If any author / maintainer wishes to use Legacy Mode at will (to see how their template will display within CA rather than waiting for the next appfeed update), the button can be displayed by going to CA's general settings and turning on developer mode.

Like I said, put Fix Common Problems into troubleshooting mode then wait for Kenny to die. Until the crash happens again, there's nothing to go on unfortunately.

Not that I have any clue about the app, but hexparrot/mineos-docker is no longer on dockerHub. You're looking for hexparrot/mineos

They're all Page Allocation Stalls (ie: computer Brain Farts). Basically harmless, but your system is pausing what its doing for seconds at a time while it scratches its head, thinks about it, forgets what it's supposed to be thinking about, and then it finally remembers and figures it out. You can try this. May or may not solve the problem, but its more of an annoyance than a actual issue: Install Tips & Tweaks plugin and change these settings: https://forums.lime-technology.com/topic/55910-out-of-memory-errors-detected-on-your-server-call-traces-found-on-your-server/#comment-546982

Nothing in the logs (btw, diagnostics are always preferred over a syslog), since its after the reboot. I'd toss Fix Common Problems into troubleshooting mode, follow what it says to do after the crash, then watch Kenny die and post up the files FCP saved for you.

Sep 3 10:51:23 kingsnake kernel: Your BIOS is broken; RMRR ends before it starts! Sep 3 10:51:23 kingsnake kernel: BIOS vendor: American Megatrends Inc.; Ver: 1501 ; Product Version: System Version Sep 3 10:51:23 kingsnake kernel: ------------[ cut here ]------------ Sep 3 10:51:23 kingsnake kernel: WARNING: CPU: 6 PID: 1 at drivers/iommu/intel-iommu.c:2662 domain_prepare_identity_map+0xa7/0x13e Look for BIOS updates. Since they're all apparently IOMMU related, and you're not running any VM's with passthrough, you can safely disable IOMMU / VT-D within your BIOS.

Snippets are very rarely useful (especially since your's didn't include the header). Post the diagnostics instead.

First things first is to do this: https://forums.lime-technology.com/topic/57181-real-docker-faq/#comment-564345 And your diagnostics would also possibly be helpful

Can you hit the shares by navigating to the IP address? (\\192.168.123.64)

General rule is that anything running in the foreground will stop once you close the pop up. A lot of factors though at play.

Not that I can particularly help, but does the time of all this happening seem to correspond with these numerous entries: Aug 31 09:18:07 Brunnhilde kernel: TCP: request_sock_TCP: Possible SYN flooding...... Also intermittently you're getting share cache full errors which if you've got your containers set to use /mnt/user/appdata on a cache only share will give you nothing but headaches

Within Chrome, CTRL-L will automatically highlight the current URL in the address bar, and place the box into focus so you can just start typing a new URL. Keyboards actually all have little microcontrollers contained within them. Since there is no display or anything on a keyboard, the only way they have to communicate is via the lights. Although these lights can actually be controlled by the computer, as a general rule any light flashing (or flashing out a code) means a physical problem with the keyboard. You stated further implies a physical problem with the keyboard. Have you tried another one? If its some sort of high-end gaming keyboard, have you checked with the manufacturer to determine what a flashing scroll lock really means? Your problems all sound like something was spilled into the keyboard. Change it out and see what happens (They are the cheapest possible peripheral available for a computer)

I don't use binhex's stuff (no offense @binhex), but you'd be best posting in his appropriate support thread, along with this:

As was I Personally, since I don't see any reason why to hide drive serial numbers, I really hope that the anonymizer doesn't start doing this. It would be rather hard to analyze a log and tell someone that I think there's a problem with a drive's serial number starting with "W" and ending in "5". But what's done is done There's only one user that I can think of who's rare replies is abrasive / sarcastic. And, that's just the type of person that he is. My feelings is that the forum at large is always helpful (or tries to be) even with the most simple or repetitive questions. If you believe that these forums are abrasive, then I'd say hang out for awhile in the FreeNAS forums. The only way that I see that it could possibly be considered abrasive / curt / whatnot is that it is more common nowadays to simply reply to questions / concerns / whatnot with a link and no explanation because the link (quite often to one of the FAQ) explains and/or answers the question already.

Its because the permissions (and ownership) set by docker applications within their own config folders may or may not be compatible with how unRaid operates over the network. Not entirely unexpected. You can run Tools - New Permissions against your appdata share, but then you might impact the ability of the applications to run. Your best bet is to move the file(s) via something like the Dolphin / Krusader applications or via midnight commander (mc) at the command prompt.

Best google results I came up with imply that you're pulling a drive out at the times of the traces. If you're not, check all connections to the drives. In particular disks 11 and 12 since they are both returning read errors, and disk 11 has an obscene amount of smart errors implying cabling: 199 UDMA_CRC_Error_Count 0x000a 196 196 000 Old_age Always - 135075 Disk 12 is similar: 199 UDMA_CRC_Error_Count 0x000a 191 191 000 Old_age Always - 3755306 This all could be marvel related. LSI controllers are always preferred. But as an experiment if possible, make sure that the following drives are on the motherboard ports: 160 Gig: WD-WX20EB9Y7327 And All the 8TB's If you don't have enough motherboard ports for all them, don't worry about the 160G. If this reconfigure does work, please reply back as I have a theory trying to test about Marvel Controllers:

Download the 6.3.5 zip file from limetech's website, and overwrite all of the bz* files contained within it onto the flash drive. (Maybe make a backup of the existing files first)

I looked at the trace yesterday, had no clue. The key question though is are your VM's still working normally?

unRaid runs from RAM, and the contents of /etc (and many, many others) are recreated at boot time. If you can't adjust the settings via the GUI, then you're going to have to make the adjustments via a script (ie: save a copy on the flash drive), and execute it either via /boot/config/go or with the user scripts plugin set to run at first array start. (along with restarting the service if necessary)

Yeah. Multiple files all referencing the exact same picture. Honestly, I would assume just add the switches. (don't use rclone - I did the appdata backup plg, which may or may not suit your purposes depending upon the destination)

Symlink / hardlinks in English (vastly simplified) Imagine a file named "x" that requires 100Meg to store. Such and such program wants to store a copy of that file under the filename "y" Without symlinks / hardlinks, the copy would take up another 100Meg. With links, the copy doesn't take up any extra space, as the "y" filename simply points to the exact same data that "x" does. Plex makes very extensive use of them, and any backup of Plex's appdata without handling symlinks / hardlinks is pointless. Either add the switches, or use CA's appdata backup.

Not quite sure how to do that, although I'm sure its possible, but this link will let you keep the existing 500G, but the image will only take up as much space as it actually needs (rather than growing and never being able to shrink)

Stores the XML files, NVRAM for the VMs along with probably some other stuff.