Project

General

Profile

Bug #7424

geli: Provider zvol/mypool/gelizvol is invalid

Added by Himan Zero over 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
-
Category:
-
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I used to follow the section "18.12. Encrypting Disk Partitions" in the FreeBSD documents to create a geli encrypted zvol in my FreeNAS server under FreeNAS version 9.2.1.5. It worked fine. But someday, when I upgraded the system to 9.2.1.8, I suddenly found I could not attach the encrypted zvol anymore. Whatever I do, system shows the following message:

geli: Provider zvol/mypool/gelizvol is invalid.

I can replay the error in following steps under version 9.3 stable:

(Suppose my zpool is named as 'mypool' and I have created a zvol namely 'gelizvol'.)
Step one - initialize geli on gelizvol:

sudo geli init /dev/zvol/mypool/gelizvol

(For easy demonstration,I just press Enter twice to give a blank password)

Step two - attach the gelizvol

sudo geli attach zvol/mypool/gelizvol

(press Enter to give a blank password)

Then the system shows the error message:

geli: Provider zvol/mypool/gelizvol is invalid.

I have tried many times in 9.2.1.5 and such operation will complete without error but when I go back to the newer version, I constantly get such error message and cannot get my geli encrypted zvol back.

I'm not sure whether this is a bug or I have missed something.

History

#1 Updated by Josh Paetzel over 5 years ago

  • Status changed from Unscreened to Screened

We set volmode=2 in 9.2.1.8 in /boot/loader.conf

That is what is harshing your gig. Change it to 1 and you should be set.

I'm on my phone, the exact tunable is not volmode.

#2 Updated by Himan Zero over 5 years ago

Thanks Josh. If that's not an option in the new version, is there any workaround for me to get back my data under 9.3 instead of falling back to 9.2.1.5? I've tried to set vfs.zfs.vol.mode to 1 in the tunable in GUI but after reset, the system cannot boot successfully.

Josh Paetzel wrote:

We set volmode=2 in 9.2.1.8 in /boot/loader.conf

That is what is harshing your gig. Change it to 1 and you should be set.

I'm on my phone, the exact tunable is not volmode.

#3 Updated by Josh Paetzel over 5 years ago

Alexander just fixed a kernel panic when setting the volmode to 1. Not sure if it's made it to an SU yet. I think not. It should be fixed in the nightly train. Otherwise wait for the next SU.

#4 Updated by Jordan Hubbard over 5 years ago

  • Status changed from Screened to Resolved
  • Target version set to Unspecified

It's in the current SU. Please update and try this again.

#5 Updated by Himan Zero over 5 years ago

Yes, it's resolved perfectly by the SU today. No kernel panic anymore to set sysctl vfs.zfs.vol.mode=1. I have successfully get back my data. Big thanks to the team!

#6 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Target version changed from Unspecified to N/A

Also available in: Atom PDF