• All drives are spun down during parity causing errors


    Auggie
    • Urgent

    I noticed this sometime ago, but I wasn't sure exactly what was happening.  About a month ago I noticed 128 errors after a parity check was completed but saw it only after a week or so had already passed.  All SMART reports were good.  I ran my monthly parity check several days ago and the exact same number of 128 errors occurred.  All SMART reports were again good with zero anomalies on all drives.  The syslog showed a spin down an hour or so after parity check was started (FYI, my disk settings are set to spin down after an hour) and that's when the read I/O errors occurred (specifically involving only three drives at that time).

     

    After performing an XFS repair on the three drives with zero issues, I again ran the parity last night.  This morning, I noted in the syslog that again an hour after parity check was initiated, UnRAID spun down ALL drives and soon thereafter I/O errors on ALL drives were reported.  Two hours later, again UnRAID spun down ALL drives and I/O errors started.

     

    This appears to be a UnRAID 6.7 bug wherein it's incorrectly spinning down drives that may be physically I/O active.  I don't believe its hardware related as I've had this particular motherboard/chassis (SuperMicro X11SPH/Chenbro 48-bay RM43348) combination running for over six months now and never experienced anything like this before.

     

    Attached is my syslog (FYI, the parity check is still in progress and although there were numerous I/O errors, the parity check has reported ZERO errors thus far).

    syslog.txt




    User Feedback

    Recommended Comments

    I should add that I'm not seeing this issue with my other UnRAID NAS, which uses an older X9SCM motherboard with one SuperMicro AOC-SAS2LP HBA, one LSI 9211-8i (IT Mode) HBA, and one IBM M1015 (IT Mode) HBA.

     

    The X11 setup has built-in SAS3 3008 chip (IT Mode) connected to the Chenbro's built-in SAS expanders so the latest UnRAID version appears to have an issue with this setup.

    Edited by Auggie
    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.