dlandon

Setting pass through will not do anything more than what you already have.

'Pass Thru' switch in the UD page.

You can't hide a device from UD. The best you can do is to mark it as passed through so UD will ignore it.

I just released an update to fix this issue.

Tips and Tweaks will set the CPU Governor for all 8 reported CPUs, so it should be working fine. I don't see an issue.

What is the output of the following command? cat /proc/cpuinfo | grep processor | wc -l

Works for me.

You can disable it in Settings->Management Access.

Clck on the '+' and then click on the check mark and see if there are disk errors. If there are, click on the run with the correct flag button.

New release of UD. Highlights: Re-arranged the UD page to more align with the Unraid disk stats. While there is not a perfect alignment of comparable table entries (pretty difficult because of the dynamic nature of UD), the table entries like FS, Size, Used, and Free are in the same columns. Device size, used, and free are now determined on a timed basis to cut down on UD page load time. These stats are done using 'df' which is prone to hanging if cifs mounts get disconnected so this should help with the appearance that UD is 'hung'. Script Edit and Log icons are now in one table entry instead of two saving some row space and allowing Size, Free, and Used to better align with Unraid disk stats. The table entry alignment is most moticeable in the Non Tabbed view.

What probably happened is that Ubuntu created multiple partitions and the first one did not have a file system. If you click on the '+' next to the drive serial number, all the partitions on the drive will show. Any that have a valid file system will show an active 'Mount' button. The first partition on the drive is the one that shows the drive mount status. So there could be mountable partitions on the drive, but not show as mountable on the drive.

Yes, I meant doesn't recognize. You aren't missing anythng. Ubuntu may be partitioning the disk in a non-standard way that Unraid can't understand. Good solution.

Unraid (Linux) does recognize a file system on those disks, so UD cannot mount them.

Before the latest release (2020.07.19a), there was an issue where this would happen. Be sure you are updated to the latest UD.

That should not be necessary. I've never had this happen. If someone gets in this situation, please post diagnostics so I can troubleshoot.

While I appreciate your interest in esthetics, there is more to consider than just 'aligning' disk drive mounts: This disk is mounted without a UD script, it is probably better to put it in the cache pool of 6.9. UD was intended to be a backup/temporary mount plugin. Now with the cache pool feature of 6.9, it is probably best to move the drive to the cache pool. You get alignment like you want with temperature and error monitoring that the cache pool provides. The remote shares also would have to be considered in any page alignment and might be more challenging. Yes, the flow doesn't work for me. All that being said, I will continue to work on the layout and improve the 'look' of UD as I see things to make it better. I am open to new ideas. UD was originally written for older versions of Unraid and the look and feel of Unraid is evolving. I work on UD as I get time because it is not a full time job for me. Really! 'Stupid thing'? It it's so stupid why do you want to use it? If you would read the first and second post, you'd see this: Your snarky attitude is not really appreciated. I find this community of volunteers providing support is the best I've ever seen for a product of this kind. We are all willing to do what we can to help you get through the challenges of Unraid and those of us doing add-on development (plugins and dockers), are more than happy to entertain new and better features if they make sense for the wider community and are not a one off request.

You need to use the English name.

Update UD to the latest version. Should fix the issue.

Unmount and re-mount your remote mounts. Re-booting the remote server probably caused these issues.

There is a device on the other end of the wireguard with the ud page open. It has nothing to do with mounts. What is the remote device?

I may have mis-spoken. The update won't make the log message go away. The csrf token check is built into Unraid and is behind the scenes. It's just that I will remove the explicit reference to the csrf token in UD that is unused.

UD does a status poll about every second and that's where the log message comes from. Somewhere you have a browser or phone app that has the UD page open. That's the only way the log message can occur. From the UD status polling.

The UD plugin mounts the remote share, but does not control access, permissions, etc to the share. You might want to look up CIFS mounts and issues like you mention here.

I'm out of ideas.

Ok. The latest version still has an explicit reference to the csrf token, even though it is not used. I'll remove it in the next release. This won't change the log message though. That being said, you still have an open browser or connecton to UD somewhere.