• 6.12.0-rc2 - ZFS - encrypted results in "Unsupported or no file system".


    mituv85
    • Solved Minor

    I had some issues and asked for help on Discord. My issue did not get resolved and i ended up not going zfs. I want to post whatever i got here since someone mentioned it after i moved on.

    I run a completely new system with reinstalled USB.
    I tried to assign zfs - encryption to all drives. All gives the "Unmountable: Unsupported or no file system".
    I tried restarting, taking array off an on, Unassigned Devices plugin and pressed the red x to remove partitions, doing it all again in every different way. Nothing worked so i ended up going with xfs and btrfs.
    Here's the log for one of the drives it tried to fromat and mount.
     

    Mar 26 09:02:33 Boxen kernel: mdcmd (36): nocheck pause
    Mar 26 09:02:35 Boxen emhttpd: creating volume: disk1 (zfs - encrypted)
    Mar 26 09:02:35 Boxen emhttpd: shcmd (281): /sbin/wipefs -a /dev/sdc
    Mar 26 09:02:36 Boxen root: /dev/sdc: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
    Mar 26 09:02:36 Boxen root: /dev/sdc: 8 bytes were erased at offset 0x3a3817d5e00 (gpt): 45 46 49 20 50 41 52 54
    Mar 26 09:02:36 Boxen root: /dev/sdc: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
    Mar 26 09:02:36 Boxen root: /dev/sdc: calling ioctl to re-read partition table: Success
    Mar 26 09:02:36 Boxen emhttpd: writing GPT on disk (sdc), with partition 1 byte offset 32KiB, erased: 0
    Mar 26 09:02:36 Boxen emhttpd: shcmd (282): sgdisk -Z /dev/sdc
    Mar 26 09:02:37 Boxen root: Creating new GPT entries in memory.
    Mar 26 09:02:37 Boxen root: GPT data structures destroyed! You may now partition the disk using fdisk or
    Mar 26 09:02:37 Boxen root: other utilities.
    Mar 26 09:02:37 Boxen emhttpd: shcmd (283): sgdisk -o -a 8 -n 1:32K:0 /dev/sdc
    Mar 26 09:02:38 Boxen root: Creating new GPT entries in memory.
    Mar 26 09:02:38 Boxen root: The operation has completed successfully.
    Mar 26 09:02:38 Boxen kernel: sdc: sdc1
    Mar 26 09:02:38 Boxen emhttpd: shcmd (284): udevadm settle
    Mar 26 09:02:38 Boxen emhttpd: shcmd (285): /usr/sbin/cryptsetup luksClose md1p1
    Mar 26 09:02:38 Boxen emhttpd: shcmd (287): /usr/sbin/cryptsetup luksFormat /dev/md1p1
    Mar 26 09:02:44 Boxen emhttpd: shcmd (290): /usr/sbin/cryptsetup luksOpen /dev/md1p1 md1p1 
    Mar 26 09:02:47 Boxen emhttpd: shcmd (291): modprobe zfs
    Mar 26 09:02:47 Boxen emhttpd: shcmd (292): /usr/sbin/zpool create -f -o ashift=12 -o autotrim=off -O compression=off -O dnodesize=auto -O acltype=posixacl -O xattr=sa -O normalization=formD -m /mnt/disk1 disk1 /dev/mapper/md1p1
    Mar 26 09:02:47 Boxen emhttpd: shcmd (293): /usr/sbin/zpool export disk1
    Mar 26 09:02:47 Boxen emhttpd: mounting /mnt/disk1
    Mar 26 09:02:47 Boxen emhttpd: shcmd (294): mkdir -p /mnt/disk1
    Mar 26 09:02:47 Boxen emhttpd: shcmd (295): modprobe zfs
    Mar 26 09:02:47 Boxen emhttpd: /usr/sbin/zpool import -d /dev/mapper/md1p1 2>&1
    Mar 26 09:02:47 Boxen emhttpd:    pool: disk1
    Mar 26 09:02:47 Boxen emhttpd:      id: 6556196458859304560
    Mar 26 09:02:47 Boxen emhttpd: shcmd (296): /usr/sbin/zpool import -N -o autoexpand=on  -d /dev/mapper/md1p1 6556196458859304560 disk1
    Mar 26 09:02:48 Boxen emhttpd: shcmd (297): /usr/sbin/zpool online -e disk1 /dev/mapper/md1p1
    Mar 26 09:02:48 Boxen emhttpd: /usr/sbin/zpool status -LP disk1 2>&1
    Mar 26 09:02:48 Boxen emhttpd:   pool: disk1
    Mar 26 09:02:48 Boxen emhttpd:  state: ONLINE
    Mar 26 09:02:48 Boxen emhttpd: config:
    Mar 26 09:02:48 Boxen emhttpd:  NAME         STATE     READ WRITE CKSUM
    Mar 26 09:02:48 Boxen emhttpd:  disk1        ONLINE       0     0     0
    Mar 26 09:02:48 Boxen emhttpd:    /dev/dm-0  ONLINE       0     0     0
    Mar 26 09:02:48 Boxen emhttpd: errors: No known data errors
    Mar 26 09:02:48 Boxen emhttpd: disk1: invalid config: 0 1
    Mar 26 09:02:48 Boxen emhttpd: shcmd (298): /usr/sbin/zpool export disk1
    Mar 26 09:02:48 Boxen emhttpd: /mnt/disk1 mount error: Unsupported or no file system
    Mar 26 09:02:48 Boxen emhttpd: shcmd (299): rmdir /mnt/disk1


     

    • Like 1



    User Feedback

    Recommended Comments

    zfs encryption is not working properly in rc2, this is a known issue and is solved in the next release.

    For the time being use plain zfs.

     

    • Like 1
    Link to comment

    If i use plain zfs, can i just run on encryption or do i have to move data back and forth because of formatting drives will be a must?

    Link to comment

    Whenever you change file system, including encryption, the device needs to be formatted, which wipes all content.

     

    If you intend to use encryption, you might be better of waiting for rc3 and use it correctly from the start without the need to copy and restore your data.

     

    Link to comment

    i ran into similar issues when attempting to create a ZFS Encrypted cache pool, 2 NVMe, mirrored. I have diagnostics logs, but it sounds like those aren't needed. Thanks for all your work on Unraid, im excited to use ZFS when encryption is ready!

    Link to comment
    5 hours ago, JorgeB said:

    This should be fixed on rc3.

    To be clear, will pools created with encryption in RC2 begin working in RC3, or will I need to reformat? I had a 7 drive zpool with encryption working great until I had rebooted, ultimately getting the same error as OP.

    Link to comment

    Should not have to reformat, and for now click on the first pool device and make sure fs it's set to zfs-encrypred, that might solve one of the current bugs.

    Link to comment
    On 4/1/2023 at 2:16 AM, JorgeB said:

    Should not have to reformat, and for now click on the first pool device and make sure fs it's set to zfs-encrypred, that might solve one of the current bugs.

    image.thumb.png.de036ad5eecc831cc6ee6d545fb06551.pngimage.thumb.png.c3998151aa7fb59593779348489d217d.pngDoesn't seem to have fixed it. I deleted the pool and remade it with the same settings and same issue. Should I just wait for RC3 or is my issue different? Can upload diagnostics if helpful. 

    Link to comment
    16 hours ago, doubley said:

    Doesn't seem to have fixed it

    Sorry, was talking about a different issue, that can happen after a new config, you will need to wait for rc3.

    • Like 1
    Link to comment
    On 4/17/2023 at 9:37 AM, JorgeB said:

    Should be, but depending on what you did with rc2 you might need to change the fs for the disks/pools manually, please post the diagnostics.

    I upgraded to rc2, stopped the array to set one of the disks to ZFS - encrypted. -> didn't work for said reason. I restored back to 6.11.5 and waited for rc3.

     

    I now did the same again, updated to rc3. Tried to format to ZFS - encrypted -> didnt work.

    Then I tried creating a ZFS non-ecrypted filesystem. This worked without issue for me. Then I set the disk back to ZFS - encrypted -> didn't work. Then I emptied another disk and set it to ZFS - encrypted. -> didn't work aswell.

     

    I've attached my diagnostics.

    nas01-diagnostics-20230420-0148.zip

    Link to comment
    10 hours ago, Akilae said:

    I now did the same again, updated to rc3. Tried to format to ZFS - encrypted -> didnt work.

    Then I tried creating a ZFS non-ecrypted filesystem. This worked without issue for me. Then I set the disk back to ZFS - encrypted -> didn't work. Then I emptied another disk and set it to ZFS - encrypted. -> didn't work aswell.

     

    I cannot reproduce this, since you are using a keyfile, are you by any chance deleting the keyfile manually or automatically after array start?

     

    Only by doing that can I reproduce your issue.

     

     

    • Thanks 1
    Link to comment

    Ah, this makes absolute sense. Yes, I have a running script which is getting the keyfile from a SMB share (which is currently not active), but the deletion script is still running.

     

    Thank you for pointing me in the right direction. It works now.

    • Like 1
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.