Hi all,

Two days ago, I noticed a notification reporting an unclean shutdown, which triggered a parity check as expected. However, for the last three days, including today, I have been receiving the same notification.

My server is configured to power on every day at 3:00 PM through the BIOS and shut down every day at 2:00 AM, except on Friday and Saturday nights, using a basic custom script:

/usr/local/sbin/powerdown

Cron schedule:

0 2 * * 1-5

Everything was working correctly until Monday. Based on the notifications, it does not appear that the scheduled shutdowns are failing. The unclean shutdown alert is being generated about four minutes after startup, around 3:05 PM.

On Tuesday, I started the server manually, and it shut down four minutes later, just as it does when it starts automatically at the scheduled time.

One thing worth mentioning is that after the unclean shutdown notification, the server appears to start normally. All services seem to work as expected, and the parity check is automatically triggered, just as it should be after an unclean shutdown. From a functional standpoint, everything looks normal apart from the repeated unclean shutdown alerts.

To be honest, I can't find anything useful in the logs, so I'm sharing the diagnostics in the hope that someone can identify the root cause of this issue.

Thx in advance!

corellia-diagnostics-20260610-1624.zip

Edited June 29Jun 29 by surferjsmc

If you shutdown manually then reboot, is it also unclean?

Here is how unclean shutdown is detected:

https://forums.unraid.net/topic/69868-dealing-with-unclean-shutdowns/page/5/#findComment-1087704

More useful information in that same "sticky" thread pinned near the top of this General Support subforum:

https://forums.unraid.net/topic/69868-dealing-with-unclean-shutdowns/

42 minutes ago, trurl said:

If you shutdown manually then reboot, is it also unclean?

Here is how unclean shutdown is detected:

https://forums.unraid.net/topic/69868-dealing-with-unclean-shutdowns/page/5/#findComment-1087704

More useful information in that same "sticky" thread pinned near the top of this General Support subforum:

https://forums.unraid.net/topic/69868-dealing-with-unclean-shutdowns/

I manually shut it down while the parity check was running at 43%, then started it again, and there were no notifications of an unclean shutdown.

1 hour ago, surferjsmc said:

I manually shut it down while the parity check was running at 43%, then started it again, and there were no notifications of an unclean shutdown.

Was everything you normally have running at the scheduled shutdown time also running when you did this test?

On 6/10/2026 at 8:21 PM, trurl said:

Was everything you normally have running at the scheduled shutdown time also running when you did this test?

Hi, sorry for the delay. Today I finally had time to check the scheduled BIOS power-on. With a monitor hooked up to the server, I followed the whole startup process and didn't notice anything wrong. The server took about 3 minutes in total from power-on to the login prompt, and nothing looked abnormal (attached is a screenshot of the boot screen). The boot finished at 15:03, but the server error occurred at 15:04, even though it never rebooted itself or failed during that time. Once again, however, the same notifications appeared.

I also performed a manual shutdown and boot, and it didn't return any errors. I even tried turning the server on in the morning before the scheduled time, and there were also no errors. Everything was running as usual—just a few containers and plugins, and no VMs.

corellia-diagnostics-20260625-1516.zip

Edited June 25Jun 25 by surferjsmc

The syslog in the diagnostics definitely shows that Unraid thought an unclean shutdown had occurred and as a result a parity check was initiated.

Note that you will get an unclean shutdown if the timers controlling disk unmounting expires, or if for any reason Unraid is unable to write to the flash drive the fact that it has been able to do a clean shutdown.

The syslog-previous in the diagnostics shows that it was the disk timeout expiring before the array could be tidily stopped that caused the unclean shutdown:

Jun 25 02:01:32 Corellia emhttpd: shcmd (55137): umount /mnt/cache

Jun 25 02:01:32 Corellia root: umount: /mnt/cache: target is busy.

Jun 25 02:01:32 Corellia emhttpd: shcmd (55137): exit status: 32

Jun 25 02:01:32 Corellia emhttpd: Retry unmounting disk share(s)...

Jun 25 02:01:34 Corellia rc.local_shutdown: Forcing shutdown...

Update: TRIM was scheduled for 2:00 AM. A manual TRIM took 2–3 minutes, which perfectly matches the timing of the unclean shutdowns on my NVMe cache pool.

I have rescheduled TRIM to run at a completely different time, far away from the shutdown window. Last night, the script executed the server shutdown perfectly. The server started manually this morning with no errors, confirming that the overlapping schedules were the root cause.

I'll monitor the system and the new TRIM schedule for a few days to make sure it's fully resolved.

New diagnostics added.
corellia-diagnostics-20260626-1106.zip

No more unclean shutdows so i can confirm the scheduled TRIM job was the root cause.

Thank you all for your feedback.