• Wrong Detection of "protected" Share


    Hexenhammer
    • Minor

    Hello,

    Version: 6.11.5

    System has no parity drives at all.

     

    The green icon saying that "all files are on protected storage", but is Cache-Only share on RAID0

    Its the least protected there is

     

    image.thumb.png.f1b68be5d7f40fbb11e828e03a2983ed.png

     

    12700-diagnostics-20230104-0501.zip




    User Feedback

    Recommended Comments

    Just now, trurl said:

    How do you know that share isn't all on the array?

    1. This is cache Only Share

    2. Look at the other icons, when i took this image I had no parity [I still dont, i only 5 minutes ago added 2 drives as parity]

    3, This is Version: 6.11.5

     

    Link to comment
    14 minutes ago, Hexenhammer said:

    This is cache Only Share

    Which simply means write new files to the designated pool, and don't move any. Doesn't tell us anything about where current files are located.

    Link to comment
    2 minutes ago, trurl said:

    Which simply means write new files to the designated pool, and don't move any. Doesn't tell us anything about where current files are located.

    I uploaded what you asked

     

    The share is empty, has nothing, but I also dont have Parity, so how any share can be protected?

    All other shares have the Yellow symbol like they should,

    Link to comment
    1 minute ago, trurl said:

    What happens if you put something in the share?

     

    No change, still greenimage.thumb.png.e2f67a4cbca54d128ae0fbe44e750194.png

    Edited by Hexenhammer
    Link to comment

    Did you originally create that pool as raid0? Or did you create it as default raid1 then convert it to raid0?

    Link to comment

    I think i found the "bug", unRaid doesn't properly detect RAID0 and thinks its RAID1 or RAID5 [or whataver else]

     

    I have another RAID0, made from 4 SATA drives, i just created a new Cache only share and its also Green

     

    image.thumb.png.4aadadb6ad085c1a00dc68496a917172.png

    Link to comment
    Just now, trurl said:

    Did you originally create that pool as raid0? Or did you create it as default raid1 then convert it to raid0?

     

    Its RAID0 from before i created a share, but of course the default is RAID1, so i had to change to RAID0

    Share was created after

     

    See my other post this bug repeats for other RAID0

    Link to comment

    Yes, this is an issue. Obviously it's not a high priority one.

     

    Rationale is that by default any multi drive pool IS protected, and it takes a deliberate action to change that, and if you select RAID0 or single, you will know that the pool no longer is protected.

     

    It still needs to be fixed though.

    Link to comment
    9 minutes ago, JonathanM said:

    Yes, this is an issue. Obviously it's not a high priority one.

     

    Rationale is that by default any multi drive pool IS protected, and it takes a deliberate action to change that, and if you select RAID0 or single, you will know that the pool no longer is protected.

     

    It still needs to be fixed though.

     

    But isnt knowing what type of  pool it is, is just a simple command line?

    The fix can be just command that checks in the background when you open that page.

     

    Honestly its not an issue just an annoyance 

    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.