I am having issues with the NAS connectivity. When I reboot and connect to it, everything seems to work.

 

The next day, I try to connect and the server can't be reached. Once I reboot the server I can connect to it again. This may be related or not, but maybe it happens when I shut down the PC I use to connect to the server.

 

Any ideas on what might cause this? I attach the ping test when it's not working and when it works after rebooting the server. I also attach diagnostics.

 

 

nas-diagnostics-20250311-1042.zip

Server may be crashing/hanging, enable the syslog server and post that after it happens again, also make sure this has been taken care of:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Understood, will do that!

On 3/11/2025 at 11:56 AM, JorgeB said:

Server may be crashing/hanging, enable the syslog server and post that after it happens again, also make sure this has been taken care of:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Here it is:

syslog-previous.txt syslog.txt

The syslog-previous only covers a couple of minutes of uptime, but there are multiple call traces and a segfault logged, suggesting a possible hardware issue.

Should I upload another log next time it happens?

You can, ideally with more uptime, or does the server typically crash after 2 minutes?

1 hour ago, JorgeB said:

You can, ideally with more uptime, or does the server typically crash after 2 minutes?

It has happened after a days of uptime. Next time it happens I'll give you the log

On 3/16/2025 at 1:51 PM, JorgeB said:

You can, ideally with more uptime, or does the server typically crash after 2 minutes?

Happens randomly and I have to reboot the server each time to fix it.

syslog.txt syslog-previous.txt

Syslog-previous again only covers 2 minutes uptime, if the server is crashing that quickly, it's almost certainly a hardware issue, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

I think I made a mistake, I had Local syslog server disabled, is that why it only covers 2 minutes? If so I may post again in a few days when it happens again. It's not crashing that quickly.

On 4/16/2025 at 11:45 AM, JorgeB said:

Syslog-previous again only covers 2 minutes uptime, if the server is crashing that quickly, it's almost certainly a hardware issue, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

This one covers more time (a bit over a day)

syslog-previous.txt

I'm afraid that there's still nothing relevant logged, did you try this?

On 4/16/2025 at 10:45 AM, JorgeB said:

 if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

 

I've tried this. I have 2 sticks, I removed one, then put it back and removed the other. Then I did it again swapping them. Every time the problem persists. Could it have something to do with the RAM BIOS config and not the hardware itself?

 

EDIT: That said, without knowing about details, I have a feeling it could also be related to the Network upgrade I did to 10gigabit.

Edited May 10, 20251 yr by AlbertoGa
Incomplete

It could be, you can try removing it.

I don't know what to look for. If I unplug 10gig and eth1 is down, I won't be able to connect to the server, will I?

These are my settings, is there something that could be causing this? Maybe the reason it's not working properly is because of a bad config?

On 5/10/2025 at 2:47 PM, JorgeB said:

It could be, you can try removing it.

 

I meant removing the NIC.