itimpi

Simply enabling the syslog server put it into listening mode. To actually get something logged you had to either put your Unraid server address into the remote syslog server field or use the mirror to flash option (or both).

Do they appear under Unassigned Devices? Posting a screenshot and/or your system's diagnostics zip file might help us see what is happening. How are these drives connected? Can you see them in your system's BIOS?

That is why I think that Limetech may simply grandfather in existing users for new releases (effectively a "lifetime" subscription). That would avoid upsetting the current user base and start up a more regular revenue stream. Existing users would I think be happy with a subscription model for additional licences they may now want to purchase if the price is right. I guess we are going to have to wait and see though.

True. I notice that even with the "embedded" messages posted it looks like they are tying any subscription to new releases so those happy to stay on their current release are OK. Having said that if the prices are reasonable (e.g. something like $10 per year or similar) I would think most current users would be happy to pay both to get new functionality and to get fixes to current functionality. Giving Limetech a regular income stream seems a good way to mean that we continue to get new functionality and fixes. I do notice that the web site still says current licences are valid for future releases so maybe they will simply grandfather in current users for future releases.

Even if Limetech switch to a subscription model for "New" licences I would be surprised if they do not honour the "Lifetime" current licences. A subscription model would allow for a much lower price entry point for new users which is something that has been that has been requested for some time. Note that is just my view - I have no insider information.

Yes. This is what is covered 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.

I would not bother unless you have problems with docker containers which are incorrectly configured and exhibit the symptoms this plugin helps hide.

Shame as that was the easiest thing to try. First time I have heard of this issue so grasping at straws for suggestions and nothing stood out in the diagnostics. Have you tried booting in Safe mode? If that works then it would identify that a plugin is the cause. If that works my first guess at a likely culprit would be theme engine plugin.

The automated licence transfer process requires internet access. Suspect it may not be needed if you contact support to get it transferred but not had to do it myself so may be wrong about that.

I do not believe you can transfer a Trial key to a different flash drive. I think instead you need to get a new Trial key for the new flash drive.

Not necessarily - it can be just the case that when all of them are plugged in the motherboard controller cannot handle the load of the total throughput required. This is one of the reasons many motherboards quote a smaller maximum RAM clock speed if all RAM slots are populated. Have you checked both the motherboard manual and the CPU spec to see if either of these imposes such a limit?

If you are talking about the "read SMART" entries in the syslog I do not think it is these spinning up the drives. They are done by the system just after detecting a drive that was spun down has been spun up because something accessed the drive. You need to identify what is accessing the drive to cause the spinup. The File Activity plugin might give you a clue.

Have you rebooted your system? If so 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.

Do you even have empty folders corresponding to those shares as that will trigger the warning. you can use the Compute All button on the Shares tab to see which drives have content for any particular share.

Those settings are correct for Giles to end up on the cache. You need to disable the docker and VM services under settings and then run mover to transfer files to the cache. After doing that you can re-enable docker and VM services. If any files will not move it may mean you have duplicates on the cache and the array as mover will not overwrite existing files, and you need to take manual action to delete the unneeded duplicate. once you have the shares completely on the cache you can improve performance of them by removing the array as secondary storage, and then enabling Exclusive shares under Settings->Global Share settings.

Sounds as the mover should be set to array->cache if you want the files to end up on the cache.

No idea why your system should use so much space under /run. On my system the space used is more like 4MB so 32MB is more than enough.

Pending sectors not being 0 is never a good sign as it indicates a sector that cannot be read reliably. Sometimes rewriting these sectors can clear that, but if not then the drive needs replacing.

No, but since even a single error is too many you should not need one.

The diagnostics show disks 2, 3, 4 and 5 dropped offline. Is there anything they share? Is perhaps the PSU struggling to power that many stoves?

You will need to contact support about this.

Yes, although I am not sure what the reference to disk share is about.

You would need to contact support for this. However once a drive is blacklisted as a result of a licence transfer I am not sure there is a mechanism for reversing this.

You have “Included Disks” set to All so the share is not restricted to disk16 even though that might be where all files are currently stored.

I think you are falling foul of the behaviour described in the Caution in this section 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.