Hello All,

I swapped out my 4 TB parity driive for an 8 TB parity drive.  Of course, Unraid had to run a full parity scan that took several days.  Since then, I rebooted unraid and upon the reboot Unraid ran a complete Parity Check again.   (again it took several days).   

 

Is this normal behavior for UNRAID?   I read that an unclean reboot can force a 'full parity scan'.   Question:  How can I tell if there was an un-clean shutdown?  I don't think  there was  but I can't be sure  and didn't anything on the UI to indicate  "UnClean Shutdown".

Does unraid  always want to do a full parity  scan after a reboot?  I never noticed this behavior when I had the 4TB 'parity' drive so I'm not sure.

 

Any thoughts?

Thanks,

ce

 

8 hours ago, [email protected] said:

How can I tell if there was an un-clean shutdown?

Please post the diagnostics.
 

On 12/18/2024 at 7:43 PM, [email protected] said:

Hello All,

I swapped out my 4 TB parity driive for an 8 TB parity drive.  Of course, Unraid had to run a full parity scan that took several days.  Since then, I rebooted unraid and upon the reboot Unraid ran a complete Parity Check again.   (again it took several days).   

 

Is this normal behavior for UNRAID?   I read that an unclean reboot can force a 'full parity scan'.   Question:  How can I tell if there was an un-clean shutdown?  I don't think  there was  but I can't be sure  and didn't anything on the UI to indicate  "UnClean Shutdown".

Does unraid  always want to do a full parity  scan after a reboot?  I never noticed this behavior when I had the 4TB 'parity' drive so I'm not sure.

 

Any thoughts?

Thanks,

ce

 

Here are my log / diagnostics.     One update:  Today my unraid server is doing another full parity scan.  I have not rebooted so I wondering why its doing this.  The first scan finished and then the system ran for over a day without issues (that I could see) and now doing another 'full' partity scan.

 

Thanks

 

tower-diagnostics-20241220-1356.zip

Dec 18 15:25:12 Tower emhttpd: unclean shutdown detected

 

2 minutes ago, [email protected] said:

Today my unraid server is doing another full parity scan.  I have not rebooted so I wondering why its doing this.

 

Check the schedule, possibly it's scheduled for 2200H

 

Dec 19 22:00:01 Tower kernel: md: recovery thread: check P ...

 

 

Cancel the check, stop the array and time how long it takes, you already have a high shutdown timeout, so possibly the array is not stopping, if it stops, look in the flash drive /logs folder for the diags from the date/time you last rebooted and post those, it should save a copy there if it cannot do clean shutdown.

I looked at my own logs and did  see a message indicating at least one unclean shutdown.  So I thinking from your answer there is no way in the UI to  see and details on why I had an unclean shutdown.

Am I correct that an unclean shutdown will result in a complete paity 're-scan'?

 

Thanks

 

Just now, [email protected] said:

Am I correct that an unclean shutdown will result in a complete paity 're-scan'?

Yep.

6 minutes ago, [email protected] said:

I looked at my own logs and did  see a message indicating at least one unclean shutdown.  So I thinking from your answer there is no way in the UI to  see and details on why I had an unclean shutdown.

Am I correct that an unclean shutdown will result in a complete paity 're-scan'?

 

Thanks

 

Ok.  I think I understand what I  was doing wrong.  For some reason, my schedule was to run every day.