squirreltats

I apologize for the slow response. I have been slammed and have not had the time to work on the server. I figured out the problem. I changed the name of the share in the gui just to see if that would work but then the minimum free space caught my eye... it was over 3TB. That was what was causing the mover not to run properly. Once I changed the minimum free space the mover has been running properly.

I thought I had gotten rid of the File Integrity plugin. I remember it gave me this issue before. So, I thought maybe I was seeing something new. Thank you for your patience with that. The Home-Backups folder is the main issue with the Mover.

I noticed yesterday and today that my cache is filling up. The mover is suppose to run on Wednesday mornings around 4:00 a.m. but it never ran. When I click "Move" on the Main page it starts to run then it stops running the "move" command. When I checked System Log it is filled with errors of corrupted files. Can someone help me figure out what is going on? emily-diagnostics-20250911-2209.zip

My apologizes for the delayed response. I will look into doing that and make sure it has not corrupted. Many thanks for y'alls patience, time, and knowledge. I hope y'all have a good Easter.

@trurl and @JorgeB, hmmmm. I am looking at logs from over the past couple of months and I am seeing a lot of corrupted files. I just remembered while typing this that I had an actual corrupted file back in January that shutdown the whole array. Maybe the disk itself is corrupted. Could this be the case?

@JorgeB, it looks like those are new writes. What plugin would cause false positives?

I checked my logs by accident (I was attempting to open System Devices) and saw a sea of red and found a mass amount of corruption mostly in my urbackups. What would be causing this issue? Any assistance will be appreciated. Diagnostics zip folder has been included. emily-diagnostics-20250412-2059.zip

I did as you suggest and use the -d (--debug) and saw some of what is in there, but I couldn't pick out anything that distinguished where it came from or what exactly was in it, I could only guess it was from a backup. Thank you for your assistance. Would parity be able to fill in the gap that is made by the lost+found? I just realized I did not get anywhere with the "file command". I will do some more research and see what I can come up with before bugging the community/mods about this. I appreciate everyone's help!

Is there a(n) guide/instructions that I may have overlooked on how to use the 'file' command? I am having an issue where when I attempt to use it I get a "XXXXXXX cannot open 'XXXXXXX' (No such file or directory)" Thankfully the lost+found file is small so I don't have much to go through, but I don't have backups currently as I am saving funds and waiting on Unraid 7 to release before I build a backup server for my current one.

I wasn't clear and I apologize. I can see the file and I can open it, but I cannot make sense of the text. Is there a way of seeing the file with it's content in proper form or seeing the content so I might have an idea of where it needs to go? Many thanks for your patience.

I figured it out, thank you. I have a lost+found file but I can't seem to see the content via the CLI. Is there a way of looking at the file via the GUI?

Thank you, Jorge. I run into this issue when I attempt to run the xfs_repair : xfs_repair -v /dev/md1 : " /dev/md1: No such file or directory /dev/md1: No such file or directory fatal error -- couldn't initialize XFS library. " I did try this in maintenance mode and in with the array started and stopped and I get the same message. Do you have an idea what could be wrong or does the issue exist between chair and keyboard?

At some point my 1st disk decided to crap its pants or the filesystem decided to corrupt itself. I'm not sure what exactly is going on. It says "Unmountable: Unsupported or no file system" Could someone help me narrow down what has happened? I thought maybe a restart would rectify the issue, but it wasn't until after that that I found the issue with the filesystem. I have been wanting to build a backup server for this exact reason but haven't had the funds. If I can do something to fix this issue without completely losing data I would be so grateful. Any help anyone can give me would be greatly appreciated. emily-diagnostics-20241215-2045.zip

I had to restart my server because it was experiencing huge cpu usage spikes and the diagnostics download would freeze up the browser tab and make it crash, and I couldn't get anything done to get you the diagnostic file. Should I delete this post and start another when it happens again?

I will get to you asap. The tab keeps crashing when I am downloading the file to the boot drive.