T4240QDS SATA SSD detection error

[stefanschmitt]

We have connected an SSD to the SATA port of the T4240QDS and encounter the following error messages:

sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: Hardreset failed, not off-lined 0
ata2: Signature Update detected @ 504 msecs
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: limiting SATA link speed to 1.5 Gbps
ata2: Hardreset failed, not off-lined 0
ata2: Signature Update detected @ 504 msecs
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: Hardreset failed, not off-lined 0
ata2: Signature Update detected @ 504 msecs
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Here are some data from the T4240QDS:

root@t4240qds:~# cat /proc/cpuinfo

processor       : 0

cpu             : e6500, altivec
supported

clock           : 1666.666650MHz

revision        : 1.0 (pvr 8040 0010)

root@t4240qds:~#
uname -a

Linux t4240qds
3.0.51-rt75 #1 SMP Sat Dec 8 19:52:16 CST 2012 ppc64 GNU/Linux

What might be the cause for this problem?

[PavelChubakov]

It looks like that there is incorrect transfers between SSD SATA and the T4240QDS board.

Your message dump shows that disk was detected but HRESET command from the T4240QDS to the SSD SATA failed.

Perhaps your SSD SATA does not support 1.5 Gbps or your cable is incorrect.

Is there problem if different SATA is connected to your T4240QDS board?

Have a great day,
Pavel Chubakov

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[stefanschmitt]

We have tried two different other SSDs without problems. After connecting an SATA protocol analyzer we assume, that this particular SSD does not behave according to the standard, i.e. the response to the ATA command IDENTIFY DEVICE (0xec) is too slow. We are in contact with the SSD manufacturer.