Readynas Ultra 6+ Bay 5 refuses to pass a disk - 18596220

I had 4 3TB disks in my NAS for about a month all working fine, just now I went to add another 3TB disk of the same make/model etc in to Bay 5 but it refuses to pass the smart test.

I thought this was odd so I tried the other brand new 3TB disk and it fails this disk too, still odd.

So I plugged one of the HDD's in to Bay 6 and voila it works and is now currently re-striping the array, it appears that Bay 5 is either broken or something isn't right at all with it and this is a big inconvenience, I'd assume there's no way to fix this as it appears to be a hardware issue, but then again it could be software but the former sounds more promising, sadly.

The HDD's aren't on the 'HCL' which is stupid because they work fine, the 'WD30EZRS' are on the list but mine are 'WD30EZRX' which is just the faster 6GB/s model.

But this has nothing to do with the fact that Bay 5 fails both disks yet Bay 6 passed 1 and is currently re-striping.

From what I gather this will end up in me sending the device back for replacement which again is an inconvenience as it needs to be on so I don't know whether you do advanced replacements? (Worst case scenario and all)

Edit: I found this in the system.log if it helps.

May 18 07:34:57 Jelly RAIDiator: New disk detected. [Disk  5] (Jelly) : A new disk was added to the ReadyNAS.  If multiple disks have been added, they will be processed one at a time.  Please do not remove any added disk(s) during this time.
May 18 07:35:41 Jelly kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
May 18 07:35:41 Jelly kernel: ata5: irq_stat 0x00400000, PHY RDY changed
May 18 07:35:41 Jelly kernel: ata5: SError: { PHYRdyChg }
May 18 07:35:41 Jelly kernel: ata5: hard resetting link
May 18 07:35:42 Jelly kernel: ata5: SATA link down (SStatus 0 SControl 300)
May 18 07:35:47 Jelly kernel: ata5: hard resetting link
May 18 07:35:47 Jelly kernel: ata5: SATA link down (SStatus 0 SControl 300)
May 18 07:35:47 Jelly kernel: ata5: limiting SATA link speed to 1.5 Gbps
May 18 07:35:48 Jelly chronyd[2799]: Selected source 65.55.21.17
May 18 07:35:48 Jelly kernel: ata5: hard resetting link
May 18 07:35:54 Jelly kernel: ata5: link is slow to respond, please be patient (ready=0)
May 18 07:35:58 Jelly kernel: ata5: COMRESET failed (errno=-16)
May 18 07:35:58 Jelly kernel: ata5: hard resetting link
May 18 07:36:02 Jelly kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 18 07:36:02 Jelly kernel: ata5.00: configured for UDMA/133
May 18 07:36:02 Jelly kernel: ata5: EH complete
May 18 07:36:12 Jelly kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
May 18 07:36:12 Jelly kernel: ata5: irq_stat 0x00400000, PHY RDY changed
May 18 07:36:12 Jelly kernel: ata5: SError: { PHYRdyChg }
May 18 07:36:12 Jelly kernel: ata5: hard resetting link
May 18 07:36:13 Jelly kernel: ata5: SATA link down (SStatus 0 SControl 310)
May 18 07:36:18 Jelly kernel: ata5: hard resetting link
May 18 07:36:18 Jelly kernel: ata5: SATA link down (SStatus 0 SControl 310)
May 18 07:36:23 Jelly kernel: ata5: hard resetting link
May 18 07:36:24 Jelly kernel: ata5: SATA link down (SStatus 0 SControl 310)
May 18 07:36:24 Jelly kernel: ata5.00: disabled
May 18 07:36:24 Jelly kernel: ata5: limiting SATA link speed to 1.5 Gbps
May 18 07:36:24 Jelly kernel: ata5: EH complete
May 18 07:36:24 Jelly kernel: ata5.00: detaching (SCSI 4:0:0:0)
May 18 07:36:24 Jelly kernel: sd 4:0:0:0: [sde] Synchronizing SCSI cache
May 18 07:36:24 Jelly kernel: sd 4:0:0:0: [sde]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 18 07:36:24 Jelly kernel: sd 4:0:0:0: [sde] Stopping disk
May 18 07:36:24 Jelly kernel: sd 4:0:0:0: [sde] START_STOP FAILED
May 18 07:36:24 Jelly kernel: sd 4:0:0:0: [sde]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
May 18 07:36:24 Jelly kernel: scsi: killing requests for dead queue
May 18 07:36:25 Jelly RAIDiator: Disk removal detected. [Disk  5]

Regards,

Rhys