dlandon

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.

There is no limit on the number of disks. The disk shows in UD but won't mount? Please post yout diagnostics zip.

I don't see a disk in your arrangement that is a UD disk. I see: flash drive. 3 data disks. 1 parity disk. 1 cache disk. Can you post a screen shot of the UD screen showing the UD disk you are trying to use?

This isn't an issue for two reasons: UD won't unmount it because it was not mounted by UD at /mnt/disks. A recent update to UD wil recognize the label is 'UNRAID' and will mark the mount button as 'Array' and disable the button.

The way we try to address security issues is get Unraid releases out in a timely manner. Unfortunately, that hasn't been happening quickly enough lately. It is being delt with behind the scenes and discusssed internally. It's much better all around to release a new version of Unraid with all the latest security fixes, rather than going back and applying patches. Unraid was not designed to apply patches. For the moment there are several ways to alleviate your comcerns: Disable mac OS interoperability. Upgrade to one of the 6.10 rc's. They are using a later version of samba. I'm working with the beta rc3 and the samba is at version 4.15.3.

Please post the contents of the file '/var/state/unassigned.devices/unassigned.devices.ini'. Please don't cut and paste it, its too laege for that. Zip it and post it as an attachmennt, or you can PM ti to me.

You could try to click the check mark and see if there is a chance the drive could be made mountable by doing a file check, but I doubt it.

You'll probably have to take it to a WIndows machine and get it straightened out there.

Be sure you are on the latest version of UD. Post diagnostics if an update doesn't make any difference. It looks like the device was mounted and then disconnected and reconnected without unmounting, but the 'Dev X' designation is duplicated. This should not happen if the 'sdX' designations are different.

It's a recent change I made that broke it. Will be fixed in the next release.

Correct. I don't know what changed that affected the default mount point, but commiting a mount point (whether it's the default or your own) will prevent this issue.

I'm going to post this as a feature enhancement to Limetech and see if it is something we want to add to UD.