Darts

OK, parity check completed and it indeed corrected the errors. Thank you 🙂

Indeed, this seems to be the way to go 👍

OMG... Indeed I see the "Write corrections to parity disk" box ticked for manual checks but the scheduled ones are not 🤦‍♂️ Thanks for pointing that out, I'll run the corrective right away.

Hello, I have been procrastinating this issue for far too long and I would like to correct it . I have sync errors in my parity checks. They are each time all the same numbers, always the same concurrent sectors. They happened after I had a lot of troubles with my server, multiple hard, unclean shutdowns those happening most probably during a parity check. I'm always running corrective checks (but after reading a lot on the subject I see I need to change this behaviour) however these errors do not self correct. Jan 1 08:38:09 Alpha kernel: md: recovery thread: P incorrect, sector=5039842800 Jan 1 08:38:09 Alpha kernel: md: recovery thread: P incorrect, sector=5039842808 Jan 1 08:38:09 Alpha kernel: md: recovery thread: P incorrect, sector=5039842816 Jan 1 08:38:09 Alpha kernel: md: recovery thread: P incorrect, sector=5039842824 etc. Could you please help me find a course of action to correct or at least get rid of these? I probably have a corrupted file that I won't be able to recover since I'm still on reiserfs but hopefully only the parity is incorrect and all the files are good. Best regards and my best wished for 2023 🙂

Thank you!

Hello! I'd like to report the same issue.

Only one pass I'm afraid. I dealt very poorly with this situation I'm afraid : my server was down the entire upgrade time as I had to remove the production disk. So more downtime was not really an option for me. Next time I'll build a small server only for the preclear to run it's 3 passes for a week or so

Alright, sorry for the triple post but I wanted to inform anyone following this thread and I don't think an edit would trigger an alert : I received my new disk on Monday morning (I asked for a replacement on amazon on Friday afternoon, so very good point for amazon, thanks guys!) The preclear just ended successfully yay! Now I'm rebuilding parity. Last word : previous disk definitively DOA, thanks to the preclear for detecting a faulty drive And thank you Joe L for making that script

Well the WD diag tool indicates the same kind of issue with a bit less details. Around 75% the extended test gets slower and slower... Why doesn't WD test their drives before selling them is completely beyond me... FYI, it's the second WD RED 3To drive that's DOA (on 2 purchases, thank you amazon for having such a great customer support )

I'm currently around 70% completed with a relatively good speed of ~90MB/s I'll post the smart results once it's completed (probably in about 6 hours). EDIT >> OK, so it's toasted in preclear, got stuck at 75% and speed dropping to a few hundreds of kb/s. I'm taking it out of the server and will check with WD diag tool. In the meantime, I'll begin the replacement procedure with amazon

FYI, I ran this and will see hopefully the log

I see, thanks for the link Is there some way to extract a report from a running preclear instance?

EDIT >> Disk3 is missing as it's the one I need to replace with the new 3TB. Here's the first error in the syslog, please let me know if you need more but the complete syslog is around 40Mb Aug 21 17:54:26 Alpha login[16018]: ROOT LOGIN on '/dev/pts/0' from '192.168.123.32' Aug 21 17:55:20 Alpha emhttp: shcmd (53005): rmmod md-mod |& logger Aug 21 17:55:20 Alpha emhttp: shcmd (53006): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Aug 21 17:55:20 Alpha emhttp: shcmd (53007): udevadm settle Aug 21 17:55:20 Alpha kernel: md: unRAID driver removed Aug 21 17:55:20 Alpha kernel: md: unRAID driver 2.1.6 installed Aug 21 17:55:20 Alpha emhttp: Device inventory: Aug 21 17:55:20 Alpha emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2987994 (sdb) 2930266584 Aug 21 17:55:20 Alpha emhttp: ST2000DL003-9VT166_5YD0TZF9 (sdc) 1953514584 Aug 21 17:55:20 Alpha emhttp: ST2000DL003-9VT166_6YD12YSL (sdd) 1953514584 Aug 21 17:55:20 Alpha emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T1113026 (sde) 2930266584 Aug 21 17:55:20 Alpha emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA0613214 (sdf) 1953514584 Aug 21 17:55:20 Alpha emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0797655 (sdg) 2930266584 Aug 21 17:55:20 Alpha emhttp: SAMSUNG_HD203WI_S1UYJ1LZ200939 (sdh) 1953514584 Aug 21 17:55:20 Alpha emhttp: WDC_WD1600AAJS-75M0A0_WD-WMAV3D708981 (sdi) 156250000 Aug 21 17:55:20 Alpha kernel: mdcmd (1): import 0 8,64 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T1113026 Aug 21 17:55:20 Alpha kernel: md: import disk0: [8,64] (sde) WDC_WD30EFRX-68AX9N0_WD-WMC1T1113026 size: 2930266532 Aug 21 17:55:20 Alpha kernel: mdcmd (2): import 1 8,80 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA0613214 Aug 21 17:55:20 Alpha kernel: md: import disk1: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA0613214 size: 1953514552 Aug 21 17:55:20 Alpha kernel: mdcmd (3): import 2 8,32 1953514552 ST2000DL003-9VT166_5YD0TZF9 Aug 21 17:55:20 Alpha kernel: md: import disk2: [8,32] (sdc) ST2000DL003-9VT166_5YD0TZF9 size: 1953514552 Aug 21 17:55:20 Alpha kernel: mdcmd (4): import 3 0,0 Aug 21 17:55:20 Alpha kernel: md: disk3 missing Aug 21 17:55:20 Alpha kernel: mdcmd (5): import 4 8,16 2930266532 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2987994 Aug 21 17:55:20 Alpha kernel: md: import disk4: [8,16] (sdb) WDC_WD30EZRX-00MMMB0_WD-WCAWZ2987994 size: 2930266532 Aug 21 17:55:20 Alpha emhttp: shcmd (53008): /usr/local/sbin/emhttp_event driver_loaded Aug 21 17:55:20 Alpha kernel: mdcmd (6): import 5 8,48 1953514552 ST2000DL003-9VT166_6YD12YSL Aug 21 17:55:20 Alpha kernel: md: import disk5: [8,48] (sdd) ST2000DL003-9VT166_6YD12YSL size: 1953514552 Aug 21 17:55:20 Alpha kernel: mdcmd (7): import 6 8,112 1953514552 SAMSUNG_HD203WI_S1UYJ1LZ200939 Aug 21 17:55:20 Alpha kernel: md: import disk6: [8,112] (sdh) SAMSUNG_HD203WI_S1UYJ1LZ200939 size: 1953514552 Aug 21 17:55:20 Alpha kernel: mdcmd (: import 7 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (9): import 8 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (10): import 9 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (11): import 10 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (12): import 11 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (13): import 12 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (14): import 13 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (15): import 14 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (16): import 15 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (17): import 16 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (18): import 17 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (19): import 18 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (20): import 19 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (21): import 20 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (22): import 21 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (23): import 22 0,0 Aug 21 17:55:20 Alpha kernel: mdcmd (24): import 23 0,0 Aug 21 17:55:20 Alpha emhttp_event: driver_loaded Aug 21 17:57:20 Alpha emhttp: shcmd (53009): rmmod md-mod |& logger Aug 21 17:57:20 Alpha emhttp: shcmd (53010): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Aug 21 17:57:20 Alpha emhttp: shcmd (53011): udevadm settle Aug 21 17:57:20 Alpha emhttp: Device inventory: Aug 21 17:57:20 Alpha emhttp: WDC_WD30EZRX-00MMMB0_WD-WCAWZ2987994 (sdb) 2930266584 Aug 21 17:57:20 Alpha emhttp: ST2000DL003-9VT166_5YD0TZF9 (sdc) 1953514584 Aug 21 17:57:20 Alpha emhttp: ST2000DL003-9VT166_6YD12YSL (sdd) 1953514584 Aug 21 17:57:20 Alpha emhttp: WDC_WD30EFRX-68AX9N0_WD-WMC1T1113026 (sde) 2930266584 Aug 21 17:57:20 Alpha emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA0613214 (sdf) 1953514584 Aug 21 17:57:20 Alpha emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0797655 (sdg) 2930266584 Aug 21 17:57:20 Alpha emhttp: SAMSUNG_HD203WI_S1UYJ1LZ200939 (sdh) 1953514584 Aug 21 17:57:20 Alpha emhttp: WDC_WD1600AAJS-75M0A0_WD-WMAV3D708981 (sdi) 156250000 Aug 21 17:57:20 Alpha kernel: md: unRAID driver removed Aug 21 17:57:20 Alpha kernel: md: unRAID driver 2.1.6 installed Aug 21 17:57:20 Alpha kernel: mdcmd (1): import 0 8,64 2930266532 WDC_WD30EFRX-68AX9N0_WD-WMC1T1113026 Aug 21 17:57:20 Alpha kernel: md: import disk0: [8,64] (sde) WDC_WD30EFRX-68AX9N0_WD-WMC1T1113026 size: 2930266532 Aug 21 17:57:20 Alpha kernel: mdcmd (2): import 1 8,80 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA0613214 Aug 21 17:57:20 Alpha kernel: md: import disk1: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA0613214 size: 1953514552 Aug 21 17:57:20 Alpha kernel: mdcmd (3): import 2 8,32 1953514552 ST2000DL003-9VT166_5YD0TZF9 Aug 21 17:57:20 Alpha kernel: md: import disk2: [8,32] (sdc) ST2000DL003-9VT166_5YD0TZF9 size: 1953514552 Aug 21 17:57:20 Alpha kernel: mdcmd (4): import 3 0,0 Aug 21 17:57:20 Alpha kernel: md: disk3 missing Aug 21 17:57:20 Alpha kernel: mdcmd (5): import 4 8,16 2930266532 WDC_WD30EZRX-00MMMB0_WD-WCAWZ2987994 Aug 21 17:57:20 Alpha kernel: md: import disk4: [8,16] (sdb) WDC_WD30EZRX-00MMMB0_WD-WCAWZ2987994 size: 2930266532 Aug 21 17:57:20 Alpha emhttp: shcmd (53012): /usr/local/sbin/emhttp_event driver_loaded Aug 21 17:57:20 Alpha kernel: mdcmd (6): import 5 8,48 1953514552 ST2000DL003-9VT166_6YD12YSL Aug 21 17:57:20 Alpha kernel: md: import disk5: [8,48] (sdd) ST2000DL003-9VT166_6YD12YSL size: 1953514552 Aug 21 17:57:20 Alpha kernel: mdcmd (7): import 6 8,112 1953514552 SAMSUNG_HD203WI_S1UYJ1LZ200939 Aug 21 17:57:20 Alpha kernel: md: import disk6: [8,112] (sdh) SAMSUNG_HD203WI_S1UYJ1LZ200939 size: 1953514552 Aug 21 17:57:20 Alpha kernel: mdcmd (: import 7 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (9): import 8 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (10): import 9 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (11): import 10 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (12): import 11 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (13): import 12 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (14): import 13 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (15): import 14 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (16): import 15 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (17): import 16 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (18): import 17 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (19): import 18 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (20): import 19 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (21): import 20 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (22): import 21 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (23): import 22 0,0 Aug 21 17:57:20 Alpha kernel: mdcmd (24): import 23 0,0 Aug 21 17:57:20 Alpha emhttp_event: driver_loaded Aug 21 18:49:22 Alpha sSMTP[28199]: Creating SSL connection to host Aug 21 18:49:22 Alpha sSMTP[28199]: SSL connection using RC4-SHA Aug 21 18:49:27 Alpha sSMTP[28199]: Sent mail for ************************* (221 2.0.0 closing connection iz19sm10981856wic.9 - gsmtp) uid=0 username=root outbytes=8116 Aug 21 19:02:26 Alpha kernel: ata6.00: exception Emask 0x0 SAct 0xff SErr 0x0 action 0x0 Aug 21 19:02:26 Alpha kernel: ata6.00: irq_stat 0x40000008 Aug 21 19:02:26 Alpha kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 21 19:02:26 Alpha kernel: ata6.00: cmd 60/00:18:18:2e:b0/01:00:0c:01:00/40 tag 3 ncq 131072 in Aug 21 19:02:26 Alpha kernel: res 41/40:00:a8:2e:b0/00:00:0c:01:00/40 Emask 0x409 (media error) <F> Aug 21 19:02:26 Alpha kernel: ata6.00: status: { DRDY ERR } Aug 21 19:02:26 Alpha kernel: ata6.00: error: { UNC } Aug 21 19:02:26 Alpha kernel: ata6.00: configured for UDMA/133 Aug 21 19:02:26 Alpha kernel: sd 6:0:0:0: [sdg] Unhandled sense code Aug 21 19:02:26 Alpha kernel: sd 6:0:0:0: [sdg] Aug 21 19:02:26 Alpha kernel: Result: hostbyte=0x00 driverbyte=0x08 Aug 21 19:02:26 Alpha kernel: sd 6:0:0:0: [sdg] Aug 21 19:02:26 Alpha kernel: Sense Key : 0x3 [current] [descriptor] Aug 21 19:02:26 Alpha kernel: Descriptor sense data with sense descriptors (in hex): Aug 21 19:02:26 Alpha kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 01 Aug 21 19:02:26 Alpha kernel: 0c b0 2e a8 Aug 21 19:02:26 Alpha kernel: sd 6:0:0:0: [sdg] Aug 21 19:02:26 Alpha kernel: ASC=0x11 ASCQ=0x4 Aug 21 19:02:26 Alpha kernel: sd 6:0:0:0: [sdg] CDB: Aug 21 19:02:26 Alpha kernel: cdb[0]=0x88: 88 00 00 00 00 01 0c b0 2e 18 00 00 01 00 00 00 Aug 21 19:02:26 Alpha kernel: end_request: I/O error, dev sdg, sector 4507840168 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480021 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480022 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480023 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480024 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480025 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480026 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480027 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480028 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480029 Aug 21 19:02:26 Alpha kernel: Buffer I/O error on device sdg, logical block 563480030 Aug 21 19:02:26 Alpha kernel: ata6: EH complete Aug 21 19:02:33 Alpha kernel: ata6.00: exception Emask 0x0 SAct 0xff SErr 0x0 action 0x0 Aug 21 19:02:33 Alpha kernel: ata6.00: irq_stat 0x40000008 I guess the smart report is from that same drive as they are both labeled sdg. I saw that there's a command to run only the last post-read step : ./preclear_disk.sh -V [-A|-a] /dev/??? Do you think that if this command returns 0 errors it's good for the drive? I'll check this WD diagnostic tool for windows to see if can be helpful, thanks for the suggestion

Yes, the time is updating. ... I think I'll just go ahead and place the drive in the array, hopefully it'll work out just fine. I would have loved to have some kind of confirmation that all the previous steps went fine though... Thanks for the help anyway

Well, that's the thing, the preclear is hanging at 76% of the last step (post read) and speed is down to around 300 KB/sec... Is there any way to save what has been done until now and relaunch only the "post read" step? EDIT >> Right now I have this : = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 76% complete. ( 2,283,337,728,000 of 3,000,592,982,016 bytes read ) 210 kB/s Disk Temperature: 34C, Elapsed Time: 46:29:17