Geli encrypted drive list not updated correctly when drive is replaced

[flami]

Hi there,

First things first: I only tried this on 8.3.1 and I really don't want to test it on any newer version
This might be what https://bugs.freenas.org/issues/2178 is talking about.

After I replaced a failing drive in my pool everything worked fine after the resilvering, but for some reason I could not create a recovery key. I kinda forgot about the issue for a few months until I wanted to upgrade this box.

Geli complains that it can not access a certain gptid/7edf... which is the drive I replaced. This id does no longer appear in the storage_disk table of the sqlite database, however it is still present in storage_encryteddisk where the new disk was just added to the end.

I fixed the issue by manually deleting the old record and then uploading the config again, at which point I could create a recovery key again.

So I changed the table from

Code:

"id","encrypted_volume_id","encrypted_disk_id","encrypted_provider"
[...]
"5","1","5","gptid/7e8e..."
"6","1","6","gptid/7edf..."
"7","1","6","gptid/ed91..."

to

Code:

"id","encrypted_volume_id","encrypted_disk_id","encrypted_provider"
[...]
"5","1","5","gptid/7e8e..."
"6","1","6","gptid/ed91..."

Now I don't know if that has been fixed in newer versions and I hope I don't have to test it, but if this is still how Freenas behaves, I think we got a bug. Anyone able to test this?

Greetings,
flami

 

[Dusan]

This is fixed in 9.1.1: https://github.com/freenas/freenas/commit/e29f266cb1f765e1f86f0fac89fd964f9d0180dc

 

[flami]

great , of course my drive had to fail before I upgraded

 

[cyberjock]

That is exactly what 2178 is about. I found that bug and I actually created a thread with step-by-step directions for what you did. :P