Hello folks.

 

I'm currently finishing the build of my new 3TB parity disk.  Overnight some backup scripts ran which copied some data to the data disks.

 

I assume that the parity was still going to be properly built, accommodating for this new data even if it impacted a part of the parity disk that was already "built".

 

Can someone confirm that Unraid does handle this type of situation correctly?  Want to make absolutely sure I don't need to re-build parity before I add my other new disks to the array.

 

Thanks.

It's fine. Run a parity check overnight to confirm.

As noted above, it's fine -- UnRAID handles that just fine.

 

Nevertheless -- with or without intervening writes -- the first thing you should do after the initial parity sync is to run a parity check, just to confirm everything went okay (the writes done during the parity sync are not otherwise validated).

 

Thanks guys.

 

Clearing now, have two drives added - it appears it is doing them serially rather than in parallel?

 

I was thinking about doing a parity check, you guys just hammered it home - thank you.

 

Still don't trust the GUI though with the "no correct" option.  So I'll have to use the command line until that is conclusively fixed.

 

Thanks again.

Still don't trust the GUI though with the "no correct" option.  So I'll have to use the command line until that is conclusively fixed.

 

Not sure why you'd want to do a "no correct" anyway ... but if you do, just do it through UnMenu (assuming you've installed it).

 

Not sure why you'd want to do a "no correct" anyway ... but if you do, just do it through UnMenu (assuming you've installed it).

 

While highly unlikely - since I did a parity check before swapping out my parity disk...  After re-creating the parity, and now expanding the array, it is possible there was a failure somewhere other than the write on the parity.  Keeping a human in the loop I think is good.

 

I haven't installed unmenu on v5, at least not yet.