• [6.12.6] Parity Check (tuning) schedule won't do correction

    sonic6

    By sonic6

      • Minor

    A Parity Check, with enabled "corrections" will start as a "Non-Correcting Parity-Check":

     

    image.thumb.png.7b10f81d6be1f96c66f7bc28e41196f6.png

     

    image.thumb.png.8bc2a688ee88fb42061668e3e651a8f2.png

     

    image.thumb.png.8721797ce25cb61962634f03cb9a615b.png

      

    Jan  2 00:00:07 Unraid-1 kernel: mdcmd (62): check NOCORRECT
Jan  2 00:00:07 Unraid-1 kernel: 
Jan  2 00:00:07 Unraid-1 kernel: md: recovery thread: check P ...
[...]
Jan  2 00:00:14 Unraid-1 Plugin Auto Update: Community Applications Plugin Auto Update finished
Jan  2 00:00:17 Unraid-1 Parity Check Tuning: Scheduled Non-Correcting Parity-Check finished (0 errors)
Jan  2 00:00:17 Unraid-1 Parity Check Tuning: Elapsed Time 10 sec, Runtime 10 sec, Increments 1, Average Speed 1.0 TB/s
Jan  2 00:00:17 Unraid-1 Parity Check Tuning: Send notification: Scheduled Non-Correcting Parity-Check finished (0 errors): Elapsed Time 10 sec, Runtime 10 sec, Increments 1, Average Speed 1.0 TB/s (type=normal link=/Settings/Scheduler)
[...]
Jan  2 00:17:35 Unraid-1 Parity Check Tuning: Manual Non-Correcting Parity-Check: Manually resumed
[...]
Jan  2 01:41:34 Unraid-1 kernel: md: recovery thread: P incorrect, sector=2353004440
Jan  2 01:41:34 Unraid-1 kernel: md: recovery thread: P incorrect, sector=2353004472

     

    idk why the parity checks stopps after 10 seconds and starts again by the plugin, but in log you can see, that the inital start was a "non-correction" one.

    unraid-1-diagnostics-20240102-0938.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    ChatNoir

    Parity check tuning is a third party plugin, not part of base Unraid.

    Have you tried without the plugin to ensure that it is indeed an Unraid issue ?

    Link to comment
    sonic6

    sonic6 156

    Posted (edited)

    6 minutes ago, ChatNoir said:

    Parity check tuning is a third party plugin, not part of base Unraid.

    i know, but the parity check was triggert by the default unraid parity check schedule and this : 

    Jan  2 00:00:07 Unraid-1 kernel: mdcmd (62): check NOCORRECT
Jan  2 00:00:07 Unraid-1 kernel: 
Jan  2 00:00:07 Unraid-1 kernel: md: recovery thread: check P ...

    isn't a part of parity-check tuning

     

    6 minutes ago, ChatNoir said:

    Have you tried without the plugin to ensure that it is indeed an Unraid issue ?

    no, not yet.

    Edited by sonic6
    Link to comment
    sonic6

    @bonienl @JorgeB

     

    50 minutes ago, ChatNoir said:

    Have you tried without the plugin to ensure that it is indeed an Unraid issue ?

    i tried this again at 11:00 without the plugin:

     

    image.thumb.png.ee5256406e176fffec3ef9a5086c1581.png

      

    Jan  2 11:00:02 Unraid-1 kernel: mdcmd (69): check NOCORRECT
Jan  2 11:00:02 Unraid-1 kernel: 
Jan  2 11:00:02 Unraid-1 kernel: md: recovery thread: check P ...

     

    Diagnostic is attached.

     

    unraid-1-diagnostics-20240102-1104.zip

    Link to comment
    ChatNoir
    10 minutes ago, sonic6 said:

    i tried this again at 11:00 without the plugin

    Perfect, thanks. :) 

    • Like 1
    Link to comment
    itimpi

    The Parity Check Tuning plugin would not have initiated the check.

     

    The only reason I can think of for it trying to resume is that there was some unexpected state information found in the plugins folder on the flash drive.   It might be useful if a listing of the files that are there could be given as that could provide a clue as to what that might be.   In addition the contents of any "progress" type files that are there.

    Link to comment
    itimpi

    While I think of it we normally recommended that scheduled parity checks are set to be non-correcting.   The rationale being that if you have a drive playing up you do not want to run a correcting check that might corrupt parity and reduce the chances of a clean data recovery.

    Link to comment
    sonic6
    5 hours ago, itimpi said:

    The Parity Check Tuning plugin would not have initiated the check.

    I said the same. 

     

    4 hours ago, itimpi said:

    While I think of it we normally recommended that scheduled parity checks are set to be non-correcting.

    Fine, but when I choose a correction for m schedule, than it should do that.

     

    On my last test from 11:00 the parity check tuning plugin wasn't installed. 

    Link to comment
    sonic6
    22 hours ago, itimpi said:

    It might be useful if a listing of the files that are there could be given as that could provide a clue as to what that might be.   In addition the contents of any "progress" type files that are there.

    what is the recommendes way to do this?

    Link to comment
    itimpi
    On 1/3/2024 at 9:36 AM, sonic6 said:

    what is the recommendes way to do this?

    If you have the Dynamix File Manager plugin installed then you can navigate to the plugins folder on the flash drive  /boot/config/plugins/parity.check.tuning/ to get a file listing.

    Link to comment
    sonic6

    sonic6 156

    Posted (edited)

    6 minutes ago, itimpi said:

    If you have the Dynamix File Manager plugin installed then you can navigate to the plugins folder on the flash drive  /boot/config/plugins/parity.check.tuning/ to get a file listing.

    okay, there any files: 

    root@Unraid-1:~# ls -la /boot/config/plugins/parity.check.tuning/
/bin/ls: cannot access '/boot/config/plugins/parity.check.tuning/': No such file or directory

    image.png.5609ddaa3e96f3b399652875801a77b3.png

    Edited by sonic6
    Link to comment
    itimpi
    3 hours ago, sonic6 said:

    Any news on this? Problem is still present.

    I assume that we will need to wait for a new Unraid release before this problem can be fixed.   I have seen suggestions that 6.12.7 might be imminent.

     

    14 minutes ago, sonic6 said:

    okay, there any files: 

    root@Unraid-1:~# ls -la /boot/config/plugins/parity.check.tuning/
/bin/ls: cannot access '/boot/config/plugins/parity.check.tuning/': No such file or directory

    image.png.5609ddaa3e96f3b399652875801a77b3.png

    That would be expected if you have uninstalled the plugin as you mentioned earlier?   That folder should always be there if the plugin is installed.

    • Thanks 1
    Link to comment
    sonic6
    2 minutes ago, itimpi said:

    That would be expected if you have uninstalled the plugin as mentioned earlier?   

     

    yes, like i said here:

    On 1/2/2024 at 11:04 AM, sonic6 said:

    @bonienl @JorgeB

     

    On 1/2/2024 at 10:12 AM, ChatNoir said:

    Have you tried without the plugin to ensure that it is indeed an Unraid issue ?

    i tried this again at 11:00 without the plugin:

     

    Link to comment
    JorgeB

    It's a bug, though not really a serious one, since scheduled checks should IMHO be always non correcting anyway, but LT is aware of the issue and it should be fixed soon.

    • Thanks 1
    Link to comment
    sonic6
    On 1/27/2024 at 12:28 PM, JorgeB said:

    but LT is aware of the issue and it should be fixed soon.

    Bug is still present on 6.12.9

     

    image.png.b9f0b0ea98d91f8373b2f52c986c54bf.png

    image.png.065e5b5590fe8073376ffbbd375fdcbf.png

    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.