itimpi

You would definitely need another 1TB drive. You just need to make sure the pool is set to the RAID1 profile (which it already should be) and then run a Balance to get the data moved around correctly. When the Balance completes then you will have 1TB usable space.

Looks like the S3 sleep plugin is actively shutting down the server. I suggest either disabling it or removing it. Not even sure that plugin is compatible with recent Unraid releases.

Do not see at the moment why web gui is not enabled, but diagnostics suggest ssh access has not been enabled under Settings->Management Access

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

I would say that the obvious answer is to set the Logging setting back to its default of disabled. The Help for that setting does warn you that the log is being written to RAM.

I would say yes. You should never be using a drive that cannot complete the Extended SMART test in your system.

This almost certainly means a hardware issue. Logging to an external source is unlikely to help if you have set the syslog server to log to the flash as that is more likely to catch something (if there is anything to catch) than a network resource. You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

Not necessarily. In theory files should not exist on other drives so you do not end up with duplicates. However if by any chance they already exist on other drives then you end up with a duplicate.

It is normally less error prone if you leave that set to include all disks, and then handle any excludes/includes on any share you want to restrict to particular drives.

Yes - you can get duplicate files. Unraid will show the first one it finds which can lead to confusing results as if for instance you delete one it promptly reappears as the other copy now gets uncovered. Using Mover to handle the move avoids duplicates but can be significantly slower particularily if there are a lot of small files.

Do NOT do this - it is likely to result in data loss as you are mixing a User Share and a physical device in the same command which can result in files being truncated to 0 size. If you had used something like the Dynamix File Manager that is built into Unraid to do the copy it would not allow this combination of source/target. In this case you need the target to be another physical device such as a specific data drive (e.g. /mnt/disk3/appdata)

I think you really mean they went to /mnt/user/appdata? The path /mnt/user/cache/appdata refers to a user Share called 'cache' that contains a sub-folder called 'appdata' Once upon a time we always used to recommend using /mnt/cache/appdata as it performed better than using /mnt/user/appdata if the files were actually on the 'cache' pool as it bypassed the Fuse layer in Unraid. . Nowadays with the support for Exclusive shares the /mnt/user/appdata path performs just as well if 'appdata' is an Exclusive share as Exclusive shares also bypass the Fuse layer.

You can do it the other way around with the Parity Check Tuning plugin (i.e. pause the array operation if mover is running).

That is true for calculating the initial parity. It is also true if you have ‘Turbo Write’ enabled to improve array write speed.

He did (probably hidden initially) ! Looked to me as if it was possibly a share not configured correctly to be moved rather than a plugin issue.

Easiest might be to use a USB dock to attach the drive (if you have one).

@foamy it might be worth posting your system’s diagnostics zip file and the name of a share you expect to move. Quite frequently issues of the sort you describe are caused by incorrect share configuration.

Do NOT use New Config because as the warning said you could then not rebuild the array drive. click on the ‘cache’ pool on the Main tab and select the option to Remove Pool. You should then be able to start the array to begin the rebuild.

UD will only mount drives that have a partition. If it does not then you can still mount it manually from the command line. However if it does not have a partition and is empty then it might be easier. to create a partition on it and reformat it so that UD can manage it going forward.

It is this one. I would try removing it to see if the problem disappears. Are you sure that is the mapping you have set up? FCP is saying there is a /mnt/disk/ (without the ‘s’) being created. This appears to be missing 😕

No. You are meant to configure docker containers so all their variable data is mapped to external storage. The docker.img file is only meant to contain files that are not part of the containers working set, so normally no reason to consider backing up the docker.img file.

The device limit applies to all storage devices attached to the server (at the point you start the array) regardless of whether they are used in the array or a pool or left unassigned. You will therefore have to continue with the device disabled or switch to a licence that allows for more devices.

I use that technique with just a few extra lines in my script that may not be strictly necessary but I think makes it a bit tidier. logger "overnight powerdown" pkill rsync shutdown -h now For me I worked out that shutting down overnight when the server would not be used is worth about £200 annually in reduced electricity costs so definitely worth doing.. That was also the impetus that made me think it was worth getting the 'restart' option working in the Parity Check Tuning plugin so I did not lose progress on an array operation if a scheduled overnight shutdown occurred.

If you look in the instruction from the diagnostics command it mentions the option of logging in at the command line and using the ‘diagnostics’ command.

A rebuild does not clear an unmountable status (It clears Disabled status). As was mentioned you need to do a check filesystem to find/fix file system level corruption. We often recommend this is done before the rebuild (in case a disabled disk is in better state than the emulated one) but it can be done at any point.