Kilrah

You have to either delete the recovery partition or use 3rd party tools to move it to the end so the free space is contiguous.

Yeah you can
docker volume prune -a

Or select/delete in portainer.

Yes, you can swap the config folders between drives just fine as long as you keep the .key files with the drive they're associated with.

Auf 7.1.2 aktualisieren.

Your global_cache pool got completely full and went read-only. 
 
Try rebooting and see if it mounts read/write, if so unload stuff from it.

Primary pool, secondary array, mover pool->array, run mover, confirm share empty on pool, then switch the primary pool to do the other. 
 
If you always only had primary array and no secondary then you may have stuff configured to write directly to the pool instead of going through /mnt/user/[share], otherwise it wouldn't have gone to the pool. That would need fixing.

1) Doesn't seem like you needed a new license in the first place? You had one, it was perpetual.
2) You need to contact support for license matters, forum can't deal with those, and you shouldn't post personal information in a public forum.
3) Don't trust LLMs.

Your logs are full of a container restarting every couple of minutes, figure out which one it is, probably the culprit
 

If a drive is failing then replacing that is the most important and should be done individually before anything else. If you do a new config to shrink the array then you lose the ability to rebuild the failing drive.

Replying to that topic is how you ask a question about one of the things in that topic if you haven't already found the answer in it.
 
The point is that the author will (hopefully) be watching this specific topic for support issues.

You'll need to delete the directory and recreate it/reinstall your apps from Previous Apps. Wouldn't have been an issue with an image, but yeah with a directory it's wrecked. 
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

Did you install the virtio drivers yet?
 

You hadn't, and it's your first post here... had you asked you'd have been pointed to the manual you could have also looked up on your own, particularly the section about "drive unexpectedly becoming unmountable":
https://docs.unraid.net/unraid-os/troubleshooting/data-recovery/#unmountable-disks
 
 
It's stable, but nothing in the world can guarantee data safety, especially not on consumer setups. The only data safety you ever get is backup copies of anything important on completely independent hardware.

Uninstall the old Mover tuning plugin you likely have that doesn't know about 7, and if you really need it install the current version.

rsync first makes a temp file, then renames it (to avoid leaving a partial file if the transfer is interrupted mid-way).
 
What format? The error is about setting permissions, if it's one that doesn't support linux permissions this is normal, should be able to set it to be ignored.
 
Also should probably be in the LuckyBackup support thread.

If you increased the vdisk size you forgot to also increase the partition size in the VM. Expand it in gparted.
 

Check on the array (/mnt/user0) and any other pool if there are files/folders that remain from those shares. Even an empty leftover folder would prevent the shares from becoming exclusive.

Correct, if there's no primary/secondary nothing will be moved.

Recently had the same issue and had to delete the chrome user profile.

There is a python plugin you can install. 

As far as I know it's perfectly normal, as btrfs does copy on writes when something is changed a new block is allocated to store it, the old location is freed internally but not deallocated. So after a while it's normal for the entire medium to be allocated and it'll remain so unless you run a balance which forces it to reorganize/consolidate everything at which point it'll deallocate what it doesn't need.
 
Here's my cache, 100% allocated too, has been for years probably. 

 
Netdata makes a warning for it but it's silent by default and is just not meaningful.
 

 
 
 
 
 

Contents are balanced according to share settings as long as you copy to /mnt/user/[share] or /mnt/user0/[share] (no cache).
 
Nope. Has to be the supported ones for array/pools i.e. xfs, btrfs or zfs.

You have Docker set to folder mode, not image. On ZFS drives that's known to be unreliable unless you set the backing FS to overlay, which isn't the case.
 
https://docs.unraid.net/unraid-os/release-notes/7.0.0/#add-support-for-overlay2-storage-driver

That's normal, at some point the GPU gets detached from unraid as it was bound to vfio so the display just freezes in its last state.
 
Depends what hardware you have/if your CPU has a built-in GPU. If so BIOS needs to be set to keep the iGPU enabled and to have it as primary.

Array started and everything available.