February 21, 201214 yr I think if you power down unRAID during the parity verification process it will be saved as successfully verified. Parity check for me was at ~10% (of 1.5 TB) and I pressed the power off button. System went down after some seconds (as usual). But next time I started up, I saw "Last checked on ..., parity valid, no errors." Maybe better to toggle a flag after successfully completing verification? Or also save the current position of the progress every 5% step.
February 21, 201214 yr There is no way to store the progress information. Writing to the flash is unacceptable because writing shortens the life of the flash. If a parity check is manually aborted the user must remember to restart the check.
February 21, 201214 yr But should be easy to set a flag to remind the user it didn't complete. Also if you have a cache drive it could save the progress there. Sent from my SGH-I727R using Tapatalk
February 21, 201214 yr But should be easy to set a flag to remind the user it didn't complete. A check is not a mandatory thing and is "technically" not needed. A lot of people here set there servers up so that a check is done at the beginning of each month. It is just good practice. Also if you have a cache drive it could save the progress there. No, I would prefer that unRAID not do that. And for those running the free version this would not be possible.
February 21, 201214 yr Author Ok, if it's an optional task then I do not care so much. Also it's not a problem to remember when you started parity check and did a reboot during that. I think the timestamp is saved anyway to flash when you start checking, same if errors are found. I think writting a single byte once in a month will not really decrease life time so much.
February 21, 201214 yr Author Does a parity check start every time you start the server? no, definately not. but during my setup stage I think it started one time automatically. This was aborted with a reboot by me. Now it shows "Last Checked" and did not start again for several boot-ups.
February 21, 201214 yr Does a parity check start every time you start the server? no, definately not. but during my setup stage I think it started one time automatically. This was aborted with a reboot by me. Now it shows "Last Checked" and did not start again for several boot-ups. It would have started a parity calculation the first time you started the array after assigning a parity drive. Cancelling that initial calculation should NOT show parity as valid, since it is guaranteed to not be correct. Any subsequent "check" of parity, (assuming it is currently valid) can be cancelled and you are correct, the display is in error saying it completed on xxxxxxxx date. It probably should track and display "last checked date" and a "last completed date" separately. If it is not working as I described, then it is a bug. Joe L.
February 21, 201214 yr Author It would have started a parity calculation the first time you started the array after assigning a parity drive. Cancelling that initial calculation should NOT show parity as valid, since it is guaranteed to not be correct. yes initial parity calculation I did and let it finish. It was also not shown any "checked" date after it. This for sure was started automatically after assigning the drives to the array.
February 21, 201214 yr Does a parity check start every time you start the server? no, definately not. but during my setup stage I think it started one time automatically. This was aborted with a reboot by me. Now it shows "Last Checked" and did not start again for several boot-ups. So you manually started it and then shut the server down when it wasn't complete? Peter
February 21, 201214 yr Author So you manually started it and then shut the server down when it wasn't complete? maybe ;-) For sure shut down when it was not complete.
February 23, 201214 yr Author just to complete information here: I replaced my parity drive. The next boot after parity sync it automatically started a parity check. And after parity check is complete, the timestamp for the check looks updated.
February 23, 201214 yr You must have not shut down the server correctly if it started a parity check when you booted. It sounds like your power button press is not the correct way to shut down your server.
February 23, 201214 yr You must have not shut down the server correctly if it started a parity check when you booted. It sounds like your power button press is not the correct way to shut down your server. Or, the flash drive was not writable, so the parity completion not recorded.
February 23, 201214 yr The USB drive being read-only could also mean that unRAID having properly unmounted the array disks before shutting down could not record that it had done so meaning unRAID believed the server was improperly powered off on the next boot. However, the USB drive being read only is usually due to file system corruption and it's not likely the server would properly start again with a damaged USB drive. Peter
February 23, 201214 yr Author the last times I shutdown by power press there was no parity check after rebooting. Using the power button the PC beeps twice and then after some seconds it is powered off. Can't be that after an parity sync/rebuild the next time it will do a parity check?
February 23, 201214 yr Can't be that after an parity sync/rebuild the next time it will do a parity check? I've never heard or seen of that happening. Generally, a parity check will only happen on a stock unRAID install after an unclean shutdown or when you press the check button.
Archived
This topic is now archived and is closed to further replies.