October 26, 20241 yr Community Expert 16 minutes ago, linuxdevil said: Can I get the file without connecting the stick to my PC If you share out the boot device (by clicking it on the Main tab) it’s contents will be available over the network as the ‘flash’ share.
October 26, 20241 yr Ok, easily done. Here is my latest diagnostics filetower-diagnostics-20240919-0519.zip
October 26, 20241 yr Community Expert The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field and log instead to a share on a pool or the array.
November 2, 20241 yr Hi, I am also having a pretty high amount of unclean shut downs lately. I have enabled the syslog server and found the errors in the following zip file. I am not sure if it is a hardware failure or some incompability. I would really like some help to stabilize my server. tower-syslog-previous-20241102-1513.zip
November 2, 20241 yr Community Expert 8 minutes ago, Kung-Fubick said: Hi, I am also having a pretty high amount of unclean shut downs lately. I assume you mean crashes, there are macvlan call traces logged, update to latest stable, that issue is resolved since 6.12.11
November 2, 20241 yr Okay, thanks for the fast answer, I have updated now and will monitor the server. I'm honestly unsure if I mean crashes. I followed the guide on how to gather information about an unclean shutdown. But every time it seems to happened (can't reach any of my docker containers webui, nor the webgui, no smb shares) it won't do a clean shutdown when I only press my power button. I always (when the server is crashed) have to shut it off by "unclean" means (force reboot)
November 5, 20241 yr Hello, I just had an unclean shutdown. I have an external syslog but that does not show anything prior the crash: Any suggestion? homelabserver-diagnostics-20241105-1845.zip
January 13, 20251 yr Community Expert Jorge, It's been a little more than 3 weeks since last the unclean reboot problem showed. It happened today and I did have the remote syslog running but I don't really see much there. Do you need to see it? Not sure if I should post that here or not. It's size 1582K I don't think it's related, but I did update from .14 to 7.0.0 yesterday (without any problems).
January 14, 20251 yr Community Expert 7 hours ago, GeorgeJetson20 said: It's size 1582K It's text, zipped it should be probably 1/10th that size
January 14, 20251 yr Community Expert It finished the parity check and then the same thing happened. Not sure where to go from here. please let me know how to figure this out.
January 14, 20251 yr Community Expert Unfortunately, The problem happened 2 more times. Both during the parity rebuilds. Here is the very latest log file. hopefully someone MUCH smarter then me can figure out where the issue is. This server was running good for over a 1 year without any issues until this rebooting issue started. My specs are in the bottom of my message for Node804. syslog-192.168.1.101.zip Edited January 14, 20251 yr by GeorgeJetson20
January 15, 20251 yr Community Expert trurl, ((I made mistake, it's a 5700X not 3700X). I never caught that till now Not sure if that changes anything? I reviewed that but my system reboots to logon screen of unraid each time of the failure. This started after upgrading to .13 but I can't say 100%. I never had any issue with any reboots of any kind prior to that. I stopped docker services the last time it rebooted just to see if that had anything to do with it. But I really don't know if this is hardware related or something in unraid. I thought about just booting to Windows OS with the system and just leave it there and see if it reboots. If that happens, then it's the hardware but I am not sure really how to try to resolve this. I'll also run a memory test - any other ideas??? Edited January 15, 20251 yr by GeorgeJetson20
January 15, 20251 yr Community Expert 2 hours ago, GeorgeJetson20 said: booting to Windows OS with the system... Boot to Unraid in SAFE mode with Docker and VM Manager disabled in Settings then 2 hours ago, GeorgeJetson20 said: ...just leave it there and see if it reboots. Might do memtest first just to eliminate that.
January 15, 20251 yr Community Expert 10 hours ago, GeorgeJetson20 said: but my system reboots to logon screen of unraid each time of the failure. If the server is rebooting by itself, that is almost always a hardware issue.
January 16, 20251 yr Community Expert Update: 12+ hours later - Still running without any reboot, parity finished last night and still running without any reboots - just disabled docker still. Quick update. After turning off docker, not seeing any reboot (after 4 of them yesterday). It's still finishing up parity check at 92%. Is there any chance that docker would causing the reboot? I thought it was all separate from the system itself. I am going to let it run as long as it doesn't reboot without docker and see what happens. But if a docker container or the vdisk had a problem, would that be enough to reboot the system, even though there is no warning about it in my syslog that I can see? If I need to rebuild the docker from scratch is no big deal but I will just leave it alone for a while until I see if the issue stops happening. Edited January 16, 20251 yr by GeorgeJetson20
January 17, 20251 yr Community Expert On 1/15/2025 at 8:32 PM, GeorgeJetson20 said: Is there any chance that docker would causing the reboot? I thought it was all separate from the system itself. More likely to be an individual container. Some have been reported to hog resources for one reason or another causing the whole system to crash.
January 18, 20251 yr Community Expert So far it's been almost 3 days without any problems since I turned off the docker. I am going to let it stay up without touching it until next weekend and then delete the docker and recreate it and see it makes a difference.
January 26, 20251 yr Community Expert I have not had any issues with the server in more than a week. I been checking logs and the only message I keep seeing 1 time per day is (Other than autofan). monitor_nchan: Stop running nchan processes What does this mean/indicate, is this anything?? Edited January 26, 20251 yr by GeorgeJetson20
January 26, 20251 yr Community Expert 3 hours ago, GeorgeJetson20 said: What does this mean/indicate, is this anything?? No, it just means the WebGUI went inactive.
January 31, 20251 yr I believe that I may be going through the same issue as the previous poster after reading his commentary. I had a sync complete yesterday and running again today, by chance I happened to notice an uptime of ~30hrs (found it strange but not much more of it), then parity running again so must rebooted unclean after the parity check. I was performing preliminaries and.... - Just went again now. Dumped diagnostics, traced syslog error, and headed for the forums, always with one eye checking for similar recent posts and I've arrived here. Should I start my own thread, perform HW diags, or look towards a common problem someplace? FTR, information of potential significance. Quote - Ryzen 7 3700x. - This is the first time I'm aware that it's happening - No major changes to unRAID aside from application/Docker updates. - Potential catalyst of entire series of events; a couple/few days ago - I did disable bifurcation in the bios (something prompted me to check its status) that procedure was likely to be the trigger for the parity check kicking off yesterday (unclean shut-down because I missed a bios prompt whilst finding a working keyboard!) Relevant log entries after tonight's reboot, (and attached diags were performed upon restart) Quote Jan 31 23:19:20 Yoda kernel: mce: [Hardware Error]: Machine check events logged Jan 31 23:19:20 Yoda kernel: mce: [Hardware Error]: CPU 10: Machine Check: 0 Bank 5: bea0000000000108 Jan 31 23:19:20 Yoda kernel: mce: [Hardware Error]: TSC 0 Jan 31 23:19:20 Yoda kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1738325934 SOCKET 0 APIC 5 microcode 8701034 yoda-diagnostics-20250131-2325.zip
January 31, 20251 yr Community Expert Not directly an answer to your problem, but if you install the Parity Check Tuning plugin and in its settings disable it taking any actions on array operations it will still enhance the parity history entries to tell you what type of check was run. That would allow you to confirm if a check was an automatic one after an unclean shutdown or if it had some other cause.
January 31, 20251 yr Community Expert 1 hour ago, Nasha said: Should I start my own thread, perform HW diags, or look towards a common problem someplace? Yes, Yes, it does not hurt. Making your own thread helps keep issues separate and less confusing for anyone trying to help as well as the individuals seeking it. Also ensure syslog is enabled and post your diagnostics in your new thread.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.