FreeNAS-11.3-U1 - Error when trying to resilver

[raproter]

Hello, this is my forum post so sorry in advance if I do something wrong.

When I replaced my HDD I followed the instructions you guys have on your YouTube channel. By which I mean going to the status of my storage pool and clicking on status in the dropdown menu and replacing the HDD from there. But when I selected the drive to replace the old one I got this:

Code:

Error: UNIQUE constraint failed: storage_encrypteddisk.encrypted_provider

But after I clicked that away it just started resilvering. Now I don't know what that error code means and searching for it on Google didn't give me a lot of answers either. The only thing I found was in a release post on FreeNAS-11.3 with another user who had the same problem. Now I am guessing that this is a bug in the FreeNAS OS and that it has nothing to do with my hardware. This code is the code from the debug window when it started resilvering and after it was done:

Code:

Mar 10 19:52:16 Artemis ZFS: vdev state changed, pool_guid=14519126106832416880 vdev_guid=14873538943975352029
Mar 10 19:52:16 Artemis GEOM_ELI: Device gptid/43221cc2-6300-11ea-972f-b42e99493ac8.eli created.
Mar 10 19:52:16 Artemis GEOM_ELI: Encryption: AES-XTS 256
Mar 10 19:52:16 Artemis GEOM_ELI:     Crypto: hardware
Mar 10 19:52:24 Artemis savecore: /dev/ada2p1: Operation not permitted
Mar 10 19:52:24 Artemis savecore: /dev/ada2p1: Operation not permitted
Mar 10 20:59:33 Artemis ZFS: vdev state changed, pool_guid=14519126106832416880 vdev_guid=14873538943975352029
Mar 10 20:59:33 Artemis ZFS: vdev state changed, pool_guid=14519126106832416880 vdev_guid=2170976084066480426
Mar 10 20:59:34 Artemis savecore: /dev/ada2p1: Operation not permitted
Mar 10 20:59:34 Artemis GEOM_ELI: Device ada2p1.eli destroyed.
Mar 10 20:59:34 Artemis GEOM_MIRROR: Device mirror/swap0 launched (2/2).
Mar 10 20:59:34 Artemis GEOM_ELI: Device mirror/swap0.eli created.
Mar 10 20:59:34 Artemis GEOM_ELI: Encryption: AES-XTS 128
Mar 10 20:59:34 Artemis GEOM_ELI:     Crypto: hardware

And I know that if this is a bug that I should probably report it. But the reason I made this post was to ask if this could do any harm and in general what I should do about it.

My FreeNAS server:
CPU: AMD FX-8350
MOBO: Gigabyte GA-970A-DS3P
HDD1: WD-WCC4M2UFH2D5
HDD2(NEW): WD-WX21AC9N7HL6

 

[dogsbodytech]

Also new to FreeNAS and just had exactly the same error on my 11.3-U1 system. This thread was the only reference on Google I could find.

Happy to share debug info but not quite sure what would be useful?

 

[raproter]

Also new to FreeNAS and just had exactly the same error on my 11.3-U1 system. This thread was the only reference on Google I could find.

Happy to share debug info but not quite sure what would be useful?

Yeah, I had the same thought. Don't really think it has something to do with us.

 

[CHL]

Same here when trying to replace a failed/missing disk but the resilver process is running and everything looks fine. Maybe just a bug in the UI?

Btw.: I have an encrypted pool. When to re-key the pool? It's not possible in 13.1-U1 during the resilver process because of an error complaining about the missing disk. After resilvering everything works as expected. But when and why to re-key? I'm still unsure about and had no time for testing.

 

[raproter]

Same here when trying to replace a failed/missing disk but the resilver process is running and everything looks fine. Maybe just a bug in the UI?

Btw.: I have an encrypted pool. When to re-key the pool? It's not possible in 13.1-U1 during the resilver process because of an error complaining about the missing disk. After resilvering everything works as expected. But when and why to re-key? I'm still unsure about and had no time for testing.

I too have an encrypted pool. Don't know if I ever tried to re-key the pool tho after resilvering. And I don't even know if I should try it because I don't want to lose my data.