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.

Wieldy

Members
  • Joined

  • Last visited

  1. Ok, I fixed that. I guess I'll enable a container and get it to crash again to see if the logs changes.
  2. Is this correct?
  3. It is enabled. I attached the log in my last comment
  4. Well, it crashed again with docker setting to ipvlan. I restarted the server disabled bonding and bridging and turned on docker with no containers. Docker is using macvlan since bonding and bridging are turned off. I'm really starting to give up here. I ran memtest and it passed I've run docker in default settings with no containers enabled and it crashed I ran docker in ipvlan with no containers enabled and it crashed. I don't enable docker and the server runs fine. No errors on disks No errors in log files. Attached are the most recent log files. apollo-diagnostics-20260309-1212.zip
  5. Ok, but I will say, that since switching to ipvlan there are no crashes yet. Coming up on 3 hours running ipvlan with one docker enabled using a custom network. Bonding and bridging are still enabled. Does anyone have theories as to why having docker use macvlan would cause a crash?
  6. Right, so that's the issue. I've checked the logs every time it crashes and there's nothing indicating a crash or errors. I found an older post on here referencing crashes when docker uses macvlan. Since restarting the server and switching docker to ipvlan it has not crashed yet, when normally it would have. I wonder if that has something to do with it? @JorgeB stated in a comment on that thread that having macvlan with bridging enabled could cause issues. I didn't change any network default settings until now, so it defaults to macvlan in docker with network settings having bridging and bonding enabled. This is the post for reference: https://forums.unraid.net/topic/151441-macvlan-crashes-6126/page/2/
  7. Sorry, just want to make sure I'm understanding. I currently have the mirror to flash option as "yes". Do I also have to set local syslog server to "enabled"?
  8. Small update, the one thing I hadn't tried was switching from macvlan to ipvlan in docker settings. I did that and enabled docker with containers stopped. So far it has been running smoothly, uptime almost 2 hours.
  9. Yes, the diagnostics I provided are when it crashed with just the docker enabled and no containers started.
  10. apollo-diagnostics-20260309-0829.zip
  11. Hi I have been trying to get my server setup for 5-6 days and I've been running into issues. Hardware: Gigabyte Z790 Aorus Elite AX Intel i5 12600k Corsair Vengeance DDR5 2x8GB 5200mhz 2 20TB Barracuda drives (shucked from expansion drives) I ran a memtest for 15ish hours and it passed with no errors. My drives show no errors. I check the logs before the crash and there are no errors. Attached is the most recent log file before the crash. You can see that I log in, enable docker, and stop the one container I have installed. I let the server run with just docker enabled and it crashes. When I have docker disabled it runs with no issue. syslog-previous.txt

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.