Jump to content
  • [6.7.0] Unable to start xfs array if xfs-encrypted is set as default filesystem


    woocash
    • Minor

    Problem description:

    Unable to manually start array. Automatic start after reboot works ok. All drives are unencrypted (xfs)

     

    Visual manifestation of the problem:

    After stopping array manually, the START button on Main screen greyed out, input field below it asks for passphrase, even though there are no encrypted drives in the system.

     

    Temporary solution:

    Set "Default file system" in Settings > Disk Settings to "xfs" instead of "xfs-encrypted"

     

    Proposed solution:

    Connect asking for array disk passphrase in the GUI with at least one drive having an encrypted filesystem, not with default settings.



    User Feedback

    Recommended Comments

    No, the current implementation is correct.

     

    When you change the default file system, it means any NEW disk will get the selected file system.

    Existing disks keep their current file system.

    In order to use encryption for any new disks (which may or may not be present) it will ask to enter a passphrase (and confirmation if it is the first time).

     

    Share this comment


    Link to comment
    Share on other sites

    Correct, so is it sensible to disable array start without an explanation, ask for a non existing password, if no new disk has been added, the existing ones are unencrypted, and there is no use for the password you are asking for?

     

    If so, what would happen if i provided the password, before starting the array?

    Share this comment


    Link to comment
    Share on other sites

    Nothing will happen with the existing disks.

     

    On second thought, a check could be added to see if any encrypted disks are present.

    Need @limetech to confirm, because there are some caveats / limitations when encryption is used (and detected).

    Share this comment


    Link to comment
    Share on other sites
    8 minutes ago, bonienl said:

    Nothing will happen with the existing disks.

    OK! Great to have it confirmed that no data loss would occur in case the passphrase is provided accidentally.

    Edited by woocash

    Share this comment


    Link to comment
    Share on other sites
    52 minutes ago, bonienl said:

    Nothing will happen with the existing disks.

     

    On second thought, a check could be added to see if any encrypted disks are present.

    Need @limetech to confirm, because there are some caveats / limitations when encryption is used (and detected).

     

    Right, interesting corner case: no encrypted disks exist, no new disks exist, and default file system type set to one of the encrypted forms - the fact it wants a passphrase is a bug.  Providing one does no harm (one workaround), setting default file system type to an unencrypted form is another workaround.

    Thanks for reporting, we'll look into it.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites


    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.