Why did a disk clear start on a pre-cleared disk?

[FreeMan]

I just ran a preclear on a new drive (using binhex's preclear docker). After 40 hours it finished with no reported issues.

 

I stopped my array, added the new drive, and started the array. Now it says that a clear is in progress.

 

Why would it start clearing the drive again? Did the preclear somehow fail to properly write the correct signature to the disk?

 

nas-diagnostics-20220406-1510.zip

[Squid]

With the binhex preclear container, there's probably some extra command line options you needed to give it for it to be recognized properly

 

Personally, on the very very rare times I preclear a drive I use Unassigned Devices Preclear

[FreeMan]

6 minutes ago, Squid said:

With the binhex preclear container, there's probably some extra command line options you needed to give it for it to be recognized properly

I used -f for a "fast" preclear, but I don't recall ever having used any other command line options, and I don't recall ever having had this issue in the past. As a matter of fact, I just precleared & installed a new drive a few weeks ago and didn't run into this issue.

 

I know preclear isn't necessary anymore as the base OS will do it without having to take down the whole array for hours while it happens, I like having it as a handy disk check utility for new drives. I know there are various theories on this, it's my preference.

[Frank1940]

I vaguely remember something that having the wrong starting sector for the partition will cause this to happen...