Hi there, so im a very happy customer so i bought 5 new 4tb hdds.

 

Today i replaced the parity only because "you cant remove a hdd and add another" (oO!)

 

But... speed? Why? 

 

Total size:	4 TB
Elapsed time:	33 minutes
Current position:	21.5 GB (0.5 %)
Estimated speed:	7.2 MB/sec
Estimated finish: 6 days, 12 hours, 34 minutes

 

I never had speed issues, always around 1gbit and the last paritys worked with 100-120mb/s.

 

 

unraid-server-diagnostics-20171215-2031.zip

edit: got sent 2 times

Edited December 15, 20178 yr by nuhll

That's definitely too slow, diagnostics may show why, go to Tool -> Diagnostics and attach the zip.

I already have.

 

Edit:

14 days, 2 hours, 32 minutes

Edited December 15, 20178 yr by nuhll

Timeout errors on the parity disk, might be a bad cable, might be the controller:

Dec 15 19:58:26 Unraid-Server kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 15 19:58:26 Unraid-Server kernel: ata7.00: failed command: WRITE DMA EXT
Dec 15 19:58:26 Unraid-Server kernel: ata7.00: cmd 35/00:40:80:f4:72/00:05:01:00:00/e0 tag 2 dma 688128 out
Dec 15 19:58:26 Unraid-Server kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 15 19:58:26 Unraid-Server kernel: ata7.00: status: { DRDY }
Dec 15 19:58:26 Unraid-Server kernel: ata7: hard resetting link
Dec 15 19:58:27 Unraid-Server kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 15 19:58:27 Unraid-Server kernel: ata7.00: configured for UDMA/133
Dec 15 19:58:27 Unraid-Server kernel: ata7: EH complete
Dec 15 19:58:58 Unraid-Server kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 15 19:58:58 Unraid-Server kernel: ata7.00: failed command: WRITE DMA EXT
Dec 15 19:58:58 Unraid-Server kernel: ata7.00: cmd 35/00:40:80:1c:75/00:05:01:00:00/e0 tag 16 dma 688128 out
Dec 15 19:58:58 Unraid-Server kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 15 19:58:58 Unraid-Server kernel: ata7.00: status: { DRDY }
Dec 15 19:58:58 Unraid-Server kernel: ata7: hard resetting link
Dec 15 19:58:58 Unraid-Server kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 15 19:58:58 Unraid-Server kernel: ata7.00: configured for UDMA/133
Dec 15 19:58:58 Unraid-Server kernel: ata7: EH complete
Dec 15 19:59:39 Unraid-Server kernel: ata7: limiting SATA link speed to 3.0 Gbps
Dec 15 19:59:39 Unraid-Server kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 15 19:59:39 Unraid-Server kernel: ata7.00: failed command: WRITE DMA
Dec 15 19:59:39 Unraid-Server kernel: ata7.00: cmd ca/00:c0:c0:a3:a1/00:00:00:00:00/e1 tag 21 dma 98304 out
Dec 15 19:59:39 Unraid-Server kernel:         res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 15 19:59:39 Unraid-Server kernel: ata7.00: status: { DRDY }
Dec 15 19:59:39 Unraid-Server kernel: ata7: hard resetting link

 

Can you post a link to the Asmedia controller you're using, unusual to see an Asmedia with more than 2 ports.

Omg,

i restart. Cables are new, hdd also...

 

https://www.mindfactory.de/product_info.php/Delock-89384-10-Port-PCIe-2-0-x2-Low-Profile-retail_993263.html

On the controller i have 4 hdds at the moment, and they dont show signs?! So its hdd or cable, right? Or.. port... on controller...

 

I changed now to the 2. 4tb hdd.

 

edit: Same error.. but 150mb/s... and now?!

 

 

edit2: Okay, after some minutes and some of the errors, also the second is running with some mb/s.

 

Whats more likly, cable or controller? (other hdds in controller work) 

 

How often single (or some in this case) ports get fugged up?

 

Also i added old parity drive back  (was unasigned) ... and now he builds parity new.. clever.

 

Edited December 15, 20178 yr by nuhll

Btw, the hdds are https://www.amazon.de/gp/product/B01N7YOH4P/ref=oh_aui_detailpage_o00_s01?ie=UTF8&psc=1

 

Thats my first "real" "server" hdds. Normal i just take what i have layin around and be fine. Is there anything i need to change to get them correct working? Jumper? Bios? anything i could have done wrong? (i just plugged in and restartet)

Only thing what is not like normal: I added a Y cable from molex to 2 sata power. COULD that be the problem?

Edited December 15, 20178 yr by nuhll

Controller is the likely problem, it probably uses a port multiplier, IIRC I told you that controller was not recommended.

This couldnt be caused by power cable? BC thats the only thing that differs from all other disks.

It can't hurt to try.

If i stop parity, i need to start from beginning, right?

Yep .

If i disable all dockers, vms and when parity is finish and i add the new ones and it still dont work, and i put parity back... do i need to do parity again?

OKay, i dont get it. I replaced the new hdd with the old one (didnt changed anything, same cables same ports etc) but now unraid says "red cross" parity device disabled", i run parity check after switching back to the old one and it finished with: 

unRAID Read check: 16-12-2017 17:38

Notice [UNRAID-SERVER] - Read check finished (0 errors)
Duration: 8 hours, 1 minute, 54 seconds. Average speed: 103.8 MB/s

 

(seems normal for me)

 

unraid-server-diagnostics-20171216-1848.zip

That's a read check, not a parity check, parity is invalid, you'll need to re-sync it.