itimpi

Just for interest - did it look like it was a valid unique GUID?

Then there will be a log in wherever you told it to store logs if you set the server to log to itself, or the 'logs' folder on the flash drive if you used the mirror to flash option.

did you enable the syslog server as mentioned earlier to get a persistent syslog.

That is expected for a share that is running in ‘Exclusive’ mode for maximum performance.

You should not have done step 4). You would have got a pop up warning that this would create an empty file system; update parity to reflect this; and was not part of any data recovery process. Without step 4) your data would have been rebuilt onto the replacement drive. the correct process to use is documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

Looking at those diagnostics it looks like the disk you were talking about is disk11? If so then I notice that disk11 has 320 reallocated sectors so the errors may have been related to that happening. While reallocated sectors are not necessarily a problem it would be a problem if that value keeps increasing.

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.

You cannot reliably split a SATA power connection more than 2 ways without risk of voltage drops. You can get away with a 4-way Molex->SATA splitter as the Molex connector has connectors that can take a higher current draw.

You should try the procedure described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

It is possible to completely reset the array via Tools->New Config and calculate new parity based on the new drive set. However that will leave you the job of copying back to the array the files from any drives that have now been removed. You have to decide if this is less trouble than rebuilding the drives to keep their data intact.

It actually woke the disk before that. That message happens when Unraid detects a disk has just been spun up.

All licences are functionally identical - the only difference being the number of drives that are allowed to be connected to the server (regardless of whether Unraid uses them) which is checked every time the array is started.

If you use something like rsync to do this then you can set it to simply skip over files that are already there.

No easy way. You can read the description given for the app, and also click on the support link to see what others have been saying about the app. At the end of the day it will probably being a case of picking one and seeing if it meets your needs. You can easily change your mind later if needed.

If there are spaces in the name they will need to be escaped (e.g. "\ "). Your screen shots show a space in the name, but an underscore in the fstab entry. It can be much easier to simply avoid using spaces in the name for just this sort of reason.

When it gets written to will depend on the Allocation Method you have selected for the share and how full your current drives are. It can be some time! You could manually create a folder corresponding to the share name on the drive if you want to force it to show up early.

ZFS drives in the main array are all single drive file systems. You can only have multi-drive ZFS arrays in a pool.

Drives do not get added to the size for a share until at least one file or folder for that share has been created on the drive.

Yes. Do not forget the Docker Service needs to be disabled while you are doing all this.

If the file is located in the ‘system’ share (which is the default), then the linked process would work. Alternatively you could use the Dynamix File Manager to do it manually.

The process is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

That was what I was saying you should do. It seems to satisfy the Use Case you mention.

According to the diagnostics the check may only have been running a couple of minutes at the point they were taken? Is this actually the case? If so new diagnostics after the check has been running for longer might show something.

It will all depend on whether the drives always stay connected - impossible to say without actually trying it. Unraid is not 'hotplug' aware so does not handle array drives disconnecting and then reconnecting. Typically when drives disconnect and reconnect then they come back with a different sd? type ID at the Linux level and Unraid cannot handle this changing dynamically while the array is started. Note that USB drives that are NOT part of the array and are being handled by the Unassigned Devices plugin are OK as that plugin can handle drives disconnecting and then reconnecting. You are welcome to try it and I believe that some people have success with using USB drives in the array but we cannot give you any guarantee that it will work because as was said it is completely subject to exactly how all the hardware works with USB drives connected.