pasgener

I realize that this is years later, but thanks for the ntfsfix tip. That worked perfectly for me as well.

Thanks, just did. Warning gone. Much appreciated.

Got it, thanks.

Hi all. FCP just threw up this warning: "Invalid folder rootshare contained within /mnt". I had just restarted my Unraid server. The folder "rootshare" is indeed in /mnt and is empty. I have just replaced my parity drive with a larger drive (the parity rebuild process is complete), and I am now in the process of replacing one of my data drives with a larger drive (that data-rebuild just started and is ongoing). I have no VM running. I have only one docker running (tonido). I don't recall creating that folder! I have standard shares and never tried to create an overarching "rootshare". tower-diagnostics-20220311-2109.zip Diagnostics attached. Appreciate any thoughts/suggestions. Should I just delete that "rootshare" folder? Thanks in advance.

I did try it -- no joy! Thanks tho.

I also have several Win10 systems on my home network, and only have problems with my Win10 Pro clients (the rest are Win10 Home). With Win10 Pro the only solution that works to allow File Manager access to my unraid server (either with server name or with IP address) is to create a User/Password combo on Unraid that matches my Win10 system, and then manually create those credentials in Windows Credential Manager. Then I can connect like I always used to, For some reason the tips to turn off password protected sharing, and allow SMB 1.0, and allow insecure guest no longer work with 20H2 without that account -- as far as I can determine!

Thank you! Your suggested change to the gpedit policy fixed the inability of one of my Win10 PCs to access unraid shares after an OS reinstall (Win 10 Home 1909).