Decay

Yes, it was, deleted it after I posted the diagnostic file. Had seen, that the diagnostic said, that it was still on the array.

I am sorry, I was stupid... Missed empty folders. Edit: Forgot to delete domains from disk1, also done that right now. Thank you for your help, I didn´t know what to do without you. There where some failures of my system, so I am not sure which answer I should mark as solution. unraid-diagnostics-20240127-1742.zip

Yes, all data and folders I backed up are in the "unique name" share. Just in that share are all folders have the original name. Edit: I´ll try something. I´ll add "_TMP" to the backup folders and will see what is going to happen. Edit2: Renaming doesn´t solved it. It looks like there are no data on the array, attaced some screenshots.

@trurl I copied all with Dynamix File Manager, Docker was offline and ther shouldn´t be any open files. @itimpi The folder I used for backup has a unique name, but all inside has the same folder name. Probably I should delete them.

Is it a wrong configuration? All files are marked with the cache as location. I added a screen of the appdata sahre setting. Just trying to find it in the diagnostics. Edit: I found it in the diagnostics. When I backed up the cache drive, I copied all onto a folder, location is on disc1, is that the problem?

Done that. It looks like all files show that they are on located on the cache, the files which should be there. unraid-diagnostics-20240127-1626.zip

Thank you for the fast response. Just checking which files I want to keep and which not, shall I keep the folders or also delete them?

They are set to: array --> cache. How to solve that?

All data are back on the cache, the docker.img is rebuild and the dockers startet. Right now it looks good. Just a few files, still got a backup, weren´t readable. I hope the problem is solved. Edit: Just wanted to do a smart check on the new drive, but the check does not start. unraid-diagnostics-20240127-1522.zip

I´ll do that and come back. Just have seen, that there is a old vdisk.img from an old VM, I would assume, that it is safe to delete.

Okay, I startet the backup. After that I´ll copy all data back to a new cach drive. Do I have to do anything after copying the data back or just try to start docker again?

I also got a new cache drive, I probably do a backup and change the drive. Do you recommand a manual backup or just set alll back to array?

Docker failed to start. Could it be possible that the docker.img, which was recreated days before, is corrupted? It was recreated with the old hardware, which had RAM problems and suddenly completly stopped to work? To be hones, I don´t understand the docker logfile from the diagnostic. Edit: Fix common Problems plugin shows: Unable to write to cache - Drive mounted read-only or completely full. The cache drive isn´t full and it does not show that it is read-only. unraid-diagnostics-20240127-1229.zip

I think parity looks better now. Just did a short smart test till now. Wondering if I should give the dockers a try again or do you see any problems with that? unraid-diagnostics-20240127-1040.zip

Just me is using the server, so the write performance was okay for me but I think I´ll replace the parity drives with non smr drives and rebuild parity. It will take some time, I´ll report the progress if it is done. The third new drive I´ll change with drive 1 of the array and copy all data from drive 2 to drive 1. Just ordered three more drives, these will replace the rest of the drives. It is hard to get new ones, most shops are sold out in my area. @trurl Have you seen the memtest log? For me it looks good or did I missed something? MemTest86-20240121-013132.log