omkar

Don't know how to say this any other way, but don't just hit the reset button unless absolutely necessary and you have no way to reboot otherwise. It might cause you to lose data... if the files being written to disks had not yet been flushed from the disk buffer cache to the physical disks they might be mangled/partially written, or lost/never written. Always stop the array first using the "Stop" button on the web-interface. Then you can reset/reboot/power down as needed. When you power back up, the array will know it shut down cleanly and not need to perform a full parity check. Joe L. Thanks for the explanation. Got it now!

The parity check is only normal if you did not stop the array cleanly before rebooting. You might want to post a syslog. If you think you stopped the array before rebooting, and the parity check was unexpected, then you might want to post a syslog to see if there was a different reason for the parity check. Joe L. That explains it then. I did not stop the array via the web interface. I only pressed the Reset button on my MD-1510. Thanks!

Thank you Joe for creating this! I no longer have any pauses when using my media player to browse my unRaid server I put the script in a folder like you indicated on an earlier post in this thread and added the appropriate lines (to set the path and kick off the script) in my go file. After rebooting, the array automatically started a parity check. Is that normal? Once it completed, everything was working just fine.