You are not logged in.

Pages: 1

#1 2016-10-17 19:17:54

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

[SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

Hi

I have new hardaware at home so I did start to install OS.
I did buy Crucial MX300 275GB version.

After I boot up from install USB I can see not errors in dmesq. And this is output of smartctl

smartctl -x /dev/sda| grep SATA                                                                                                                    :(
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x13       GPL     R/O      1  SATA NCQ Send and Receive log
SATA Phy Event Counters (GP Log 0x11)

I am using parted to create two partitions

parted /dev/sda                                                                                                                                    :(
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                            
Model: ATA Crucial_CT275MX3 (scsi)
Disk /dev/sda: 275GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  337MB  336MB  ext4         BOOT
 2      337MB   275GB  275GB  ext4         ROOT

then creating filesystem:

mkfs.ext4 -L BOOT /dev/sda1                                                                                                                        :(
mke2fs 1.43.3 (04-Sep-2016)
/dev/sda1 contains a ext4 file system
	created on Mon Oct 17 20:40:46 2016
Proceed anyway? (y,n) y
Discarding device blocks: done                            
Creating filesystem with 327680 1k blocks and 81920 inodes
Filesystem UUID: f98d8b74-7153-4679-9945-cb8b7f70b2db
Superblock backups stored on blocks: 
	8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

but there is ERROR message in dmesg

[   16.000474] r8169 0000:02:00.0 enp2s0: link up
[   16.000524] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[  771.112052] ata2.00: Enabling discard_zeroes_data
[  771.116383]  sda: sda1 sda2
[ 1003.923129] ata2.00: exception Emask 0x10 SAct 0x18020000 SErr 0x400100 action 0x6 frozen
[ 1003.923239] ata2.00: irq_stat 0x08000000, interface fatal error
[ 1003.924526] ata2: SError: { UnrecovData Handshk }
[ 1003.925830] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1003.927630] ata2.00: cmd 61/a8:88:80:15:0a/00:00:00:00:00/40 tag 17 ncq 86016 out
                        res 40/00:e4:b8:1c:0a/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 1003.930687] ata2.00: status: { DRDY }
[ 1003.932181] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1003.933949] ata2.00: cmd 61/a8:d8:10:1c:0a/00:00:00:00:00/40 tag 27 ncq 86016 out
                        res 40/00:e4:b8:1c:0a/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 1003.937279] ata2.00: status: { DRDY }
[ 1003.938916] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1003.940807] ata2.00: cmd 61/a8:e0:b8:1c:0a/00:00:00:00:00/40 tag 28 ncq 86016 out
                        res 40/00:e4:b8:1c:0a/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 1003.944438] ata2.00: status: { DRDY }
[ 1003.946215] ata2: hard resetting link
[ 1004.253187] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1004.253450] ata2.00: supports DRM functions and may not be fully accessible
[ 1004.255536] ata2.00: supports DRM functions and may not be fully accessible
[ 1004.256862] ata2.00: configured for UDMA/133
[ 1004.256915] ata2: EH complete
[ 1004.290095] ata2.00: Enabling discard_zeroes_data
[ 1004.813465] ata2.00: exception Emask 0x10 SAct 0x700000 SErr 0x400100 action 0x6 frozen
[ 1004.820905] ata2.00: irq_stat 0x08000008, interface fatal error
[ 1004.828406] ata2: SError: { UnrecovData Handshk }
[ 1004.836007] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1004.840286] ata2.00: cmd 61/a8:a0:e8:40:d3/00:00:0f:00:00/40 tag 20 ncq 86016 out
                        res 40/00:b4:38:42:d3/00:00:0f:00:00/40 Emask 0x10 (ATA bus error)
[ 1004.849039] ata2.00: status: { DRDY }
[ 1004.851990] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1004.854968] ata2.00: cmd 61/a8:a8:90:41:d3/00:00:0f:00:00/40 tag 21 ncq 86016 out
                        res 40/00:b4:38:42:d3/00:00:0f:00:00/40 Emask 0x10 (ATA bus error)
[ 1004.861128] ata2.00: status: { DRDY }
[ 1004.863520] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1004.865902] ata2.00: cmd 61/a8:b0:38:42:d3/00:00:0f:00:00/40 tag 22 ncq 86016 out
                        res 40/00:b4:38:42:d3/00:00:0f:00:00/40 Emask 0x10 (ATA bus error)
[ 1004.870813] ata2.00: status: { DRDY }
[ 1004.873331] ata2: hard resetting link
[ 1005.183241] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1005.184010] ata2.00: supports DRM functions and may not be fully accessible
[ 1005.186616] ata2.00: supports DRM functions and may not be fully accessible
[ 1005.188354] ata2.00: configured for UDMA/133
[ 1005.188532] ata2: EH complete
...
...
...
[ 1005.655195] ata2: hard resetting link
[ 1005.967414] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1005.968370] ata2.00: supports DRM functions and may not be fully accessible
[ 1005.971777] ata2.00: supports DRM functions and may not be fully accessible
[ 1005.974410] ata2.00: configured for UDMA/133
[ 1005.975224] ata2: EH complete
[ 1005.976383] ata2.00: Enabling discard_zeroes_data
[ 1006.006643] ata2.00: Enabling discard_zeroes_data
[ 1006.033303] ata2: limiting SATA link speed to 3.0 Gbps
[ 1006.033334] ata2.00: exception Emask 0x10 SAct 0x1000000 SErr 0x400100 action 0x6 frozen
[ 1006.047158] ata2.00: irq_stat 0x08000000, interface fatal error
[ 1006.054628] ata2: SError: { UnrecovData Handshk }
[ 1006.062101] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1006.066973] ata2.00: cmd 61/a7:c0:e1:d4:d3/00:00:0f:00:00/40 tag 24 ncq 85504 out
                        res 40/00:c4:e1:d4:d3/00:00:0f:00:00/40 Emask 0x10 (ATA bus error)
[ 1006.076680] ata2.00: status: { DRDY }
[ 1006.080316] ata2: hard resetting link
[ 1006.390277] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 1006.390839] ata2.00: supports DRM functions and may not be fully accessible
[ 1006.393531] ata2.00: supports DRM functions and may not be fully accessible
[ 1006.395186] ata2.00: configured for UDMA/133
[ 1006.395223] ata2: EH complete
[ 1006.431061] ata2.00: Enabling discard_zeroes_data

and link is change to lower speed

smartctl -x /dev/sda| grep SATA
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x13       GPL     R/O      1  SATA NCQ Send and Receive log
SATA Phy Event Counters (GP Log 0x11)


PLEASE, I am trying too search what does it mean but I did not find anything helpfull.
Any idea what is going on?
thank you

Last edited by jancici (2016-10-27 18:54:11)

Offline

#2 2016-10-17 20:30:00

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

Please provide more information about your hardware, such and motherboard, which sata cables you are using and anything else that might provide clues to the problem or be useful guiding further debugging.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#3 2016-10-17 20:49:12

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

This is SATA communication error resulting in speed reduction. See here. Does it work reliably at 3G?

Probably it's bad cable or bad cable routing (avoid bending SATA cables too much).

There are also weird stories like this one.

Last edited by mich41 (2016-10-17 20:54:02)

Offline

#4 2016-10-17 21:19:46

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

I have this motherboard http://www.jetwaycomputer.com/NF591.html
and using M.2 version of Crucial SSD http://www.crucial.com/usa/en/storage-s … bout-mx300

so there is not SATA cable ...

Offline

#5 2016-10-17 21:57:17

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

Update the bios/fw/uefi to the latest version if you haven't done so already, then check for any option related to the M.2 disk, or any sata/pcie options that might influence how the disk/connection works.

You should also post the full output of dmesg as some clues might be on the output you omitted.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#6 2016-10-18 07:27:51

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

That SSD is quite new and there is no fw update.
There is possible bios update for motherboard, I will try that.

I am trying to run simple speed test for SSD and looks that it is slow, it shoud be faster. Before running test I did check and SATA link was at 6GB/s

hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:   3098 MB in  2.00 seconds = 1549.00 MB/sec
 Timing buffered disk reads: 724 MB in  3.00 seconds = 241.16 MB/sec

running same test on my laptop with mSata ssd I am getting cca 400MS/sec.

during that test there is NOT any error message in log, but when I try to copy photos from USB to SSD there is a lot of errors and after while it is switching to 3GB/s.

running spee test again:

hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:   3110 MB in  2.00 seconds = 1555.31 MB/sec
 Timing buffered disk reads: 620 MB in  3.00 seconds = 206.38 MB/sec

Offline

#7 2016-10-18 08:30:43

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

I did update bios of motherboard but it did not help.  User manual saying that M.2 slot is shared with SATA2 port. There is nothing special configuration in BIOS about SATA, I can choose interface speed, so I did choose GEN3, only AHCI mode is avaible. And I did enable both ports.

this is in dmesq log after boot

[    2.318675] Bluetooth: HCI device and connection manager initialized
[    2.318682] Bluetooth: HCI socket layer initialized
[    2.318688] Bluetooth: L2CAP socket layer initialized
[    2.318699] Bluetooth: SCO socket layer initialized
[    2.323180] ata2.00: exception Emask 0x10 SAct 0x3fe000 SErr 0x400100 action 0x6 frozen
[    2.323511] ata2.00: irq_stat 0x08000000, interface fatal error
[    2.323740] ata2: SError: { UnrecovData Handshk }
[    2.323935] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.324137] ata2.00: cmd 61/10:68:e0:37:0b/00:00:00:00:00/40 tag 13 ncq 8192 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.324675] ata2.00: status: { DRDY }
[    2.324871] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.325073] ata2.00: cmd 61/08:70:10:38:0b/00:00:00:00:00/40 tag 14 ncq 4096 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.325607] ata2.00: status: { DRDY }
[    2.325793] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.325993] ata2.00: cmd 61/08:78:20:38:0b/00:00:00:00:00/40 tag 15 ncq 4096 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.326701] ata2.00: status: { DRDY }
[    2.326917] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.327150] ata2.00: cmd 61/28:80:60:38:0b/00:00:00:00:00/40 tag 16 ncq 20480 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.327743] ata2.00: status: { DRDY }
[    2.327944] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.328141] ata2.00: cmd 61/10:88:90:38:0b/00:00:00:00:00/40 tag 17 ncq 8192 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.328727] ata2.00: status: { DRDY }
[    2.328942] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.329145] ata2.00: cmd 61/18:90:d0:38:0b/00:00:00:00:00/40 tag 18 ncq 12288 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.329739] ata2.00: status: { DRDY }
[    2.329948] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.330142] ata2.00: cmd 61/08:98:f8:38:0b/00:00:00:00:00/40 tag 19 ncq 4096 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.330686] ata2.00: status: { DRDY }
[    2.330890] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.331101] ata2.00: cmd 61/10:a0:18:39:0b/00:00:00:00:00/40 tag 20 ncq 8192 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.331638] ata2.00: status: { DRDY }
[    2.331815] ata2.00: failed command: WRITE FPDMA QUEUED
[    2.332005] ata2.00: cmd 61/08:a8:38:39:0b/00:00:00:00:00/40 tag 21 ncq 4096 out
                        res 40/00:74:10:38:0b/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[    2.332537] ata2.00: status: { DRDY }
[    2.332738] ata2: hard resetting link
[    2.644782] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.645153] ata2.00: supports DRM functions and may not be fully accessible
[    2.646881] ata2.00: supports DRM functions and may not be fully accessible
[    2.648300] ata2.00: configured for UDMA/133
[    2.648371] ata2: EH complete
[    2.662358] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    2.666133] thermal LNXTHERM:00: registered as thermal_zone0

after copy some photos file to new directory on same disk I am getting this log message

[    4.672321] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    4.672327] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[    4.672331] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    4.672336] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    4.672341] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x19
[    4.691580] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[    4.692359] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[    4.692504] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[    4.692630] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[    5.818370] r8169 0000:02:00.0 enp2s0: link up
[    5.818419] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[   10.855884] random: nonblocking pool is initialized
[  238.362296] ata2.00: exception Emask 0x10 SAct 0x2000000 SErr 0x400100 action 0x6 frozen
[  238.374960] ata2.00: irq_stat 0x08000000, interface fatal error
[  238.387774] ata2: SError: { UnrecovData Handshk }
[  238.394265] ata2.00: failed command: WRITE FPDMA QUEUED
[  238.400643] ata2.00: cmd 61/f0:c8:e0:0e:ce/02:00:0f:00:00/40 tag 25 ncq 385024 out
                        res 40/00:cc:e0:0e:ce/00:00:0f:00:00/40 Emask 0x10 (ATA bus error)
[  238.409196] ata2.00: status: { DRDY }
[  238.413446] ata2: hard resetting link
[  238.723443] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  238.724138] ata2.00: supports DRM functions and may not be fully accessible
[  238.727458] ata2.00: supports DRM functions and may not be fully accessible
[  238.729626] ata2.00: configured for UDMA/133
[  238.729713] ata2: EH complete
[  238.768966] ata2.00: Enabling discard_zeroes_data
[  300.560750] ata2.00: exception Emask 0x10 SAct 0x1fff0 SErr 0x400100 action 0x6 frozen
[  300.565982] ata2.00: irq_stat 0x08000008, interface fatal error
[  300.571783] ata2: SError: { UnrecovData Handshk }
[  300.577516] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.581565] ata2.00: cmd 61/00:20:00:28:71/08:00:00:00:00/40 tag 4 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.589531] ata2.00: status: { DRDY }
[  300.593051] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.596435] ata2.00: cmd 61/00:28:00:30:71/08:00:00:00:00/40 tag 5 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.603219] ata2.00: status: { DRDY }
[  300.606623] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.610072] ata2.00: cmd 61/00:30:00:38:71/08:00:00:00:00/40 tag 6 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.616992] ata2.00: status: { DRDY }
[  300.620432] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.623864] ata2.00: cmd 61/00:38:00:40:71/08:00:00:00:00/40 tag 7 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.630936] ata2.00: status: { DRDY }
[  300.636087] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.639908] ata2.00: cmd 61/00:40:00:48:71/08:00:00:00:00/40 tag 8 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.647445] ata2.00: status: { DRDY }
[  300.650747] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.654024] ata2.00: cmd 61/00:48:00:50:71/08:00:00:00:00/40 tag 9 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.660666] ata2.00: status: { DRDY }
[  300.664014] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.667398] ata2.00: cmd 61/00:50:00:58:71/08:00:00:00:00/40 tag 10 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.674133] ata2.00: status: { DRDY }
[  300.677476] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.680817] ata2.00: cmd 61/00:58:00:60:71/08:00:00:00:00/40 tag 11 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.687449] ata2.00: status: { DRDY }
[  300.690748] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.694029] ata2.00: cmd 61/00:60:00:68:71/08:00:00:00:00/40 tag 12 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.700590] ata2.00: status: { DRDY }
[  300.703870] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.707147] ata2.00: cmd 61/00:68:00:70:71/08:00:00:00:00/40 tag 13 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.713350] ata2.00: status: { DRDY }
[  300.716397] ata2.00: failed command: WRITE FPDMA QUEUED
[  300.719453] ata2.00: cmd 61/00:70:00:78:71/08:00:00:00:00/40 tag 14 ncq 1048576 out
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.725615] ata2.00: status: { DRDY }
[  300.728702] ata2.00: failed command: READ FPDMA QUEUED
[  300.731811] ata2.00: cmd 60/00:78:00:14:28/02:00:00:00:00/40 tag 15 ncq 262144 in
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.738079] ata2.00: status: { DRDY }
[  300.741215] ata2.00: failed command: READ FPDMA QUEUED
[  300.744339] ata2.00: cmd 60/00:80:00:16:28/02:00:00:00:00/40 tag 16 ncq 262144 in
                        res 40/00:34:00:38:71/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  300.750586] ata2.00: status: { DRDY }
[  300.753665] ata2: hard resetting link
[  301.062261] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  301.062801] ata2.00: supports DRM functions and may not be fully accessible
[  301.065226] ata2.00: supports DRM functions and may not be fully accessible
[  301.067237] ata2.00: configured for UDMA/133
[  301.067436] ata2: EH complete
[  301.093645] ata2.00: Enabling discard_zeroes_data
[  301.667438] ata2: limiting SATA link speed to 3.0 Gbps
[  301.667467] ata2.00: exception Emask 0x10 SAct 0xe00 SErr 0x400100 action 0x6 frozen
[  301.683077] ata2.00: irq_stat 0x08000000, interface fatal error
[  301.691182] ata2: SError: { UnrecovData Handshk }
[  301.699538] ata2.00: failed command: WRITE FPDMA QUEUED
[  301.704800] ata2.00: cmd 61/00:48:20:72:60/08:00:16:00:00/40 tag 9 ncq 1048576 out
                        res 40/00:5c:00:96:2a/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  301.714984] ata2.00: status: { DRDY }
[  301.718887] ata2.00: failed command: READ FPDMA QUEUED
[  301.722751] ata2.00: cmd 60/00:50:00:94:2a/02:00:00:00:00/40 tag 10 ncq 262144 in
                        res 40/00:5c:00:96:2a/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  301.730554] ata2.00: status: { DRDY }
[  301.745615] ata2.00: failed command: READ FPDMA QUEUED
[  301.760717] ata2.00: cmd 60/00:58:00:96:2a/02:00:00:00:00/40 tag 11 ncq 262144 in
                        res 40/00:5c:00:96:2a/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[  301.777394] ata2.00: status: { DRDY }
[  301.782746] ata2: hard resetting link
[  302.094663] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  302.095236] ata2.00: supports DRM functions and may not be fully accessible
[  302.098653] ata2.00: supports DRM functions and may not be fully accessible
[  302.101171] ata2.00: configured for UDMA/133
[  302.101268] ata2: EH complete
[  302.126972] ata2.00: Enabling discard_zeroes_data

well, I dont have any other M.2 ssd disk to test :-(

I have 2.5'' ssd disk with classic SATA connector, I will test that one. If that will work without errors then I think that M.2 slot is not compatible with that crucial drive :-(

Offline

#8 2016-10-18 09:15:20

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

jancici wrote:

I am trying to run simple speed test for SSD and looks that it is slow, it shoud be faster.

Is it this unit factory new or secure-erased? Performance of used and not erased SSDs may be lower.

jancici wrote:

User manual saying that M.2 slot is shared with SATA2 port.

Wait, so you are saying that M.2 and SATA2 are physically connected to the same port on this Intel chip? That's a bit unorthodox thing to do on a high-speed serial link and it could be responsible for errors on either one or both of these connectors.

If you have some known-good SSD, try these things:

1. Check performance on SATA1. Maybe this Intel chip just sucks.

2. Compare perf between SATA1 and SATA2.

3. Try this M.2 SSD with unpowered disk connected to SATA2.

Last edited by mich41 (2016-10-18 09:22:37)

Offline

#9 2016-10-18 09:22:42

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

1) SSD is factory new

2) well, I did used only M.2 ssd, no other SSD/HDD drives

I am just connect  another old / used corsair SSD to SATA1 boot from M.2 drive { I already install arch there} and want to make some test ...

Offline

#10 2016-10-18 09:49:27

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

Wait, does this board have integrated port multiplier? Check dmesg. If it does than forget everything I wrote about high-speed link splitting and communication errors. In such case the multiplier may just be crap.

Offline

#11 2016-10-18 09:50:24

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

what I should looking for in dmesq?

Offline

#12 2016-10-18 09:54:12

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

so my configuration:
- Crucial SSD connected to M.2 slot
- Corsair SSD connected to SATA1 port

During boot I can see error messages. Doing "copy" files from one to another I did see errors on both ata1 ata2 links and they are switch to 3Gbps speed.

I did change interface speed in BIOS from gen3 to gen2 and there are not any erros :-(

Offline

#13 2016-10-18 10:04:51

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

forgot to post this:

lspci 
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21)
00:13.0 SATA controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller (rev 21)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 21)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 21)
00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)
00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 21)
00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 21)
00:1c.3 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #4 (rev 21)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 21)
00:1f.3 SMBus: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller (rev 21)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
00:13.0 SATA controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller (rev 21) (prog-if 01 [AHCI 1.0])
	Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 119
	I/O ports at f060 [size=32]
	Memory at 81415000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [70] Power Management version 3
	Capabilities: [a8] SATA HBA v1.0
	Kernel driver in use: ahci
	Kernel modules: ahci

Offline

#14 2016-10-18 11:31:28

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

Check also Corsair at the other port, you have nothing to lose. Even if they used passive splitting instead of port multiplier, there still is a way to make one connector almost as good as if there was no splitting.

In dmesg, look for things like

[    7.533451] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[    7.534406] ata4.15: Port Multiplier 1.1, 0x1a62:0x0003 r23, 14 ports, feat 0x0/0x0

And of course, the ultimate test would be getting some Windows installation with all OEM drivers. If anything at all can work on this hardware, this should. If Windows fails there is a possibility that they just screwed one or both SATA links on the motherboard and it will never run at 6G.

Last edited by mich41 (2016-10-18 11:42:23)

Offline

#15 2016-10-18 11:46:27

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

There is not "Port Multiplier" in dmesg. Also, they are saying that if you using M.2 slot then you should not be connect anything into port SATA2. I am guessing it is passive split.
Errors appears on both SATA ports, so I think it is configuration or compatibility issue Or that SATA chip is lazy.

I did buy board at mini-itx.com
Already communicating with them, they are responding OK so hope they will find solution with jetway ...


In worst case, I will run SATA interfaces in Gen2 speed {seting that in BIOS} :-(

Offline

#16 2016-10-18 12:08:20

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

There is not "Port Multiplier" in dmesg. Also, they are saying that if you using M.2 slot then you should not be connect anything into port SATA2. I am guessing it is passive split.
Errors appears on both SATA ports, so I think it is configuration or compatibility issue Or that SATA chip is lazy.

I did buy board at mini-itx.com
Already communicating with them, they are responding OK so hope they will find solution with jetway ...


In worst case, I will run SATA interfaces in Gen2 {seting that in BIOS} speed :-(

Offline

#17 2016-10-27 18:53:18

jancici
Member
From: svk
Registered: 2011-12-04
Posts: 192

Re: [SOLVED] Crucial MX300 : WRITE FPDMA QUEUED , limiting link spe

problem solved, it was incompatibility.
I did send that MX300 back to shop and receive money back, then I did buy intel 540s SSD and it is working without errors.

Offline

Pages: 1

Board footer

Powered by FluxBB