July 31, 20241 yr Hello together, a few months ago, I had constant problems with my server. That system was over 10 years old, and so I decided to set up a new machine. The new server is completely new. I used basically nothing from the old machine. During the first parity check, the system fixed a lot of sectors. This shows up in the log file: Jul 30 19:34:21 Tower kernel: md: recovery thread: Q corrected, sector=3249428320 During the second parity check, I got a lot of read errors again: Jul 31 16:57:54 Tower kernel: md: disk12 read error, sector=1167649920 Any ideas how to solve this? Might be the drive? Bye. Edited November 27, 2025Nov 27 by shire
July 31, 20241 yr Author Between the error segments it writes now: Jul 31 18:33:57 Tower kernel: sd 2:0:3:0: [sde] tag#139 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jul 31 18:33:57 Tower kernel: sd 2:0:3:0: [sde] tag#139 Sense Key : 0x3 [current] Jul 31 18:33:57 Tower kernel: sd 2:0:3:0: [sde] tag#139 ASC=0x11 ASCQ=0x0 Jul 31 18:33:57 Tower kernel: sd 2:0:3:0: [sde] tag#139 CDB: opcode=0x88 88 00 00 00 00 00 87 92 f7 c0 00 00 02 40 00 00
August 1, 20241 yr Author Here is the report... WDC_WD40EFZX-68AWUN0_WD-WX42D91ND945-20240801-1120.txt
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.