I woke up this morning to this error. I'm trying to be self sufficient so I dug through some of the logs and did some online searching in an attempt learn and possibly come up with a solution. The solution is that this is beyond my current capabilities lol.

I did see some reoccurring errors. I found a I/O error, dev sdm - Looking through the array "Var" log I was able to locate that device by serial number and that device was listed as a historical unassigned device which I then promptly removed from UD, why is a historical device generating I/o errors? No other drive in my array appears to be using dev/sdm

I'm thinking the big problem is that I am seeing get_swap_device: Bad swap file entry 3fd400979278f ### [PREVIOUS LINE REPEATED 1585193 TIMES] ###

Searching for this problem didn't bring up anything helpful to me.

I read that a reboot will temporarily help, but I haven't rebooted yet in case it may cause some other issue to arise. What do I need to do from here?

zeus-diagnostics-20250527-1345.zip

Looks like connection problems with your cache drive as well. Reboot will clear log but won't fix those connection problems of course.

Unrelated. Why do you have 165G docker.img? Have you had problems filling it?

I saw those cache drive errors as well, I recently rebuilt my server and plan to change my cache to an nvme SSD within a week or so, so I ignored it.

I'm not sure about the large docker.img What causes it to grow? I had a lot of problems with my previous server hardware- and constantly had issues with containers having faults - randomly being removed, hanging and such. Is there anything I can do to fix the file - does it even matter?

Anything I can do about the swap errors?

Thanks.

46 minutes ago, moose1207 said:

Anything I can do about the swap errors?

That doesn't look stock, did you ever use the swapfile plugin or similar?

2 hours ago, JorgeB said:

That doesn't look stock, did you ever use the swapfile plugin or similar?

Nope. I just figured that had something to do with the OS itself. Been running Unraid for years, this is the first time I've seen this.

It was a RAM problem for the first two Google results for that error, so try running memtest.

On 5/28/2025 at 6:44 AM, JorgeB said:

It was a RAM problem for the first two Google results for that error, so try running memtest.

Ran memtest and it passed with no issues.

memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

If the same, try booting in safe mode.