March 17, 20206 yr Hi. After parity sync error check there was 330 errors found. It started about 2 months ago when errors was found and have been increased since. So far about 10 tests have been made. Have been reading through the forum threads for a solution but I would like some guidance in this matter. I have checked all sata Cables and the hot swap Bays, all secured and in position. Smart test on all drives without any errors. Memtest86 ran for a couple of hours, no errors found System spec: Case: inter-tech IPC SC-4100 Mobo: asrock j5005-itx Memory: Crucial DDR4 2400MHz 16GB SODIMM 16GB 2400MHz (PC4-19200) DDR4 CL17 DR x8 Unbuffered SODIMM, 260pin Hdd: 2x wd red 6TB, 2x wd green 5tb Cache: Samsung SSD 840 EVO 500GB Psu: Sea Sonic SS-250SU Sata card: 2 Port SATA III PCI-e 2.0 x1 Card - SY-PEX40039 tower-diagnostics-20200316-2302.zip Edited March 17, 20206 yr by TIE Fighter wrong spell
March 17, 20206 yr Community Expert Run a couple of non correcting parity checks and post new diags after that (before rebooting) but first check/replace cables on disk2.
March 17, 20206 yr Author 1 hour ago, johnnie.black said: Run a couple of non correcting parity checks and post new diags after that (before rebooting) but first check/replace cables on disk2. Thx i will revert once done and post the results.
March 20, 20206 yr Author So I replaced the sata cable for disk 2 And run two non correcting parity checks. 1st check gave 5 errors 2nd check gave 2 errors Attached diagnosstics tower-diagnostics-20200320-1239.zip Edited March 20, 20206 yr by TIE Fighter wrong spell
March 21, 20206 yr Author 19 hours ago, johnnie.black said: Based on that bad RAM would be my main suspect, run memtest. 3rd non correcting parity check gave 1 error. So the errors are almost gone now since i replaced the sata cable. Can i do a 4th parity check before I do a memtest cause I have already made that in the past and the memory are new. tower-diagnostics-20200321-0853.zip
March 21, 20206 yr Community Expert 1 hour ago, TIE Fighter said: So the errors are almost gone now since i replaced the sata cable. The cable wasn't the problem, the different number of errors (on different sectors) suggest very strongly that there's a hardware problem, like bad RAM.
March 21, 20206 yr Author Finished 4th non correcting parity sync error check with 0 errors. Will this mean that all is okay from now and I can stop investigate and rest this case. Att: diagnostics from last parity check. From here the server have been restarted tower-diagnostics-20200321-2331.zip
March 22, 20206 yr Community Expert 9 hours ago, TIE Fighter said: Will this mean that all is okay from now Unlikely the problem went away on its own, you'll probably get more errors on future checks.
March 27, 20206 yr Author Now i discovered warnings and errors in the disk log info for disk 3, but I dont really understand what they mean. Mar 26 22:31:27 Tower kernel: ata6.00: exception Emask 0x10 SAct 0x3f800000 SErr 0x400000 action 0x6 frozen Mar 26 22:31:27 Tower kernel: ata6.00: irq_stat 0x08000000, interface fatal error Mar 26 22:31:27 Tower kernel: ata6: SError: { Handshk } Mar 26 22:31:27 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED Diagnostics att. tower-diagnostics-20200327-0158.zip
March 27, 20206 yr Community Expert That looks like a connection issue, check/replace cables on disk3.
Archived
This topic is now archived and is closed to further replies.