My cache pool got filled 100% and after that I have had 3 random restarts. Can anyone tell me why this is happening?

nas-diagnostics-20250217-1914.zip

Server restarting by itself is almost always a hardware issue, and should be unrelated to the pool getting filled up.

Before upgradeing to unraid 7 I had 0 issues. MOBO, RAM, CPU are 2 months old and the RAM had a lot of testing before I took it in use. Only thing I can think of is the flash drive. Could the flash drive cause the restarting? Or what should i look in the diagnostics to get any hints?

You can downgrade back to v6.12 to confirm, the upgrade could just have been a coincidence, unlikely that a bad flash drive would make the server restart, and typically, it will leave some signs on the syslog, but the regular syslog starts over after every boot, enable the syslog server and post that after the next reboot.

Just now it crashed. I tried to gather files with unbalanced an it crashed. New diagnostic file with syslog enabled.

nas-diagnostics-20250220-2055.zip

7 minutes ago, Soulman said:

file with syslog enabled

And where is the persistent syslog? It doesn't come with the diags.

I did not know this. But now I looked at the destination folder and there was nothing in it. Is there something wrong with my settings? I changed the location to appdata. It was on the array before. Alos i changed the mirror syslog to flash to Yes. Anyway I hope that it will work next time. How can i be sure that it logs now?

 

You should find a file in the ‘logs’ folder on the flash drive since you have the ‘Mirror to Flash’ options set to yes.   If you want a file instead to be written to the ‘appdata’ folder that you specified as Local Syslog Server setting then you need to put the IP address of your Server into the Remote Syslog Server field.

 

This should be explained in the diagnostics link, but if you find that unclear then I suggest you mention in what way so that Limetech can use that is input to improving the documentation.

Started the mover and it crashed. Last time i tried to gather files with unbalanced and it crashed. Now the syslog is included. Should i downgrade to 6.12 where i was before and see if this changes anything?

syslog.log

There's nothing relevant logged.

 

11 hours ago, Soulman said:

Should i downgrade to 6.12 where i was before and see if this changes anything?

You can try, and see if it stops crashing.

After downgrading it does not crash anymore. What does this mean for me? Stay on 6.12 until support lasts?

Without anything logged can't guess what the issue is, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days with v7.0, if it doesn't crash start turning on the other services one by one, including the docker containers, if it still crashes without anything running, retest once Unraid 7.1 is out, the newer kernel can make a difference.

So I found some youtube comments where people removed mover tuning plugin after upgrading to 7.0 because it brakes it. I think my problem is related to that. Does anyone have more info about that? 

2 minutes ago, Soulman said:

So I found some youtube comments where people removed mover tuning plugin after upgrading to 7.0 because it brakes it. I think my problem is related to that. Does anyone have more info about that? 

The only mover tuning plugin which should be used on 7.0 is from masterwishx.  Fix Common Problems (if installed) would have notified everyone that the others are all deprecated

 

24 minutes ago, Squid said:

The only mover tuning plugin which should be used on 7.0 is from masterwishx.  Fix Common Problems (if installed) would have notified everyone that the others are all deprecated

 

I have fix common problems installed but it did not show any faults with mover tuning plugin. The last update for my mover tuning plugin was somewhere in 2024. I will try this one now.