trurl

Not broken on my chrome. Maybe clear the browser cache.

Which, of course, is the first method in that wiki. Might be worth reading though. The main point that might be worth noting there is that any data that was on that removed disk will no longer be in the array, as I mentioned

And the simplest procedure for him to follow is New Config without the disk and rebuild parity.

I don't see any reason to assume he followed any procedure.

As I said

Are you saying you have nothing assigned to that slot? You MUST rebuild parity. It is NOT VALID without ALL the disks it was originally built with.

You have to rebuild that disk to another disk in the same slot. Or if you don't want anything in that slot and you don't care about any of the data that might have been on that disk, you can New Config and rebuild parity without anything in that slot.

Those look OK, but I'm not entirely sure how to interpret your cache pool since they are small and different sizes. Do you have this configured in "single" mode? https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480421 Which plex docker are you using?

Rebooting starts syslog over. The point of setting up syslog server is to get the syslog saved so that after a hang or crash forces a reboot, you can get the syslog from before the reboot. Maybe that will give a clue.

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

appdata, domains, and system shares should be cache-prefer, or cache-only. Ideally, you want them all on cache with nothing on the array. Your dockers and VMs will perform better if they are not impacted by the slower parity writes, and your dockers and VMs will keep parity and array disks spinning if you have any of it on the array since these files are always open. Mover will move cache-prefer shares to the array, and these shares are cache-prefer by default, so you must have changed them. But, mover cannot move open files, so before you can get them moved, you must disable docker and VM services as I explained above. Set those shares to cache-prefer and Then run Mover. Wait for it to complete and post new diagnostics so we can see if anything else needs to be done to get those fixed.

Your docker image is 40G and completely full. It is extremely unlikely you would ever fill even 20G if you had things configured correctly. Also, your domains and system shares are not set to use the cache correctly, and have files on the array. Go to Settings - Docker and disable dockers. Delete the docker image. Go to Settings - VM Manager and disable VMs. Leave these disabled until we get those shares configured correctly.

Parity does not have a filesystem so there is no point in formatting it. Looks like it's still having problems communicating with that disk.

Cache-yes user shares will overflow to the array if Unraid decides cache doesn't have enough space. The way it decides this is with the Minimum Free setting in Global Share Settings. Unraid doesn't know how large a file will become when it chooses a disk to write it to. If cache has less than Minimum Free, it will choose an array disk instead. Once it has chosen a disk, it will try write the entire file to that disk even if it runs out of space. You should set Minimum Free larger than the largest file you expect to write to cache. Each user share has a Minimum Free setting also, and it works in similar manner. If a disk has less than minimum, Unraid will choose another disk. Using those old, small disks Unassigned seems a good compromise. I always discourage people from using disks just because they have them, especially in the parity array or cache pool. Each additional disk is an additional point of failure. To reliably rebuild a disk in the parity array, Unraid must reliably read all the other disks, so if any aren't reliable, they can compromise a rebuild. Make sure you set up Notifications to alert you immediately be email or other agent as soon as a problem is detected. Unraid monitors certain SMART attributes for you. The default SMART monitoring is in Disk Settings, and you can override these for specific disks by clicking on a disk to get to its settings.

^this

The reason I asked is because I wondered if some problem updating your flash drive made it forget that disk had been rebuilt. If you rebuild it and reboot on purpose, does it still think it needs to be rebuilt?

Unraid monitors SMART attributes for you. You should setup Notifications to alert you immediately by email or other agent as soon as a problem is detected. In Settings - Disk Settings, you can specify which SMART attributes are monitored for all disks. You can override that setting for specific disks by clicking on the disk to get to its settings page. Unraid will Notify when any monitored SMART attribute changes.

Did you rebuild the disabled drive? It won't get enabled unless you rebuild it (recommended) or set a New Config and rebuild parity instead.

Probably less trouble free in general to not include the syslog from Syslog Server, since there is no telling how large someone might let it become, and it isn't needed nearly as often as the diagnostics are.

Those are definitely not the default settings for the Krusader docker template. If you did not change them now then you must have already set them this way before. These things don't happen by themselves. I think many people are initially confused just by the word "map" in this context. In more abstract settings such as mathematics, a "mapping" is just a correspondence. Just as a place on a road map corresponds to a place in the world, a docker container mapping corresponds to something on the host. A volume mapping is a correspondence between a path inside the container, and a path on the host computer. Similarly, a port mapping is a correspondence between a port used by the container, and a port on the host computer. You had set up 2 different container paths for the same host path in several places. You can see in that first screenshot you posted, for example, that /boot (which is the flash drive) is mapped twice. But what you can't really see in that screenshot is what it is actually mapped to. The "Container Path" text that appears below that is just text that you can edit and it isn't really used for anything except a reminder to yourself. If you click on the Edit button for that mapping, you can see the details for the mapping. That is why I asked for the docker run command, because the screenshot didn't give all the information. If you click on the Edit button for each of those /boot mappings you have, you will see one of them in lowercase and the other in uppercase, which results in 2 different paths (differing by case), to the same exact thing on the host (when you look at it within the container).

USB2 will probably be more trouble-free even if you could get SD to work.

That said, I have installed the beta on my only server. But I have good backups.

Works on my touchscreen, and nobody has ever reported it not working on touchscreen. Also, a mouseover will show the icon is an active element.

But you've already been told how to backup your original flash and restore it.

This thread is not the place for plugin support.