May 2, 20233 yr Is this anything to be concerned about? I recently upgraded the parity drive last week, and parity was rebuilt with no issue. A couple days later I upgraded Disk 1 (sdh) and the data was rebuilt from parity with no issues. No this is the first parity-check that has been run (scheduled) since those changes were made. After ~4-5TB of progress in the check it has slowed way down and is estimated to take 900+ days to finish that doesn't seem right. Does anyone have any recommendations of what I can check/change? tower-diagnostics-20230502-0816.zip
May 2, 20233 yr Community Expert Solution There's something writing to disk1, stop that activity and see if speed improves.
May 2, 20233 yr Community Expert 7 minutes ago, Sean Mooney said: parity-check that has been run (scheduled) Scheduled parity checks should be NON-correcting. May 1 14:40:55 Tower kernel: mdcmd (36): check correct May 1 14:40:55 Tower kernel: md: recovery thread: check P ... Correcting parity checks should only be run when you have eliminated all I/O problems and still have some sync errors after a non-correcting check. You don't want to change parity if there are other problems going on. May 1 14:20:24 Tower emhttpd: unclean shutdown detected That might possibly account for the 1447 sync errors in your screenshot. May 1 19:19:05 Tower kernel: md: recovery thread: P corrected, sector=4823598056 May 1 19:19:05 Tower kernel: md: recovery thread: stopped logging It won't log all sync errors so there are more after that but they probably stopped not long after that timestamp and before 16 minutes ago, Sean Mooney said: ~4-5TB of progress in the check 18 minutes ago, Sean Mooney said: it has slowed way down Is anything reading or writing to your server? Do any of your disks show SMART warnings ( 👎 ) on the Dashboard page? Have you been using Unraid long? Why are any of your disks still ReiserFS? You will have to get those converted to another filesystem.
May 2, 20233 yr Author 1 hour ago, JorgeB said: There's something writing to disk1, stop that activity and see if speed improves. Thank you! How did you know it was disk1?
May 2, 20233 yr Author 34 minutes ago, JorgeB said: It's in the diags. Sorry, I should have been more clear. Where in the diags would I find that disk1 is being used? I'm trying to learn what to check for future trouble shooting before coming to the forum for help.
May 2, 20233 yr Community Expert loads.txt in the diags, if you scroll down you see this part: sda (flash)=0 0 5481 377 sdb (cache)=0 0 37201 65069 sdc (dacker_data)=0 1850112 113707 1383939 sdd (disk3)=512 0 7730694 558 sde (parity)=928256 514048 11153340 72257 sdf (disk2)=131584 0 11077649 2352 sdg (disk4)=131584 0 11077593 2375 sdh (disk1)=176640 524288 11150876 61448 1st column is current read speed, 2nd column is current write speed, in bytes/s.
May 2, 20233 yr Author 1 hour ago, JorgeB said: loads.txt in the diags, if you scroll down you see this part: sda (flash)=0 0 5481 377 sdb (cache)=0 0 37201 65069 sdc (dacker_data)=0 1850112 113707 1383939 sdd (disk3)=512 0 7730694 558 sde (parity)=928256 514048 11153340 72257 sdf (disk2)=131584 0 11077649 2352 sdg (disk4)=131584 0 11077593 2375 sdh (disk1)=176640 524288 11150876 61448 1st column is current read speed, 2nd column is current write speed, in bytes/s. Thank you!
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.