UNRAID 5.0.4 setup

 

NZXT Technologies H2 Classic Silent Midtower Chassis CS-NT-H2-B (Black)

AMD A6-3500 APU with AMD Radeon 6530 HD Graphics 2.1/2.4GHz Socket FM1 65W Triple-Core Processor

ASRock MB-A75EX6 Socket FM1/ AMD A75 FCH/ AMD Quad CrossFireX/ SATA3&USB3.0/ A&GbE/ ATX Motherboard

Corsair Vengeance Blue 4GB (1x4GB) DDR3 1600 MHz (PC3 12800) Desktop Memory (CMZ4GX3M1A1600C9B)

Kingston Digital DataTraveler 101 Generation 2 - 4 GB Flash Drive DT101G2/4GBZET

Thermaltake TR2 RX 750W Bronze W0382RU ATX 12V v2.3 / EPS 12V v2.91 SLI Ready CrossFire Ready 80 PLUS BRONZE Certified Modular Active PFC Power Supply

 

Tried both these PCI SATA controller :

HighPoint Rocket 640L Lite Version 4-Port PCI-Express 2.0 x4 SATA 6Gb/s RAID Controller

 

Tried another card after reading 640L is not compatible with Unraid, but still with the new card problems prevail.

IO Crest SATA III 4 Port PCI-e 2.0 x1 Card with Low Profile Bracket (SI-PEX40064)

 

To isolate swapped Power Supply with Antec EarthWatts EA-650D Green 650 Watt 80 PLUS BRONZE as well but no effect.

 

With both these PCI Xpress SATA controller I am having troubles when hard drives are connected to them there will be write errors on one drive (4TB WD Red Drive) and when I start rebuilding parity the other drives connected on the controller (2 3TB Red Drives) start showing timeouts in the syslog.

 

Such as these :

 

Mar 26 22:08:46 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 26 22:08:46 Tower kernel: ata7.00: failed command: SMART

Mar 26 22:08:46 Tower kernel: ata7.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in

Mar 26 22:08:46 Tower kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 26 22:08:46 Tower kernel: ata7.00: status: { DRDY }

Mar 26 22:08:46 Tower kernel: ata7: hard resetting link

Mar 26 22:08:47 Tower kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Mar 26 22:08:47 Tower kernel: ata7.00: configured for UDMA/133

Mar 26 22:08:47 Tower kernel: ata7: EH complete

 

Disk3, Disk9 and Disk10 are connected to PCI Xpress Sata adapter card and all the other disks are connected to motherboard sata connectors.

 

Attaching the Smart information of all my hard drives.

 

Is this the problem due SATA PCI Xpress Card or Hard drives ?

 

Currently I need to rebuild Disk 10 because of disk write error making the disk disable, which had earlier happened on 2 occasion in the past and I have rebuilt it, but there were timeouts in the log at that time as well. This time I am planning of fixing the problem for good.

 

So the disks having problems are Disk3, Disk 9 and Disk 10 all connected to PCI Xpress SATA controller card.

 

Disk layout for my Unraid setup : https://drive.google.com/file/d/0B49biUY4bVT6TU5yY2dkblZhbjA/edit?usp=sharing

 

Large syslog is here with highpoint rocket raid card: https://drive.google.com/file/d/0B49biUY4bVT6ZkRvaGNzaGsxN0k/edit?usp=sharing

 

Thanks for your help.

syslog.zip

Check for BIOS and firmware updates.

Updated the Bios to latest version from Asrock website.

 

It's rebuilding parity

 

But I can still see this in the syslog

 

Mar 28 21:50:49 Tower cache_dirs: ----------------------------------------------

Mar 28 21:50:49 Tower cache_dirs: cache_dirs process ID 3902 started, To terminate it, type: cache_dirs -q

Mar 28 21:50:49 Tower avahi-daemon[2897]: Service "Tower" (/services/smb.service) successfully established.

Mar 28 21:56:32 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 28 21:56:32 Tower kernel: ata5.00: failed command: SMART

Mar 28 21:56:32 Tower kernel: ata5.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in

Mar 28 21:56:32 Tower kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 28 21:56:32 Tower kernel: ata5.00: status: { DRDY }

Mar 28 21:56:32 Tower kernel: ata5: hard resetting link

Mar 28 21:56:33 Tower kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Mar 28 21:56:33 Tower kernel: ata5.00: configured for UDMA/133

Mar 28 21:56:33 Tower kernel: ata5: EH complete

Mar 28 21:57:53 Tower sshd[8192]: Accepted password for root from 192.168.1.13 port 50298 ssh2

Mar 28 22:00:42 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 28 22:00:42 Tower kernel: ata7.00: failed command: SMART

Mar 28 22:00:42 Tower kernel: ata7.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in

Mar 28 22:00:42 Tower kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 28 22:00:42 Tower kernel: ata7.00: status: { DRDY }

Mar 28 22:00:42 Tower kernel: ata7: hard resetting link

Mar 28 22:00:43 Tower kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Mar 28 22:00:43 Tower kernel: ata7.00: configured for UDMA/133

Mar 28 22:00:43 Tower kernel: ata7: EH complete

Completed Building parity and run parity check in about 26 hours combined for both processes.

 

Attaching syslog zip.

 

Also I get this errors whenever I tried to access hard disk from http://tower to see progress on the operation.

 

syslog.zip

I am still getting this errors

 

Apr  1 23:22:31 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Apr  1 23:22:31 Tower kernel: ata5.00: failed command: IDENTIFY DEVICE

Apr  1 23:22:31 Tower kernel: ata5.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in

Apr  1 23:22:31 Tower kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Apr  1 23:22:31 Tower kernel: ata5.00: status: { DRDY }

Apr  1 23:22:31 Tower kernel: ata5: hard resetting link

Apr  1 23:22:31 Tower kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Apr  1 23:22:31 Tower kernel: ata5.00: configured for UDMA/133

Apr  1 23:22:31 Tower kernel: ata5: EH complete

 

Even when I am copying to other disks  does this indicate problems with the Drive ?

 

 

In my experience that is normally a cabling issue (SATA or Power).  It can sometimes be hard to track down as borderline cables can work sometimes and not at others.  It can also happen if the power supply is struggling to provide enough power for all the currently active drives.