February 2, 20242 yr My setup: 2 unraid servers and a windows desktop all connected on the same network. The unraid docker settings have been appropriately adjusted to run two servers on the same network. Both unraid servers have been switched to ipvlan. Rocinante (server 1) works fine. Razorback (Server 2) has constant issues that bring down the entire network and require a hard reboot. It usually does not stay up longer than a few hours, but sometimes lasts for days before crashing. Bit of background in case it's relevant: Rocinante's original hardware (motherboard, cpu, RAM) is currently in Razorback, so I know that it worked correctly with unraid before. Rocinante originally started on 6.9.x, then upgraded to 6.12.6, without issue, and has been running this way for almost two whole years now. Razorback started on 6.12.x, and is currently on 6.12.6 as well. Nothing but constant crashes since I put it together a few months ago. I will attach both the most recent syslog and the diagnostics from this server. Edit: removed the extra syslog file as I realized it was included in the anonymized diagnostics Edited February 10, 20242 yr by paralyze296
February 3, 20242 yr Community Expert There are constant call traces, but difficult to see if they are hardware or software related, one thing you can try is to boot the server in safe mode with all docker/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.
February 3, 20242 yr Author Thanks, will definitely do that if it crashes again. After my last edit I lost my patience with it, shut it down, and re-seated the CPU and swapped out the RAM. So far, it's running fine, and has managed to get almost halfway into a data rebuild, so fingers crossed. I will update in a week or so if it's still going strong.
February 10, 20242 yr Author Solution Update: Server has been running fine for a full week now, and this good behavior has persisted through a reboot, a parity rebuild, and the addition of an extra cache drive. Current uptime is 48 hours, which was very unlikely before, so I'll consider this solved. It looks like the culprit here was either faulty RAM (which has been replaced entirely) or a poorly installed CPU, which I re-seated and applied new thermal paste to.
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.