dlandon

Are you using NFSv3 or NFSv4?

You’d probably have better luck with the Unraid Nvidia support forum.

The problem is with one or several of your plugins. I woud do this: Be sure to update all plugins. I saw in the log at least one is out of date. See if an update fixes the issue. You'll then need to remove pugins and re-install them one at a time watching the monitor for the plugin that displays those messages on the console when it is installed. Start with the ones you suspect are causing the errors on the console. Network Stats Plugin? VM Backup? If you find the plugin(s) causing the errors, report the issues to the plugin authors so they can apply a fix. One of the things I notice is it looks like something that wants to do downloads. And failed to connect to hypervisor? Not sure what that's all about. The author of the plugin(s) will have the answer for this. If nothing else, those errors are messy and confusing.

Just hold where you are until JorgeB can lend a hand. It will take him a while to respond because of the time difference.

I'd say this is an issue with the SSD disks. I think that we should call in the big gun. @JorgeB Can you weigh in on this user's issues? Looks like some SSD compatabiity issues.

I see several things: Feb 18 21:08:28 DataCore cache_dirs: Arguments=-i Backups -i Media -i Software -i Temp -i appdata -i domains -i isos -i system -l off Feb 18 21:08:28 DataCore cache_dirs: Max Scan Secs=10, Min Scan Secs=1 Feb 18 21:08:28 DataCore cache_dirs: Scan Type=adaptive Feb 18 21:08:28 DataCore cache_dirs: Min Scan Depth=4 Feb 18 21:08:28 DataCore cache_dirs: Max Scan Depth=none Feb 18 21:08:28 DataCore cache_dirs: Use Command='find -noleaf' Feb 18 21:08:28 DataCore cache_dirs: ---------- Caching Directories --------------- Feb 18 21:08:28 DataCore cache_dirs: Backups Feb 18 21:08:28 DataCore cache_dirs: Media Feb 18 21:08:28 DataCore cache_dirs: Software Feb 18 21:08:28 DataCore cache_dirs: Temp Feb 18 21:08:28 DataCore cache_dirs: appdata Feb 18 21:08:28 DataCore cache_dirs: domains Feb 18 21:08:28 DataCore cache_dirs: isos Feb 18 21:08:28 DataCore cache_dirs: system Feb 18 21:08:28 DataCore cache_dirs: ---------------------------------------------- Don't cache appdata, domains, isos, or system. It doesn't help on those shares. I assume you have them on a SSD cache or Pool device. For the moment, I'd remove the cache dirs plugin. Also remove S3 sleep and preclear plugins for now. There's nothing wrong with these plugins, I just want to limit the number of things that could get in the way. I also see these, but I don't know if this is an issue or not: Feb 18 21:09:03 DataCore root: Starting Nginx server daemon... Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.974 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.974 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *60 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *59 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *14 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *60 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *59 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *14 limiting requests, excess: 20.968 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *60 limiting requests, excess: 20.966 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:08 DataCore nginx: 2022/02/18 21:09:08 [error] 9771#9771: *15 limiting requests, excess: 20.384 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" Feb 18 21:09:08 DataCore nginx: 2022/02/18 21:09:08 [error] 9771#9771: *61 limiting requests, excess: 20.383 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main" You said this is a disk mounted with UD. Can you give a screen shot of the UD page? Also, how are you doing your copying?

Didn't you say that you had a nvme disk installed that gave you the performance you were looking for?

One of the other things I've done is to remove the clear disk and remove partition red X's when the destructive mode is enabled and this switch is on. I have a Windows disk in my test server and I'm constantly afraid I'll remove a partition or clear the disk as I work with UD trying different things. This keeps me from screwing up.

You mean like mount and unmount buttons or multiple devices buttons? I consider the mount/unmount to be different modes of the 'mount' button and not necessarily just when iit says 'mount'.

Sorry, I was under the impression that we were talking about an issue with samba shares. How are the SSDs attached sata or nvme?

What you are seeing is the disk caching happening with Linix. It will initially fill the ram disk cache and then start writing to disk when the disk cache gets to a set threshold. These are the Disk Cache settings iin Tips & Tweaks. If I recall, you have 128GB of ram. @ 1% dirty background, that's 1.28GB. A file transfer will fill that ram cache before committing to disk. That's why you are seeing high speeds on a reboot, because the disk cache is empty. You're theoretical max is about 100MB/s your 1GB network. Honestly, the 80MB/s is reasonable really. I want you to do some adjustments in Tips and Tweaks to the network though and let's see if it helps: Disable NIC Flow Control. Disable NIC Offload. Set Ethernet NIC Rx Buffer to 1024. Set Ethernet NIC Tx Buffer to 1024. These settings help on Intel NICs at times. See if that improves your speed. As for the high CPU use and temps, I have no idea what's happening there. I'm not an expert on iowaits, but could they also be from NIC io?

Ok, I like all your settings. Now review the issues with me. Lets start with non spinners and work our way up from there. As I understand you are not seeing good performance with a SSD device? Give me some details.

First, I apologize if I walk you back through things you've already done, but I'd like to get an assessment of where you are so we can do some troubleshooting. First look at your SSD disks and be sure they are formatted like this: For best operation, they should show 1 MiB-aligned. Give me a screen shot of the Tips & Tweaks page so I can see what you've 'Tweaked'.

This is what I've done: Please note that the switch says "Disable Mount Button". This means both mount and unmount. I need to change the text in the tool tip to "DIsable Mount Button:.

Post your diagnostics file. I see multiple things going on here.

And your network and disk controller hardware?

So in your use case, you auto mount disks and then don't unmount them manually?

Might be more cumbersome than I prefer. A few too many steps to unmount a device manually.

Cache and pool devices are not normally spinners. You can organize the log by shares and only look at the ones you want.

A passed through disk will not autmount. If it's passed through and mounted by a docker container or VM and UD mounts it, there would be data corruption. Probably the best way to handle this is with an enable check box like that used in the recycle bin plugin, and on the plugins page. The 'Unmount' button would not be enabled until the check box is checked. It would be a bit harder to acidentally click the 'Mount' button. I'll have to think about this a bit though to be sure it makes sense for everyone.

I'm a little late to this party and wasn't able to determine your current Unraid version. What Unraid version are you running?

Normally the syslog server is on the cache or a pool device. Cache and Pool devices can be set to not be monitored. The syslog server doesn't have to be on a array device.

It's that self healing feature I built into UD. It just fixes itself.

That's a lot of disks.

The limits apply to array disks, not UD disks.