I'm currently trying to set up a new install of unraid.  I got the shares set up, and was in the process of copying over the data, but the transfer kept stopping.  I've narrowed it down to being able to tell that unraid is rebooting itself every few hours or so.  The unraid box I'm trying to set up has been used for years with no issue, I've tried multiple unraid USB drives, I've confirmed the box doesn't reboot with other OS's, and am somewhat stymied.  The issue seems to be with unraid itself, but this is just a basic install, no addons, no nothing.  The syslog entries are being wiped every reboot, so the logs show the startup logs for that one run only.  I've tried enabling the syslog server locally, but I get one line of data and that's it there.

 

Is there something obvious I'm missing here?  I've been using unraid for years, but I've had nothing but problems with trying to set up this new box and am wondering if it's worth continuing to use unraid given all the problems I'm having setting up this new box.

Edited April 14, 20233 yr by I.M.APseudonym
clarity

Post diagnostics so we know a bit more than the symptoms

Also, enable syslog mirroring to flash drive and see what ends up there leading to the reboot

Doing so now, I'm going to have to rebuild things because I wasn't thinking and used my last name as part of the share names and I'd rather not post logs with that, but I'll just start from scratch, rename the share, and post the diagnostics.  Thank you for responding.

Attached are the requested diagnostics.  Please let me know if any additional information is required.  I'm a little confused about why my name suddenly disappeared when the system rebooted itself, but that's also in line with what I was saying about the logs disappearing.

waystation-diagnostics-20230415-2020.zip

21 hours ago, I.M.APseudonym said:

I'm going to have to rebuild things because I wasn't thinking and used my last name as part of the share names

You didn't have to do that, non default share names are confiscated in diagnostics. All I see is S--a

 

I don't see anything special in diagnostics, except for a warning about usb boot drive filesystem. But that should not cause issues during file copy after system is already booted 

Was the diagnostics during a file transfer? If not, do it when transfer is running. If yes, or if nothing else comes in diagnostics, wait for reboot and then let's look at syslog saved to usb drive

It hung at some point overnight.  Unresponsive to website, and I couldn't ping it.  I have it hooked up to a KVM, and it seemed unsresponsive even when I switched over.  I did a hard reboot, these are the logs after it rebooted. 

waystation-diagnostics-20230416-1311.zip

Model name:                      AMD Ryzen 5 1600 Six-Core Processor

 

Have you also ensured that the the Typical Idle Power Supply Current (or similar wording) is set to be Typical (or similar wording)

 

See also https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-819173

 

 

And also never hurts to run a memtest for a minimum of a pass or two

18 hours ago, Squid said:

Model name:                      AMD Ryzen 5 1600 Six-Core Processor

 

Have you also ensured that the the Typical Idle Power Supply Current (or similar wording) is set to be Typical (or similar wording)

 

See also https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-819173

 

 

And also never hurts to run a memtest for a minimum of a pass or two

I didn't see a setting that matched exactly that, but I confirmed all of the settings were not customized, or anything other than stock.  I can try updating the firmware, but this system has been running windows and linux for years without problems, so I'm kinda doubting it's bios related.  But it's a good thought, and I appreciate you suggesting it.

If there's no "Power supply idle control" setting looks for a BIOS update, if still not disable C-States globally.

I disabled the recommended setting and am still having the same problem. Attached are the most recent diagnostics.

 

waystation-diagnostics-20230418-1844.zip

Have you run a memtest for a minimum of a pass or two?  (If you're booting via UEFI, then you will need to switch temporarily to legacy boot or set up another stick to run https://www.memtest86.com/)

 

Another (unlikely) possibility is do the CL timings match on your mismatched sets of memory?

 

Is no change, enable the syslog server (mirror to flash) and after it reboots, post the resulting syslog contained within /logs on the flash drive

My mobo (b350-f) is blacklisted under memtest per this list:https://forums.passmark.com/memtest86/5743-list-of-motherboards-with-issues-when-running-memtest86-in-multi-cpu-selection-modes.  

I'm going to pretend I was aware I was running mismatched memory, I'll try to pull the mismatched sets and see if a configuration works there.  I've tried enabling the syslog server as suggested, but the logs keep getting wiped (or just have one line, which was really confusing to me).  I'll re-enable them and paste if you think they'll be different than any of the logs I've posted so far.

 

I've also upgraded the bios on my box, and it's still doing the same thing.

 

I'm not sure what changed it changed, but I decided to do the "automatic tuning" in bios, and just set the computer for general desktop use, and the system has now been running for 20 hours without rebooting, so the issue may be fixed.  I wish I had a real root cause to point to, but I at least wanted to update with what got it working in case someone was having similar issues.

 

Thanks for the help everyone.

Edited April 20, 20233 yr by I.M.APseudonym
clarity