October 29, 20169 yr Just had a month old PS go kaput, after replacing PS and booting up no unclean shutdown was detected, and this was a very unclean shutdown, as I was in the middle of copying files to unRAID. PS: there's a canceled parity check that I had manually started because now it's not really a good time, will do it overnight. tower7-diagnostics-20161029-1722.zip
October 29, 20169 yr I can confirm this, has happened to me at least twice, pretty sure 3 times, where I was positive a boot was unclean, but no 'unclean shutdown' indication and no parity check. Each time, I quickly forgot about it, never reported it. It would have mostly been with 6.2.0, but may have also been with 6.1.9 (I should have recorded something, I'm sorry). I have suspected it might be related to the 'New config', 'Retain old config' changes, where on setting up a new super.dat, the dirty flag wasn't getting set. The retain feature is the one related thing that has changed in that time frame.
October 30, 20169 yr Author No, related to dual-parity - fixing now. Cool, lately there's been a few reports of sync errors after parity checks with users admitting there were unclean shutdowns before, and if unRAID doesn't detect it some users don't know they need to do a check ASAP. Last check completed on Sun 30 Oct 2016 05:59:33 AM GMT (today), finding 1855 errors.
October 30, 20169 yr I suppose I should mention that I've never touched dual parity on my system. So it's possible that my undetected unclean shutdowns may have a different cause.
October 30, 20169 yr I had an unclean shutdowns on my test server that did not result in an automatic parity check a couple weeks ago. Didn't actually realize it hadn't done a parity check after that shutdown until I read this discussion and checked the "History" of parity checks. [A UPS failed, and before I shut down and replaced it, we had a power outage. I replaced the UPS and rebooted the server, but didn't use it that day, so I had assumed it had simply done a check] I'll force an unclean shutdown after the next update to confirm this has been fixed. However, Rob's experience indicates this may be not just a dual parity issue.
October 30, 20169 yr I had an unclean shutdowns on my test server that did not result in an automatic parity check a couple weeks ago. Didn't actually realize it hadn't done a parity check after that shutdown until I read this discussion and checked the "History" of parity checks. [A UPS failed, and before I shut down and replaced it, we had a power outage. I replaced the UPS and rebooted the server, but didn't use it that day, so I had assumed it had simply done a check] I'll force an unclean shutdown after the next update to confirm this has been fixed. However, Rob's experience indicates this may be not just a dual parity issue. Sorry, meant to say the issue was introduced with the dual-parity feature, i.e., starting with release 6.2.
October 30, 20169 yr Good to know there aren't two different issues -- clearly you know about it and it'll be resolved with the next release
Archived
This topic is now archived and is closed to further replies.