trurl

Looks OK. Since you haven't started the array yet, you can just skip the first step Stop array Unassign disk Start array with disk unassigned Stop array Reassign disk Start array to begin rebuild (In this case, "disk" refers to your parity disk, but those instructions are the same for rebuilding a data disk to the same disk since it is all the same parity calculation.)

Post new diagnostics

That's OK. The reason I was concerned about whether your new disk assignments had been saved successfully was because if it thought that disk was still parity it would overwrite its data with parity. If you still have that flash drive out, put it in your PC and edit config/disk.cfg to set autostart to no so you can boot up and check your disk assignments.

You shouldn't lose any data since parity doesn't have any data and all of the data disks are independent. I guess it really doesn't matter at this point exactly how you got to where you are. Rebuilding parity is what you need to do and maybe even that is what it was doing when you said it was doing a parity check since if you put a new disk in the parity slot it is going to want to rebuild parity. Did you have any data on that new data (old parity) disk yet?

You seem to have left out a lot of important details and it makes me think you have done all of this wrong. You had a disk in the parity slot. You put a new disk in the parity2 slot and built parity2. ..... Somehow you got from there to having the new parity2 disk in the parity slot and the old parity disk as a new data disk. Is that correct? Parity and parity2 are not the same and can't be exchanged.

Still unclear. You said you added new drive as second parity drive. Did you not mean you put that new drive in the parity2 slot?

So are you saying you now have a disk assigned to the parity2 slot but nothing assigned to the parity slot?

OOPS! Guess that went backwards. We completely lost the Docker FAQ like that one time.😅 Moved it from General Support back to Docker Containers too.

I have merged your thread with the correct support thread. For future reference, you can always go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support.

Just to be safe, can you confirm that you rebooted after the new parity build and everything was fine? The reason I ask is because we need to be sure your new disk assignments were saved so it won't think your old parity (now data) disk is still parity. Can't tell much from those diagnostics, but the symptoms, including the empty diagnostics, suggest flash drive has been dropped. Put flash in your PC and let it checkdisk. While there make a backup. Make sure you use a USB2 port on your server for the flash. For future reference, you can always download a zipped backup of flash at Main - Boot Device - Flash - Flash Backup.

Your share settings look fine. One share (other than the usual) named M--O is set to prefer cache but it is all on cache so it isn't clear why anything would be getting moved to cache. Or did you change some of your share Use cache settings after those notifications?

Also for the next time, you can get to the correct support thread for any docker by clicking on its icon and selecting Support.

What happens if you click on that "Allow insecure connection"?

I know you said you copied it but sometimes people make a mistake and wind up copying the source folder into the destination folder instead of the contents of the source folder so I wanted you to confirm that not only had you copied it but that you had checked the results of the copy. If that all looks OK then the next thing I would suggest is just try to get this plex docker running with new appdata to see if you can at least access the plex server.

This means your server isn't getting DHCP. Check cabling, ports, router.

👍

Looks similar to this one: https://forums.unraid.net/topic/75436-guide-how-to-use-rclone-to-mount-cloud-drives-and-play-files/?do=findComment&comment=729731

Another possible cause of post-read fail is bad RAM. Happened to me and others.

You didn't specifically answer this question:

11

Have you tried signing out of plex and signing in again?

Any time you make any settings on the Add Container page, that whole form is saved on flash as an XML file, which is "your template", named for the container. Your template can be reused at any time by simply selecting it from the User Templates in the Select Template dropdown at the top of the Add Container page. Your template is also reused by the Previous Apps feature on the Apps page.

Another way to accomplish the same exact thing without using Previous Apps. Just go to the Docker page and click the Add Container button, then select your template from the User Templates in the dropdown at the top of the page. Whether you do it that way or use Previous Apps, you can see what it fills in on the Add Container page you get before you create the container.

Yes. It gets your docker templates from flash and uses them. I've never heard of anybody having a problem with this because they don't use appdata. All sorts of variations are possible and I have seen people specify specific array drives for the path, or specify cache instead of a user share. I'm pretty sure some people are even using an Unassigned Device for this. It should just use whatever paths you have in each template.

I see you have 50GB for your docker image. If you have everything configured correctly it is extremely unlikely to ever need even 20G. When a user has such a large docker image, I suspect they have had issues with docker image filling up and they try to fix those issues by making it larger. Making it larger only makes it take longer to fill, it doesn't fix anything. But it is currently using only 4.7G, which is very reasonable. Have you ever had docker image filling up? Looks like you do have docker image corruption though: Mar 25 09:06:04 TOWER kernel: BTRFS warning (device loop2): csum failed root 372 ino 9239 off 12288 csum 0x6373a212 expected csum 0x07b4d05b mirror 1 Mar 25 09:06:04 TOWER kernel: BTRFS warning (device loop2): csum failed root 372 ino 9239 off 16384 csum 0x11cc18e0 expected csum 0x5ecef011 mirror 1 Mar 25 09:06:04 TOWER kernel: BTRFS warning (device loop2): csum failed root 372 ino 9239 off 12288 csum 0x6373a212 expected csum 0x07b4d05b mirror 1 Delete docker image, recreate it at the more reasonable size of 20G, and then you can reinstall all your dockers exactly as before using the Previous Apps feature on the Apps page. Not likely related, but are all your plugins up-to-date? I notice Wake-on-LAN is replacing libraries installed by Unassigned Devices with older versions.