asim2202

Update few months later. I found that the server was stable with no dockers running. (i wasnt running VMs anyways). So I was using it as just an SMB server for a few months because it hosts some important files for me. I then cleared out everything docker related and rebuilt itwith just core dockers that i needed. arr*, nzbget, Jellyfin, NPM, and a few others. And it would keep crashing again even with brand new docker setup. I then started eperimenting with each docker 1by1. and found that jellyfin was the issue but still it was intermittent and couldnt figure out what was wrong. Now i thinkive narrowed it down to iGPU transcode. I think this crashes the server. But i dont know why. Any one have experiecne with this?

I have already tried 3 different sets of RAM. It eventually ends up crashing the same with no evidence. So far i have swapped. CPU, MOBO, PSU, RAM, CACHE DRIVE, FLASH DRIVE. I've also ordered another HBA to see if thats causing the issue.

So my unraid just crashed after about 7 hours. The whole system goes unresponsive and needs a hard shut down. All i got from it are the below logs. syslog-previous

Hello All, I havebeen facing horrible instability of my Unraid system since the last 6 months. I have changed everything from RAM CPU MOTHERBOARD CACHE FLASH etc. It seems to be running now but my logs show some weird things Jan 19 18:32:21 Tower kernel: veth44e5217: entered allmulticast mode Jan 19 18:32:21 Tower kernel: veth44e5217: entered promiscuous mode Jan 19 18:32:21 Tower kernel: eth0: renamed from veth2e8f577 Jan 19 18:32:21 Tower kernel: br-15893e96a455: port 2(veth44e5217) entered blocking state Jan 19 18:32:21 Tower kernel: br-15893e96a455: port 2(veth44e5217) entered forwarding state Jan 19 18:32:45 Tower kernel: br-15893e96a455: port 3(vethbdc4a4b) entered disabled state Jan 19 18:32:45 Tower kernel: veth09c7797: renamed from eth0 Jan 19 18:32:45 Tower kernel: br-15893e96a455: port 3(vethbdc4a4b) entered disabled state Jan 19 18:32:45 Tower kernel: vethbdc4a4b (unregistering): left allmulticast mode Jan 19 18:32:45 Tower kernel: vethbdc4a4b (unregistering): left promiscuous mode Jan 19 18:32:45 Tower kernel: br-15893e96a455: port 3(vethbdc4a4b) entered disabled state Jan 19 18:32:45 Tower kernel: br-15893e96a455: port 3(veth0608df3) entered blocking state Jan 19 18:32:45 Tower kernel: br-15893e96a455: port 3(veth0608df3) entered disabled state Jan 19 18:32:45 Tower kernel: veth0608df3: entered allmulticast mode Jan 19 18:32:45 Tower kernel: veth0608df3: entered promiscuous mode Jan 19 18:32:45 Tower kernel: eth0: renamed from veth0fda395 Jan 19 18:32:45 Tower kernel: br-15893e96a455: port 3(veth0608df3) entered blocking state Jan 19 18:32:45 Tower kernel: br-15893e96a455: port 3(veth0608df3) entered forwarding state Jan 19 18:33:00 Tower kernel: br-15893e96a455: port 4(vethee7ac57) entered disabled state Jan 19 18:33:00 Tower kernel: veth4a18e32: renamed from eth0 Jan 19 18:33:00 Tower kernel: br-15893e96a455: port 4(vethee7ac57) entered disabled state Jan 19 18:33:00 Tower kernel: vethee7ac57 (unregistering): left allmulticast mode Jan 19 18:33:00 Tower kernel: vethee7ac57 (unregistering): left promiscuous mode Jan 19 18:33:00 Tower kernel: br-15893e96a455: port 4(vethee7ac57) entered disabled state Jan 19 18:33:00 Tower kernel: br-15893e96a455: port 4(veth718f0a8) entered blocking state Jan 19 18:33:00 Tower kernel: br-15893e96a455: port 4(veth718f0a8) entered disabled state Jan 19 18:33:00 Tower kernel: veth718f0a8: entered allmulticast mode Jan 19 18:33:00 Tower kernel: veth718f0a8: entered promiscuous mode Jan 19 18:33:01 Tower kernel: eth0: renamed from veth7e627c9 Jan 19 18:33:01 Tower kernel: br-15893e96a455: port 4(veth718f0a8) entered blocking state Jan 19 18:33:01 Tower kernel: br-15893e96a455: port 4(veth718f0a8) entered forwarding state Jan 19 18:33:11 Tower kernel: i2c i2c-4: sendbytes: NAK bailout. Jan 19 18:33:34 Tower kernel: i2c i2c-4: sendbytes: NAK bailout. Jan 19 18:33:34 Tower kernel: br-15893e96a455: port 5(veth2b5ea20) entered disabled state Jan 19 18:33:34 Tower kernel: veth9f8a52a: renamed from eth0 Jan 19 18:33:34 Tower kernel: br-15893e96a455: port 5(veth2b5ea20) entered disabled state Jan 19 18:33:34 Tower kernel: veth2b5ea20 (unregistering): left allmulticast mode Jan 19 18:33:34 Tower kernel: veth2b5ea20 (unregistering): left promiscuous mode Jan 19 18:33:34 Tower kernel: br-15893e96a455: port 5(veth2b5ea20) entered disabled state Jan 19 18:33:35 Tower kernel: br-15893e96a455: port 5(vethad5b601) entered blocking state Jan 19 18:33:35 Tower kernel: br-15893e96a455: port 5(vethad5b601) entered disabled state Jan 19 18:33:35 Tower kernel: vethad5b601: entered allmulticast mode Jan 19 18:33:35 Tower kernel: vethad5b601: entered promiscuous mode Jan 19 18:33:35 Tower kernel: eth0: renamed from vethfaf6e2f Jan 19 18:33:35 Tower kernel: br-15893e96a455: port 5(vethad5b601) entered blocking state Jan 19 18:33:35 Tower kernel: br-15893e96a455: port 5(vethad5b601) entered forwarding state Jan 19 18:33:46 Tower kernel: br-15893e96a455: port 6(vethfa24a54) entered disabled state Jan 19 18:33:46 Tower kernel: vethda43b85: renamed from eth0 Jan 19 18:33:46 Tower kernel: br-15893e96a455: port 6(vethfa24a54) entered disabled state Jan 19 18:33:46 Tower kernel: vethfa24a54 (unregistering): left allmulticast mode Jan 19 18:33:46 Tower kernel: vethfa24a54 (unregistering): left promiscuous mode Jan 19 18:33:46 Tower kernel: br-15893e96a455: port 6(vethfa24a54) entered disabled state Jan 19 18:33:46 Tower kernel: br-15893e96a455: port 6(veth79153f7) entered blocking state Jan 19 18:33:46 Tower kernel: br-15893e96a455: port 6(veth79153f7) entered disabled state Jan 19 18:33:46 Tower kernel: veth79153f7: entered allmulticast mode Jan 19 18:33:46 Tower kernel: veth79153f7: entered promiscuous mode Jan 19 18:33:47 Tower kernel: eth0: renamed from vethe11f8f1 Jan 19 18:33:47 Tower kernel: br-15893e96a455: port 6(veth79153f7) entered blocking state Jan 19 18:33:47 Tower kernel: br-15893e96a455: port 6(veth79153f7) entered forwarding state Jan 19 18:33:57 Tower kernel: i2c i2c-4: sendbytes: NAK bailout. How do i fix this issue? Thanks in advance tower-diagnostics-20260119-1834.zip

Hello All, I've been using Unraid on my system for the last 8 years with no issues up until last year where ive been delaing with instability issues. I've changed RAM, Cache SSD, Flash over the last year. I recently had a crash which meant my system was not boooting at all after, i removed the 780ti i had in the system and it booted up no problem after. Now i am seeing this error filled in my logs: May 1 11:07:26 Tower kernel: i2c i2c-4: sendbytes: NAK bailout. I have attached diagnostics. please help me out. tower-diagnostics-20250501-1131.zip

Bump

I have attached the latest diagnostics. The previous logs are from when the server last crashed on 27th november. I could only restart it today.tower-diagnostics-20241130-1836.zip

Here it i, the diagnostics file tower-diagnostics-20241127-1011.zip

Hello, This is the first time that ive had a issue that im unable to figure out in my 7 years of using unraid, Ever since i have updated to unraid 6.12 and beyond. my server hard crashes after few days of runtime. I have attached some logs from the flash after the last crash, im not sure it crashed because of the persistent reason but i do see some weird stuff on 26th novemeber 2024 at 4am approximately. Please help me out and i will post more logs when it crashes again thank you in advance syslog-previous