Drive Replacement Too Small Error

[winnielinnie]

@Protopia

I find it very odd indeed that two disks with identical model numbers should have different sizes. Whilst they both technically meet the 12TB (12 * 10^12) definition, I would expect a change in engineering to result in a (perhaps minor) change of model number.

This is why I think it’s shortsighted to remove the 2-GiB “swap” partition when creating or adding drives to a vdev. Even if you never use swap, it provides an essential “buffer” to mitigate against this very issue that the OP is experiencing.

I know SCALE completely disabled swap, even on the boot-pool. Did they also remove the default 2-GiB partition buffer as well?

Expand point #1 to read and understand my concerns about switching from Core to SCALE about this very issue.

@@winnielinnie

In Core, I currently have it set to create a 2-GiB partition at the beginning of every newly added/replaced drive. Although I don’t use swap, this 2-GiB “buffer partition” serves an important role: It safeguards you against purchasing a drive of the “same” capacity, only for it to be slightly smaller. Will SCALE allow making a “buffer partition”, even without activating it as swap? (i.e, unformatted / undefined 2-GiB partition.) Even if this hasn’t happened to someone yet, it future-proofs against any changes by the manufacturers, where 20-TiB and 20-TiB might not be exactly the same.