Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Random reboot every couple of months

Featured Replies

  • Community Expert

As the title says, every couple of months I have a random reboot, afterwards my server runs perfectly fine.

After setting up syslog (and waiting some months for another reboot I noticed my USB was having errors.

I replaced my USB and though that would be the end of it, but a couple weeks later I just had another random reboot.

The reboot happened around ~11:00-11:15 am. I've had a look at the log files, but couldn't really find anything suspicious, hopefully someone here with more knowledge can find the culprit.


One thing I noticed was that when it was starting it was installing stuff/plugins, not sure if Unraid does that on every start.

oddnas-diagnostics-20250525-1123.zip

Solved by OddMagnet

  • Community Expert

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), 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 to a share instead.

  • Author
  • Community Expert

Ah, sorry, forgot to attach the one from the syslog server, here it is:

I've gone ahead and removed entries from before today, let me know if you need to see more.

Though I don't think it really shows much, these two entries specifically are the last before the reboot and after (when the syslog server is started again)

May 25 10:47:38 OddNas emhttpd: read SMART /dev/sdb
May 25 11:24:32 OddNas rc.rsyslogd: Syslog server daemon...  Started.

syslog-192.168.178.200.log

  • Community Expert

Server rebooting by itself is almost always a hardware issue, since you have multiple RAM sticks, try using the server with just one, if the same try with the other one, that will basically rule out bad RAM.

  • Author
  • Community Expert

Would a MemTest be good enough to rule out bad RAM? Since the reboots are quite far apart I'd like to avoid running my server with half RAM for that long

  • Community Expert

Memtest is only definitive if it finds errors, but you can try that first.

  • Author
  • Community Expert

Initially I tried running the Live Memory Test plugin, after one pass without errors I decided to reboot into Memtest86+ after all.

After stopping the plugin and attaching monitor and keyboard to my server it had rebooted again, tried disconnecting and replugging them a few times to check if that was a fluke, no further reboots from that. (Also tried un- and replugging my Monitor from the UPS, nothing here either)

I'd assume that neither my UPS or the connections from the Monitor/Keyboard caused the reboot, weird though that it happened in just that moment.

Or maybe it's bad RAM and happened from stopping the Live Memory Test plugin?

Either way, gonna report back when Memtest has run long enough

  • Author
  • Community Expert

Memtest86+ has ran for 10 passes, almost a day. I think it's safe to say the problem isn't the RAM.

Gonna start a CPU stress test for a couple of hours now.

The only thing that changed when moving from my old server case to the new one (aside from the case, :D ) was the Mainboard.

Not sure if it's even possible to test that though

  • Community Expert
42 minutes ago, OddMagnet said:

I think it's safe to say the problem isn't the RAM.

Unfortunately memtest is only definitive if it finds errors. It is quite possible to pass memtest and still have RAM issues.

  • Author
  • Community Expert

Sure, but what is the likelihood that RAM is gonna be the issue then?
Running my server for 3+ months with half RAM isn't really an option either.

  • Community Expert
48 minutes ago, OddMagnet said:

Running my server for 3+ months with half RAM isn't really an option either.

If you only get reboots that infrequently o be honest I would not worry about it. It is something to bear in mind though if it starts getting more frequent.

I can remember the days when machines typically had to be rebooted several times per day 😊

  • Author
  • Community Expert

I guess I could, but it certainly annoys me every time it happens, I always panic a bit about there being a bigger problem.

CPU Stress test didn't show anything out of the ordinary either (in fact I'm surprised my CPU doesn't go above 48°C even after 3+ hours of max load).

Gonna leave the thread open for now, maybe the next time it happens I have more clues

edits:

29.05.25: Happened again, no clues in the syslog

29.05.25: Wow, twice in one day...

06.06.25: Seems to happen more now than every couple of months...

11.06.25: ...

25.06.25: ...

06.08.25: just when I thought it was just running...

21.08.25, 14.09.25
20.11.25: Was about to post that I might've solved the problem and it happened again, lmao

21.11.25: and again...

Edited by OddMagnet

  • 10 months later...
  • Author
  • Community Expert
  • Solution

If anyone is still seeing this, it seems a BIOS update finally solved this for me. At least I haven't had any unplanned reboots anymore.

Almost 2 Months uptime now

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.