A couple of weeks ago I started having problem whit my unraid server. Started losing connection to the server. Need to reboot it to get access for a couple of seconds. I've changed the USB stick, change the motherbord put an SLI SAS. Bun I cand fix the problem, deleted the network. cfg. Can't make an diagnostic file Can anyone have an ideea how to fix the problem.

medhp-diagnostics-20260323-2331.zip

Edited March 23Mar 23 by blue8lucian

44 minutes ago, blue8lucian said:

Can't make an diagnostic file

What happens when you try?

You can also get diagnostics from the command line

Do you have an attached keyboard and monitor?

yes i have connected an monitor and an keyboard, i can't ping nothing

Just some advice on using the forum.

When you edit a previous post, nobody who has already read that post will know there is anything new in it unless they actually take the trouble to go looking. In fact, if no other posts are made to the thread, the thread might never be visited again by someone who was trying to help. I almost didn't notice you had added diagnostics to that first post since when I first entered the thread, it positioned the page on the first new post and if I hadn't scrolled up I would never have known. That is why I always say

Attach Diagnostics ZIP to your NEXT post in this thread.

Setup syslog server.

Was everything working before you upgraded to the beta?

Can you start the array and post new diagnostics?

I thought upgrading is going to fix, but the problem started weekend before upgrading to beta. The problem is that i can't mange to find what is rong

I thought it is a hardware problem, changed the motherboard, memory cpu, and i have the same problems. Thinking to change the power suply.

@trurl Thank you for you help. Changed the power supply whit an older one, gen 4. fix the immo and started to rebuild the array. this is the new diagnostic zip maybe the community can find an bug and help me get a more stable system.

medhp-diagnostics-20260324-1237.zip

i have to restart the router or to use "ip link set eth0 down / ip link set eth0 up" to get access to the server

@trurl Do you have any idea why the link is going down? I use opensense. Used it for the past 4 years, no problem. Everything started 4 weeks ago. thinking now of changing the network card

Did you follow the FAQ recommendation linked above for Ryzen CPUs?

Also enable the syslog server and post that after a crash.

@JorgeB no. I didn't follow the link. But the same setup i've use for 5 years . and no problems.

15 minutes ago, blue8lucian said:

same setup i've use for 5 years

4 hours ago, blue8lucian said:

changed the motherboard, memory cpu

same motherbord and cpu...had a back up never used keep them for an second server, didn't had time to make it

I thought to keep the same CPUs , RAM, MB, Just to fix easy problems if i have whit one. I've started using an Aquantia AQC113 (Antigua 10G) and looking online found out that it may be a problem whit it. Found this solution /boot/config/go: ethtool --set-eee eth0 eee off hope is going to work. I'll make today some changes to make the system log persist on my cache pool

2 hours ago, blue8lucian said:

But the same setup i've use for 5 years . and no problems.

There have been cases where the issues started after a kernel change, so I still recommend checking that; there's nothing to lose.

@JorgeB i've set the log.thank you

Post a screenshot of your Syslog Server settings.