Encrypted drive won't mount

[Tomo82]

Hi All,

I hope someone can help me, I am having multiple issues with Unraid at the moment, but the biggest one is suddenly my single drive array with zfs encryption will not mount. The message in the main tab is "Unmountable - volume not encrypted". Which is total BS. I created everything from scratch within Unraid, this is not imported from a foreign system or anything. The passphrase is accepted.
I searched and found some people reporting this and the message is generally "sucks to be you, format it". Is encryption so tempramental in Unraid? Because it seems like encryption is not recommended. If this is the case - then why offer it as an option?

And why is there no official support for Unraid? Normally when you pay for something the vender who took your money offers you support for it, this is especially true in the software world.

Anyway, mini-rant aside, can anyone help me fix it?

[Kilrah]

What did you do exactly? If you chose ZFS-encrypted in the GUI (ZFS in a LUKS volume) that is fine, if you used ZFS's own encryption from the command line that is not.

 

And supposing you're on 6.12RC if you're using ZFS, RCs are for testing and not stable for use. If not clarify.

Edited April 16, 2023 by Kilrah

[MrGrey]

13 hours ago, Tomo82 said:

the biggest one is suddenly my single drive array with zfs encryption

I only run "stable" 6.11.5... and I would never encrypt drives/volumes because/whatever.

 

Consider this post "bumped" because I want to and I think it should be.

 

MrGrey.

 

[JorgeB]

Please post the diagnostics.

[Tomo82]

Hi All,

Thank you your responses.
Yes I am on 6.12rc3, I was on rc2 so maybe the upgrade is what killed it. I will try to keep in mind the RC versions are betas. I am very eager to get Unraid working with a proper ZFS pool, maybe I'm toooo impatient 😄

@JorgeB Thank you, here are the diagnostics...

ungb-diagnostics-20230417-1133.zip

[JorgeB]

Are you sure disk1 was encrypted? Please post output of

blkid

 

[Tomo82]

Hi Jorge, this is the output:
 

root@UNGB:~# blkid
/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdf2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="4653481705694029441" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="0d701f1c-0ceb-43a3-80ae-3e233f4f960c"
/dev/nvme0n1p1: LABEL="Data" UUID="4425326131143143847" UUID_SUB="7980830101821951246" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="c4023445-40d6-4e80-bda6-490ed40292ce"
/dev/sdd2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="4014620395716939300" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="d0c86c4f-5222-415d-9d93-ea8f8aa48fee"
/dev/sdb2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="16148661145758674678" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="6e6dfbe8-3bec-48f3-ad4e-18631cd80eb0"
/dev/sdi2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="2371367520519899344" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="d1273b47-cf72-41c2-a638-2f53226e4177"
/dev/nvme2n1p1: LABEL="Data" UUID="4425326131143143847" UUID_SUB="11107764850259308245" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="96d66c53-3314-4ea7-bbae-34f5a5375a6f"
/dev/sdg2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="2181119398401058338" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="1787b7cb-f97a-4867-92d4-7d2ee1870031"
/dev/loop0: TYPE="squashfs"
/dev/sde2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="2653561897780408385" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="c06d4061-3a52-4521-9748-812482e60b7c"
/dev/sdc2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="11490087289074098495" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="da8b6e6b-1bd6-43a8-a211-4bc2baabcbf5"
/dev/nvme1n1p1: LABEL="disk1" UUID="677435318427908930" UUID_SUB="2878345105989975532" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="518dd946-cec7-47bb-b3fd-a8903cd7b5a4"
/dev/sdh2: LABEL="Data" UUID="4425326131143143847" UUID_SUB="1008136221314140058" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="16a8b497-07ff-4a53-9055-e7a919e30829"
/dev/md1p1: LABEL="disk1" UUID="677435318427908930" UUID_SUB="2878345105989975532" BLOCK_SIZE="4096" TYPE="zfs_member"
/dev/sdf1: PARTUUID="f14197b3-e7b4-4d56-a1de-0f1b368c2404"
/dev/sdd1: PARTUUID="62a7f470-dcd7-475e-aa56-7e51d2e81453"
/dev/sdb1: PARTUUID="fa190476-92a9-4a22-86f7-8738009f6050"
/dev/sdi1: PARTUUID="dd1f69c3-30b0-464b-9899-a559daf04563"
/dev/sdg1: PARTUUID="ad0d9f54-d177-4019-b9ba-21eaaf726993"
/dev/sde1: PARTUUID="51279591-c29a-4ac8-abda-cb87130f5737"
/dev/sdc1: PARTUUID="fa7d96b1-490b-42b2-9f79-d560ab009532"
/dev/sdh1: PARTUUID="49237ae0-dd30-468d-b3d3-ee0f46853926"

I have had to insert the passphrase for this drive many times, I have not removed the encryption so it should be still on it...

[Tomo82]

I just double checked and the gui will not let me start the array without entering a passphrase.

[JorgeB]

11 minutes ago, Tomo82 said:

I just double checked and the gui will not let me start the array without entering a passphrase.

That's because the fs is set to encrypted, but according to output above it's not, with the array stopped click on disk1, change fs to zfs (or auto) and start the array, if it doesn't mount post new diags.

[Tomo82]

That worked, thank you. But now I am questioning my sanity - could the upgrade to RC3 do that or is the only way this can happen through a user action(s) and I litterally forgot I did it?!

[JorgeB]

There were issues with rc2 and zfs encryption, so you might have though it was encrypted but it wasn't, you can now convert since those issues are fixed, but will need to backup and re-format.

[Tomo82]

@JorgeB Thanks for the info, on that note; I have a quick question - Is it better to roll back to the latest stable release and use the ZFS Plugin(s)? Would I have any problems importing/mounting a 2x4 wide RAIDZ1 pool with metadata and log special vdevs with some of the datasets encrypted?

[JorgeB]

5 minutes ago, Tomo82 said:

with some of the datasets encrypted?

Unraid doesn't currently support zfs native encryption, only LUKS whole device encryption.