Jump to content

Sync Errors Remain, Yelp!


Recommended Posts

i Guy's as usual when i am away i have issue's lol Never when i am home with he server i think she likes to punish me for being away XD 

 

So i ran a Non Correcting Parity Scan and it retuned about 2500 ish sync errors So i shut the server down and ra an Error Correcting Scan and that returned the same value XD 

 

So i shut the server down left it over night and its 50% threw another parity scan and showing 336 errors so far. 

Ill attach logs so peoples can have a look for me as i cba do all that digging on an ipad screen, If someone can give me an idea of what or where to look Which disk etc from the logs, Server hasn't moved its a R720XD with all drives fixed in drive trays. 

TIA 

 

L33 

libvirt.txt docker.txt vfio-pci.txt syslog.txt 35000c5006528dea3-20210315-1638 disk2 (sdd).txt 35000cca291c6b6cb-20210315-1638 parity (sdb).txt 35000c5006d5861c8-20210315-1638 disk3 (sde).txt 35000c500bf23945e-20210315-1638 disk7 (sdj).txt 35000c500beab9f32-20210315-1638 disk6 (sdi).txt 35000cca28ed4ae4d-20210315-1638 disk1 (sdc).txt 3500a0751e2077dd8-20210315-1638 (sdl).txt 35000cca2a3e27058-20210315-1638 parity2 (sdm).txt 35000c500a5e3a832-20210315-1638 disk5 (sdg).txt 35000c500bf08cd01-20210315-1638 disk8 (sdh).txt 35002538e49b06602-20210315-1638 cache (sdo).txt 35000c50087f56c95-20210315-1638 disk9 (sdk).txt 35002538e49b06ae3-20210315-1638 cache2 (sdn).txt 35000c50087c020ef-20210315-1638 disk4 (sdf).txt

Link to comment

Sorry didn’t mean to be short with you there’s years of my life on there like 10 years and currently it’s my only copy due to COVID. Where or what am I looking for in the logs? I’d like to be able to understand instead of trying to sort it during work and hectic life. I started another at 1950 so I guess have to wait another 24 ish hours and prey a drive doesn’t fail but hey ho of it fails I’ll swap it with a 12 

 

cheers 

Link to comment

I just want to see if the errors are in the same sectors or not, if it starts finding errors you don't need to let it finish since only the first ones will be logged, e.g., previous one:


 

Mar 17 11:29:51 R720XD kernel: md: recovery thread: check P Q ...
...
Mar 18 00:33:05 R720XD kernel: md: recovery thread: stopped logging

 

It stopped logging after 13 hours or so, you can stop the current one when it also stops logging (assuming errors are found), then post diags.

Link to comment

Ok thats returned 0 sync errors :) So is the way forward if i run it every 3 months and it shows sync errors Do i simply run it again error correcting with no reboot? Was there actual errors and now showing 0 as its corrected then or did it think they was errors and is now happy there isn't. 

Many Thanks for your help with this i just do not Get the time to sort stuff out research stuff i am always working and rarely at home with the server and when i am at home its family time XD 

r720xd-diagnostics-20210320-0854.zip

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

×   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.

×
×
  • Create New...