One of my drive seem to have failed but it's passing smart.

However, when I tried to start array, I notice following errors in system log and it has not started array for last 30 mins.

 

Oct  3 23:27:59 UnRaid kernel: ata10.00: failed to read SCR 1 (Emask=0x40)
Oct  3 23:27:59 UnRaid kernel: ata10.01: failed to read SCR 1 (Emask=0x40)
Oct  3 23:27:59 UnRaid kernel: ata10.01: failed to read SCR 0 (Emask=0x40)
Oct  3 23:27:59 UnRaid kernel: ata10.01: limiting speed to UDMA/100:PIO4
Oct  3 23:27:59 UnRaid kernel: ata10.02: failed to read SCR 1 (Emask=0x40)
Oct  3 23:27:59 UnRaid kernel: ata10.03: failed to read SCR 1 (Emask=0x40)
Oct  3 23:27:59 UnRaid kernel: ata10.04: failed to read SCR 1 (Emask=0x40)
Oct  3 23:27:59 UnRaid kernel: ata10.15: exception Emask 0x4 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct  3 23:27:59 UnRaid kernel: ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct  3 23:27:59 UnRaid kernel: ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct  3 23:27:59 UnRaid kernel: ata10.01: failed command: WRITE DMA EXT
Oct  3 23:27:59 UnRaid kernel: ata10.01: cmd 35/00:00:40:84:00/00:02:00:00:00/e0 tag 6 dma 262144 out
Oct  3 23:27:59 UnRaid kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct  3 23:27:59 UnRaid kernel: ata10.01: status: { DRDY }
Oct  3 23:27:59 UnRaid kernel: ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct  3 23:27:59 UnRaid kernel: ata10.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct  3 23:27:59 UnRaid kernel: ata10.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct  3 23:27:59 UnRaid kernel: ata10.15: hard resetting link
Oct  3 23:27:59 UnRaid kernel: ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Oct  3 23:27:59 UnRaid kernel: ata10.00: hard resetting link
Oct  3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is disabled
Oct  3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is enabled
Oct  3 23:28:00 UnRaid kernel: ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Oct  3 23:28:00 UnRaid kernel: ata10.01: hard resetting link
Oct  3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is disabled
Oct  3 23:28:00 UnRaid kernel: ahci 0000:02:00.0: FBS is enabled
Oct  3 23:28:00 UnRaid kernel: ata10.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Oct  3 23:28:00 UnRaid kernel: ata10.02: hard resetting link
Oct  3 23:28:01 UnRaid kernel: ata10.02: SATA link down (SStatus 0 SControl 320)
Oct  3 23:28:01 UnRaid kernel: ata10.03: hard resetting link
Oct  3 23:28:01 UnRaid kernel: ahci 0000:02:00.0: FBS is disabled
Oct  3 23:28:01 UnRaid kernel: ahci 0000:02:00.0: FBS is enabled
Oct  3 23:28:01 UnRaid kernel: ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Oct  3 23:28:01 UnRaid kernel: ata10.04: hard resetting link
Oct  3 23:28:02 UnRaid kernel: ata10.04: SATA link down (SStatus 0 SControl 320)
Oct  3 23:28:02 UnRaid kernel: ata10.00: configured for UDMA/133
Oct  3 23:28:02 UnRaid kernel: ata10.01: configured for UDMA/100
Oct  3 23:28:02 UnRaid kernel: ata10.03: configured for UDMA/133
Oct  3 23:28:02 UnRaid kernel: ata10: EH complete
 

I even tried replacing SATA cable thinking it might be faulty but it didn't help.

I even tried replaceing power cable by borrowing it form SSD and it didn't help either.

 

Array doesn't start for me to run xfs_repair -v /dev/sdc1

 

Can someone please help?

 

 

I'd suggest posting your full diagnostics, Tools->Diagnostics.

16 hours ago, curiouskid said:

ata10.01: limiting speed to UDMA/100:PIO4

This make me think you might have some of your MB ports set to PATA mode rather than SATA/AHCI mode.  So you may have multiple problems if my suspicion is correct.

 

Definitely post the WHOLE diagnostics as that will help those that can read logs better then I can an idea of any and all problems you might have and whether I'm even close to being correct above or not.

Attached here are diagnostic file.

 

My data drive is now unmountable. xfs_repair didn't help either.

I am getting the feeling that i my data is in extreme danger.

Parity is still valid. So, if someone can advice me on how to rebuild it, I would appreciate.

 

root@UnRaid:~# xfs_repair -v /dev/sdc1
Phase 1 - find and verify superblock...
        - block cache size set to 660784 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 91463 tail block 91448
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
 

unraid-diagnostics-20171005-1606.zip

It is quite normal to get that message.   When you do you just need to run xfs_repair with the -L option.    It is very rare for there to be any data loss as a result and even if it there was it would only affect the last file written.   Another option is to do a manual mount/umount of the disk (which clears the need for the -L flag) before running the xfs_repair.