Prem0

Removing the faulty drive(sdc) resolved the issue. I should have started there, thank you for the assistance.

hedonistmedia-diagnostics-20220710-1943.zip

The active drives are /dev/sdf1 and /dev/sdj1

I had a cache pool drive fail and replaced with new drive, mirror repair finished successfully but after system reboot I am getting the error: Unmountable: Invalid Pool Config. I searched and found that this is a bug and a reboot should fix the issue but that is not happening here, I have rebooted multiple times and the error persists. I checked the syslog and I see this but do not know how to resolve the problem, it looks like the bad drive is still in the pool config(it is still in the system but not mounted, waiting to remove) Jul 10 19:42:45 UnraidServer emhttpd: shcmd (52): mkdir -p /mnt/vm_cache_mirror Jul 10 19:42:45 UnraidServer emhttpd: /mnt/vm_cache_mirror uuid: 735f5a28-a992-4be9-b621-47603518b082 Jul 10 19:42:45 UnraidServer emhttpd: /mnt/vm_cache_mirror Label: none uuid: 735f5a28-a992-4be9-b621-47603518b082 Jul 10 19:42:45 UnraidServer emhttpd: /mnt/vm_cache_mirror Total devices 2 FS bytes used 187.40GiB Jul 10 19:42:45 UnraidServer emhttpd: /mnt/vm_cache_mirror devid 1 size 931.51GiB used 185.06GiB path /dev/sdc1 Jul 10 19:42:45 UnraidServer emhttpd: /mnt/vm_cache_mirror devid 2 size 931.51GiB used 190.03GiB path /dev/sdf1 Jul 10 19:42:45 UnraidServer emhttpd: /mnt/vm_cache_mirror devid 3 size 931.51GiB used 190.03GiB path /dev/sdj1 Jul 10 19:42:45 UnraidServer emhttpd: /mnt/vm_cache_mirror mount error: Invalid pool config Jul 10 19:42:45 UnraidServer emhttpd: shcmd (53): umount /mnt/vm_cache_mirror Jul 10 19:42:45 UnraidServer root: umount: /mnt/vm_cache_mirror: not mounted. Jul 10 19:42:45 UnraidServer emhttpd: shcmd (53): exit status: 32 Jul 10 19:42:45 UnraidServer emhttpd: shcmd (54): rmdir /mnt/vm_cache_mirror Any assistance would be appreciated.

Well I have applied the upgrade again and it was doing the same thing but this time after the reboot it let me connect to the shares after putting in user/pass for a public share. This is only happening in Win10 as Linux has no issues connecting to shares. Is there something I am missing in Win10 settings for network shares? I did use the regedit HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth but that did not seem to fix the issue before. Any advice would be appreciated because I have had issues accessing a private share at times as well.

I upgraded to 6.6.3 and once the system had rebooted I was unable to access the shares via a windows 10 machine, it would constantly ask for a user/password then fail. I have one share that is private but all the others are set to public, after the upgrade I set the private folder to public as well and this did not fix the issue. I was able to revert back to 6.6.2 and everything started working again. I am new to unraid and installed with 6.6.1 and the upgrade to 6.6.2 went without issues. Any ideas of things to try? I am have not tried the upgrade again because I need access to these shares and downtime is a problem.