Hey forum.

 

my unRAID server has been locking me out/freezing/becoming inaccessible.  Usually happens 1 or 2 times a month, it always happens when I'm away or the server is unused (discs without any activity)

 

 

The only error that appears in the "System log" is the following.

 

Jul 18 16:52:57 NAS-Unraid kernel: xhci_hcd 0000:00:0d.0: PCI post-resume error -19!

 

I can upload "System Log" and  diagnostics.

 

Any idea?

 

Thanks.

Edited July 19, 20241 yr by Lerk

9 minutes ago, Lerk said:

I can upload "System Log" and  diagnostics.

Do that, syslog only if it's the persistent one, the normal one already comes with the diags.

syslog-previous.txt

13 minutes ago, JorgeB said:

Haz eso, syslog solo si es el persistente, el normal ya viene con los diagnósticos.

Always the same error, yes.

 

NAS-Unraid kernel: xhci_hcd 0000:00:0d.0: PCI post-resume error -19!

 

Edited July 19, 20241 yr by Lerk

Attach Diagnostics to your NEXT post in this thread.

16 hours ago, trurl said:

Attach Diagnostics to your NEXT post in this thread.

Cant access to the server  via ssh, telnet or monitor attached (no signal) when the server become inaccessible, so cant get Diagnostics

 

What Can I do?

Edited July 20, 20241 yr by Lerk

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  If you have not already done so you should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

4 minutes ago, itimpi said:

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  If you have not already done so you should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

Ok perfect.

 

I have the Syslog activated but no with the option "Mirror to Flash" . I'm going to enable them and when the server crashes I'll upload the syslog, right?

 

The server crashed last night. I don't see anything strange in the syslog

syslog-previous.txt

Unfortunately there's nothing relevant logged, this can be a hardware issue, 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, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

4 minutes ago, JorgeB said:

Lamentablemente no hay nada relevante registrado, esto puede ser un problema de hardware, una cosa que puedes intentar es iniciar el servidor en modo seguro con todos los contenedores/VM de Docker deshabilitados, dejarlo funcionar como un NAS básico durante unos días, si aún falla es probable que sea un problema de hardware, si no comienza, enciende los otros servicios uno por uno.

Okay, it's a bitch.

 

 

The only error that appears in the syslog is the following.

 

NAS-Unraid kernel: xhci_hcd 0000:00:0d.0: PCI post-resume error -19!

 

I don't know if it can be relevant

Don't think it is.

5 minutes on "Safe Mode" and freezing.

 

 

Edited August 2, 20241 yr by Lerk

I change the motherboard, the memory RAM, and same problem.

Assuming that when it was in safe mode it still froze without the docker or VMs running, it could be other hardware issue, like PSU or CPU for example.