trurl

The Unraid OS runs in RAM. The OS is unpacked from the archives on flash into RAM and it runs completely in RAM. All the usual Linux OS folders such as /etc are in RAM. Only mounted storage persists. If you want any changes to the OS folders you will have to reapply them at each boot.

Did you copy that backup config folder with all its contents, or did you just copy the contents of that backup config folder? You need to have the folder with all its contents on the flash drive as a folder named config.

Unmountable could have been due to problems trying to emulate the disk with errors on the other disks. Fixing the connections might have fixed the errors on the other disks and so made the emulated disk mountable again, and thus the rebuild would have been mountable when it completed. In any case, even unmountable can often be repaired to recover most if not all data. So even if it was still unmountable after a successful rebuild there were still ways to fix it. From your description I think your situation wasn't really that bad until you proceeded to make it worse. Next time come here and ask for help.

It was telling you that mnt/user/Sutflix should have been /mnt/user/SutFlix Your way of listing these mappings isn't very helpful. Just post the docker run command.

If you don't have the docker templates from your previous config then you won't be able to work with your dockers from the Unraid webUI. Deleting docker image and setting them up again would be the way forward unless you can make a good install with a good backup of your previous config.

Your screenshot says it is trying to access unraid on port 82. Any idea why this would be so? The default port is 80 like any webserver, and if you don't specify a port in your browser port 80 is what it assumes.

Do you have other browsers open to the webUI? What is the specific error you are talking about here: As mentioned previously, even with a completely new install, there are some things still with the dynamix name because dynamix is the webUI itself. Looking at the syslog in these diagnostics, I can see that no plugins are loading. And no plugins exist on flash. But I can also see that you have some files on flash that are not the defaults, such as user share settings. And other cfg files are not default either. Your disks are assigned and mounted and you even have an unclean shutdown. Is your new flash a Sandisk Cruzer Glide? Somehow you are confused about having made a new install.

See the "Need Help" sticky pinned near the top of this same subforum for suggestions on how to get us more information.

Parity is not top priority since parity doesn't contain any of your data. Fixing connections on all disks and then starting the rebuild of the data disk again would have likely resulted in success.

We have certainly helped people recover data in similar situations. Without more information at this point it would be speculation but I would say probably. From your description these were likely just connection issues as often happens when people open the case. The way you approached the problem from the beginning was not really correct. Shouldn't have been necessary to remove any disks at all. I think you must have misinterpreted the wiki. It probably just said to unassign the disk, not physically remove it.

If you delete the appdata then install plex you will be starting fresh with plex on your server. I don't know if that is what you're asking.

You have asked this question on 2 different threads. I have split this into the thread you originally asked it on so the responses can be coordinated.

Did you delete the plex appdata? If there is any corruption that is where it would be.

You have never posted here before.

Have you read any of the thread for the Nvidia "plugin"? Hint: Don't ask that question there, just go read.

You downgraded to Unraid OS 6.8 then. The Nvidia "drivers" you reinstalled is not simply the drivers. It is actually a custom build of a specific version of Unraid itself. So you are no longer running Unraid 6.8.1

You left out the smiley then

Just rename config/network.cfg on flash so it will use default network settings, which includes DHCP. I always use DHCP instead of static and then reserve IPs by MAC in the router. That way there is only one place to manage the IPs for everything on my network.

Unless specifically asked for something else, you should always Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your NEXT post.

Why didn't you ask for help? Actual data loss is rare if you do things right.

Just an update to the docker or an update to the application wouldn't have fixed the problem since the docker or the application wasn't the cause of the problem. Probably you changed something else that caused it to stop. I still think your docker image usage is too large at 38G, and docker allocation of 200G is ridiculous. Exactly my thoughts. Are you actually using all those NerdPack modules you install?

Still recommend booting from USB2 port. USB3 often gives problems with disconnects for the Unraid boot flash, and USB3 speed has no benefit for the Unraid flash since it just loads the OS into RAM at boot and the OS runs in RAM.

Does it log those messages in SAFE mode? Unrelated, but you have literally the largest docker image I have ever seen, 200G. I guess it's possible but unlikely that your large number of dockers is legitimately using the 38G of that 200G it has currently, but usually a docker image that large means one or more applications are misconfigured and are writing into the docker image instead of to mapped storage. Have you had problems filling docker image? If so that might explain why Making docker image large will not fix this problem, it will only make it take longer to fill. Docker image should not grow. I usually recommend 20G as being sufficient for most users. The typical cause of filling docker image is application writing to a path that does not match the container mappings. Common mistakes are not using the same upper/lower case as in the mappings (Linux is case-sensitive) or not using an absolute path (beginning with /). And your system share is on the array instead of all on cache where it belongs.

Was there something actually wrong with the old flash? Are you booting from a USB2 port? You should be.

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.