Hi folks,

 

I just finished transferring all my data to Unraid and calculating parity, during that process that lasted more than a week, everything was working fine with the uptime.

 

I suspect that after installing some docker containers this issue happened but it could be something else.

 

Here is what I tried so far and did not work:

 

-Change from macvlan to ipvlan: still becomes unresponsive but I got trace calls at least instead of a black screen, is it related who knows?

 

What I will try now:

 

-Safe mode and reboot with one container at a time.

 

-Check bios settings regarding power management and CPU

 

Do I really have to recheck parity every time this happens if I was not writing any files or doing anything special?

 

All that being said, here is my diagnostics file if it can help you, help me pin point this down.

 

Thanks again for any help.

taichi-diagnostics-20250224-1658.zip

I wanted to add that after posting this I updated to 7.0.1 in the hope that it helps and I will also run a memtest.

Enable the syslog server and post that if it crashes again.

Will do I am now running the parity check in safe mode and reading the guide to set up the syslog server.

 

Thanks again.

I finished setting up the syslog server but to my surprise I only have 4 lines and it's been a few minutes...

 

10.0.0.246    Feb 27 10:25:52    Taichi    daemon    info    ool www[55435]    /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config
10.0.0.246    Feb 27 10:25:52    Taichi    user    notice    rc.rsyslogd    Restarting Syslog server daemon...
10.0.0.246    Feb 27 10:25:52    Taichi    user    notice    rc.rsyslogd    Stopping Syslog server daemon...
10.0.0.246    Feb 27 10:25:52    Taichi    user    notice    rc.rsyslogd    killall --ns 55444 rsyslogd

 

I was expecting this to have more verbose? If it's normal then never mind.

Edited February 27, 20251 yr by MonadProxy

In the meanwhile @JorgeB, I also wanted to add some pictures that I took while it was unresponsive maybe something relevant can be seen on there?

 

Thanks again for your help.

 

 

According to a knowledgeable person around me:

 

seems like you have a random syscall that stalls because the nvidia driver attempts to do something and just gets stuck

you should blacklist the module to test it out

(and from what I see, looks like the console is in textmode already - not even framebuffer. so what is the driver even doing?)

Those look Nvidia related, try without the Nvidia driver

I'm running in safe mode so the nvidia plugin should not be loaded, I will keep you updated on this.

1 hour ago, JorgeB said:

Those look Nvidia related, try without the Nvidia driver

 

Hi,

 

It seems to be working so far with the nvidia driver uninstalled and without safe mode but let me wait it out a little further.

 

That being said, does that mean that I will be just 'barred' from using the nvidia driver or wait for further updates if that ends up being the culprit?

 

I don't have an old odd card, just an evga 2060 super that I wanted to use for transcoding in emby and stash as well as for some ffmpeg/staxrip jobs that I would prefer to move to the server.

 

Isn't there a possibility for instance to switch to an older driver version to test out or is there a latest and a more stable build or something to that effect? If so, please let me know.

 

If I understand I wouldn't need the driver if I want to use it in a VM? Ultimately though, I would prefer not to have to run some things through the overhead of a VM if possible, especially if they are available as containers.

 

Thanks again for letting me know @JorgeB

 

EDIT: I just realized I could change from latest to production and previous releases when it comes to the driver version so I am trying that out

Edited March 2, 20251 yr by MonadProxy

After changing the nvidia driver to production, I did not get the issue again and it's been 3 days. If it happens again I'll just post a new thread with a more detailed syslog.

 

Thanks again.

On 3/3/2025 at 2:23 PM, MonadProxy said:

After changing the nvidia driver to production, I did not get the issue again and it's been 3 days. If it happens again I'll just post a new thread with a more detailed syslog.

 

Thanks again.

Just to confirm, it's been almost 6 days of up time now.