MX500 intermittent libata errors during startup of Manjaro Linux

SOLVED
Binary Boss

MX500 intermittent libata errors during startup of Manjaro Linux

Hi, I get these error messages occasionally with my new MX500 SSD. It doesn't happen every boot but randomly.

 

29/03/2018 19:07|ata1|irq_stat 0x00000011, unknown FIS 00478027 a0000830 00000000 08000001|
29/03/2018 19:07|ata1|SError: { UnrecFIS }|
29/03/2018 19:07|ata1|hard resetting link|

 

I'm wondering if there's an NCQ compatibility issue here with libata that needs addressing with a firmware update because I've checked power management settings and they seem fine. there's similar issues mentioned for the MX100 SSD in the kernel patch list. I thought the controller in the MX500 is different though? reference - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.15.14 (when you open the page, issue find on this page terms crucial MX100 in the browser which will take you straight to the relevant section of the mailing list) I believe I can rule out ALPM in this instance though as I have tried using max_performance as well as med_power_with_dipm, it made no difference. further reference* - https://forum.manjaro.org/t/information-crucial-mx500-500gb-ssd-ata-errors-during-system-boot/43598/... Any ideas? I have of course double-checked the data and power cables are connected properly and not damaged.

 

sudo tlp-stat -d
[sudo] password for antikythera: 
--- TLP 1.1 --------------------------------------------

+++ Storage Devices
/dev/sda:
  Model     = CT500MX500SSD1                          
  Firmware  = M3CR010 
  APM Level = none/disabled
  Status    = active/idle
  TRIM      = supported
  Scheduler = mq-deadline

  Runtime PM: control = on, autosuspend_delay = (not available)

  SMART info:
      5 Reallocated_Sector_Ct     =        0 
      9 Power_On_Hours            =       18 [h]
     12 Power_Cycle_Count         =       15 
    180 Unused_Rsvd_Blk_Cnt_Tot   =       46 
    194 Temperature_Celsius       =       33 (Min/Max 0/38)  [°C]


+++ AHCI Link Power Management (ALPM)
/sys/class/scsi_host/host0/link_power_management_policy  = med_power_with_dipm
/sys/class/scsi_host/host1/link_power_management_policy  = med_power_with_dipm

+++ AHCI Host Controller Runtime Power Management
/sys/bus/pci/devices/0000:00:11.0/ata1/power/control = on
/sys/bus/pci/devices/0000:00:11.0/ata2/power/control = on

Runtime Power Management ON actually means power management is disabled.

6 Replies
Binary Boss

Re: MX500 intermittent libata errors during startup of Manjaro Linux

I've checked the cable today to see what it is rated for as I wasn't sure if it was decent enough quality for the drive which may have been contributing to the libata issue. It's one of two that came bundled with the mainboard. It's the clipped black flat generic AWS variety which says it is rated for SATA 6Gbps on it so I think it is okay but I'm open to suggestions for some better cables anyway. I'm considering some rounded Akasa ones (AK-CBSA01-05BK) from amazon.

Binary Boss

Re: MX500 intermittent libata errors during startup of Manjaro Linux

I went ahead and got two of the Akasa cables and can now rule out the original gigabyte mainboard bundled cable as being the issue, they are compliant to the same specification as the standards information printed on the side of the new cables confirms. the error still happened when I turned the machine on this morning with the new cable in place.

 

System Information:

 

 inxi -Fxms
System:    Host: Aures Kernel: 4.15.14-1-MANJARO x86_64 bits: 64 compiler: gcc v: 7.3.1 
           Desktop: KDE Plasma 5.12.3 Distro: Manjaro Linux 17.1.7 Hakoila 
Machine:   Type: Desktop Mobo: Gigabyte model: AM1M-S2H v: x.x serial: N/A UEFI: American Megatrends v: F2 
           date: 06/20/2014 
Memory:    RAM Report: permissions: Unable to run dmidecode. Are you root? 
CPU:       Topology: Quad Core model: AMD Athlon 5350 APU with Radeon R3 type: MCP arch: Jaguar rev: 1 
           L2 cache: 2048 KB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 16368 
           Speed: 798 MHz min/max: 800/2050 MHz Core speeds (MHz): 1: 799 2: 798 3: 798 4: 798 
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] driver: radeon 
           v: kernel bus ID: 00:01.0 
           Display Server: N/A driver: ati,radeon unloaded: fbdev,modesetting,vesa tty: 124x25 
           Message: Advanced graphics data unavailable in console. Try -G --display 
Audio:     Card-1: Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 
           Card-2: Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 
           Sound Server: ALSA v: k4.15.14-1-MANJARO 
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 
           v: 2.3LK-NAPI port: e000 bus ID: 01:00 
           IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: 74:d4:35:a6:5a:1f 
Drives:    HDD Total Size: 465.76 GiB used: 7.28 GiB (1.6%) 
           ID-1: /dev/sda model: CT500MX500SSD1 size: 465.76 GiB 
Partition: ID-1: / size: 45.84 GiB used: 6.07 GiB (13.2%) fs: btrfs dev: /dev/sda3 
           ID-2: /boot size: 476.2 MiB used: 118.6 MiB (24.9%) fs: ext4 dev: /dev/sda2 
           ID-3: /home size: 376.43 GiB used: 1.10 GiB (0.3%) fs: xfs dev: /dev/sda4 
           ID-4: swap-1 size: 18.12 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 11.0 C mobo: N/A gpu: radeon temp: 11 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 197 Uptime: 1:41 Memory: 7.24 GiB used: 1.55 GiB (21.4%) Init: systemd Compilers: 
           gcc: 7.3.1 Shell: bash v: 4.4.19 inxi: 2.9.08 

kernel loggin of the same error from this morning booted with latest 4.15.14 kernel

06/04/2018 10:48	ahci 0000	0:11.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
06/04/2018 10:48	ata1	SATA max UDMA/133 abar m1024@0xfeb6e000 port 0xfeb6e100 irq 31
06/04/2018 10:48	ata2	SATA max UDMA/133 abar m1024@0xfeb6e000 port 0xfeb6e180 irq 31
06/04/2018 10:48	ata1	SATA link up 6.0 Gbps (SStatus 133 SControl 300)
06/04/2018 10:48	ata2	SATA link up 1.5 Gbps (SStatus 113 SControl 300)
06/04/2018 10:48	ata1.00	supports DRM functions and may not be fully accessible
06/04/2018 10:48	ata1.00	ATA-10: CT500MX500SSD1, M3CR010, max UDMA/133
06/04/2018 10:48	ata1.00	976773168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
06/04/2018 10:48	ata2.00	ATAPI: HL-DT-ST DVDRAM GH24NSB0, LM01, max UDMA/133
06/04/2018 10:48	ata1.00	supports DRM functions and may not be fully accessible
06/04/2018 10:48	ata1.00	READ LOG DMA EXT failed, trying PIO
06/04/2018 10:48	ata1.00	failed to get Identify Device Data, Emask 0x40
06/04/2018 10:48	ata1.00	ATA Identify Device Log not supported
06/04/2018 10:48	ata1.00	Security Log not supported
06/04/2018 10:48	ata1.00	configured for UDMA/133
06/04/2018 10:48	ata1	exception Emask 0x2 SAct 0x0 SErr 0x2000000 action 0x6 frozen t4
06/04/2018 10:48	ata1	irq_stat 0x00000011, unknown FIS 00478027 a0000830 00000000 08000001
06/04/2018 10:48	ata1	SError: { UnrecFIS }
06/04/2018 10:48	ata1	hard resetting link
06/04/2018 10:48	ata2.00	configured for UDMA/133
06/04/2018 10:48	ata1	SATA link up 6.0 Gbps (SStatus 133 SControl 300)
06/04/2018 10:48	ata1.00	supports DRM functions and may not be fully accessible
06/04/2018 10:48	ata1.00	supports DRM functions and may not be fully accessible
06/04/2018 10:48	ata1.00	configured for UDMA/133
06/04/2018 10:48	ata1	EH complete

drive information extracted from msecli

Bit Baby

Re: MX500 intermittent libata errors during startup of Manjaro Linux

This issue seems to be arch linux related as the Intel 540s suffers from the same error messages during boot.

Here and here you will find more information.

Surprinsingly only arch and it's derivates seem to be affected.

The bug causes minimal boot delay but has no further drawbacks

Binary Boss

Re: MX500 intermittent libata errors during startup of Manjaro Linux

I've read those previously too before opening this thread. They were resolved by Intel in a firmware patch so I'm surprised my much newer Crucial drive now has the issue since the two companies are supposedly in a strategic storage manufacturing partnership with regards SSD production. Either way, that demonstrates it can be addressed by Crucial.

We're in 2018 and the kernel has also been patched many times since then. I can see it's something I'll need to open a proper support ticket over. I'm aware it's not doing any harm but it still needs addressing and the issue is not exclusive to arch. libata is part of the upstream kernel packages so all distributions are therefore affected as and when they too get the latest kernel packages.

I'm guessing you didn't intend to submit that twice, either way the forum notified me twice for each post. So the forum has a few bugs as well unfortunately.
Binary Boss

Re: MX500 intermittent libata errors during startup of Manjaro Linux

 @Crucial_YogiH or any other @Crucial representative - How can I email the contents of this thread to Crucial Support? there's no live chat even though it's within the stated opening hours for the UK site and I don't really want to have to bother with telephoning when all I want to do is send this information for your firmware team to investigate if they can fix the issue or not.

there's no longer a 'more contact options' link on the support website, only the forum, live chat and telephone so please update your article accordingly

 

EDIT - I managed to contact Live Chat in USA tonight and the very helpful Kyle gave me an email address. I've sent in the pertinent information from this thread.

Tags (3)
Binary Boss

Re: MX500 intermittent libata errors during startup of Manjaro Linux

For informational purposes this is now SOLVED by Firmware M3CR022 for the MX500 released 19th June 2018. Please download it or the latest newer version from the Crucial SSD support website if you encounter the same issue.

 

Thanks @Crucial_Benny for unlocking. you can now lock again if you want Smiley Wink