im pretty noob about unraid 

i tried to search for similar problem but didnt find any that fit the description.

 

i have a 23tb array

i rebooted my unraid server last week and did a parity check and it went at 1mb/s instead of 100mb/s

i canceled and rebooted a couple of time but nothing changed.

now i updated unraid to 6.6.5 and it did nothing.

usually it took 10h but now it say 23 days lol

what may be the cause of the problem?

Edited November 15, 20187 yr by Jederek
grammar

Post your diagnostics from when a parity check is being run.

 

Have you tried adjusting your Tunables?

i think this is the file you asked

as for tunables i didnt touch that i dont even know what it is... sorry

diagnostics-20181115-0444.zip

In the bios change the onboard SATA controller from IDE to AHCI and try again.

11 hours ago, johnnie.black said:

In the bios change the onboard SATA controller from IDE to AHCI and try again.

sorry i was at work

i changed it but still the same speed.

i tried some tips ans retried again a parity check and it still slow

i checked the diagnostic file and i found this:

i have no idea what it mean or if its usefull lol

 

Nov 15 18:56:07 Tower kernel: mdcmd (309): set md_num_stripes 1280
Nov 15 18:56:07 Tower kernel: mdcmd (310): set md_sync_window 384
Nov 15 18:56:07 Tower kernel: mdcmd (311): set md_sync_thresh 192
Nov 15 18:56:07 Tower kernel: mdcmd (312): set md_write_method
Nov 15 18:56:07 Tower kernel: mdcmd (313): set spinup_group 0 0
Nov 15 18:56:07 Tower kernel: mdcmd (314): set spinup_group 1 0
Nov 15 18:56:07 Tower kernel: mdcmd (315): set spinup_group 2 0
Nov 15 18:56:07 Tower kernel: mdcmd (316): set spinup_group 3 0
Nov 15 18:56:07 Tower kernel: mdcmd (317): set spinup_group 4 0
Nov 15 18:56:07 Tower kernel: mdcmd (318): set spinup_group 5 0
Nov 15 18:56:07 Tower kernel: mdcmd (319): set spinup_group 6 0
Nov 15 18:56:27 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov 15 18:56:27 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Nov 15 18:56:27 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
Nov 15 18:56:27 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
Nov 15 18:56:27 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
Nov 15 18:56:27 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
Nov 15 18:56:27 Tower kernel: ata2.00: configured for UDMA/33
Nov 15 18:57:50 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov 15 18:57:50 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Nov 15 18:57:50 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
Nov 15 18:57:50 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
Nov 15 18:57:50 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
Nov 15 18:57:50 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
Nov 15 18:57:50 Tower kernel: ata2.00: configured for UDMA/33
Nov 15 18:58:32 Tower emhttpd: req (28): startState=STARTED&file=&cmdCheck=Check&optionCorrect=correct&csrf_token=****************
Nov 15 18:58:32 Tower kernel: mdcmd (320): check correct
Nov 15 18:58:32 Tower kernel: md: recovery thread: check P ...
Nov 15 18:58:32 Tower kernel: md: using 1536k window, over a total of 4395394532 blocks.
Nov 15 18:58:32 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen
Nov 15 18:58:32 Tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Nov 15 18:58:32 Tower kernel: ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Nov 15 18:58:32 Tower kernel: ata2.00: failed command: READ DMA EXT
Nov 15 18:58:32 Tower kernel: ata2.00: cmd 25/00:40:80:16:00/00:05:00:00:00/e0 tag 20 dma 688128 in
Nov 15 18:58:32 Tower kernel:         res 50/00:00:7f:16:00/00:00:00:00:00/e0 Emask 0x50 (ATA bus error)
Nov 15 18:58:32 Tower kernel: ata2.00: status: { DRDY }
Nov 15 18:58:32 Tower kernel: ata2: hard resetting link
Nov 15 18:58:37 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov 15 18:58:38 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Nov 15 18:58:38 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
Nov 15 18:58:38 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
Nov 15 18:58:38 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
Nov 15 18:58:38 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
Nov 15 18:58:38 Tower kernel: ata2.00: configured for UDMA/33
Nov 15 18:58:38 Tower kernel: ata2: EH complete
Nov 15 18:58:38 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen
Nov 15 18:58:38 Tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Nov 15 18:58:38 Tower kernel: ata2: SError: { PHYRdyChg 10B8B LinkSeq DevExch }

Edited November 16, 20187 yr by Jederek

here the latest diagnostics files wich i took while doing a parity

tower-diagnostics-20181115-1900.zip

10 hours ago, Jederek said:

i changed it but still the same speed.

I expected so, there were ATA errors before but because it was in IDE mode it was affecting two disks, now we can see it's disk1, replace cables if errors persist it's likely a disk problem.

neverming i changed the sata cable as you said and it worked! 

thx a lot!!

Edited November 16, 20187 yr by Jederek