So with the upgrade to 6.4.0 I'm now working on encrypting each of my disks. I did some searching around the forums, and didn't find anything related, but my apologies if I am doing this wrong or if this is answered somewhere else. But, here's the process I'm going through which is forcing me to do a parity check as I convert each disk.

 

Steps:

1. Empty disk to be encrypted. I'm using mc to move all contents of diskX to other disks on the array,

2. Stop array. Change filesystem type of diskX from xfs to xfs - encrypted.

3. Return to start array, however I'm stymied with this:

 

 

which is peculiar since I didn't shutdown my system.

 

A little more info:

I've gone through the process of starting the array, which successfully encrypts the disk and does the parity check. The parity check reports back zero errors corrected.

 

Obviously this doesn't create any problems per se, it just massively increase the time its going to take to convert my entire array.

Hi SRB

 

Stopping the array should not force a parity-check.

 

I have seen your issue on one of my unRAID instances running 6.4.1. Stopping the array causes "Unclean shutdown detected."

 

You should be safe in cancelling the parity-check and formatting the drive you set to XFS-Encrypted.