yogy Posted March 7, 2021 Share Posted March 7, 2021 Yeap, that did the trick. No parity check after changing the disk timeout setting. What do you think caused this. Is it v6.9.0 related? Quote Link to comment
JorgeB Posted March 7, 2021 Share Posted March 7, 2021 21 minutes ago, yogy said: What do you think caused this. Is it v6.9.0 related? Not sure, but don't think so. Quote Link to comment
itimpi Posted March 7, 2021 Share Posted March 7, 2021 47 minutes ago, JorgeB said: Settings - disk settings - shutdown timeout Try 100 secs or similar just to save the new value. worth pointing out that for many of the timeouts you have to enabled Advanced view. Quote Link to comment
invik Posted March 13, 2021 Share Posted March 13, 2021 I had the same issue. Upgrade to 6.9.0 (and 6.9.1 for that matter) and parity was checked at each reboot. I applied the 100 sec shutdown timeout and it is ok now. Quote Link to comment
macieksoft Posted March 14, 2021 Share Posted March 14, 2021 Was getting the constant parity check with 6.9.1, set the timeout to 100 seconds and its fixed. This is definitely a bug. Quote Link to comment
JorgeB Posted March 14, 2021 Share Posted March 14, 2021 9 hours ago, macieksoft said: This is definitely a bug. I would now agree, since it happened to at least a handful of users. Quote Link to comment
Jessie Posted March 24, 2021 Share Posted March 24, 2021 On 3/14/2021 at 11:30 AM, macieksoft said: Was getting the constant parity check with 6.9.1, set the timeout to 100 seconds and its fixed. This is definitely a bug. Me too. Coincided with the installation of my 9th array disk, installation of 2 extra secondary cache drives and upgrade to 6.9. So not sure what triggered it. I'm thinking it just has more to do during the timeout period of the shutdown. I just set the timeout to 100. Will see what happens. Quote Link to comment
dartworth Posted April 8, 2021 Share Posted April 8, 2021 I was having this issue also. Changing the timeout value seems to have corrected the situation. Thanks Quote Link to comment
privateer Posted April 11, 2021 Share Posted April 11, 2021 I'm having this exact same problem, and changing the timeout from the default 90 to 180 did nothing. Recheck started. Anyone offer some tips on where I might need to look to solve this? Quote Link to comment
trurl Posted April 11, 2021 Share Posted April 11, 2021 Stop the array but don't shut down or reboot. After it finishes stopping the array (or if it doesn't) post diagnostics. See here for how "unclean shutdown" works: 1 Quote Link to comment
bally12345 Posted August 19, 2021 Share Posted August 19, 2021 (edited) This issue has crept up again for me, original fix was to change shutdown timeout to 100 but in the last few months I have noticed this happening again. Currently on 6.10.0-rc1 server-diagnostics-20210819-1423.zip Edited August 19, 2021 by bally12345 Quote Link to comment
JorgeB Posted August 19, 2021 Share Posted August 19, 2021 32 minutes ago, bally12345 said: original fix was to change shutdown timeout to 100 but in the last few months I have noticed this happening again. Aug 19 13:05:50 Server emhttpd: unclean shutdown detected You likely need to increase the timeout even more. Quote Link to comment
trurl Posted August 19, 2021 Share Posted August 19, 2021 1 hour ago, JorgeB said: Aug 19 13:05:50 Server emhttpd: unclean shutdown detected You likely need to increase the timeout even more. Stop the array, time how long it takes to actually finish stopping, and give it more than that. Quote Link to comment
Opawesome Posted August 20, 2021 Share Posted August 20, 2021 (edited) On 3/7/2021 at 1:05 PM, yogy said: Since the upgrade to 6.9.0 after every clean reboot of my server, parity check is starting. This wasn't the issue on 6.8.3. From the syslog I get: Mar 7 12:39:34 unrsrv emhttpd: unclean shutdown detected, but all I did was a click to REBOOT button in the main page. Please find attached my diagnostics file. unrsrv-syslog-20210307-1155.zip 34.15 kB · 1 download I have exactly the same issue (parity check after each normal reboot/shutdown via the WebGUI, syslog saying "unclean shutdown", etc.). This also started to happen right after i updated from 6.8.3 to 6.9.2. I will try the fix provided in this thread but I think @limetech could maybe consider a fix in the next version. Best, OP UPDATE 1: changing "Settings > disk settings > shutdown timeout" from 90 to 120 seems to have fixed the issue for me. Edited August 20, 2021 by Opawesome Quote Link to comment
Recommended Posts
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.