December 30, 20214 yr Parity checks have started happening after every reboot which usually means there was an unclean shutdown.. I can't seem to figure out what is causing an unclean shutdown or if that is the issue. I've attached a diagnostics from the flash drive. Edited December 31, 20214 yr by Chandler
December 30, 20214 yr I had this issue too for awhile. Turned out it was my unassigned devices NFS connections that was at issue. When I disconnected them before the reboot, life was good. Not sure what the permanent fix was, but eventually reboots began to happen as normal.
December 30, 20214 yr Community Expert When Unraid can't shutdown cleanly it saves the current diags in the flash drive, logs folder, those diags might give a clue on what the problem is.
December 30, 20214 yr Author 1 hour ago, JorgeB said: When Unraid can't shutdown cleanly it saves the current diags in the flash drive, logs folder, those diags might give a clue on what the problem is. Yes, I looked there first but I didn't see anything stand out. That's why I attached them to the original post.
December 31, 20214 yr Community Expert Solution 11 hours ago, Chandler said: That's why I attached them to the original post. Sorry, missed that those were from the flash drive. You need to increase the shutdown timeout, it's set at 90 seconds and Unraid was still in the middle of umonting the disks at that time, with the array running normally press stop and time how long it takes, add 30 seconds and set that as the new shutdown timeout, or just try setting to like 150secs or similar, should be enough.
December 31, 20214 yr Author 11 hours ago, JorgeB said: Sorry, missed that those were from the flash drive. You need to increase the shutdown timeout, it's set at 90 seconds and Unraid was still in the middle of umonting the disks at that time, with the array running normally press stop and time how long it takes, add 30 seconds and set that as the new shutdown timeout, or just try setting to like 150secs or similar, should be enough. Got it, thanks! I had found a similar post and the solution was upping from 30 to 60 seconds. Mine was at 90 so I figured it was fine. But I added 3 to the array and 1 to the parity earlier this month and I think that is roughly when this started happening so it makes sense!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.