540s 'SError: { UnrecFIS }' on linux boot irregulary

[NZeju]

I'am trying to understand the meaning and severe of a totally irregular appearing error during boot according to one of the SSDs connected to my NUC5I5RYH:

New SSD M.2 240GB INTEL SSDSCKKW24 (Modell: 540s), Firmware Version: LSF036C, checked without any errors with Intels SSD Tool (with W10), SMART values unremarkable.

SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) (prog-if 01 [AHCI 1.0])

CPU: Intel(R) Core(TM) i5-5250U (Broadwell-U)

OS: ArchLinux, 4.8.12-3 x86_64 GNU/Linux

I testet reboot, boot after shutdown and boot after shutdown with power unplugged.

On every ca. fifth to tenth boot I get:

[code]

ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

ata4.00: ATA-10: INTEL SSDSCKKW240H6, LSF036C, max UDMA/133

ata4.00: 468862128 sectors, multi 16: LBA48 NCQ (depth 31/32), AA

ata4.00: READ LOG DMA EXT failed, trying unqueued

ata4.00: failed to get Identify Device Data, Emask 0x40

ata4.00: configured for UDMA/133

ata4: exception Emask 0x2 SAct 0x0 SErr 0x2000000 action 0x6 frozen t4

ata4: irq_stat 0x00000011, unknown FIS 00478027 a0000830 00000000 08000001

ata4: SError: { UnrecFIS }

ata4: hard resetting link

[/code]

Perhaps related to former June 2016 031C firmware release which provided the following changes:

* Corrected errant FIS causing BSOD when Write Cache disabled

[NZeju]

Installation 1:

lubuntu 16.04 / legacyBoot / Linux lubu1 4.4.0-21-generic # 37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

tested reboot, shutdown -> boot, shutdown -> de-energized -> boot: was able to reproduce same issue after several tries!

Dez 16 01:18:38 lubu1 kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dez 16 01:18:38 lubu1 kernel: ata4.00: ATA-10: INTEL SSDSCKKW240H6, LSF036C, max UDMA/133

Dez 16 01:18:38 lubu1 kernel: ata4.00: 468862128 sectors, multi 16: LBA48 NCQ (depth 31/32), AA

Dez 16 01:18:38 lubu1 kernel: ata4.00: READ LOG DMA EXT failed, trying unqueued

Dez 16 01:18:38 lubu1 kernel: ata4.00: failed to get Identify Device Data, Emask 0x40

Dez 16 01:18:38 lubu1 kernel: ata4.00: configured for UDMA/133

Dez 16 01:18:38 lubu1 kernel: ata4: exception Emask 0x2 SAct 0x0 SErr 0x2000000 action 0x6 frozen t4

Dez 16 01:18:38 lubu1 kernel: ata4: irq_stat 0x00000011, unknown FIS 00478027 a0000830 00000000 08000001

Dez 16 01:18:38 lubu1 kernel: ata4: SError: { UnrecFIS }

Dez 16 01:18:38 lubu1 kernel: ata4: hard resetting link

[idata]

Hi Nadotu,

Thanks for the update. We would like to engage additional resources in order to better address this situation. We will keep you posted.Regards,NC

[idata]

Hello nadotu,

While we're still reviewing your case, is there any possibility for you to test this drive using Windows*?We look forward to hearing back from you.Best regards,Carlos A.

[NZeju]

Hello Carlos;

I'am sorry but I do not have any windows licenses or installation media as I do use linux only.

Moreover I do not have the time to install another OS every other day.

Meanwhile I am using a Transcend MTS800 M.2 which works flawless and reliable in my NUC5I5RYH.

Please let me know if this problem with the 540s is a firmware issue that will be resolved with next fw update or if my ssd is defective and I should ask for replacement.

Regards;

Nadotu

[idata]

Nadotu,

As of right now, this is the only report we have regarding this issue. So we're trying to gather as much data as possible to help our engineering team get to the bottom of it.Don't worry about the Windows* test, we're just trying to check all angles in order to isolate the cause.I'll try to have an answer for your question as soon as possible. Right now, we're actively investigating this error. In the mean time, we would like to have some more information:What type of impact does this error generate? Is this drive's performance being impacted, does it cause hangs, black screen, or something else? Or are you simply (and understandably) concerned by the error and wish to know more about it in order to resolve it?We look forward to hearing back from you.Best regards,Carlos A.