Jump to content

problem with Parity Check taking estimated time of 100 days for 6 tb


Go to solution Solved by itimpi,

Recommended Posts

hello everyone

normally my parity check would take from 10 to 20 hours to finish but 3 days ago i started another one but my estimated finish time is 100 days and the desk temp go up to 50°c but if i stops the check it goes back to normal levels

the case have good airflow the cpu and gpu temp are normal

i changed some sata cables for some of the drives before that also deleted about 4-5 tb of data

images have info about the Parity desk (the last wb red 4tb cmr parity desk had the same issue before i replaced it but at least it lasted 4 years so i didn't suspected anything the current one i just got 6 months ago)

also the server logs are in the attachments

are the drive is toast or i have another problem on my hand from my sampling it seems all my data is fine and the server is fast handling them
 

Screenshot 2023-06-15 221403.png

Screenshot 2023-06-15 221342.png

Screenshot 2023-06-15 221324.png

Screenshot 2023-06-15 221247.png

Screenshot 2023-06-15 223518.png

server-syslog-20230615-1927.zip

Link to comment
12 hours ago, itimpi said:

That syslog is full of errors on device ata4 (without full diagnostics not sure what device that is) that look like cabling issues, and also read errors on disk1.

i changed the cables but now disk 1 (the device with errors in the log) is disabled i will get new cables try again and i will get back to you with full diagnostics but it might take me sometime

thanks

Link to comment
On 6/16/2023 at 1:12 AM, itimpi said:

That syslog is full of errors on device ata4 (without full diagnostics not sure what device that is) that look like cabling issues, and also read errors on disk1.

 

On 6/16/2023 at 1:21 PM, ahmed_master23 said:

i changed the cables but now disk 1 (the device with errors in the log) is disabled i will get new cables try again and i will get back to you with full diagnostics but it might take me sometime

thanks

i got new sata cables ran the check again and this the full diagnostics

server-diagnostics-20230621-1215.zip

Edited by ahmed_master23
Link to comment

Disk2 in the array.  When the syslog contains entries like:

Jun 20 20:50:11 Felix-Server kernel: md: disk2 read error, sector=271816
Jun 20 20:50:11 Felix-Server kernel: md: disk2 read error, sector=271824
Jun 20 20:50:11 Felix-Server kernel: md: disk2 read error, sector=271832
Jun 20 20:50:11 Felix-Server kernel: md: disk2 read error, sector=271840

this always refers to disk2 in the Unraid GUI as Unraid does not care how the drives are physically located.

  • Thanks 1
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...