mik Posted August 4, 2017 Share Posted August 4, 2017 (edited) hey, i just had a power outage (a scheduled correcting parity check was running). I booted the server and started a noncorecting parity check. 10% done and I have over 600 Sync errors detected. Should I be conserd that my data is corrupted. I check the files I was working on just before the power went and they all look fine. What should I do when the noncorrecting parity check is completed? I am running version 6.3.5 with a 6TB parity drive and 1TB 2TB 3TB storage drives. syslog: Aug 4 19:05:46 minpc kernel: mdcmd (42): check nocorrect Aug 4 19:05:46 minpc kernel: md: recovery thread: check P ... Aug 4 19:05:46 minpc kernel: md: using 1536k window, over a total of 5860522532 blocks. Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=0 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=96 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=112 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=320 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=1848 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=1856 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=2440 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=60296 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=60304 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=77648 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=77656 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=77664 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=129920 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=130456 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=130496 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=131088 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=132608 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=153824 Aug 4 19:05:46 minpc kernel: md: recovery thread: P incorrect, sector=153832 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=392800 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=394208 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=394240 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=394248 Aug 4 19:05:47 minpc kernel: md: recovery thread: P incorrect, sector=448536 Aug 4 19:05:52 minpc kernel: md: recovery thread: P incorrect, sector=1987240 Aug 4 19:05:53 minpc kernel: md: recovery thread: P incorrect, sector=2371488 Aug 4 19:05:53 minpc kernel: md: recovery thread: P incorrect, sector=2371504 Aug 4 19:06:00 minpc kernel: md: recovery thread: P incorrect, sector=4756008 Aug 4 19:06:13 minpc kernel: md: recovery thread: P incorrect, sector=9330152 Aug 4 19:06:15 minpc kernel: md: recovery thread: P incorrect, sector=10079688 Aug 4 19:06:15 minpc kernel: md: recovery thread: P incorrect, sector=10079696 Aug 4 19:06:16 minpc kernel: md: recovery thread: P incorrect, sector=10231672 Aug 4 19:08:33 minpc kernel: md: recovery thread: P incorrect, sector=58813000 Aug 4 19:08:33 minpc kernel: md: recovery thread: P incorrect, sector=58813048 Aug 4 19:09:09 minpc kernel: md: recovery thread: P incorrect, sector=71848016 Aug 4 19:09:10 minpc kernel: md: recovery thread: P incorrect, sector=71934032 Aug 4 19:09:10 minpc kernel: md: recovery thread: P incorrect, sector=71936672 Aug 4 19:09:10 minpc kernel: md: recovery thread: P incorrect, sector=71946752 Aug 4 19:10:10 minpc kernel: md: recovery thread: P incorrect, sector=93504336 Aug 4 19:10:22 minpc kernel: md: recovery thread: P incorrect, sector=97560096 Aug 4 19:10:22 minpc kernel: md: recovery thread: P incorrect, sector=97560104 Aug 4 19:10:22 minpc kernel: md: recovery thread: P incorrect, sector=97560112 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97884536 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97900512 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97900520 Aug 4 19:10:23 minpc kernel: md: recovery thread: P incorrect, sector=97900528 Aug 4 19:10:24 minpc kernel: md: recovery thread: P incorrect, sector=98503536 Aug 4 19:10:38 minpc kernel: md: recovery thread: P incorrect, sector=103401392 Aug 4 19:10:38 minpc kernel: md: recovery thread: P incorrect, sector=103401400 Aug 4 19:10:38 minpc kernel: md: recovery thread: P incorrect, sector=103457040 Aug 4 19:10:45 minpc kernel: md: recovery thread: P incorrect, sector=106048656 Aug 4 19:11:18 minpc kernel: md: recovery thread: P incorrect, sector=117445056 Aug 4 19:11:18 minpc kernel: md: recovery thread: P incorrect, sector=117445096 Aug 4 19:11:18 minpc kernel: md: recovery thread: P incorrect, sector=117445104 Aug 4 19:11:19 minpc kernel: md: recovery thread: P incorrect, sector=117831432 Aug 4 19:11:19 minpc kernel: md: recovery thread: P incorrect, sector=117831440 Aug 4 19:11:20 minpc kernel: md: recovery thread: P incorrect, sector=118275696 Aug 4 19:11:20 minpc kernel: md: recovery thread: P incorrect, sector=118275704 Aug 4 19:11:23 minpc kernel: md: recovery thread: P incorrect, sector=119416120 Aug 4 19:11:29 minpc kernel: md: recovery thread: P incorrect, sector=121564472 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124089920 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124106304 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124106336 Aug 4 19:11:36 minpc kernel: md: recovery thread: P incorrect, sector=124106344 Aug 4 19:11:37 minpc kernel: md: recovery thread: P incorrect, sector=124262224 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128909064 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128909072 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128909080 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=128915032 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=129106816 Aug 4 19:11:50 minpc kernel: md: recovery thread: P incorrect, sector=129106856 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130426272 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130426360 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130500952 Aug 4 19:11:54 minpc kernel: md: recovery thread: P incorrect, sector=130501128 Aug 4 19:11:55 minpc kernel: md: recovery thread: P incorrect, sector=130597080 Aug 4 19:12:13 minpc kernel: md: recovery thread: P incorrect, sector=136882824 Aug 4 19:12:13 minpc kernel: md: recovery thread: P incorrect, sector=136882832 Aug 4 19:12:13 minpc kernel: md: recovery thread: P incorrect, sector=137001880 Aug 4 19:24:10 minpc kernel: md: recovery thread: P incorrect, sector=381521488 Aug 4 19:24:10 minpc kernel: md: recovery thread: P incorrect, sector=381521496 Aug 4 19:24:10 minpc kernel: md: recovery thread: P incorrect, sector=381645464 Aug 4 19:24:13 minpc kernel: md: recovery thread: P incorrect, sector=382585696 Aug 4 19:24:16 minpc kernel: md: recovery thread: P incorrect, sector=383529584 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413368 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413376 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413544 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413552 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384413560 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727968 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727976 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727984 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384727992 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728000 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728008 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728016 Aug 4 19:24:19 minpc kernel: md: recovery thread: P incorrect, sector=384728024 Aug 4 19:24:21 minpc kernel: md: recovery thread: P incorrect, sector=385316928 Aug 4 19:24:21 minpc kernel: md: recovery thread: P incorrect, sector=385316936 Aug 4 19:24:43 minpc kernel: md: recovery thread: P incorrect, sector=392694880 Aug 4 19:24:55 minpc kernel: md: recovery thread: stopped logging Edited August 4, 2017 by mik added more info Quote Link to comment
JorgeB Posted August 4, 2017 Share Posted August 4, 2017 It's normal to have some sync errors after an unclean shutdown, your data should be fine unless you were in the process of writing data at the time of the power cut. Run a correcting check. Quote Link to comment
mik Posted August 4, 2017 Author Share Posted August 4, 2017 About 2-3 min. before the power disappeared I was moving/deleting files from shares. I actually started a shutdown about 5-10 seconds before the power disappeared. So maybe the server was doing something? Quote Link to comment
JorgeB Posted August 4, 2017 Share Posted August 4, 2017 Your data should be fine, sync errors are normal, run a correcting check. Quote Link to comment
mik Posted August 4, 2017 Author Share Posted August 4, 2017 52 minutes ago, johnnie.black said: Run a correcting check sorry i am a newbie, do you mean a "Write corrections to parity check"? Quote Link to comment
Recommended Posts
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.