trurl

Only you would know what was there. Dynamix File Manager plugin will let you work with folders and files directly on the server.

Do you have any VMs?

Plug I in to another computer.

Post new diagnostics

Yes

You can have .cfg files in config/shares folder which contain the settings for shares that no longer exist. These will not create any shares, they just have settings that would be applied if the corresponding share actually did exist. And deleting these won't have any effect on containers that specify paths which would create a share. They would still get created with default settings. If you did want to automate the search in some way (instead of manually inspecting the paths specified in each of your containers on the Dockers page), you would need to search the contents of each of your docker templates in config/plugins/dockerMan/templates-user.

Attach Diagnostics to your NEXT post in this thread.

Attach diagnostics to your NEXT post in this thread.

My plex only has 570MB for container and 210MB for writable. Post docker run for your plex.

Something about your config is breaking things then. You will have to work through that. Try starting from a new install, then copy your config except for any of config/plugins. That should get all of your settings except plugins and docker templates. Also, edit docker.cfg and domains.cfg in your config to disable Docker and VM Manager.

Simple as that, except no need to set slot to no device. Just select the new device in that slot. I prefer to reserve the verb "add" for situations where you are actually adding a disk to a new slot that didn't already have a disk assigned. Parity2, for example, in your case, but could be used when talking about a new data slot. What you are doing with the data disk is "replace".

This was a new install on a new flash drive? And it worked before copying your config?

When this happens, what do you get from command line with this? df -h /

Unrelated, your system share has files on the array. Possibly you enabled Docker and/or VM Manager before you had cache. Ideally, appdata, domains, and system shares would have all files on fast pool such as cache with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

Don't see any problems. Looks like it had only been running a short time when you posted those diagnostics. Has the speed improved?

Try the adguard fix first.

Probably disturbed connections. Attach diagnostics to your NEXT post in this thread.

If adguard is the actual problem and not theme engine then that would be a good idea. Simpler to eliminate that too.

You can test it on another flash drive if you want, but you don't have to do a license transfer if there is nothing wrong with your flash drive. Just be sure you have a backup of your config folder, create a new install on the same flash drive, copy config except theme engine.

Disk access will affect parity check speed, and parity check will affect disk access speed. But file access, even writing files, will not affect parity results. If you and your dockers don't access the disks a lot during the parity check, then it won't make a lot of difference.

Start from there, copy all of your config, except theme engine .plg and folder.

Much better. Mar 9 19:15:55 DLVTOWER kernel: md: recovery thread: P incorrect, sector=0 Mar 9 19:15:55 DLVTOWER kernel: md: recovery thread: P incorrect, sector=8 Mar 9 19:15:55 DLVTOWER kernel: md: recovery thread: P incorrect, sector=16 Mar 9 19:15:55 DLVTOWER kernel: md: recovery thread: P incorrect, sector=32 Mar 9 21:07:40 DLVTOWER kernel: md: recovery thread: P incorrect, sector=2576730632 Mar 9 21:07:40 DLVTOWER kernel: md: recovery thread: P incorrect, sector=2576730640 Run a correcting parity check. Then post new diagnostics so we can see if it finds exactly those same few sectors and corrects them.

Just let parity do its job and rebuild to a larger disk. If you keep the original until you are satisfied with the rebuild, actually less risky than copying/moving files with whatever method, because it's simpler.