itimpi

Yes - I’m the idiot 😊 The settings just put the server into listening mode for log messages from another machine. To actually get anything logged for this machine you either need to use the Mirror to flash option or put your server’s IP address into the remote server field. This is described in the link.

Especially as that is now an old release that has been superseded.

The diagnostics do not seem to include a file from the syslog server. It might be worth posting a screenshot of your syslog server settings so we can check they are correct.

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

UNraid has already failed to mount the file system, so you need to select the option to zero the log. After doing that you restart the array in normal mode and the drive should now mount.

Your screen shots suggest you need to check the "Yes I want to do this" to be able to start the array.

In normal running you should not get files on both cache and array which was why I asked if you had done anything that might cause this. In terms of removing files you can use the Dynamix File Manager built into Unraid. as it allows you to navigate directly to drives/pools However as I mentioned it will be up to you to determine if the copy on the cache or the copy on the array is the one you want to keep. Do NOT delete files from the User Share level while doing this as you cannot tell at that level whether the file is on the cache or the array as User Shares are a combined view across drives and pools.

The mover logging shows that files it wants to move from the cache to the array already exist on the array. Mover will not overwrite existing files, so you have to decide which copy to keep. Not sure how you got into this situation? Have you been trying to manually move files? BTW: You do not normally want to leave Mover logging on permanently, so turn it off again once the issue is resolved.

Did not spot anything obviously wrong on a quick look through the diagnostics. Perhaps you should clarify exactly what you mean as it is not clear what your issue actually is? Is this a problem that mover is not transferring them to the array on schedule or do you mean something else? If so then enabling Mover logging and then getting new diagnostics might give a clue and it might also be worth mentioning a share that you think has problems. If it is something else then what exactly? BTW: I notice that you do not seem to have set the Minimum Free Space setting for either your 'cache' pool or for the User Shares. It is always a good idea to have this set and ideally the value would be larger than the biggest file you expect to write to Unraid.

We normally want the whole of the zip file generated by using Tools->Diagnostics (attached to a new post in the thread so we get notified something has been added).

The most likely reason is that the plugin does not think there is a parity rebuild going on? Having said that, when you first start a parity rebuild it can take some time for the plugin to notice. When the plugin is idling there can be quite a long delay between it checking (up to 17 minutes), although it checks more frequently once it knows an array operation has started. The diagnostics, however, do not show that a parity build is in progress so maybe something else is causing your disk activity.

The parity.check.tuning plugin can pause/resume a running check, but it does not initiate one (that is up to Unraid) so something else is going on. Also if the plugin is taking any action there should be entries in the syslog and I could not see any. Having said that it is easy enough to disable the plugin from doing any pause/resumes by disabling the options to do so in the plugin settings.

As you can see lots of .plg files there - one for each plugin installed. If you want to temporarily disable a plugin without completely removing it you can change its .plg file to have a different file extension and then rebooting. Reverse the process to enable it again.

The key would be invalid if used on a new flash drive. You need to get network working as internet access is required to allow a licence transfer to be done.

Earlier Unraid releases did not have built-in support for NTFS so reusing drives previously used with Windows was showing the drive as “unmountable’ so users formatted it so this issue was much less common.

If a drive was already formatted, then UNraid uses the existing format.

I would try using the file manager built into Unraid.

Good catch - fixing as part of next release (which is about translation support requirements).

The diagnostics suggest there is a capitalisation issue as it mentions both a d————-s and a D———-s type share under config/shares

Unraid is now fussy about whether the case of the share .cfg files in the config/shares folder on the flash drive matches the case of the actual share folder on the arrsy/pools.

Make sure the capitalisation of the .cfg file for the share in the config/shares folder on the flash drive matches the actual capitalisation of the share folders on the hard drives/pools.

Read errors are frequently related to connection issues (power or SATA). The best way to test a disk’s health is to run the extended SMART test on it. 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.

CRC errors do not cause disk to be disabled - they just trigger retries. A disk only gets disabled when a write to it fails. The CRC error could, though, be indicating a cabling issue for the drive (either SATA or power).

UNraid thinks it is NOT in IT mode since it is using the megaraid dtiver.

You can use the Tools -> New Config tool to allow you to reset the device assignments