Jump to content

  • Parity check when array is "unprotected"

    madshi

    By madshi

      • Closed

    This happened with 6.3.5. I'm sorry, I'm not going to upgrade unRAID while my array is in unprotected state, so I can only report this issue with 6.3.5.

     

    I've had a power outage. After booting up, one disk was dead. I started the array, nevertheless. The missing disk is now being "emulated", which is nice. However, unRAID insisted on doing a full Parity check. Which makes no sense, whatsoever. I only have 1 Parity disk, and with one disk missing it means that a Parity check can't possible do any good. So unRAID shouldn't insist on doing a Parity check. Maybe unRAID should even disable the option to run a Parity check manually?

     

    Should be easy for you guys to check if this was already fixed in the latest unRAID build or not.

     

    It's not a dramatic problem, but it's more than an "Annoyance", because any disk accesses while the array is unprotected is "dangerous". So insisting on doing a useless full Parity check in this situation is a really bad idea, IMHO.

    Go to reports Stable Releases

    User Feedback

    Recommended Comments



    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.

×
×
  • Create New...