-
Preclear.sh results - Questions about your results? Post them here.
Attached is a syslog I just collected. I swapped SATA cables as well and am still seeing the same errors. syslog.txt
-
Preclear.sh results - Questions about your results? Post them here.
I just purchased 2x WD20EARS drives from Amazon. When I received them, I immediately jumpered 7-8 prior to installing into my unRaid. I tried putting 1 drive in as my new parity drive, replacing a 500GB that I previously had in there as parity. Everything seemed to boot ok and unRaid recognized it, but when it did the re-build of the parity after hitting Start, that's when I seem to be having problems. It was poking along at something ridiculous like 20k/sec and would have taken 3 months (this is probably an exaggeration) to complete. When checking the syslog, I'm getting absurd amounts of this message: Dec 5 15:36:14 media kernel: ata3: drained 32768 bytes to clear DRQ. Dec 5 15:36:14 media kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 15:36:14 media kernel: ata3.00: failed command: READ DMA Dec 5 15:36:14 media kernel: ata3.00: cmd c8/00:80:60:68:37/00:00:00:00:00/e0 tag 0 dma 65536 in Dec 5 15:36:14 media kernel: res ff/ff:ff:ff:ff:ff/ff:ff:ff:ff:ff/ff Emask 0x2 (HSM violation) Dec 5 15:36:14 media kernel: ata3.00: status: { Busy } Dec 5 15:36:14 media kernel: ata3.00: error: { ICRC UNC IDNF ABRT } Dec 5 15:36:14 media kernel: ata3: hard resetting link Dec 5 15:36:14 media kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 5 15:36:14 media kernel: ata3.00: configured for UDMA/33 Dec 5 15:36:14 media kernel: ata3: EH complete This repeats a billion times with a few of these thrown in randomly: Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531648 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531649 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531650 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531651 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531652 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531653 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531654 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531655 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531656 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531657 I canceled the parity, un-assigned the drive in Settings, then ran a preclear (preclear_disk.sh /dev/sdc) on it to test the drive. I'm seeing it take insane amounts of time during the pre-read. I let it run for 36 hours and it ended up getting to 1%, completing around 30gb out of 2tb. I ended up canceling the pre-clear and trying my second drive. Same exact thing on both. I've attached the SMART log that was run prior to the pre-read. It isn't reporting any re-allocated sectors, so I'm not really sure what is going on. From what I've read, the pre-read shouldn't be taking 36 hours to reach 1%. I never ran these drives un-jumpered. They were immediately jumpered out of the box (thanks to reading these forums), then installed into my unRaid. My hardware specs on the system: AMD 2800+ Gigabyte GA-7N400 1.5gb DDR2 RAM 2x 2-port PCI SATA card - different brands. I can't really see what the exact model they are, as they're currently installed. I don't think it's a bad cable/card, as my previous parity drive ran just fine on the same port, but who knows. Can anyone shed some light on what may be happening? I'm thinking I received a set of bad drives, but since I didn't see any re-allocated sectors on the SMART report, I'm not really sure. Thanks in advance for any help! smart_start1528.txt
crumshizzle
Members
-
Joined
-
Last visited