blueboyscout325

Is there no way other than to rebuild? I don't have a spare 8TB to swap in or back up the data to and I'd rather not have to risk losing the data already on the disk during the rebuild if an error were to occur.

I've had an issue with a drive becoming inaccessible and showing in the array as "not installed". I rechecked the connections and eventually swapped the SATA cable for this drive. It had been emulated for the past week or two. Now rebooting the server, it still says "not installed" for that drive in the array, but this drive is now showing up as an unassigned device in Unraid. Why is Unraid not recognizing the old drive being apart of the array? Were changes being made to the emulated drive and now I have to rebuild it on top of the old drive that should have almost the same information? Is there a way to bring it back into the array without a rebuild? I have attached my diagnostics. I appreciate any help with this. tower-diagnostics-20211211-1801.zip

I'm having issues with my R605 becoming disconnected and then cannot be readopted. I'll also noticed that my two EAP245s will become periodically disconnected at the same time and will automatically be readopted. I don't think this is expected behavior and I'm wondering if it's related to the discovery ports. I currently have it set to network host with the ports passed through. Could switching it to the br0 bridge and giving the controller it's own IP potentially solve my issues?

Yes, I had tried that, but I couldn't seem to get the container to start up with the port 80, it kept defaulting back to 8080, probably from a clash with Unraid's webUI using port 80. But I did get it to work for me by changing from bridge to br0 and setting a custom IP address.

Any update with using this with a port other than 80? Or how do we go about changing port 80 on Unraid so that we can use this docker with it?