It seems every time I boot my server, I get notified of an unclean shutdown and parity runs. I just ignored the issue before, but it's bothering me as why my server doesn't seem to think the update from 7.2.4 to 7.2.5 is an unclean shutdown. Also, I don't know why my server would think that the 'Reboot' option from the Main page isn't a clean shutdown.

I've attached the diagnostics from right after the reboot, although I believe they won't have much information in them. Therefore, I'm also attaching diagnostics from a few days ago when I was trying to diagnose another small issue (can' see notifications unless I press Alert, Info, All Types, Warnings, then back to Info). I noticed that issue in 7.2.4 (not sure if it started when I updated to 7.2.4), but I switched from black to white color scheme and it made no difference.

Should I re-run a complete parity check again or is there something else that might be triggering an unclean shutdown notification?


tower-diagnostics-20260501-1740.ziptower-diagnostics-20260427-1311.zip

Edited May 4May 4 by ATEglauer
Removed duplicate screenshot of parity history

If your flash drive couldn't be written while stopping the array, such as might happen if it dropped offline or was made read-only due to corruption, then it will look like an unclean shutdown since the flash drive is where stopped/started is saved.

There are a couple of FSCK files on flash which would be due to "fixing" corruption.

Sorry, I'm not following. Are you saying I should delete a couple of FSCK files off the flash drive?
(I've had to reboot again, this time due to nVidia driver, so I stopped the array first, then hit reboot on the main page, but I've not done anything on the flash drive yet.)

Upon reboot this time, it appears it was a clean shutdown and parity check didn't start. I also see the two FSCK files on the flash drive, so I assume if I delete those it might help? I note they are dated from 1979!

Edited May 2May 2 by ATEglauer
Added details about the reboot following nVidia driver update

The date of those FSCK files are meaningless. And deleting them won't help anything but they can be deleted since they are taking up space.

Unraid stores the array started/stopped status on the flash drive. If the array is started, that status is stored on flash. Then, when the array is stopped, unless it can write that stopped status to the flash drive, next time it boots it will see that array status as still started (not stopped) and so it is an unclean shutdown. Reading that status is literally how it decides if there was an unclean shutdown.

18 minutes ago, trurl said:

The date of those FSCK files are meaningless

The "zero" timestamp for DOS (FAT) is 00:00:00 1980-01-01, so it probably just doesn't timestamp those FSCK files