February 27, 201313 yr I changed my parity drive (no problem here), then rebuilt the parity, this was slow (started 40mb/s, ended 5mb/s - 22 hours) but no issues either. I then did a complete 920 minute parity check.... (: Now it is starting a parity check every time the drives spin up...what the heck can I do here, it has made my server almost useless! What can I do about this? syslog-2013-02-27.txt
February 27, 201313 yr apparently the array was not stopped cleanly, or never got to record the successful parity calc, and you keep cancelling the resulting parity check. Feb 27 07:53:57 Tower emhttp: unclean shutdown detected, checking parity...
February 27, 201313 yr Author And how do I take care of this? It's telling me that the parity is valid, was checked on Wed Feb 27 12:06:53 2013 EST, finding 0 errors Is this normal
February 27, 201313 yr And how do I take care of this? How are you shutting down your server? You should be using the GUI interface. On the Main Page, you first stop the array and then you will see the options to shut the server off.
February 27, 201313 yr If you run out of things to check, pull the USB stick and do a chkdisk. The successful proper shutdown of unraid has to write to the USB stick to indicate a good shutdown, if it can't write or read that file on the usb stick, it will assume the previous shutdown was unclean and start a correcting parity check.
February 27, 201313 yr Author I use the GUI to shut it down just as you stated. New log shows no shutdown error chkdisk is fine, no errors syslog-2013-02-27.txt
February 28, 201313 yr Author I think this one can be removed or marked as solved, thanks for the help Ice
February 28, 201313 yr I think this one can be removed or marked as solved, thanks for the help Ice Edit your first post to change the subject and icon.
Archived
This topic is now archived and is closed to further replies.