After Updating from Version 6.9.2 to the most recent version 6.12.6, my Unraid Server no longer wants to stay in sleep mode.

I tried using the S3 Sleep Plugin and I also follwed the guide in the Unraid Documentation, where I put the Server to sleep by using

the command:

echo -n mem > /sys/power/state

My Problem is that the Server either just wakes up again or it reboots the whole system like from a shutdown state.

I captured a log file after the Server is put to sleep and added it in this post.

Maybe this section could have something to do with the sleepmode not working correctly:

Jan  7 15:57:33 Tower kernel: PM: suspend entry (deep)
Jan  7 15:57:34 Tower kernel: Filesystems sync: 0.555 seconds
Jan  7 15:57:34 Tower kernel: Freezing user space processes
Jan  7 15:57:54 Tower kernel: Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Jan  7 15:57:54 Tower kernel: task:rs:main Q:Reg   state:D stack:0     pid:1710  ppid:1      flags:0x00004006
Jan  7 15:57:54 Tower kernel: Call Trace:
Jan  7 15:57:54 Tower kernel: <TASK>
Jan  7 15:57:54 Tower kernel: __schedule+0x5b2/0x612
Jan  7 15:57:54 Tower kernel: schedule+0x8e/0xcc
Jan  7 15:57:54 Tower kernel: request_wait_answer+0xf7/0x1d3
Jan  7 15:57:54 Tower kernel: ? _raw_spin_rq_lock_irqsave+0x20/0x20
Jan  7 15:57:54 Tower kernel: fuse_simple_request+0x1b0/0x1ef
Jan  7 15:57:54 Tower kernel: fuse_getxattr+0xde/0x137
Jan  7 15:57:54 Tower kernel: fuse_xattr_get+0x28/0x2d
Jan  7 15:57:54 Tower kernel: __vfs_getxattr+0x5f/0x6e
Jan  7 15:57:54 Tower kernel: cap_inode_need_killpriv+0x1a/0x27
Jan  7 15:57:54 Tower kernel: dentry_needs_remove_privs+0x25/0x37
Jan  7 15:57:54 Tower kernel: __file_remove_privs+0x70/0xe9
Jan  7 15:57:54 Tower kernel: fuse_file_write_iter+0x165/0x42d
Jan  7 15:57:54 Tower kernel: ? update_cfs_rq_load_avg+0x176/0x189
Jan  7 15:57:54 Tower kernel: ? update_load_avg+0x46/0x398
Jan  7 15:57:54 Tower kernel: vfs_write+0x10f/0x1b9
Jan  7 15:57:54 Tower kernel: ksys_write+0x76/0xc2
Jan  7 15:57:54 Tower kernel: do_syscall_64+0x6b/0x81
Jan  7 15:57:54 Tower kernel: entry_SYSCALL_64_after_hwframe+0x64/0xce
Jan  7 15:57:54 Tower kernel: RIP: 0033:0x15233dc9dbdf
Jan  7 15:57:54 Tower kernel: RSP: 002b:000015233ce738e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
Jan  7 15:57:54 Tower kernel: RAX: ffffffffffffffda RBX: 000015232c007cf0 RCX: 000015233dc9dbdf
Jan  7 15:57:54 Tower kernel: RDX: 000000000000007a RSI: 000015232c007fe0 RDI: 0000000000000009
Jan  7 15:57:54 Tower kernel: RBP: 000000000000007a R08: 0000000000000000 R09: 0000000000000000
Jan  7 15:57:54 Tower kernel: R10: 0664089c5a409404 R11: 0000000000000293 R12: 000015232c007fe0
Jan  7 15:57:54 Tower kernel: R13: 0000000000000000 R14: 0000000000000002 R15: 000015232c007cf0
Jan  7 15:57:54 Tower kernel: </TASK>
Jan  7 15:57:54 Tower kernel: OOM killer enabled.
Jan  7 15:57:54 Tower kernel: Restarting tasks ... done.
Jan  7 15:57:54 Tower kernel: random: crng reseeded on system resumption
Jan  7 15:57:54 Tower kernel: PM: suspend exit
Jan  7 15:59:25 Tower kernel: veth3bc18ca: renamed from eth0

I also included the Diagnostics Archive of my Server so maybe you can find something I did wrong in my configuration.

 

syslog-192.168.178.42.log tower-diagnostics-20240107-1614.zip

^