Squid

Typical idle power? And with all those segfaults, you definitely want to do a memtest (temporarily switch the boot mode to be Legacy if you're currently using UEFI) for a couple of passes

It looks good

Also, this message Pool overlaps with other one on this address space implies that you're running docker containers on their own dedicated IP address. If this is the case, you should also upgrade to 6.10-rc2+ and switch from using macvlan to instead ipvlan in Docker Settings, as some users do have crashing problems with macvlan

If only to get it out of the way, have you looked and did the suggestions in this post: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-819173

Toss the drive in, right click on it from My Computer/This PC, Properties, Tools, Check

The mce happened during processor initialization and is harmless. These errors: Feb 20 21:47:10 UNRAID root: Fix Common Problems: Warning: Share appdata references non existent pool cache Feb 20 21:47:10 UNRAID root: Fix Common Problems: Warning: Share domains references non existent pool cache Feb 20 21:47:10 UNRAID root: Fix Common Problems: Warning: Share system references non existent pool cache Should be rectified (change the reference in the share's settings to properly reflect "cachedrive") If it looks correct when going to the settings, make any change and revert it then apply. Failure to do this *might* result in stuff going into RAM causing you heartache and grief It also never hurts to run a memtest whenever any crashing is present for at least a pass or two. I also wouldn't be surprised (based on the age of the CPU) if your power supply is also starting to show it's age and having power delivery problems.

The symptoms (growing usage of the image and then suddenly it decreases) sounds typical of downloading within the image and when the download is finished it gets moved to the appropriate share. Double check your paths within the app's settings for where incomplete etc goes and make sure it's mapped outside of the container (spelling and capitalization count here)

Ideally, grab the diagnostics (you can do it from a command prompt) and post it here.

Unraid does a quick check on the integrity of the flash on every reboot, and in 6.10+ it also does a quick check on certain files to make sure they're readable (the ones which are guaranteed to exist -> of which docker.cfg is one of them) and alerts you in the GUI if there's any problems To really check, power down, pull the stick and run the file system checks on it in a Windows / Mac box

I would assume "Clicking" The drive isn't showing any SMART reports, and has basically disappeared from the system. I'd assume that its toast and needs to be replaced

Absolutely ancient (circa 2011) instructions, and doesn't come close to taking into consideration anything else running on the server (VMs, docker, other services etc) You want to do powerdown

Most versions of Unraid are too "extreme" in what they consider an Unclean shutdown. In 6.10's so far, if any process has to be killed in order to stop the array then an unclean shutdown results (which isn't unclean in and by itself so long as the disks can be unmounted) - This is supposed to be fixed on the next release The other scenario is if your flash drive keeps dropping offline, so it can't mark the shutdown as being "clean"

Basically, yes I know that I had "lost" some files a long time ago because I inadvertently (somehow) via Windows Explorer moved multiple folders into another show's folder and Kodi couldn't really figure it out on a rescan. I don't use Emby, but another user here on Plex a while back had Plex set to automatically delete watched episodes after a while.

Don't take this the wrong way, but thank you. The forum has always known that there are "rules" in place on how conflicts like this are handled, and because of this we now know that conflicts are simply "subtracted" from each other, and that user shares only get enabled if there are actual disks being involved.

Here's one issue. Not quite sure if it'll affect it or not From your Global Share Settings, shareUserInclude="disk2" shareUserExclude="disk2" You're telling the system that user shares should only be put onto disk 2 and you're at the same time telling it that user shares should never go onto disk 2 So where are they supposed to go? Fix Common Problems should have been telling you about that. Only ever use include or exclude, never both as they are opposites of each other with it never being necessary to specify both. Fix that, reboot and post a new set if problems continue

Missing quotes, mnT.user/system..... isn't a valid path etc Easiest way for any flash to get corrupted is during a power cut in the middle of a write Or via SMB to the Flash share if it's exported (config folder) If this is a continuing issue, then you'll need to ultimately replace the flash drive

Both those shares exist on disks 2,3,4 and 5 and those disks definitely aren't empty. Can you navigate to them via Main (there's an icon at the far right of each line to let you navigate through the disks) and confirm they're physically no longer present. It's unlikely that any data loss is due to Unraid itself. Most losses are results of inadvertent deletions etc, and there doesn't appear to be any problem per se easily discernable

You'll need to start the array and then post a new set of diagnostics, so we can see how everything looks when it's in that state.

Corruption on that file (docker.cfg) at the very least LOCKER_ENABLED="yes" DOCKER_IMAGE_FILE= 'mnT.user/system/docker/docker.img" DOCKER_IMAGE_SIZE<b40" DOCOER_APP_CONFIG_PA]H="/mnt/user/appdata/" DOCKGR_QPP_UNRAA_PATH5"" DOCKER_CUSTOM_NETGORKS=" " DOCJER_TIMEOUT}"10# DOCKER_LOG_ROTAION="yes" DOCKER_LOÇ_SIZE="µ0m" ÄNCKER_LKG_FILES="1" DOCKER_AUTHOBING_MMDE=#no" DOCKER_USER_NETWORKS="remove" Restore the flash drive from a backup. Or if none available, delete the file from the flash and reboot (it looks to be basically stock anyways)

Where are you files that are missing stored? In what share? On the //MELCO/Share SMB share?

Why not just set GUI boot as the default? What shows up on the screen during the "normal" boot method?

That out of memory that FCP is detecting is the TCP thing (never seen that message before, and it's not what FCP is designed to catch). I would start by rebooting and then go from there.

I'm always looking for suggestions on how to streamline installations and make things better. I'd suggest that you create a post in maybe Feature Requests after you gather your thoughts with how you think the system could be better. Thanks.

https://unraid.net/contact

Is everything running normally when accessing locally?