• Array contains 1 invalid disk (s) 6.5.1 RC6


    vanes
    • 6.5.1 Solved Annoyance

    Updated to Rc6, everything works fine, vm`s, dockers, but i see strange warning!

    All shares are on their places, fix common problems says that everything is good.

    Do I have to worry? Need parity check? Rebooted 2 times, warning is still here.

    wtf.jpg.b596af8529566a479fa239dd42f1d28c.jpg

    unraid-diagnostics-20180416-0001.zip

    • Upvote 1



    User Feedback

    Recommended Comments

    Good catch.  I never would have noticed on my system. 

     

    From my system:

     

    @limetech

    mdNumDisks="23"
    mdNumDisabled="1"
    mdNumInvalid="1"

    23 is correct (22 data + 1 parity).  Both disabled and Invalid though are incorrect.  I originally did play with Dual Parity, decided against it for various reasons.  Would've done a new config as what I was using for Parity 2 did get reused as a data drive.  A quick glance through other user's diags shows Parity 2 status as always being DISK_NP_DSBL when not installed.

     

    Link to comment
    6 minutes ago, chatman64 said:

     

    I have the same problem with 6.5.1 rc6> when I go back to 6.5 it is gone.

     

    rc6 shows a next scheduled date and time for parity check. This works fine for people having two 2 parity disks, but shows an error message instead for those with a single parity disk, which can be ignored.

     

    Edited by bonienl
    Link to comment
    19 minutes ago, Squid said:

    Good catch.  I never would have noticed on my system. 

     

    From my system:

     

    @limetech

    
    mdNumDisks="23"
    mdNumDisabled="1"
    mdNumInvalid="1"

    23 is correct (22 data + 1 parity).  Both disabled and Invalid though are incorrect.  I originally did play with Dual Parity, decided against it for various reasons.  Would've done a new config as what I was using for Parity 2 did get reused as a data drive.  A quick glance through other user's diags shows Parity 2 status as always being DISK_NP_DSBL when not installed.

     

     

    This is correct. A missing 2nd parity disk is seen as invalid. GUI should ignore this, but I overlooked this when adding the new parity info on the dashboard (I run a dual parity system obviously).

    Link to comment

    Yep I have the same with a single Parity Drive.

    I was looking for the next Parity check Scheduled and found it too. 

     

    I suppose I live until the next release. xD

    Link to comment

    Sorry for this inconvenience :(

     

    It is supposed to look like this

     

    image.thumb.png.dd26a2169fa8d4349c40883288a4be6e.png

    Edited by bonienl
    • Like 2
    Link to comment
    7 minutes ago, bonienl said:

    Sorry for this inconvenience :(

     

    Nah man You know we :x you!!!!!!!

     

    I was just riding on the giving you grief train. All these little refinements are so nice. unRAID has come a long long way and I have to admit I'm constantly finding little tweaks you've done that I think. "Man I never noticed that before, but it totally makes sense that its there."

     

    The little Text next to Start Parity and Start Mover that says (schedule). I think I've seen it many times and thought. Has it been here all along? Sometimes I'm a little slow. :$

     

    Thanks for posting up that image. I figured it went there. Nice!!!

    • Upvote 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.