Attempting to replace a failed drive.

[telarium]

Attempting to replace a failed drive, as I have so many times before (thanks, Seagate). I didn't need to 'Offline' the disk, as 'Replace' was the only option. Physically replaced the toasted disk with a new one.

Oddly, this appeared:

Any thoughts?

Thanks.

 

[SweetAndLow]

You pool is encrypted and the disk you are using to replace is formatted with zfs or something already. Are you sure you want to reuse it?

That is what that red stuff is telling you.

 

[telarium]

The pool is indeed encrypted, but the disk I'm replacing it with was fresh out of the box. Wiped the new disk, just to be sure. Still the same error...

Perhaps I inadvertently placed a partition on there or perhaps Western Digital places a partition on there for whatever reason. Perhaps I'll try to wipe it again?

Edit: I'm aware about the key invalidation - just trying to figure out the partition situation on the fresh disk.

 

[SweetAndLow]

You could just check the force box

 

[m0nkey_]

Replacement instructions are in the docs. You should have a read: http://doc.freenas.org/9.10/freenas_storage.html#replacing-an-encrypted-drive

 

[danb35]

You could just check the force box

Yes, but the question is why FreeNAS thinks there's something on the disk when there isn't. The update notification for the latest 9.10 update mentions that it fixes a bug relating to "tasting" a disk when doing drive replacement, which might be relevant to what @telarium is seeing.

 

[SweetAndLow]

Gpart list will show all partitions on the drive. See if there really is anything.

 

[telarium]

Gparted it this morning before I ran out the door -- it's all 'Unallocated Space' on the new drive. I'll replicate the test again after work and then fdisk it on my other Linux machine to confirm.

 

[cyberjock]

Does it have a ZFS label? With no partitions you can still have zfs labels.

 

[telarium]

I don't believe so, but I was out the door on the way to work. I literally unwrapped the drive from the static case and swapped it with the failed drive. That's when the ZFS label issue occurred. I doubt Western Digital sends out new drives with ZFS labels - but, who knows?

I assume I can safely force it without destroying the pool?

Edit: Or <zpool labelclear -f> the new drive?

 

[danb35]

The bug is https://bugs.freenas.org/issues/10799, but I'm not sure it's what you're seeing--if anything, what you're seeing sounds like its resolution.

 

[telarium]

Can't say what it was, but 'forcing' it allowed for a successful resilver.

Thanks, all.