ive done alot of reading and im seeing that this has todo with path configurations.

main issues here started after i tried watching content on plex and nothing would load. i then went into unraid and check to findout why and my cache drive was unmounted somehow and couldnt be read. i rebooted and started all my disks again then everything was completely wiped out including my dockers . all of my content is still on the respected drives but everytime i try and download something new the above error is what im getting. didnt have this issue before the cache crashed now its like it has no idea where anything is supposed to go. after reformatting my cache drive all dockers were able to be reinstalled from the apps tab retaining most of if not all of their origional data but as soon as i get into the apps i have to setup everything again. i know theres alot here but ive spent 8 hours racking my mind over this and any input would be wonderful as i am not the best with linux based systems. ive done alot of reading and im seeing that this has todo with path configurations.

6 minutes ago, microminipimp said:

after reformatting my cache drive all dockers were able to be reinstalled from the apps tab retaining most of if not all of their origional data but as soon as i get into the apps i have to setup everything again

In addition to the settings Previous Apps uses to setup your dockers again. each container needs its appdata or you will have to setup the application again. You need backups of appdata.

For additional advice

Attach Diagnostics ZIP to your NEXT post in this thread.

attatched i have provided the diag reports you requested.

unraid-diagnostics-20260608-1448.zip

where exactly would i find backups of said "appdata" ?

Your appdata and system shares have files on the array. You probably had Docker/VM Manager enabled when cache wasn't working, so those got created on the array. Better if Docker/VM related shares are all on cache or other pool with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. Nothing can move open files, so you will have to disable Docker and VM Manager in Settings before these shares can be moved.

There is a plugin for appdata backups:

so what would i do after disabling docker and vm in the settings tab? like i said this is new to me so alot of this is foreign concept in my eyes.

Those shares are already configured to be moved to cache when Mover runs. You can run it from Main - Array Operation. Mover won't replace files so if there are duplicates you will have to remove those manually using the File Manager.

You should do an extended SMART self-test on cache.

running the mover now as we speak

after starting the mover do i have todo anything or will it move things where they need to be already?

It will move the array files from appdata and system to cache, except for duplicates as mentioned. If a file is already on cache it won't be moved from the array. After mover finishes post new diagnostics and we will see if anything got left on the array.

here is the diag report after mover was ran

unraid-diagnostics-20260608-1515.zip

Looks like everything got moved where it belongs.

Noticed you don't have parity. Do you plan to add a parity drive?

this is the issue im currently running into figured id get an actual photo to show the issue. BUT i want to get a parity at some point just wasnt in the budget when building this. i literally put this together as a what i could find to build kinda thing lol.

What application is that screenshot from?

this is coming from sonarr. but the same issue persists with radarr as well. it looks like sab is setup properly because the content is downloading its just like it got lost in the process of transfering to its final home for viewing.

What application is doing the downloads?

application used to download is sabnzbd.

Edited June 8Jun 8 by microminipimp

Post docker run for sabnzbd and sonarr

trying to figure out how to get docker run. the attatched explanation is a little confusing to me .

Click on the container icon to get its popup menu, select Edit

On 5/26/2017 at 12:03 PM, Squid said:

edit the application (you can always make any change and then change it back and hit "Apply" to get the docker run command to appear

i believe this is it

i changed the port number on both sonarr and radarr in order to get the docker run page to show up. afterwards i reinstalled then changed the ports back to their origional status.

You didn't have to "apply" the change, you just needed to make a change to enable the "Apply" button. Then you could have changed it back before doing "Apply".

And the changes you made failed due to the port change, but I assume when you changed them back they reinstalled OK.

In any case, you got the information I wanted to see. I will take a look at it.

yes when reinstalling it went back to its normal state before i made any changes to it .

also displaying this issue as well which im guessing is because things arent being pointed in the proper direction./path

1 minute ago, trurl said:

you got the information I wanted to see

except

17 minutes ago, trurl said:

docker run for sabnzbd