AnsweredAssumed Answered

SATA SSD Detection Error

Question asked by Krishnaraj D on Jan 13, 2016
Latest reply on May 13, 2016 by Surendra Dhobale

Hi,

 

I am using P2040 Processor with Linux-3.8.13-rt9 which comply with Serial ATA 2.6 specification.  I was using SATA1 port of processor to plug in external 128GB SSD. Recently higher memory requirement came for 512 GB or above. When the 512 GB is plugged in the place of 128GB , it is not working. Errors where shown on the device boot up.

 

Both SSD are of same make, but 128GB supports SATA2 and 512GB supports SATA3. I guess SATA3 is backward compliant. I have checked the 512GB SSD  in a Ubuntu14.0 PC and it is getting detected properly. From the error log, I could find that the device is getting is detected with its size. But due to some reason, Linux is not able to mount it. Whether the size(512GB) could be the reason? If there are any pointers someone could provide, it would be awesome.

 

The relevant booting messages are copied below.

 

ata1.00: ATA-9: 2.5" SATA SSD 3MG2-P, M140815, max UDMA/133

ata1.00: 968959152 sectors, multi 1: LBA48 NCQ (depth 16/32)

ata1.00: failed to read native max address (err_mask=0x1)

ata1.00: HPA support seems broken, skipping HPA handling

ata1.00: configured for UDMA/133

scsi 0:0:0:0: Direct-Access     ATA      2.5" SATA SSD 3M M140 PQ: 0 ANSI: 5

sd 0:0:0:0: [sda] 968959152 512-byte logical blocks: (496 GB/462 GiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: Attached scsi generic sg0 type 0

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

ip_tables: (C) 2000-2006 Netfilter Core Team

TCP: cubic registered

Initializing XFRM netlink socket

NET: Registered protocol family 10

ip6_tables: (C) 2000-2006 Netfilter Core Team

sit: IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

NET: Registered protocol family 15

8021q: 802.1Q VLAN Support v1.8

Key type dns_resolver registered

fsl_dpa_macless: FSL DPAA MACless Ethernet driver ()

rtc-ds1307 0-0068: setting system clock to 2016-01-08 15:57:46 UTC (1452268666)

ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x180000 action 0x6 frozen

ata1: SError: { 10B8B Dispar }

ata1.00: failed command: READ FPDMA QUEUED

ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in

          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

ata1.00: status: { DRDY }

ata1: hard resetting link

ata1: Hardreset failed, not off-lined 0

ata1: Signature Update detected @ 504 msecs

ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

ata1.00: configured for UDMA/133

ata1.00: device reported invalid CHS sector 0

ata1: EH complete

ata1.00: NCQ disabled due to excessive errors

ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x180000 action 0x6 frozen

ata1: SError: { 10B8B Dispar }

ata1.00: failed command: READ FPDMA QUEUED

ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in

          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

ata1.00: status: { DRDY }

ata1: hard resetting link

ata1: Hardreset failed, not off-lined 0

ata1: Signature Update detected @ 504 msecs

ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40)

ata1.00: revalidation failed (errno=-5)

ata1: hard resetting link

ata1: Signature Update detected @ 504 msecs

ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

ata1.00: configured for UDMA/133

ata1.00: device reported invalid CHS sector 0

ata1: EH complete

Outcomes