sunkenrat Posted January 1, 2017 Share Posted January 1, 2017 I have now tried to run a parity check twice and I got 9 errors both time. I can't se anywhere what the errors are. But now I can see that one of my harddrive have a smart error. Reported uncorrect 0x0032 099 099 000 Old age Always Never 1 I am running a long test on the disk right now. But I am not very much into all these numbers. Should I bee worried about the disk? I have attached the smart log. ST2000DM001-9YN164_Z1E1QHGE-20170101-1312.txt Quote Link to comment
JorgeB Posted January 1, 2017 Share Posted January 1, 2017 That error was a long time ago (6246 power on hours ago), so it's not related to your issue. This maybe be obvious but are you running correcting check? If not errors are not corrected. Post the complete diagnostics after a parity check and before rebooting. Quote Link to comment
sunkenrat Posted January 1, 2017 Author Share Posted January 1, 2017 Yes I have always have checked in (write corrections to parity) should I run a new parity check the last one finished about 5 hours ago can that bee used? I haven't rebooted after. Quote Link to comment
JorgeB Posted January 1, 2017 Share Posted January 1, 2017 If you haven't rebooted after the last one post the current diagnostics. Quote Link to comment
sunkenrat Posted January 1, 2017 Author Share Posted January 1, 2017 I hope these are the correct things. diag.zip Quote Link to comment
JorgeB Posted January 1, 2017 Share Posted January 1, 2017 First check was no correct: Dec 27 16:38:43 Server kernel: mdcmd (41): check nocorrect Dec 27 16:38:43 Server kernel: md: recovery thread: check P ... Dec 27 16:38:43 Server kernel: md: using 1536k window, over a total of 3907018532 blocks. Dec 27 19:36:17 Server kernel: md: recovery thread: P incorrect, sector=2936977104 Dec 27 19:36:17 Server kernel: md: recovery thread: P incorrect, sector=2936977120 Dec 27 19:36:17 Server kernel: md: recovery thread: P incorrect, sector=2936977128 Dec 27 19:36:22 Server kernel: md: recovery thread: P incorrect, sector=2938288648 Dec 27 19:36:22 Server kernel: md: recovery thread: P incorrect, sector=2938288664 Dec 27 19:36:22 Server kernel: md: recovery thread: P incorrect, sector=2938288672 Dec 27 19:36:22 Server kernel: md: recovery thread: P incorrect, sector=2938288680 Dec 27 19:36:22 Server kernel: md: recovery thread: P incorrect, sector=2938288696 Dec 27 19:39:37 Server kernel: md: recovery thread: P incorrect, sector=2988685016 The second one was a correcting check: Jan 1 03:05:25 Server kernel: md: recovery thread: P corrected, sector=2936977104 Jan 1 03:05:25 Server kernel: md: recovery thread: P corrected, sector=2936977120 Jan 1 03:05:25 Server kernel: md: recovery thread: P corrected, sector=2936977128 Jan 1 03:05:30 Server kernel: md: recovery thread: P corrected, sector=2938288648 Jan 1 03:05:30 Server kernel: md: recovery thread: P corrected, sector=2938288664 Jan 1 03:05:30 Server kernel: md: recovery thread: P corrected, sector=2938288672 Jan 1 03:05:30 Server kernel: md: recovery thread: P corrected, sector=2938288680 Jan 1 03:05:30 Server kernel: md: recovery thread: P corrected, sector=2938288696 Jan 1 03:08:43 Server kernel: md: recovery thread: P corrected, sector=2988685016 So next check should come up with 0 errors. Quote Link to comment
sunkenrat Posted January 1, 2017 Author Share Posted January 1, 2017 Thanks I try run another check and see if the errors disappear. 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.