I'll start by mentioning I did read https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/, however I was under the impression since I used the Unraid USB Creator tool to restore from my USB backup, I would not have to deal with a parity rebuild as my array and pool configs carried over.

 

The only mention of parity was if you are uncertain of your drive slot assignments or if you used New Config. Since I did not see an option next to the Start button for me to indicate the parity was already valid, I'm not sure why a parity sync started again.

 

I've booted from my USB with my license key intact. There was no option next to the Start button to start the array and indicate parity was already valid.

 

My question is - since parity sync is running again, if I were to cancel it, create a new config, and indicate parity is valid, would it in fact be valid? I would assume no considering the parity disks were probably wiped after I started the array and the parity sync process started, right?

 

Should I have done this instead?
 

1. Restore usb boot drive from backup
2. created a new config preserving array and pool slots
3. ticked checkbox that parity was valid
4. start array

 

 

I think that the problem will be that the backup was made with the Array started and this was the status recorded in the USB backup.   When you started on the new flash drive Unraid saw this status and assumed that an unclean shutdown had happened and thus the parity check. 

 

Your process would have avoided this, but I feel that it should not be needed if transferring the licence to a new flash drive.   I cannot remember if in the past I have done a licence transfer without encountering this issue as the last one was some time ago.  Maybe something for Limetech to look into?

5 minutes ago, itimpi said:

I think that the problem will be that the backup was made with the Array started and this was the status recorded in the USB backup.   When you started on the new flash drive Unraid saw this status and assumed that an unclean shutdown had happened and thus the parity check. 

 

Your process would have avoided this, but I feel that it should not be needed if transferring the licence to a new flash drive.   I cannot remember if in the past I have done a licence transfer without encountering this issue as the last one was some time ago.  Maybe something for Limetech to look into?

Hmm....I didn't think about that - very good point. I will keep that in mind for next time - to create the backup when the array is stopped. And also, if the drive goes bad and I use the flash backup from Unraid connect, to create a new config, and indicate parity is valid first. Either way, it seems the only way to indicate the parity is valid is to start with a new config, at least from what I've experienced. 

 

Thanks