lfas

On a whim, I downgraded to 6.9.2, renamed "rootshare" to something else, then updated to 6.11.1. The share is now there and behaving as expected.

Yes, it was probably the first share I created when I first started using Unraid. Well before I even knew about or installed the Unassigned Devices plugin.

I've been on 6.9.2 for ages since any time I've tried to update past it, a single share called "rootshare" disappears. All other shares are still there. The data for "rootshare" is all still there and I can access it through Krusader. But it isn't listed under the Shares section, and I can't access it through NFS or SMB. Any ideas? I'd like to update the the latest Unraid version. Diagnostics were taken immediately after upgrading to 6.11.1 icaria-diagnostics-20221021-1516.zip

Thank you, I will do both those things. For the scrub, should I enable "repair corrupted blocks"?

Thank you for the reply. I will setup the syslog server as you recommended. The only way I know how to test if it is the controller or power is to use a different motherboard and different PSU. Is there an easier way to test?

I was having issues booting my Windows VM, so I did a clean reboot of unraid. When it came back online, my parity disk was disabled. I stopped the array, removed the disk, started then stopped the array, and re-added the disk and now it is doing a parity rebuild/check. But I am concerned, and don't understand how to interpret the logs. In the past, disk 4 would randomly disable itself (and as far as I could tell all the SMART tests checked out). I eventually determined disk 4 was disabling due to a bad cable, which I removed from the system. Disk 4 has been fine since then, but now that the parity disk disabled, I am worried since I didn't touch it. What should I do to make sure my system is running correctly? The diagnostics I attached are from right after I rebooted and noticed the drive was disabled. icaria-diagnostics-20220727-1046.zip