All top level folders on any array or pool drive are automatically treated as User Shares by Unraid (no setting involved).
If you accidentally created some User Shares in this way and have subsequently removed the folders you can delete the associated share settings file from the config/shares folder in the flash drive.
Safe mode does not stop the GUI running unless your system NEEDS a particular plugin to get GUI mode to work.
You can also stop plugins running by renaming the .plg files on the flash drive to have a different file extension. This can allow you to experiment with different combinations of plugins being loaded.
If you started rsync from the command line then by default the rsync command terminates when the console session is closed.
To avoid this install the 'screen' app (using the Nerd Tools plugin) and first start a screen session from the command line, and then run rsync under that.
You would also have got away with just * - adding the leading / made it an absolute path rather than one relative to the current folder.
I always tend to do a ls command before using a rm command as a check on what the rm command will operate on.
It depends on the BTRFS profile they are set to use. The default is raid1 and that means they are protected, but the usable space is only that of the smaller device.
It seems to happen more often that it should after doing an upgrade, not sure why. Having a spare, though, is never a bad idea as if the USB is going to fail it always seems to do it at the worst possible time.
The problem is that licensing issues do not allow the later versions to be included.
I think it would be a good idea to make it more obvious that a later version can be downloaded and used for free (for personal use).
You might want to also carefully check your power/SATA cabling. Your syslog is full of resets on device ata6 (logs do not go back far enough to identify the exact device)
Since you are starting by getting the data off the emulated drive, then a faster set of steps would be:
2. Stop array
3. Plugin in new drive
4. Boot the system and make sure array is not started.
5. Use the New Config tool to reset the array. Use the option to keep all assignments (not compulsory but minimises chance of error)
6. Return to Main tab and assign new parity drive, and also old parity drive to array (probably to replace removed drive). Make any other changes to array drives you might want such as re-order them
7. Start array to commit new assignments and build parity based on the current set of array drives
8. Format old parity drive to make it usable (it will start off unmountable). This only takes a minute or so and can be done while the parity rebuild is in progress.
this avoids the lengthy clear process that would take place in your original step 6.
Which share do you think should be moving files to the array and from which device?
in the syslog I can see mover trying to move files off ssdone but failing because it says the files already exist. Mover will not overwrite existing files.
I can see reference to several shares having files on both ssdone, and on ssdcache which may be confusing things if the same files exists at both locations. Have you tried to move files from one to the other manually at some point and left the original behind so you have duplicates. I also do not see ssdcache being listed in the output of the ‘df’ command which I find strange.as it appears to be mounted in the syslog.
Anything other than 0 for Pending Sectors is never a good sign, and with the number you have I would think the drive could fail completely any time now.