Got up this morning to discover my X15 server completely unresponsive. No connection to webui, ssh or any dockers. Had to hard reset the system. I have attached the most recent syslog server log file.

syslog-10.0.1.20.log

Seeing lots of kernel errors. I don't pretend to understand the entries though.

There are some PCI related corrected errors spamming the log, add the option below then start a new syslog and post that if it hapens again.

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009

Not sure I understand how to do this. Tried googling and got this-

Not sure this is correct though since I don’t see a Syslinux Configuration tab anywhere.

Settings - Boot Parameters, then add that option to the boot option you are using.

Maybe I found it? Is this correct???

9 minutes ago, JorgeB said:

Settings - Boot Parameters, then add that option to the boot option you are using.

Like this???

Or maybe this?

I used the switch and here are the current settings for my boot mode-

menuentry "Unraid OS" {
echo "Loading..."
linux /boot@/bzimage pcie_aspm=off
  linux /bzimage pcie_aspm=off
initrd /boot@/bzroot
}

Please confirm this is correct before I reboot.

You can use the toggle with 7.3.x, then reboot

27 minutes ago, JorgeB said:

You can use the toggle with 7.3.x, then reboot

Deleted the syslog file and rebooted. Will post back here if the issue recurs.

Server locked up again. syslog attached.

syslog-10.0.1.20.log

These are the last entries before the freeze/hard reset-

Jun 9 16:00:03 BrunnhildeTwo root: /var/lib/docker: 14.8 GiB (15930499072 bytes) trimmed on /dev/loop2

Jun 9 16:00:05 BrunnhildeTwo root: /var/lib/docker/btrfs: 14.8 GiB (15930925056 bytes) trimmed on /dev/loop2[/btrfs]

Jun 9 16:00:24 BrunnhildeTwo root: /mnt/cache: 135 GiB (144437903360 bytes) trimmed on /dev/nvme1n1p1, /dev/nvme0n1p1

Jun 9 16:00:24 BrunnhildeTwo root: /mnt/flash: 2.00 GiB (2142236672 bytes) trimmed on /dev/nvme2n1p3

Not sure if they have any bearing?

11 hours ago, wgstarks said:

Not sure if they have any bearing?

They shouldn't be, and there's nothing else there. If possible, try booting in safe mode and disable Docker and VM services; basically, use the server as a basic NAS, and see if it still crashes to rule out plugins or other apps.

I did a bunch of googling last night and it appears that using macvlan for the docker network can possibly cause this sort of problem so I have switched to ipvlan. Will give it a couple of days and see what happens. 🤞

If the crashes continue I’ll try your suggestion but I haven’t added any dockers recently and VMs are disabled.

Thanks for your help.

Macvlan should no longer be an issue, since 6.12.11, but it's worth a try in case the problem is still related to Docker in general and that change helps.

On 6/10/2026 at 7:37 AM, JorgeB said:

Macvlan should no longer be an issue, since 6.12.11, but it's worth a try in case the problem is still related to Docker in general and that change helps.

I have avoided making any changes to this server other than the docker network type for more than a week and haven't had anymore recurrances of the freezes. Changing macvlan to ipvlan seems to have fixed the problem.