Hi guys,

A parity check was started automatically last midnight and as I woke up I heard painfull sounds from the server. Sounds like all drives are spinning up and then suddenly stopping. I saw that the parity check is still on zero percent after 7 hours so I stopped it immediatelly. The system log is full of errors. If I start the parity check manualy, this is what I get.

Oct 16 21:34:13 Tower emhttpd: req (12): startState=STARTED&file=&cmdCheck=Check&optionCorrect=correct&csrf_token=****************
Oct 16 21:34:13 Tower kernel: mdcmd (46): check correct
Oct 16 21:34:13 Tower kernel: md: recovery thread: check P Q ...
Oct 16 21:34:13 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks.
Oct 16 21:34:14 Tower kernel: ata10.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen
Oct 16 21:34:14 Tower kernel: ata10.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Oct 16 21:34:14 Tower kernel: ata10: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Oct 16 21:34:14 Tower kernel: ata10.00: failed command: READ DMA EXT
Oct 16 21:34:14 Tower kernel: ata10.00: cmd 25/00:00:00:3d:00/00:03:00:00:00/e0 tag 8 dma 393216 in
Oct 16 21:34:14 Tower kernel: res 50/00:00:ff:3c:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct 16 21:34:14 Tower kernel: ata10.00: status: { DRDY }
Oct 16 21:34:14 Tower kernel: ata10: hard resetting link
Oct 16 21:34:20 Tower kernel: ata10: link is slow to respond, please be patient (ready=0)
Oct 16 21:34:24 Tower kernel: ata10: COMRESET failed (errno=-16)
Oct 16 21:34:24 Tower kernel: ata10: hard resetting link
Oct 16 21:34:29 Tower kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Oct 16 21:34:29 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT1.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Oct 16 21:34:29 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT1.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516)
Oct 16 21:34:29 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT1.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Oct 16 21:34:29 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT1.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516)
Oct 16 21:34:29 Tower kernel: ata10.00: configured for UDMA/33
Oct 16 21:34:29 Tower kernel: ata10: EH complete
Oct 16 21:34:30 Tower kernel: ata10.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen
Oct 16 21:34:30 Tower kernel: ata10.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Oct 16 21:34:30 Tower kernel: ata10: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Oct 16 21:34:30 Tower kernel: ata10.00: failed command: READ DMA EXT
Oct 16 21:34:30 Tower kernel: ata10.00: cmd 25/00:40:c0:7c:00/00:05:00:00:00/e0 tag 7 dma 688128 in
Oct 16 21:34:30 Tower kernel: res 50/00:00:bf:7c:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Oct 16 21:34:30 Tower kernel: ata10.00: status: { DRDY }
Oct 16 21:34:30 Tower kernel: ata10: hard resetting link
Oct 16 21:34:33 Tower emhttpd: req (14): startState=STARTED&file=&csrf_token=****************&cmdNoCheck=Cancel
Oct 16 21:34:33 Tower kernel: mdcmd (47): nocheck Cancel

No errors appear asside the drives list in the main tab and everything works. Apart from the  parity check.  I turned it off and checked all cables already, even thought I did not touch them in the last week.

I have already done the parity check on this setup for four times. I attached my diagnostic files. Have you encountered this? Are you able to help?

 

Thanks  

tower-diagnostics-20191016-1951.zip

43 minutes ago, vitis said:

Sounds like all drives are spinning up and then suddenly stopping

Power supply.

That is an interesting point actually! I will check the PSUs internals for bad caps as that is the only thing that can be bad. I doubt that it is overloaded. Server sits at idle during the parity check start and as I mentioned I already did the parity check with this setup.

Attached are specs of the PSU.

You should also check/replace both cables on parity disk, since it appears to be the only disk having issues.

Hooked up the drive bays with Corsair AX860i and it works. Case closed.

 

Cables are already new. Errors showed up with the old ones and I am (well unraid is) still watching these smarts.

 

Thank you guys! You are the best!  

Edited October 17, 20196 yr by vitis
reply to johnie.black