Jakobustrop

Just as an update the rebuild was successful and the server is back up and parity check didnt return errors.

Checked the Data on the emulated Disk 1 and it seemed to be all okay. Tested some media files and they all played back fine. Started the rebuild and it is half way done. Seems to be doing okay.

Alright, I have the file integrity plugin installed. Would it be smart to let that verify the contents of the emulated disk 1 one to check if everything is in order before proceeding?

So I would follow those steps and then run a parity check to correct the faulty parity data for disks 2 and 3 right?

As far a i can see I have two options right now: 1. Rebuild Disk 1 onto itself assuming the parity data for that drive is good. I assume the parity data for disk 2 and 3 will be bad because the parity sync continued while they threw errors. 2. Create a new Config and rebuild parity from there.So assuming the data on the disc is fine, assuming the Controller failed in a way that took down the drives and didn't destroy data already on there. Or am I missing something?

Alright here is the new Diag. I am able to see the contents of the emulated disc. jarvis-diagnostics-20260426-1143.zip

I have powered off the system and swapped Mainboards to one with a known good Sata controller. I rebooted into Maintenance mode and all the drives show up fine. Also did a short smart test on drive 1 and that also came back without error, same with drive 2 and 3. Sorry i forgot the Diagnostics. Should have also taken one earlier before the reboot. I was in kinda of a frenzy/panic waking up to the notifications and wanted to get it under control. I have now attached the diag from the current boot jarvis-diagnostics-20260426-1054.zip

I stopped the Parity Sync and checked all the Drives that dropped. They were all connected to the same controller. So pretty sure that is dead. I checked the smart data of the drives in a different system and they all check out fine. Is the correct step now to rebuild drive 1 onto itself? or do I take a different appraoch because of the last parity check that accumulated errors because of the lost connection to drive 2 and 3? Because theoretically i would assume the data on drive 1 is still good.

The Log is full of Disk 2 and 3 Read errrors. I feel liek the Parity sync should continue

Help, i just woke up and got the message that one of my Drives failed. That is during my routine parity Check. and now two of my other drives are climbing in sync errors. What do i do now?

I seem to have found the answer myself. So apparently duplicati is putting temp files into:"/run/duplicati-temp/" so you have to change the docker path to that or use the "tempdir" options in the "Default options" Section of the Duplicati settings to remap it.

I have been having the same issue and it is Duplicati filling up the Docker Image. I have the /temp directory mapped but at some point he stopped writing in to it. I found files from 2024 in there but no new ones. I would really like help here. What do we need to do to have it use the correct directory again?

Sorry for the late update. The Problem relatively suddenly went away and what maybe solved the issue, even though i would find it odd, is that I remembered that I had to update the DNS rebinding exceptions in my router (Fritz Box) with the new URL and IP that wasn't in there. I would find it odd because the HTTP 500 error only appeared after some time and only after Log-In, I would have expected such a rebind protection to kick in instantly. and to quickly respond to this. Sadly cant send you a log because the problem went away but I did restart nginx back when it was happening and it restarted just normally. So I think it really was external factors.

It must have happened after Apr 20 18:59:11 and before Apr 21 00:00:38. At Apr 20 18:59:11 I started configuring the Cloudflare Docker and testing that. And a few minutes before Apr 21 00:00:38 I went to check on the Server before going to bed and it had the HTTP 500. And at Apr 21 00:00:38 I tried to login through firefox which also threw the HTTP 500 Error. Edit: Even though it probably got nothing todo with the Problem I uninstalled unassigned.devices.preclear becuase I don't need it and the csrf error was bothering me.

Hello, i have been having Issues with the Web interface becoming completely inaccessible after a fews hours of running my Server. The LogIn page appears but after that only HTTP 500. I can SSH into the server to shut it down / restart it. I have looked through the logs but cant find anything pointing in me in the right direction. For context I build a new Server because my old one is out of space. Right now I am copying TBs of data from the old to the new and trying to setup my dockers better than before. At the moment I only got two Dockers container and no parity disks to copying goes faster. I also got an Intel X540 Dual Lan Card installed maybe that's causing some trouble. I attached my most recent Diagnostic tower-diagnostics-20240421-0915.zip