itimpi

Not sure why you want to look at the legacy documentation as most of it is out-of-date. What is wrong with the FAQ entries under the Unraid OS part of it which is far more comprehensive and relevant to current Unraid releases.

The diagnostics show continual resets on what I think is disk5. This suggests what is most a cabling issue (SATA or power) to the drive although I guess it could be the drive although this is less likely.

The Documentation links at the bottom of this forum, and the one at the bottom of the Unraid GUI work fine for me.

Just follow the process 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.

You have a limited number of automated licence transfers per year. If you need to do more than that then you need to contact support.

The second screen shot shows nothing assigned as Secondary storage. You would require Merlin as primary storage and array as secondary storage to have the array->Merlin option available for mover.

You should wait until the 6.13 release appears to see if it happens in that timeframe. I believe it requires some fundamental changes to Unraid do is not a trivial change.

A point to note is that Unraid itself effectively cannot get corrupted as a fresh copy is loaded into RAM every time the system is booted. I did not see any obvious signs of file level corruption on the drives either.

The online documentation is accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The You want to go to Unraid OS ->Manual->Troubleshooting section for guidance on Unclean shutdowns.

No. The plugin will never cause an unclean shutdown to happen but it simply tries to make it obvious when it happens. The message is correct if a parity check started. Have you looked at the section of the documentation that the notification suggests you look at.

The syslog server file is not part of the diagnostics. You need to post that file separately.

That is expected behaviour. The potential cutover points are based on the size of the largest data drive. Since you say this is 8GB the first cutover point will occur when disk1 has 4TB left. Since at this point no drive has more than 4TB free then disk1 will continue to be used until it has 2TB free. It as that point you should expect disk2 to be used until it is down to 2TB free, etc This is described in some detail 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.

Try using the Manual method of creating the flash drive - it tends to be more reliable.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

Should not need to do this if files are copied over the network. It tends to be needed when some other mechanism (e.g. rsync) is used to copy the files that bypasses setting the security the way it would be if done via SMB. There should never be any problems with rerunning this utility though if needed.

There are two possible things coming into play. One is the difference between decimal GB and GiB (binary v Decimal), and the other is space occupied rather than size of the data in the files.

This is always the most likely. Do not forget, however, power cabling to drives can also cause difficult to diagnose issues, particularly if splitters are used to get the required number of connections. The PSU itself is sometimes the culprit as well if failures tend to occur at times of peak load.

This is the one that is not always conclusive. A failure definitely means you have a problem, whereas a pass is merely indicative. Having said that it is a good resource - I may make a note of it for suggesting it be used in the future for those experiencing potential hardware problems.

In my experience waking at a specified time is almost universal. What is less common is Wake-on-LAN. I personally make use of that in conjunction with the Parity Check Tuning plugin option to restart array operations (from previous point reached) to allow me to automatically power my system off every night without it causing me issues.

You should probably run Tools->New Permissions (probably better named as Reset Permissions) on the shares to get them to the Unraid defaults so that the SMB level ones then get applied for network access.

Not at the moment as far as I know. Whether an official API is ever going to appear I have no idea but with the large number of internal changes likely to be needed for the 6.13 release that release is probably Limetech's priority at the moment.

It is also worth pointing out that disk1 and disk2 are still using reiserfs which is now deprecated. Maybe now is the time to consider getting these converted to one of the other file system types supported by Unraid.

I would suggest following the steps described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

You could have also selected the 'mirror to flash' option that puts it into the 'logs' folder on the flash drive.

Are you getting the Unraid boot menu? If not then rewriting the bz* type files as described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom might help.