trurl

If the controller has a BIOS update for this issue then update it. I had a controller with this issue and BIOS update fixed it.

I have one disk with 2 CRC errors. I acknowledged them long ago by clicking on the "thumbs down" on the Dashboard. Since they haven't increased I don't get any further warnings. Is that what you have done to acknowledge them? Have they increased?

You didn't mention those details in OP. If your dockers are setup with only mappings to user shares (or possibly cache or unassigned device), and the data is transferred to those same user shares on the new server, then the dockers should all just work when you get all the data transferred. Don't enable docker service until the transfer is complete. The templates containing all your docker settings are on flash, and you can reinstall them exactly as they were using the Previous Apps feature on the Apps page. Then the applications should work just as before using their existing appdata.

You can tell FCP to ignore the warnings. CA and dockerMan (the parts of the Unraid webUI that manages dockers) don't currently work with docker compose.

syslog is in the logs folder of those diagnostics you posted. The csrf errors I posted earlier are an excerpt, and your parity error corrections can be seen near the end of that syslog. Other than that I was just going on your description and making the usual recommendation for when parity needs correction.

Since this is your first post I wonder if you are aware that the WireGuard VPN is builtin to Unraid now:

Some older controllers only support 2.2TB

Since this is not installed using Community Applications or Add/Edit Container page (dockerMan), CA doesn't know about it and the Unraid webUI has limited ability to manage it.

And in case you don't know, you will have to rebuild parity (after you get your hardware problems resolved) to get it enabled again.

You don't want to run very long on UPS before shutting down since you don't want to start back up with a low UPS battery. But your syslog goes back a couple of weeks so your UPS must have kept your server up. I didn't notice any UPS messages in syslog, does it have a data connection? A non-correcting parity check after a correcting parity check is the way to go since if there are still parity errors they may have some other cause than the actual parity data so correcting them doesn't really help anything. That is also a good reason to run non-correcting parity checks normally, since you expect to have zero errors, and if you don't you might like to investigate some other cause before you actually correct them.

Then again, using that page should let you launch it with all its parameters from the form without having to actually type it all in each time, since the page saves the template.

A lot of this in syslog but it was a couple of weeks ago: Apr 25 19:46:52 Jiraiya root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 25 19:46:52 Jiraiya root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Apr 25 19:46:53 Jiraiya root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 25 19:46:54 Jiraiya root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Just FYI here is the FAQ on that: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=545988 Was this a scheduled check or did you start it yourself? If you did start it yourself, why did you want to run a parity check? Do you normally run a correcting parity check? Always recommend another parity check to confirm no parity errors still detected. Sometimes problems like bad RAM can give inconsistent results.

OK, I get it. Really no point in getting Add/Edit Container involved at all then if you have to do an actual docker run. Don't know about those additional dockers it spawns, maybe that is just the way it works. Do they go away when it has finished?

Can you be more specific? What exactly do you enter at the Unraid terminal? Do you get any error messages from the docker run?

You can edit files directly on the server from the webUI using this:

Why not just move the existing disks and Flash to the new build before adding anything else? Then you will already have all the data and dockers just as they are.

The Add/Edit Container page is just a form to enter the parameters of the docker run command. Once you have submitted that form, you have executed the docker run command. Then you just need to get into its command line. When you had it running could it actually access your cd?

This is what docker does when you don't specify a name, it makes up a name from some builtin dictionary. Even though this is a command line application, you should be able to use the Add/Edit Container in the usual way. If the container includes bash you should be able to get to the command line within the container by clicking on its icon (generic unless you specify one in the template) and selecting Console. How exactly are you doing this?

Maybe if you had a more concrete example your question would make more sense. Do you have a particular container in mind? Many have their "working storage" in appdata, but specific containers may not expose the files you need. If you do have a specific docker in mind, it might be more useful to ask on its support thread. You can always go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support.

It doesn't go back to zero, and it isn't a sign of a failing disk as noted. You can acknowledge the SMART warning on the Dashboard by clicking on it and it will alert you again if it increases.

Why have you attached a .rar file? The Diagnostics are given to you as a single ZIP file. Attach that ZIP file just as you got it.

If an application writes to a path that doesn't exactly match the container path including upper/lower case, or a path that isn't an absolute path, then that path is inside the docker image. This is how you can fill docker image. If you map a host path that isn't an actual disk or user share, then that host path is in RAM just like the rest of the Unraid OS. This is how you can fill RAM with docker. You certainly have a lot of dockers. Do you really need all those, or are you just experimenting? Are you really using emby and also plex, for example? Many of those I have no experience with or even know what they are for. Probably we are not going to get into the details of many of them so it would be best if you can figure this out on your own.

Do you have a link where you read this? This seems like a paraphrase of a misunderstanding. And rebuilding instead of trusting parity is almost always the right choice, since the disabled disk is the one out-of-sync. You must not have followed through on the New Config because that would definitely have gotten you out of the state where the disk was disabled. You left out some steps in your description here, but you must have done them or it wouldn't be rebuilding the disk. stop array unassign disabled disk start array stop array reassign disabled disk start array to begin rebuild The reason you have to start the array with the disk unassigned is so Unraid will acknowledge that you have replaced the disk when you reassign it, so it will begin rebuilding. It really would have been better if you had asked before doing anything. Many people have fumbled around and gotten themselves into a situation where they can't recover because they tried different things before asking for help. It sounds as if you may have stumbled on the recommended procedure at last though. Going through New Config before getting to that recommended procedure could have been a very bad mistake if the disk truly was bad. If you have further trouble, ask (and post your diagnostics).

I don't use the plexinc docker, I am using Linuxserver.io plex instead. But your plexinc docker mappings don't make sense to me. Why do you have 3 different container paths mapped to the same host path "/mnt/user/appdata/PlexMediaServer"? I just looked at the plexinc documentation on dockerhub, and your mappings don't seem to conform to those docs either. What is the purpose of the container path "/data" in your mappings? And wouldn't it make more sense if the "/transcode" container path was mapped to something other than the exact same path "/config" (your plex library) is mapped to so your transcodes aren't just dumped into that same folder with your plex library? None of that would cause filling docker image problem, but it does make me wonder if you know how to setup dockers. The reason I picked on NextCloud and Plex is because I am using those myself and have some idea what they are and how to set them up. One of the others you are running may be the cause of your problems but it would take a lot more research for me to figure out what you may have done wrong with those. Do you understand docker mappings of host paths to container paths? Do you know Linux is case sensitive? Do you know to use absolute and not relative paths to refer to the container paths within the application? Do you know why I'm asking these questions and what their importance is?