https://community.solidigm.com/t5/solid-state-drives-nand/intel-540s-linux-ata-errors-in-dmesg-sata-link-reset/m-p/22590#M10703 <P>Hi,</P><P></P><P>I am experiencing read and write errors with my Intel 540s ssd, as per dmesg logs under Linux. The Windows Intel utility says the drive is healthy and so does smartctl. I have the computer's latest firmware and the latest firmware for the ssd as well (the error occured before updating as well).</P><P></P><P>I get these errors shown by dmesg.</P><P></P>[8.949378] blk_update_request: I/O error, dev sda, sector 466836144[8.949398] ata1: EH complete<P>[ 39.335649] ata1.00: exception Emask 0x1 SAct 0x3fe0400 SErr 0x0 action 0x6 frozen</P><P>[ 39.335658] ata1.00: irq_stat 0x40000008</P><P>[ 39.335665] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335675] ata1.00: cmd 60/08:50:a8:ae:b5/00:00:0e:00:00/40 tag 10 ncq dma 4096 in</P> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout) <P>[ 39.335680] ata1.00: status: { DRDY }</P><P>[ 39.335684] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335693] ata1.00: cmd 60/08:88:50:78:cf/00:00:15:00:00/40 tag 17 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335698] ata1.00: status: { DRDY }</P><P>[ 39.335701] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335709] ata1.00: cmd 60/08:90:00:a1:ce/00:00:14:00:00/40 tag 18 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335713] ata1.00: status: { DRDY }</P><P>[ 39.335717] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335725] ata1.00: cmd 60/08:98:30:5b:d3/00:00:1b:00:00/40 tag 19 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335729] ata1.00: status: { DRDY }</P><P>[ 39.335732] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335739] ata1.00: cmd 60/08:a0:e0:da:4e/00:00:15:00:00/40 tag 20 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335743] ata1.00: status: { DRDY }</P><P>[ 39.335747] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335754] ata1.00: cmd 60/08:a8:18:30:85/00:00:14:00:00/40 tag 21 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335758] ata1.00: status: { DRDY }</P><P>[ 39.335761] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335769] ata1.00: cmd 60/08:b0:d8:21:d9/00:00:14:00:00/40 tag 22 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335773] ata1.00: status: { DRDY }</P><P>[ 39.335777] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335784] ata1.00: cmd 60/20:b8:a0:60:ed/00:00:14:00:00/40 tag 23 ncq dma 16384 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335788] ata1.00: status: { DRDY }</P><P>[ 39.335792] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335799] ata1.00: cmd 60/08:c0:60:a0:f9/00:00:14:00:00/40 tag 24 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335803] ata1.00: status: { DRDY }</P><P>[ 39.335807] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335814] ata1.00: cmd 60/08:c8:50:65:0a/00:00:15:00:00/40 tag 25 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335818] ata1.00: status: { DRDY }</P><P>[ 39.335824] ata1: hard resetting link</P><P>[ 39.653111] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)</P><P>[ 39.653969] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded</P><P>[ 39.653975] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out</P><P>[ 39.653979] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out</P><P>[ 39.654471] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded</P><P>[ 39.654475] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out</P><P>[ 39.654478] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out</P><P>[ 39.654728] ata1.00: configured for UDMA/133</P><P>[ 39.664861] ahci 0000:00:17.0: port does not support device sleep</P><P>[ 39.664870] ata1.00: device reported invalid CHS sector 0</P><P>[ 39.664934] ata1: EH complete</P><P>[ 39.715671] ata1.00: exception Emask 0x0 SAct 0x1efb2aa SErr 0x0 action 0x0</P><P>[ 39.715678] ata1.00: irq_stat 0x40000008</P><P>[ 39.715684] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.715693] ata1.00: cmd 60/08:38:30:5b:d3/00:00:1b:00:00/40 tag 7 ncq dma 4096 in</P> res 41/40:08:30:5b:d3/00:00:1b:00:00/40 Emask 0x409 (media error) <P>[ 39.715698] ata1.00: status: { DRDY ERR }</P><P>[ 39.715701] ata1.00: error: { UNC }</P> Fri, 28 Jul 2017 02:18:18 GMT aburn7 2017-07-28T02:18:18Z https://community.solidigm.com/t5/solid-state-drives-nand/intel-540s-linux-ata-errors-in-dmesg-sata-link-reset/m-p/22590#M10703 <P>Hi,</P><P></P><P>I am experiencing read and write errors with my Intel 540s ssd, as per dmesg logs under Linux. The Windows Intel utility says the drive is healthy and so does smartctl. I have the computer's latest firmware and the latest firmware for the ssd as well (the error occured before updating as well).</P><P></P><P>I get these errors shown by dmesg.</P><P></P>[8.949378] blk_update_request: I/O error, dev sda, sector 466836144[8.949398] ata1: EH complete<P>[ 39.335649] ata1.00: exception Emask 0x1 SAct 0x3fe0400 SErr 0x0 action 0x6 frozen</P><P>[ 39.335658] ata1.00: irq_stat 0x40000008</P><P>[ 39.335665] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335675] ata1.00: cmd 60/08:50:a8:ae:b5/00:00:0e:00:00/40 tag 10 ncq dma 4096 in</P> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout) <P>[ 39.335680] ata1.00: status: { DRDY }</P><P>[ 39.335684] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335693] ata1.00: cmd 60/08:88:50:78:cf/00:00:15:00:00/40 tag 17 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335698] ata1.00: status: { DRDY }</P><P>[ 39.335701] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335709] ata1.00: cmd 60/08:90:00:a1:ce/00:00:14:00:00/40 tag 18 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335713] ata1.00: status: { DRDY }</P><P>[ 39.335717] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335725] ata1.00: cmd 60/08:98:30:5b:d3/00:00:1b:00:00/40 tag 19 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335729] ata1.00: status: { DRDY }</P><P>[ 39.335732] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335739] ata1.00: cmd 60/08:a0:e0:da:4e/00:00:15:00:00/40 tag 20 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335743] ata1.00: status: { DRDY }</P><P>[ 39.335747] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335754] ata1.00: cmd 60/08:a8:18:30:85/00:00:14:00:00/40 tag 21 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335758] ata1.00: status: { DRDY }</P><P>[ 39.335761] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335769] ata1.00: cmd 60/08:b0:d8:21:d9/00:00:14:00:00/40 tag 22 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335773] ata1.00: status: { DRDY }</P><P>[ 39.335777] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335784] ata1.00: cmd 60/20:b8:a0:60:ed/00:00:14:00:00/40 tag 23 ncq dma 16384 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335788] ata1.00: status: { DRDY }</P><P>[ 39.335792] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335799] ata1.00: cmd 60/08:c0:60:a0:f9/00:00:14:00:00/40 tag 24 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335803] ata1.00: status: { DRDY }</P><P>[ 39.335807] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.335814] ata1.00: cmd 60/08:c8:50:65:0a/00:00:15:00:00/40 tag 25 ncq dma 4096 in</P> res 40/00:cc:50:65:0a/00:00:15:00:00/40 Emask 0x1 (device error) <P>[ 39.335818] ata1.00: status: { DRDY }</P><P>[ 39.335824] ata1: hard resetting link</P><P>[ 39.653111] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)</P><P>[ 39.653969] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded</P><P>[ 39.653975] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out</P><P>[ 39.653979] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out</P><P>[ 39.654471] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded</P><P>[ 39.654475] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out</P><P>[ 39.654478] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out</P><P>[ 39.654728] ata1.00: configured for UDMA/133</P><P>[ 39.664861] ahci 0000:00:17.0: port does not support device sleep</P><P>[ 39.664870] ata1.00: device reported invalid CHS sector 0</P><P>[ 39.664934] ata1: EH complete</P><P>[ 39.715671] ata1.00: exception Emask 0x0 SAct 0x1efb2aa SErr 0x0 action 0x0</P><P>[ 39.715678] ata1.00: irq_stat 0x40000008</P><P>[ 39.715684] ata1.00: failed command: READ FPDMA QUEUED</P><P>[ 39.715693] ata1.00: cmd 60/08:38:30:5b:d3/00:00:1b:00:00/40 tag 7 ncq dma 4096 in</P> res 41/40:08:30:5b:d3/00:00:1b:00:00/40 Emask 0x409 (media error) <P>[ 39.715698] ata1.00: status: { DRDY ERR }</P><P>[ 39.715701] ata1.00: error: { UNC }</P> Fri, 28 Jul 2017 02:18:18 GMT https://community.solidigm.com/t5/solid-state-drives-nand/intel-540s-linux-ata-errors-in-dmesg-sata-link-reset/m-p/22590#M10703 aburn7 2017-07-28T02:18:18Z https://community.solidigm.com/t5/solid-state-drives-nand/intel-540s-linux-ata-errors-in-dmesg-sata-link-reset/m-p/22591#M10704 <P>These errors always occur on boot and wakeup from sleep and during normal system operation.</P> Fri, 28 Jul 2017 02:19:23 GMT https://community.solidigm.com/t5/solid-state-drives-nand/intel-540s-linux-ata-errors-in-dmesg-sata-link-reset/m-p/22591#M10704 aburn7 2017-07-28T02:19:23Z