Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Errors on scheduled parity check

Ruato
in General Support

Featured Replies

It has been years without any major problem. Now, with a scheduled parity check I got 13563 errors. The reason might an incident where the server crashed because it run out of memory (a docker container was the culprit).

I checked that the array disks are not reporting any errors. What should I do next? Run another parity check without correcting to check that the report is valid or run a parity check with parity drive correcting enabled?

Is the most probable issue / cause for parity errors that because of the crash the parity drives have not been correctly updated but the data drives and files are OK. Or is it impossible to say or even say anything about probabilities? That is, I am wondering how probable it is that I have lost something valuable.

Thank you for any help!

Here are the related lines from the log:

Feb  2 03:30:01 Tower kernel: mdcmd (38): check NOCORRECT
Feb  2 03:30:01 Tower kernel: md: recovery thread: check P Q ...
Feb  3 01:30:01 Tower kernel: mdcmd (39): nocheck pause
Feb  3 01:30:01 Tower kernel: md: recovery thread: exit status: -4
Feb  3 03:30:01 Tower kernel: mdcmd (40): check resume
Feb  3 03:30:01 Tower kernel: md: recovery thread: check P Q ...
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911280
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911288
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911296
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911304
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911312
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911320
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911328
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911336
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911344
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911352
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911360
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911368
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911376
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911384
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911392
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911400
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911408
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911416
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911424
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911432
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911440
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911448
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911456
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911464
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911472
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911480
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911488
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911496
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911504
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911512
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911520
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911528
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911536
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911544
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911552
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911560
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911568
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911576
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911584
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911592
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911600
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911608
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911616
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911624
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911632
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911640
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911648
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911656
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911664
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911672
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911680
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911688
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911696
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911704
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911712
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911720
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911728
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911736
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911744
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911752
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911760
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911768
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911776
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911784
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911792
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911800
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911808
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911816
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911824
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911832
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911840
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911848
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911856
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911864
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911872
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911880
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911888
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911896
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911904
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911912
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911920
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911928
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911936
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911944
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911952
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911960
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911968
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911976
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911984
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543911992
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912000
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912008
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912016
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912024
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912032
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912040
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912048
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912056
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912064
Feb  3 07:40:41 Tower kernel: md: recovery thread: PQ incorrect, sector=24543912072
Feb  3 07:40:41 Tower kernel: md: recovery thread: stopped logging
Feb  4 01:30:01 Tower kernel: mdcmd (41): nocheck pause
Feb  4 01:30:01 Tower kernel: md: recovery thread: exit status: -4
Feb  4 03:30:01 Tower kernel: mdcmd (42): check resume
Feb  4 03:30:01 Tower kernel: md: recovery thread: check P Q ...
Feb  4 18:04:58 Tower kernel: md: sync done. time=52497sec
Feb  4 18:04:58 Tower kernel: md: recovery thread: exit status: 0
  • Quote

    • Solved by JorgeB

    Go to solution
    • Community Expert
    • Solution

    If there was an unclean shutdown, some sync errors are expected; run a correcting check.

  • Quote
    • Thanks 1

    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
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.