• Completed parity check not recognized after dirty shutdown


    CS01-HS
    • Annoyance
    1. Force a dirty shutdown and consequent parity check on startup
    2. Let parity check complete
    3. Stop array

     

    If you start the array you're forced to run a parity check because the completed run's not recognized.

     

    Reboot gets around it.




    User Feedback

    Recommended Comments

    I thought the error might have been legitimate until I rebooted and it went away.

     

    Are the post-reboot diagnostics useful? If they are let me know and I'll upload them.

     

    EDIT: Looks like I changed the bug status. Sorry about that, not sure what I changed it from.

    Edited by CS01-HS
    Link to comment
    23 minutes ago, CS01-HS said:

    Are the post-reboot diagnostics useful?

    Syslog resets on reboot, and that is where we would look for evidence. Unless you also have Syslog Server setup to preserve syslogs

    Link to comment
    2 hours ago, trurl said:

    Syslog resets on reboot, and that is where we would look for evidence. Unless you also have Syslog Server setup to preserve syslogs

    I do. Diagnostics and saved syslog attached.

     

    Parity check

    starts: 06-11-2020 07:35

    finishes: 06-11-2020 21:01

     

    You'll notice a lot of BTRFS messages. What caused the dirty shutdown was a system freeze while running rebalance.

     

    syslog-10.0.1.50.log.zip nas-diagnostics-20201107-1753.zip

    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.