I have installed 2 disks in a new unraid server. However the parity check is taking longer than I've seen previous topics discuss. I am also copying data to the server at the same time but have read this should have almost no impact. I still have 2 disks to add but just wanted to make sure this crazy long parity time was normal:

 

 

 

This screenshot is 24hrs after starting.

 

Thanks.

Several people reporting issues with that 5TB drive.

I realise some have had problems with this drive in Windows too, but I didn't have these problems. It was detected fine in Windows and performed very well; in fact I had write speeds higher than most of my other drives. It just seems to be slow in the unraid system. Could there be a setting somewhere I am missing?

It might be worth providing a syslog to see if the drive seems to be reporting any problems in unRAID.

I took out hard drive and put it into another pc to do some checks with seatools. All tests passed ok so I formatted and put it back in unraid server. This time it worked fine. In fact parity is already complete. Weird!

The only errors I got this time were:

 

Dec 29 15:24:39 Tower kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Dec 29 15:24:39 Tower kernel: ata3.00: irq_stat 0x08000000, interface fatal error (Errors)
Dec 29 15:24:39 Tower kernel: ata3: SError: { UnrecovData 10B8B BadCRC } (Errors)

 

This shows a few times. Other than that my array is up.

 

Now that I think back I believe the first time I booted the machine the web interface stopped working so I rebooted without stopping array. This may have led to the crazy long time.

This time the web interface crashed again but I had unmenu installed so checked that instead.

10B8B BadCRC indicates a bad or loose SATA cable.

Thanks. It has not appeared again since parity finished, but if it does I'll check out the sata cables.