itimpi

Doing this for all forum posts would be a big job and thus I suspect this would not happen. Most of the information that was in forum posts should already be in the new docs. If you notice any broken links internally with the Unraid OS or Unraid Connect parts of the documentation these are worth pointing out as they should be fixed as that is deemed to be the most up-to-date documentation.

On a newish drive I would be worried if this value is not 0. In theory reallocated sectors are OK as long as the number stays stable, but this number on a new disk suggests to me it may have been damaged in transit.

Since mover is about individual files rather than the whole array I would not consider it an ‘array level’ activity. That does not mean that there is not a case for having more visibility of when it is running. As you say mover can affect performance and if you have the Parity Check Tuning plugin installed you can get ‘notice’ level notifications when mover starts and stops if it happens at the same time an array operation is running as these two types of operation interact badly from a performance perspective. There is a trade-off around when to generate notifications. I think many people prefer to get none at all in normal daily running if everything is running smoothly, and only get informed about deviations from that.

Enable the syslog server.

Unraid never moves files between array drives by itself. This needs to be done manually or using something like the unbalance plugin. Not sure therefore what you are running that might move files in this way.

If the process you outlined here does not complete then it strongly suggests there really is a problem with the drive and it may need replacing. No point in resetting the array configuration if the rebuild continually fails until you have a replacement. Having said that I would carefully first check the cabling to the drive, especially the power side and avoid using power splitters if possible because as was mentioned earlier cabling is a far more common that physical failure of a drive.

The diagnostics show that the drive drive dripped offline and subsequently got write errors which is why it was disabled. The commonest cause for this is the power and/or sata cabling but you say you have checked both of these. To clear the disabled state the drive needs rebuilding and if you want to do using the same drive you can do this 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. The Unraid OS->Manual section covers most aspects of the current Unraid release.

At one level I agree with you, but since a parity check is a major array operation that has a long elapsed time and can significantly affect performance while it is running I can see why it might be deemed more appropriate to treat it as a warning rather than a simple notification.

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.

A CPU overheating would definitely cause random crashes as the system shuts itself down due to thermal overload to protect the CPU.

What is this - it is not normal.

Once you have enabled the global option it should be automatic if a share is set up to have all its files to be on a single pool/drive and that is how they are actually currently placed If it is not enabling then you have probably not met that criteria.

You currently have the number of array devices set to be a max of 3. You need to increase that if you want to add more drives.

You could also try rewriting the bz* type files as descibed 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. The Unraid OS->Manual section covers most aspects of the current Unraid release.

The CRC errors never reset themselves, so you only have an issue if they keep increasing - and even then it is normally a sata/power cabling issue rather than a problem with the actual drive.

No.

In principle that will work if set up correctly. You need to allow for the behaviour of move commands at the Linux level as described in the Caution section of this part of 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.

Unraid never moves files between array drives by itself, and mover will only move files between a pool and the main array. Were you expecting something else?

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.

I think you must have reinstalled Tailscale after booting in Safe Mode?

No problem doing what you mention, and in fact checking out Unraid satisfies your needs before you commit to buying it is always recommended.

I could not spot an obvious reason in the diagnostics. The definitely show that the media share has files on both cache pool and on disk1. I would suggest running a check filesystem on disk1 as sometimes file system corruption has stopped shares showing up.

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

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

According to the diagnostics you HAVE enabled the option to run rebuild/sync in increments, and the increment active time is 01:15 to 04:00 so outside that timeslot it will be paused.