trurl

Nothing can move open files. Typically, if Docker and/or VM Manager is enabled, system share can't be moved.

How large is current parity?

Do you mean you configured it for internal boot? You still need the flash drive for trial license.

Use an external enclosure and access the drives as Unassigned Devices

Did you ever do memtest?

Probably better if you ask on the support thread for that docker. I would be surprised if the container mappings could access that. Do you understand docker path mapping?

Did you fix the shares? Post new diagnostics if you want more detailed instructions about that.

You haven't told us what the problem is

Do you have a problem?

?

Have you done memtest?

Looks like you unassigned parity, are you still getting those speeds without parity?

Not related to your question, but several of your shares are misconfigured, as indicated by Fix Common Problems. Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Foundry Data is an implied array-only share, but files / folders exist on the cache Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share system is an implied array-only share, but files / folders exist on the cache Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Time Machine is an implied array-only share, but files / folders exist on the cache Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Documents set to cache-only, but files / folders exist on the array Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Emulators set to cache-only, but files / folders exist on the array Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Files set to cache-only, but files / folders exist on the array Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Macintosh OS set to cache-only, but files / folders exist on the array Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Video set to cache-only, but files / folders exist on the array Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Windows OS set to cache-only, but files / folders exist on the arrayMover will ignore these shares because they have no Mover action because they have no Secondary. Ideally, Docker/VM related shares - appdata, domains, system - will have all files on cache or other pool with none on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. Nothing can move or delete open files, so you have to disable Docker and VM Manager in Settings before these shares can be worked with.

Do you really mean 30-50 MB/s? https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/overview/#array-write-modes

That won't get those shares moved to cache. Mover ignores them since they have no Mover action since they have no Secondary. That's OK, you can move them yourself.

This suggests a misunderstanding of mover. It isn't doing backup. We can get further into this after your other problems are fixed.

Not the cause of your problem, but your appdata and system shares have files on the array, and, in fact, are configured to be moved to the array. Better if these shares are on cache or other pool outside the array so Dockers will perform better and so array disks can spin down since these files are always open. Nothing can move open files so you have to disable Docker in Settings before these shares can be managed. See here for some ideas about configuring your Ryzen server:

Everything else is unmounted. Do you have a current flash backup?

You don't need to, just thought that might be what had cache busy.

Do you have a command line open on cache?

The "folder icon" is on the LEFT. It looks like a square with an arrow sticking up to the right.

You appear to have 2 shares on cache with the same name but different case. Linux is case-sensitive, so these are different shares. Possibly you accidentally created one of these by specifying a host path in a container with the wrong case. Even though the share with the lowercase name is on cache, it has default settings since they weren't configured. One of those defaults is to not use cache. You should probably consolidate those 2 shares by moving the files from the lowercase share to the uppercase share, and checking that all of your containers are using the uppercase share. But leave that for later. Not sure what is going on with your dockers. Possibly some of your appdata was on disk1 but it is disabled, and the emulated disk1 isn't mountable. I recommend going to Settings - Docker and disable Docker until you get these other problems fixed. Then check filesystem on emulated disk1. Post the output.

Except for Unassigned Devices, I don't recommend hotswapping drives with Unraid. Unraid won't do anything with a disk until you assign it, and you can't assign a disk without stopping the array.

Hasn't been rebooted since Oct 1, but disk identifiers (sdX) seem to change. Were you hotswapping?

I correct Claude and Gemini all the time. But This has been explained innumerable times on this forum, and especially in the context of converting from ReiserFS.