topic Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width in Notebook / Netbook

E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width x2)

dgtdabbler — Mon, 02 Dec 2024 17:01:43 GMT

Hello,

On compatible SSD I could not find any information in manual and on OEM webpage. Are you possibly aware of any recommended list of compatible NVMe and how to find it?

Please can you advise on how to handle the PCIe mismatch of ‘PCIe bridge and NVMe’ and the related PCIe error ‘RxErr’, described below?

Your advise is highly appreciated!

Kind Regards,

dgtdabbler

Akoya E14412, Board SF40CM, AMI1.02.00.MN.V05, i5-10210U, 16 GB RAM, 1x m.2 slot for SSD,

NVMe WD Blue SN570 1TB (firmware updated to ver 234110WD, 3500 MB/s (read), PCIe Gen3 x4, acc, to OEM spec.)

---

Brief Summary

Linux was installed at the very begin on this notebook, on a brandnew NVMe ‘WD Blue SN570 1TB’, which I inserted in the notebook’s sole m.2 slot for SSD. Disk benchmark test shows 1.6 GB/s (read) and 1.4 GB/s (write), fine for my applications. The system has been running nice for long time, incl. browser, e-mail client, LibreOffice. My favourite notebook!

The Concern

When I check the system messages from sudo dmesg, I note PCIe errors ‘RxErr’ ongoing. Sifting thru the entire dmesg, there is mentioned:

- ‘01:00.0 15,752 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x2 link at 0000:00:1d.0’
(so, the width of the NVMe WD Blue SN570 1TB is limited from x4 to x2, when this link is set up/negotiated, that’s how I read this)

- ‘capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link’

(this likely relates to the NVMe WD Blue SN570 1TB also, I think. The WD Blue SN570 1TB can handle PCIe x4, acc to OEM WD. Not sure if alternatively this message (the point ‘PCIe x4’) could relate to the capability of the PCIe bridge, possibly.)

HeLo@E14412:~$ sudo dmesg -T | grep --color -i -E ‘00.1d.0|01:00.0|bandwith|RxErr’
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0: [8086:02b0] type 01 class 0x060400
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0: PTM enabled (root), 4ns granularity
[Sa Nov 30 13:15:03 2024] pci 0000:01:00.0: [15b7:501a] type 00 class 0x010802
[Sa Nov 30 13:15:03 2024] pci 0000:01:00.0: reg 0x10: [mem 0xb1200000-0xb1203fff 64bit]
[Sa Nov 30 13:15:03 2024] pci 0000:01:00.0: reg 0x20: [mem 0xb1204000-0xb12040ff 64bit]
[Sa Nov 30 13:15:03 2024] pci 0000:01:00.0: 15.752 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x2 link at 0000:00:1d.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0: PCI bridge to [bus 01]
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0:   bridge window [mem 0xb1200000-0xb12fffff]
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0: PCI bridge to [bus 01]
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0:   bridge window [mem 0xb1200000-0xb12fffff]
[Sa Nov 30 13:15:03 2024] pci 0000:00:1d.0: Adding to iommu group 11
[Sa Nov 30 13:15:03 2024] pci 0000:01:00.0: Adding to iommu group 14
[Sa Nov 30 13:15:04 2024] pcieport 0000:00:1d.0: PME: Signaling with IRQ 122
[Sa Nov 30 13:15:04 2024] pcieport 0000:00:1d.0: AER: enabled with IRQ 122
[Sa Nov 30 13:15:04 2024] pcieport 0000:00:1d.0: DPC: enabled with IRQ 122
[Sa Nov 30 13:15:04 2024] pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[Sa Nov 30 13:15:04 2024] nvme 0000:01:00.0: platform quirk: setting simple suspend
[Sa Nov 30 13:15:04 2024] nvme nvme0: pci function 0000:01:00.0
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0: AER: Corrected error message received from 0000:00:1d.0
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0:   device [8086:02b0] error status/mask=00000001/00002000
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0:    [ 0] RxErr                  (First)
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0: AER: Corrected error message received from 0000:00:1d.0
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0:   device [8086:02b0] error status/mask=00000001/00002000
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0:    [ 0] RxErr                  (First)
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0: AER: Corrected error message received from 0000:00:1d.0
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[Sa Nov 30 13:15:07 2024] pcieport 0000:00:1d.0:   device [8086:02b0] error status/mask=00000001/00002000
...

List of PCIe devices and their ‘PCIe slot ID’ as provided by sudo lspci -PPb:

- 00:1d.0 is the PCIe slot of the PCI bridge

- 01:00.0 is the the NVMe WD Blue SN570 1TB, linked to 00:1d.0 PCIe bridge

HeLo@E14412:~$ sudo lspci -PPb # List of PCIe devices
00:00.0 Host bridge: Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH-LP Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi WiFi
00:14.5 SD Host controller: Intel Corporation Comet Lake PCH-LP SCS3
00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller
00:15.1 Serial bus controller: Intel Corporation Comet Lake Serial IO I2C Host Controller
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
00:1a.0 SD Host controller: Intel Corporation Device 02c4
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller
00:1f.3 Audio device: Intel Corporation Comet Lake PCH-LP cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH-LP SMBus Host Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake SPI (flash) Controller
00:1d.0/01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN570 NVMe SSD 1TB
00:1d.4/02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

Details (by lspci) on PCI bridge: Capabilities, Status, Control, Width, Latencies (and downgrade) of/for Devices, Control and Link are listed using sudo lspci -PPvvv, by filtering these key words with grep (below). And in analogy details for WD Blue SN570 1TB (further below). Additionally, on memory organisation, there is mentioned ‘disabled’ a couple of times. Is that possibly a hint on the mismatch's reason?

HeLo@E14412:~$ sudo lspci -PPvvv -s 00:1d.0 | grep --color -i -E '00:1d.0|status|bridge|capabilities|lnkcap|lnkctl|lnksta|width x.?|speed|.?GT/s|downgraded|latency|.?ns |driver|nvme|pcieport'
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) (prog-if 00 [Normal decode])
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: f000-0fff [disabled] [16-bit]
        Memory behind bridge: b1200000-b12fffff [size=1M] [32-bit]
        Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff [disabled] [64-bit]
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
        Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
                LnkCap: Port #9, Speed 8GT/s, Width x2, ASPM L1, Exit Latency L1 <16us
                LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
                LnkSta: Speed 8GT/s, Width x2
                SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
                RootSta: PME ReqID 0000, PMEStatus- PMEPending-
                LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
                LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
                LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: Elitegroup Computer Systems Comet Lake PCI Express Root Port
        Capabilities: [a0] Power Management version 3
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [100 v1] Advanced Error Reporting
        Capabilities: [140 v1] Access Control Services
        Capabilities: [150 v1] Precision Time Measurement
        Capabilities: [200 v1] L1 PM Substates
        Capabilities: [220 v1] Secondary PCI Express
                LnkCtl3: LnkEquIntrruptEn- PerformEqu-
        Capabilities: [250 v1] Downstream Port Containment
        Kernel driver in use: pcieport
HeLo@E14412:~$ 
HeLo@E14412:~$ sudo lspci -PPvvv -s 01:00.0 | grep --color -i -E '01:00.0|status|bridge|capabilities|lnkcap|lnkctl|lnksta|width x.?|speed|.?GT/s|downgraded|latency|.?ns |driver|nvme|pcieport'
00:1d.0/01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN570 NVMe SSD 1TB (prog-if 02 [NVM Express])
        Subsystem: Sandisk Corp SanDisk Ultra 3D / WD Blue SN570 NVMe SSD (DRAM-less)
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Capabilities: [80] Power Management version 3
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [90] MSI: Enable- Count=1/32 Maskable- 64bit+
        Capabilities: [b0] MSI-X: Enable+ Count=17 Masked-
        Capabilities: [c0] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <1us, L1 unlimited
                LnkCap: Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <8us
                LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
                LnkSta: Speed 8GT/s, Width x2 (downgraded)
                LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
                LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
                LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
        Capabilities: [100 v2] Advanced Error Reporting
        Capabilities: [150 v1] Device Serial Number 00-00-00-00-00-00-00-00
        Capabilities: [1b8 v1] Latency Tolerance Reporting
                Max snoop latency: 3145728ns
                Max no snoop latency: 3145728ns
        Capabilities: [300 v1] Secondary PCI Express
                LnkCtl3: LnkEquIntrruptEn- PerformEqu-
        Capabilities: [900 v1] L1 PM Substates
        Kernel driver in use: nvme
        Kernel modules: nvme
HeLo@E14412:~$

Do these messages point on hardware/setting issues, I could inspect, check, fix, adjust, optimise, ..?

Please can you advise how to handle the mismatch and get rid of the error message?

If any additional information is needed, please let me know.

As mentioned above, your support is highly appreciated!

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Tue, 03 Dec 2024 06:58:49 GMT

Hello,

Here a quick correction: In the list of PCIe devices I highlighted the wrong line in red: '00:1d.4 PCI bridge: ... PCI Express Root Port #13' is the port, which links the '02:00.0 Ethernet controller', but NOT the NVMe WD Blue SN570 1TB. Sorry for causing confusion.

Actually '00:1d.0 PCI bridge .. PCIe Root Port #9' is the port, which links '01:00.0 NVMe WD Blue SN570 1TB'. Here is how I should have highlighted correctly,:

...
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0)
...
00:1d.0/01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN570 NVMe SSD 1TB
00:1d.4/02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

The notebook is labelled with MSN30032849.

Kind Regards,

dgtdabbler

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Thu, 12 Dec 2024 15:13:00 GMT

Reusability of NVMe ‘WD Blue SN570 1TB’

Hello,

Thank you for accepting the present case in the Medion Community system.

Confirmation of the reusability of NVMe ‘WD Blue SN570 1TB would be a nice step to go forward, I thought. Below a summary of tests performed accordingly. Since the test results do not indicated a crucial failure, I finally decided to reuse the NVMe.

Please advise on how to improve my humble assessment of the NVMe’s reusability and my attempts to interpret the related test-results. Your support is is highly appreciated!

Kind Regards

dgtdabbler

Overview on contributions, recently uploaded

(A)) PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width x2)

B) Reusability of NVMe ‘WD Blue SN570 1TB’

---

B) Reusability of NVMe ‘WD Blue SN570 1TB’ - (Decision: NVMe shall be reused for the time, see below)

1) Command: sudo smartctl --all /dev/nvme0

Result:

- No hint on message ‘RxErr’ or crucial error was indicated.

- SMART – health test: passed

- Percentage used: 0%

- Power cycles (24000+) and unsafe shutdowns (23000+) appear pretty high

- Error Information Log Entries: 2 (not fully clear about importance and consequences)

HeLo@E14412:~$ sudo smartctl --all /dev/nvme0
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-27-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       WD Blue SN570 1TB
Serial Number:                      2147C5472405
Firmware Version:                   234110WD
PCI Vendor/Subsystem ID:            0x15b7
IEEE OUI Identifier:                0x001b44
Total NVM Capacity:                 1.000.204.886.016 [1,00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1.000.204.886.016 [1,00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            001b44 4a49c5ab37
Local Time is:                      Wed Dec 11 21:03:32 2024 CET
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     80 Celsius
Critical Comp. Temp. Threshold:     85 Celsius
Namespace 1 Features (0x02):        NA_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     4.20W    3.70W       -    0  0  0  0        0       0
 1 +     2.70W    2.30W       -    0  0  0  0        0       0
 2 +     1.90W    1.80W       -    0  0  0  0        0       0
 3 -   0.0250W       -        -    3  3  3  3     3900   11000
 4 -   0.0050W       -        -    4  4  4  4     5000   44000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         2
 1 -    4096       0         1

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        23 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    9.186.753 [4,70 TB]
Data Units Written:                 6.877.912 [3,52 TB]
Host Read Commands:                 52.209.910
Host Write Commands:                59.937.179
Controller Busy Time:               477
Power Cycles:                       24.836
Power On Hours:                     959
Unsafe Shutdowns:                   23.528
Media and Data Integrity Errors:    0
Error Information Log Entries:      2
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged

2) Command: sudo nvme smart-log /dev/nvme0

Result:

- No hint on message ‘RxErr’ or crucial error was indicated.

- critical_warning: 0

- percentage_used: 0

- endurance group critical warning summary: 0

- Power cycles (24000+) and unsafe shutdowns (23000+) appear pretty high

- num_err_log_entries: 2 (not fully clear about importance and consequences)

HeLo@E14412:~$ sudo nvme smart-log /dev/nvme0 
Smart Log for NVME device:nvme0 namespace-id:ffffffff
critical_warning                        : 0
temperature                             : 24°C (297 Kelvin)
available_spare                         : 100%
available_spare_threshold               : 10%
percentage_used                         : 0%
endurance group critical warning summary: 0
Data Units Read                         : 9.186.770 (4,70 TB)
Data Units Written                      : 6.878.000 (3,52 TB)
host_read_commands                      : 52.210.320
host_write_commands                     : 59.939.020
controller_busy_time                    : 477
power_cycles                            : 24.836
power_on_hours                          : 959
unsafe_shutdowns                        : 23.528
media_errors                            : 0
num_err_log_entries                     : 2
Warning Temperature Time                : 0
Critical Composite Temperature Time     : 0
Thermal Management T1 Trans Count       : 0
Thermal Management T2 Trans Count       : 0
Thermal Management T1 Total Time        : 0
Thermal Management T2 Total Time        : 0

3) QDiskInfo (Linux tool with graphical user interface)

- Result is similar to that from sudo nvme smart-log

- No hint on message ‘RxErr’ or crucial error was indicated.

- Health Status: Good, 100 %

- critical_warning: 0

- percentage_used: 0

- endurance group critical warning summary: 0

- Power cycles (24000+) and unsafe shutdowns (23000+) appear pretty high

- Num Err Log Entries: 2 (not fully clear about importance and consequences)

4) WD Dashboard is the OEM’s (Western Digital) diagnose tool for this NVMe and requires to be run under Windows. Accordingly I used another (Windows-based) computer, connected the WD Blue SN570 via external NVMe to USB adapter (to be clear: with the notebook’s m.2 socket left free/empty) and ran WD Dashboard with following results:

- Short and Extended Diagnose were ‘..successfully completed’

- Both, Short and Extended Diagnose with result ‘no problems were detected’ and

- ‘Health test .. PASSED’ was confirmed.

- No hint on message ‘RxErr’ or crucial error was indicated.

5) WD Dashboard diagnose, with WD Blue SN570 1TB situated in the notebook’s m.2 socket

- WD Dashboard results were same as in test (4), above.

- Additionally, WD Dashboard offered a Trim-function, which I activated and ran for a day.

- Utilised are 2 lanes (of 4 provided by NVMe) by Windows, acc. to WD Dashboard (by analogy with Linux)

- Searching for ‘RxErr’: Sifting thru the system I could not find a hint on such error, due to lack of skills.

- No hint on message ‘RxErr’ or crucial error was indicated.

6) Firmware upgrade to 234110WD was successfully implemented using WD Dashboard.

- No hint on message ‘RxErr’ or crucial error was indicated.

7) Partitioning and formatting (EXT4 and FAT) succeeded on the WD Blue SN570 1TB, connected via external NVMe to USB adapter (with the notebook’s m.2 socket left free/empty), by using command sudo cfdisk /dev/nvme0n1 as well as by using the Linux utility Disks, each without failure indication. Result is displayed by command

sudo fdisk -l

HeLo@E14412:~$ sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WD Blue SN570 1TB                       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8ec5c9bd

Device         Boot     Start        End    Sectors  Size Id Type
/dev/nvme0n1p1        2101248  136318975  134217728   64G 83 Linux
/dev/nvme0n1p2      136318976  236982271  100663296   48G 82 Linux swap / Solaris
/dev/nvme0n1p3      236982272 1952452607 1715470336  818G 83 Linux
/dev/nvme0n1p4 *         2048    2101247    2099200    1G  c W95 FAT32 (LBA)

😎 Debian could be installed on the WD Blue SN570 1TB (connected via external NVMe to USB adapter (to be clear again: with the notebook’s m.2 socket left free/empty), by running a debian-live-system from USB stick.

- Then debian booted and ran nice and flawless during a test, which I ended after a week of daily use.

- Here, the message ‘RxErr’ did not show up, obviously since the WD Blue SN570 was linked via PCIe SATA Bridge/AHCI (so no longer via PCIe NVMe Bridge as before).

(Only, with this test, flawless communication of the WD Blue SN570 1TB via NVMe with the PCIe Bridge can not be confirmed, of course.)

- This result (no more ‘RxErr’-messages) is very nice – however the operating system is sitting on the NVMe situated in the external adapter, connected via unsteady USB cable .. not really what you prefer for every day use. For the better, the NVMe has to go back into the m.2 socket on the notebook’s main board, to ensure a mechanically stable connection.

- No hint on crucial error of WD Blue SN570 1TB was indicated. The result may be an indication of a conflict related to the WD Blue SN570 1TB’s link to the PCIe NVMe Bridge.

Considering all points (1 to 😎 above, I decided to reuse the NVMe WD Blue SN570 1TB, because none of the utilised tools and tests indicated a crucial failure of the NVMe, and despite clarification is still lacking for following annoying message/test result:

- RxErr message ongoing with NVMe installed in the notebook’s m.2 socket (so, connected via PCIe NVMe Bridge)

- unsafe shutdowns count > 23000

- power on count > 24000

Your view on the reusability of the WD Blue SN570 1TB is highly appreciated!

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Fri, 13 Dec 2024 10:53:53 GMT

Hardware test & visual inspect

Hello,

Thank you again for accepting the present case in the Medion Community system. Getting your advice would be really great!

Hardware test & visual inspect might help with identifying, what disturbs the link of the WD Blue SN570 1TB to the PCIe NVMe Bridge (and causes the message ‘RxErr’), or confirm the hardware’s reusability, I think. Related tests and results are described below.

Please could you advise, how to simplify and get forward with this? Your recommendation is highly appreciated!

Kind Regards

dgtdabbler

Overview on contributions, recently uploaded

(A)) PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width x2)

B) Reusability of NVMe ‘WD Blue SN570 1TB’ - (Decision: NVMe shall be reused for the time)

C) Hardware test & visual inspect

---

C) Hardware test & visual inspect – (Result: Deficiency not remedied. Message RxErr is ongoing, see below)

Hardware test & visual inspect, performed so far

- memtest86+ (for one day)

- remove NMVe WD Blue SN570 1TB, inspect it and the socket for deficiencies/dirt, reinstall

- remove related data cable, inspect it and the connectors and the mini board for deficiencies/dirt, reinstall

- remove wifi&bluetooth card, inspect it and the socket for deficiencies/dirt, reinstall

- disconnect BIOS backup battery (and battery pack), press the start button, then after 1 day reconnect, set up BIOS

(- assessment of the WD Blue SN570 1TB’s reusability and its firmware update was performed as described before)

(Required, prior to any remove/dis-&reconnect/reinstall: Disconnect battery, press start button for 10+ sec, don’t touch any electrical contact/pin, make sure any potential is equalised/statics grounded, ..)

Upon completing the above tests and inspections the issue still exists, unfortunately: The message ‘RxErr’ is ongoing.

Accordingly, still open/not entirely clarified are:

- Data cable, mini board, socket, connectors still might be faulty, though ‘no findings’ were discovered during visual inspect.

- To confirm the WD Blue SN570 1TB’s NVMe-capabilities, it might be tested in another computer.

- Well, the mother board’s controller/bridge/port capabilities .. on especially this item, I kindly ask for your recommendation.

Result of hardware test & inspect: Deficiency is not remedied. Message RxErr is ongoing.

Please could you advise, how to simplify and get forward with this?

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Wed, 18 Dec 2024 14:20:50 GMT

Capabilities and compatibility of the notebook’s SSD port

Hello,

On the notebook’s SSD capabilities and compatibility I could not find any relevant information in the manual and on the webpages of Medion (and EPC), please see details below.

How to confirm the notebook’s SSD port capabilities and compatibility, please could you advise? Your recommendation is highly appreciated!

Kind Regards

dgtdabbler

Overview on contributions, recently uploaded

(A)) PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width x2)

B) Reusability of NVMe ‘WD Blue SN570 1TB’ - (Decision: NVMe shall be reused for the time)

C) Hardware test & inspect - (Deficiency is not remedied. Message RxErr is ongoing)

D) Capabilities/compatibility of the notebook’s SSD port

---

D) Capabilities/compatibility of notebook’s SSD port (Result: No info in manual and on Medion and EPC webpage, see the following)

Information on the notebook’s capabilities typically are made available in the notebook’s (motherboard’s) manual and on the manufacturer’s webpage (by including updates). Here is what I collected:

1) Medion instruction manual:

The manual is silent on compatible SSD and on the notebook’s SSD port capabilities. Whether the notebook supports SATA/AHCI, PCIe/NVMe or both, is not mentioned, as well as the PCIe generation and available lanes (manual's table of contents below).

How/where to get data on notebook’s SSD port capabilities and compatible SSD?

2) Medion search tool on webpage:

The Medion search tool (www.medion.com/sg/_lightbox/gsa.php), upon submitting one of the notebook’s identification numbers (E14412, MD64010, MSN30032849), replies just ‘no drivers/software/manuals found’.

How to get information on notebook’s SSD port capabilities and compatible SSD from this Medion tool?

3) Another Medion search tool on webpage:

The other Medion tool (www.medion.com > Service > Service Portal), upon submitting anyone of the notebook’s identification numbers, does not reply at all. It simply keeps on showing ‘busy’ (a ‘spinning circle’) for ever. I unsuccessfully tried for a couple of days.

How to get information from this Medion tool?

4) Medion Service Shop and description of offered parts and their features:

Searching in the Medion service shop (www.medion.com > Service > Service Shop ), there are listed i.e.

- the notebook with its typical identification numbers

- the SSD board (but without details on m.2 slot configuration)

- the CPU (Intel i5-10210U 1.6GHz 15W SRGKY B)

- .. furthermore pad, monitor, hinge, power supply, etc.

- but nothing on SSD is mentioned

The descriptions of parts, offered in the Medion Service Shop, do not help figuring out the missing information on the notebook’s SSD port capabilities.

5) ECS webpage (the notebook SF40CM is an ECS make) - Download Centre:

The ECS download centre (ECS Home > Support > Download Centre) does not find the notebook SF40CM.

6) ECS webpage – Home > Search

The search tool (ECS Home > Search) finds the notebook SF40CM and lists following details (see also at the bottom of the screenshot):

14" performance laptop Compared to the traditional HDDs,

SSD offer better read/write speeds and booting-up times.

SSD storage 30% faster speed. It is compliant with MIL-..

Clicking forward, the ECS tool displays another page, listing once again SF40CM (14.’’) now with the options ‘Specification/Download/FAQ/Support’. But as soon as you click on one of these options, the tool displays ‘oops, something went wrong’.

That's kind of strange, isn't it? (For other similar board IDs, the tool actually lists appropriate details.)

7) A couple of recommended replacement NVMe SSD for this notebook are listed in an online offer on the webpage of ‘ipc-c…’: 990 EVO PCIe NVMe SSD .., 970 EVO ((PCIe)).., P3 PCIe NVMe SSD . This webpage I found, when searching the net for keywords ‘Medion Akoya E14412 (SF40CM) Ersatzteile’. Not sure whether these SSD fit the present notebook, since its MSN is not mentioned in the offer, only just E14412 and MD64010 match the offer. (Medion Service Support and Shop do not mention/suggest any replacement SSD at all, unfortunately. That is why I included the offers of ipc-c here.)

😎 The built-in m.2 socket is M-key (below photo). For m.2-module keyings the Wikipedia article ‘m.2’ lists ‘M’ and ‘B’ , so M-key and B-key:

M - PCIe x4 (NVMe), SATA, SMBus

B - PCIe x2 (NVMe), SATA, USB, UIM, SSIC, UART-I2C, SMBus

Some motherboards however might not provide full support of the SSD port – acc. to a few publications mentioned in the literature list of Wikipedia article ‘NVM Express’. The involved authors recommend to see the motherboard/computer manufacturer’s manual, to figure out the supported SSD port capabilities and features.

The WD Blue SN570 1TB involved with the message ‘RxErr’ is displayed in the photo. The originally supplied SSD ‘S3+ m.2 SATA 2280 SSD 512GB (B+M key)’ was removed at the very begin of setting up and using the notebook.

Result, looking at above items 1 to 9: No final clarity about the notebook’s and its SSD port capabilities. Still not.

Any idea on how to simplify and ease the way of getting clarity on the notebook's SSD capabilities, compatible SSD and on how to get rid of the 'RxErr' message, mentioned earlier? Your advice is highly appreciated.

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

daddle — Thu, 19 Dec 2024 07:35:00 GMT

@dgtdabbler

Quite a lot of questions. But you misunderstand the purposes of a forum. We (other Users) likely give you some information, but we can not make a complete tutorial.

This is a User helping Users Forum vor owners of Medion computers.

Because the Medion service page is offline (some IT problems), we other users cannot at he moment give you

any further information, except another user with exact the same notebook can help you out.

But before we first need to know about which computer you are talking about. Second ECS pc we can not support at all. Your pictures can not be seen yet, they first have to be authorized by a moderator.

Edit:

Now the pictures are seen, but I also see you want a general teaching in M.2 SSDs incl the diagnosis of fault messages, including even LInux questions. Second you are talking about two different PCs, a Medion E 14412 and an ECS SF40CM. Or is the ECS SF 40 the mainboard?

I do not think somebody can help you here, your pages filling screenshot no one feels for reading, nor does someone does understand them really.

Me surely not.

Sorry, Cheers, daddle

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

Fishtown — Wed, 18 Dec 2024 21:58:41 GMT

Hi @dgtdabbler

driver:

https://www.medion.com/gb/service/product-detail/30032849

bye Fishtown

EDIT: Unfortunately, I “have nothing to do with Linux”. This page may be able to help you with upgrade options:

https://linux-hardware.org/?probe=6d14dd3a06&upgrade

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Thu, 19 Dec 2024 12:21:00 GMT

Hi @Fishtown and @daddle ,

Many thanks! Very concise reply. 'Driver update to get rid of 'RxErr'-message (and possibly to upgrade the motherboard's SSD compatibility)', that's what I read between your lines.

'Driver Package MEDION AKOYA E1441x Notebook Series / Version: / OS: Win 11 64bit' is the item listed for download, when opening the recommended link. So I cannot prevent any longer and finally need to install Win11 64bit on the notebook, to prepare running the update, as the 'Win11 64bit' in the driver packages name may indicate.

Your support is very welcome! Thank you very much again.

Bye/cheers

dgtdabbler

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Fri, 21 Mar 2025 09:46:18 GMT

Hi @Fishtown,

Thanks again for pointing me to the updated Windows driver set from Medion and to the tool/webpage Linux-Hardware.org in your above message.

Whether or not the updated Windows driver set is helpful to overcome the occurring RxErr-messages and PCIe mismatch - still I do not have the answer to this. Here is why: When running the Windows installation from an USB boot stick, the Windows installer does not complete the installation, but continues asking me to provide Windows drivers in an endless loop. Providing your/Medion’s updated Windows driver set or the old driver set originally supplied with the notebook, on either an USB Stick or otherwise on the WD Blue SN570 1TB, all that does not make any difference. The loop runs endlessly, with no hint on how to exit. Several installation attempts failed. I gave up this. Running Linux is my focus, not Windows.

The tool/webpage Linux-Hardware.org lists 3 similar notebooks (your link https://linux-hardware.org/?probe=6d14dd3a06&upgrade 😞

Using this webpage’s menu item <Find Computer> and selecting Mfg. “Year 2021”, Type “Notebook”, Vendor “Medion”, Model “E14412” the webpage lists 3 Medion notebooks with CPU i5-10210U, mem 16 GB, 14” display and the drive "S3+ S3SSDA512-ECS-1 512 GB" (a SATA-SSD).

All 3 listed notebooks show a configuration similar to that of the present notebook as originally supplied by Medion, so incl the “S3+ S3SSDA512-ECS-1 512 GB”. Since this is a SATA-SSD, it is linked to the notebook’s SSD port via AHCI, as confirmed by Linux-Hardware.org. However, there is no hint from Linux-Hardware.org on a NVMe-SSD in any of the 3 similar notebooks. So, there is no example with a NVMe-SSD, I could learn from, unfortunately.

Nevertheless, the present notebook (here in front of me), is equipped with the WD Blue SN570 1TB, which is linked via pcieport (NVMe protocol) to the notebook’s PCIe port. Only, it still runs with ongoing RxErr-messages, as already described at the begin of this thread.

Any further idea on how to find a NVMe (a list of NVMe s) compatible with the present notebook, please let me know.

Kind Regards

dgtdabbler

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

daddle — Fri, 21 Mar 2025 22:15:46 GMT

@dgtdabbler

I do admire your patience, with the drive, and with us, the unknowing lot. 😉

First of all your list of Linux protocol or faults doesn't help us really to understand a lot, at least me. But I also never have really seen an experienced Linux user here in the forum. 😏 So first some questions

1. Does your NB has two physical M.2 slot?
2. If you look direction into the M.2 Port is the key notch (the place with the missing contact) on the left or right sight side
the left is a B- , the right is a M-key notch Most PCIe M.2 SSDs have a M-key. Most SATA M.2 SSDs nowadays have a B- and aM key.
But the slots, or with the B. or the M notch can accept or a PCIe or a SATA. It depends on th eprotocol which is linked to th eport.
Click here also --> https://en.wikipedia.org/wiki/M.2
Look under --> Form factors and keying
3. If you try to install the Windows with an USB stick? Is it an installaion stick made with Microsoft MediaCreatonTool? If not please do so. For Win 10 or Win 11?
4. You try to install on the now again empty WD Blue SN570 ?
Or is it sttill partitioned by Linux with Ext4 or other schemes? Just wipe the newSSD completly.
5. Put the Intel VDM Drivers on the installation stick as well. They are needed for driving an PCIe M.2 drive.You can load them before installation begins with the F6 tab.. You will be asked for it
6. Before you begin, take the SATA M.2 SSD out.. If there is a Win Installation on the machine already, the installation might go wrongly

daddle

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Wed, 17 Sep 2025 18:10:24 GMT

Hi @daddle,

Many thanks for your helpful hints on installing Win11. Following your advice, the installation proceeded without asking for any drivers and successfully completed partitioning, unpacking and copying files. After a while however the installation process aborted with error messages, indicating disconnection of the NVMe from the PCI bus, see below.

Because the error is related to the connection/compatibility of NVMe and the notebook’s related port, I tried to find a replacement NVMe on the Medion service webpage, earlier indicated by @Fishtown. This nice and clear-arranged Medion webpage however does not offer/suggest any replacement SSD (instead just parts like touch pad, display, power supply, hinge, ..). The related Medion manual is silent on the notebook’s SSD port capabilities.

Which NVMe is recommended by the OEM Medion to replace or upgrade the originally built in SSD? Please could you help with this? I’m very happy getting your support.

Kind regards
dgt.dabbler

Reply to Questions as submitted by @daddle on 21th March 2025:
‘.. So first some questions’

1. Does your NB have two physical M.2 slots?

R: No, the Medion E14412/MD64010 has just one single (one and only) M.2 slot for SSD.

2. If you look direction into the M.2 Port is the key notch (the place with the missing contact) on the left or right sight side
the left is a B- , the right is a M-key notch Most PCIe M.2 SSDs have a M-key. Most SATA M.2 SSDs nowadays have a B- and a M-key.
But the slots, or with the B. or the M notch can accept or a PCIe or a SATA. It depends on the protocol which is linked to the port.
Click here also --> https://en.wikipedia.org/wiki/M.2
Look under --> Form factors and keying

R: The notebook’s single M.2 slot is M-key (notch on right side, by view from SSD into the opening of the notebook’s M.2 slot), see also the photo of the notebook’s M.2 slot and NVMe in above section D, of Dec 18th, 2024.

The notebook could successfully detect and link both types of SSD situated in its single M.2 slot, a SATA SSD and a NVMe SSD:

- If a SATA SSD like ‘S3+ S3SSDA512-ECS-1 512 GB’ is situated in the M.2 slot, it is linked to the notebook via AHCI.

- If a NVMe SSD like ‘WD Blue SN570 1TB’ is situated in the M.2 slot, it is linked to the notebook via pcieport (→PCI 00:1d.0/01:00.0). The established link involves the limitation to just 2 lanes (width x2) and it involves repeatedly occurring error messages ‘RxErr’, related to the PCI bus.

- The ‘WD Blue SN570 1TB’ and the notebook’s M.2 slot, both are M-key. The WD Blue SN570 1TB provides 4 lanes. In contrast, the notebook apparently provides just 2 lanes. The result is a limitation (downgrade) of the established link to just 2 lanes, and ongoing ‘RxErr’ messages.
3. If you try to install the Windows with an USB stick? Is it an installation stick made with Microsoft MediaCreatonTool? If not please do so. For Win 10 or Win 11?

R: I only try Win11 (which is included in the package originally supplied by Medion).

In order to comply with your recommendations (and MS instructions) for preparing the Win11 USB stick,
- at first I inserted into the notebook’s M.2 slot the SATA-SSD ‘S3+ S3SSDA512-ECS-1 512 GB’ , which is included in the package, originally supplied by Medion, then
- completed the installation of Win11 pre-installed on this SATA-SSD, originally supplied (a task which was pending for long time),
- then booted the notebook from the SATA-SSD,
- and carried out the the MediaCreationTool on MS webpage for creating/preparing the Win11 USB stick, as per your advice.
And that worked!
(Previously I had used Linux for downloading and for copying to the USB stick, a direct easy approach, I had thought. Now I am aware, I was completely wrong and acted against all requirements and rules. I have learned my lesson!)

4. You try to install on the now again empty WD Blue SN570 ?
Or is it still partitioned by Linux with Ext4 or other schemes? Just wipe the new SSD completely.

R: Yes, I tried to install on the WD Blue SN570. To ‘wipe’ the NVMe WD Blue SN570, I decided to erase/format the entire NVMe to FAT32. Here a few points on the related quite lengthy experience:

- Erasure/Formatting the NVMe to FAT32 failed, as long as the NVMe was situated in the notebook’s M.2 slot (and linked via the protocol pcieport). Neither the Win11 installation process nor Linux tools (running from debian live system) could complete the erasure/formatting process. Instead either of them after a while aborted the erasure/formatting and showed error messages like ‘storage/disk no longer available/missing ..’, ‘path not found ..’.

- When the abort occurred during formatting with Linux, the Linux diagnose tools showed,
-- that the NVMe was no longer connected to the PCI bus (commands lsblk, fsck, lspci, gparted, ..),
-- and that the RxErr incidences significantly increased (commands dmesg, journalctl),
-- that the NVMe temperature displayed by command smartctl raised from around 30 to around 45°C, shortly before the disconnection occurred. Temperature figures below 50°C should not be an issue.

- However formatting the NVMe to FAT32 succeeded right away, as soon as it was situated in the external NVMe to USB adapter and connected to the notebook via USB C port. This formatting took quite a while. By that, daddle, ‘the SSD was completely wiped’, in line with your advice!

- Now the NVMe was inserted into the notebook’s M.2 slot again and the installation process was started: The Win11 installation process did not ask any more for drivers! Instead it wrote partitions, decompressed packages and wrote files to the NVMe (which I found later-on). However the installation process aborted before the installation could be completed, see further below, section ‘Win11 installation ..’.

5. Put the Intel VDM Drivers on the installation stick as well. They are needed for driving an PCIe M.2 drive.You can load them before installation begins with the F6 tab.. You will be asked for it

R: The Win11 installation process did not ask for any drivers, upon I had followed your hints on creating the Win11 USB stick and ‘completely wiping the SSD’ , as mentioned.
6. Before you begin, take the SATA M.2 SSD out.. If there is a Win Installation on the machine already, the installation might go wrongly

R: Just one single M.2 slot for SSD is available in this notebook. Such conflict is excluded.

Win11 installation began fine but after a while aborted:
(Upon connecting the NVMe via external NVMe to USB adapter, formatting it to FAT32, inserting it back into the notebook’s M.2 slot it was ready for the installation of Win11.)

- The Win11 installation process (‘Win11 installation system’) on USB stick booted fine. Language, locale were same as with the Win11 included in the package originally supplied by Medion.

- Partitioning was confirmed as suggested by the Win11 installation process.

- The installation process successfully completed partitioning, unpacking and copying files, ..), according to the status information .. and the completion status bar steadily grew until ..

- .. until at some point beyond 50% completion status the installation process aborted and an error message like ‘path not found’, ‘disk missing’, ‘access to file failed’, .. occurred, which indicate that the NVMe was no longer connected to the PCI bus. The installation got stuck and reboot was required.

- Booting from NVMe failed, since the Win11 installation obviously had been aborted too early, so before the creation of a bootable system on the NVMe could be completed.

- To continue, the Win11 installation process had to be booted from USB stick again and all the steps were repeated.

- In 3 sessions, each with 4 installation attempts I tried to complete the Win11 installation, but without success. During these attempts I tried the following variations:
-- Create/prepare a Win11 installation USB stick once again, by using a brand new USB stick and of course the MS MediaCreationTool,
-- formatting the NVMe once again to FAT32, upon connecting it to the notebook via external NVME to USB adapter (and then inserting it back into the notebook’s M.2 slot),
-- alternatively reuse of the existing partitions (so no formatting),
-- wait 24 h or more before starting the next installation session.
All the tried out variations did not change a thing. Always the installation process aborted.

- During an installation session, with each further installation attempt the abort occurred earlier, so at lower completion status. After a break a day, the first installation attempt reached again a higher completion status, before it aborted. Then things continued as obeyed before.

- The environmental temperature may have impact. On very warm summer days, the abort occurs earlier, so at lower completion status.

- The Win11 install process does not offer diagnose tools for looking into the system. At least I am not aware of such tools.

Would Linux install on this NVMe, though Win11 obviously doesn’t? Let’s give it a try.

- The NVMe WD Blue SN570 1TB once again was formatted by Linux to FAT32 upon connecting it via the ‘external NVMe to USB adapter’ to the notebook’s USB C port.

- Upon inserting the NVMe again into the notebook’s M.2 slot, a debian live system was booted and the Linux installation was started. Linux allows using diagnose tools for monitoring the temperature, checking the NVMe, NVMe connection status, error messages related to PCI bus, ..

- Upon selecting language, locale, partition parameters (and creation of new GUID) the Linux installation began fine, but after a while it aborted with error messages like ‘can’t read file’, ‘can’t write ..’, ‘disk no longe available..’, ‘access to random file blocked ..’. In that situation the NVMe was no longer connected to the PCI bus (acc. to command lsblk, fsck, lspci, gparted, ..). The incidence of ‘RxErr’, ‘type=physical’ significantly increased when the installation aborted, acc. to the output of commands dmesg, journalctl.

- Upon rebooting the debian live system, I saw Linux partitions and a lot of files on the NVMe, but the Linux system was still incomplete. Accordingly booting from the NVMe failed.

- Repeating the Linux installation failed in the same manner as the Win11 installation had failed before. Attempt by attempt the installation aborted with lesser and lesser completion status. After a break of a day, the first installation attempt reached again a higher completion state, before it aborted. All as obeyed before with the Win11 installation process.

- The NVMe temperature indicated by command smartctl generally was in the range of around 30 to around 45°C. The max. temperature figure of around 45°C was displayed shortly before the NVMe was disconnected. A temperature below 50°C should not be an issue.

- Adding a thermal pad to the NVMe’s surface did not have a significant impact on the abort of the installation and on the temperature displayed by command smartctl. The space available in the notebook does not allow installing a substantial heat sink on the NVMe.

- To confirm the NVMe temperature displayed by command smartctl by a different method,
-- the thermal pad was removed from the NVMe again,
-- a debian live system was booted and the installation of debian was started (while the notebook’s bottom cover remained removed) .
-- While the installation was going on, the temperature of the NVMe’s main chip did not raise a lot,
-- but the temperature of a smaller chip on the NVMe (close to M.2 connector) significantly raised!
-- Yet, in that situation the command smartctl displayed a temperature of around 45°C. Obviously the temperature displayed by smartctl does not consider the smaller chip getting very warm.

Summary: During the debian installation (involving steady write and read on the NVMe)
- the incidence of ‘RxErr’ significantly increases,
- the temperature of a small chip on the WD Blue SN570 1TB significantly increases (without command smartctl does display this),
- the NVMe is disconnected from PCI bus and
- the installation is aborted.
All above issues occur only when the WD Blue SN570 1TB is situated in the notebook’s M.2 slot.

However, when the NVMe is connected via the external NVMe to USB adapter, not any issue like installation abort, errors related to link or significant chip temperature increase occurs. NVMe benchmark test, writing large files on the NVMe, even installing debian on the NVMe is no problem at all. Just I don’t like the system running from an NVMe connected to the notebook’s USB C port via external NVMe to USB adapter.

How to go on from here?

- Do you still recommend installing Win11? What is the plan with running Win11, and what the benefit?
(To get your advice and guidance, I agree to temporarily run Win11 and carry out whatever you recommend to resolve the occurring PCI bus issue, i.e. a firmware upgrade, etc.. As soon as resolution is achieved, I will go back to Linux.)

- Should I try to confirm the present WD Blue SN570 1TB’s proper PCI connectivity capabilities by other means?

- Which NVMe is recommended by the OEM Medion as replacement and/or upgrade? (The Medion webpage is silent on this. Also the related Medion manual is silent.)

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

daddle — Wed, 17 Sep 2025 20:09:04 GMT

@dgtdabbler

I am sorry but I can not support or read your Linux protocols,

And why Windows11 Installation aborted I do not know. Did your PC pass d the Win 11 Test?

For exchanging the M.2 SSD, you can make use of any market producht.

If your chipset only supports 2 lanes, and PCIe V 2 or 3, that what it is. You can not change this..

daddle

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Wed, 17 Sep 2025 21:29:21 GMT

Hi @daddle,

No need to read Linux protocols, I summarized them.

The Win11 installation aborts, because the NVMe is disconnected from PCI bus during installation.

Any M.2 SSD market product shall be compatible to this notebook, that's what you're saying. That is good news! And the WD Blue SN570 1TB can be used.

To exclude the WD Blue SN570 1TB as the error reason of the 'RxErr' and disconnect problem, I installed it in another notebook, in a ‘Lenovo i5, 11th Gen’, PCIe 3.0 with nice result: No 'RxErr' messages, no disconnection during formatting, installing, intensive write/read! All just normal, nothing wrong with the WD Blue SN570 1TB, while running in that Lenovo.

Back to the present E14412: I am fine with 2 lanes. Using just 2 lanes is not the issue here.

For exchanging the M.2 SSD, I will make use of another (any) market product, that is good news.

Thank you

dgt.dabbler

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Fri, 19 Sep 2025 15:56:20 GMT

Hi @daddle,

There are 2 recently mentioned key points on replacing the notebook E14412’s SSD, that I repeat here:
- ‘For exchanging the M.2 SSD, you can make use of any market product.’
- You have to accept the nb E14412 making use of just PCIe 3.0 with 2 lanes, ‘if your chip set supports only 2 lanes.’
That’s fine! I’d be happy using the nb E14412, providing a stable connection to its NVMe via PCIe 3.0 at 2 lanes, like it worked before!

Let’s go on: Could a different NVMe run stably and help to get rid of the disconnection issue, which repeatedly occurred with the earlier WD Blue SN570 1TB during intensive write/read? To figure out, I inserted a brand new Crucial P310 (PCIe Gen4 NVMe 2280 M.2 SSD) into the notebook’s (one and only) M.2 slot, to test it.

I’m afraid to say, with the P310 the nb E14412 behaves just like obeyed earlier with the WD Blue SN570 1TB:

- The P310 is disconnected from PCI bus during OS installation.

- The P310 is disconnected from PCI bus during intensive read/write.

- Messages ‘RxErr’, ‘..physical layer’, ‘severity=corrected’ get more frequent, when the disconnection from PCI bus occurs. The error messages occur more frequently at increased ambient temperature.

- The link established between notebook’s SSD port and P310 uses 2 lanes (of the P310’s 4 lanes).

- The benchmark test shows 1.6 Gb/s (read) and 1.5 Gb/s (write). Fine for PCIe 3.0 at 2 lanes and fine for me!

Differential diagnose: When the P310 is installed in the M.2 slot of the earlier mentioned Lenovo (CPU i5, PCIe 3.0), the P310 runs flawlessly at read/write rates typical for PCI 3.0 and 4 lanes.
Now back to the present E14412: When the P310 is connected via NVMe to USB adapter to the nb E14412, the P310 runs flawlessly at USB 3.2-typical read/write rates. All in analogy to the earlier WD Blue SN570 1TB.

Any info/check unclear/missing? How to go on, please can you advice?

Thanks in advance
dgt.dabbler

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

daddle — Fri, 19 Sep 2025 19:09:08 GMT

@dgtdabbler

During Windows installation you were asked in the beginning, to load if necessary

drivers with the F6 tab.

Get the Intel VDM Drivers, they are sometimes included in the RST drivers, or find them in the Internet; preferably the floppy disk version, and upload them during installation. Here :

--> https://drive.google.com/file/d/10D3O6XIW9T-vZr_ZNz4gS684eFT8BHhi/view?usp=sharing

good luck, daddle

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

dgtdabbler — Thu, 16 Oct 2025 23:44:02 GMT

Hi @daddle,

Modifying two PCIe bus-settings improves PCIe bus stability and prevents disconnection of the NVMe from the notebook’s NVMe port during intensive read/write!

By setting the ..

- the PCIe parameter ASPM to L1 (ASPM - Active-state power management) and

- the PCIe speed to Gen2 (5 GT/s), so by downgrading from the nb’s regular speed Gen3 (8 GT/s), ..

the notebook E14412 runs stably for days and the earlier obeyed issues do no longer occur:

- The NVMe no longer is disconnected during intensive read/write,

- the ‘RxErr’-messages no longer occur in the output of dmesg and

- the controller chip on the NVMe no longer warms up!

However the reduced speed ‘PCIe Gen2’ limits the notebook’s NVMe port data transfer rate to 0,87/0,85 GB/s (read/write). Previously, with ‘PCIe Gen3’, the transfer rate had been 1,7/1,6 GB/s (read/write). (Just to remind: Two lanes to m.2 slot for NVMe SSD (so width x2s) are implemented/available in this notebook, @daddle, acc. your earlier reply above.)

How were this changes implemented?

By adding the PCIe setting ‘pcie_aspm=off’ in the Linux configuration file ‘grub’ to the line

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off"

the PCIe ASPM setting ends up with ‘ASPM L1’ for ..

- for the NVMe and its related notebook port, as well as

- for the Ethernet port and its related notebook port.

(Setting the notebook’s NVMe port to ‘ASPM Disabled’ did not succeed, no matter which other ASPM parameter I tried out in the configuration file grub. The notebook’s NVMe port always remained ‘ASPM L1’.)

To change PCIe speed to Gen2, I used the script of Alex Forencich ‘pcie_set_speed.sh’, which is easy to find on his webpage and in Linux forums. Here a quick example of changing the PCIe speed in 3 steps (the present notebook’s NVMe port is 0000:00:1d.0):

1) Confirmation of current speed (the nb’s regular speed) PCIe Gen3 (8 GT/s), upon booting, before changing:

fan_of@e14412:~$ sudo lspci -PPvv |grep --color -iE 'LnkSta: Speed [0-z]GT/s|00:1d.0|01:00.0'

00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) (prog-if 00 [Normal decode])

LnkSta: Speed 8GT/s, Width x2

00:1d.0/01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN570 NVMe SSD 1TB (prog-if 02 [NVM Express])

LnkSta: Speed 8GT/s, Width x2 (downgraded)

2) Setting PCIe speed to Gen2 by executing Alex’ script ‘pcie_set_speed.sh’:

fan_of@e14412:~$ sudo ./pcie_set_speed.sh 0000:00:1d.0 2

Link capabilities: 09724823

Max link speed: 3

Link status: 7023

Current link speed: 3

Configuring 0000:00:1d.0...

Original link control 2: 001e0003

Original link target speed: 3

New target link speed: 2

New link control 2: 001e0002

Triggering link retraining...

Original link control: 70230042

New link control: 70230062

Link status: 7022

Current link speed: 2

fan_of@e14412:~$

3) Confirmation of speed PCIe Gen2 (5GT/s) upon executing ‘pcie_set_speed.sh’:

fan_of@e14412:~$ sudo lspci -PPvv |grep --color -iE 'LnkSta: Speed [0-z]GT/s|00:1d.0|01:00.0'

00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0) (prog-if 00 [Normal decode])

LnkSta: Speed 5GT/s, Width x2

00:1d.0/01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN570 NVMe SSD 1TB (prog-if 02 [NVM Express])

LnkSta: Speed 5GT/s (downgraded), Width x2 (downgraded)

Now, with PCIe Gen2 (5 GT/s), the notebook runs stably without the NVMe is disconnected during intensive read/write!

Yet, upon every start-up the notebook regularly runs at PCIe Gen3. Hence, every time the script needs to be applied again, in order to switch it to Gen2.

Open issue: Booting succeeds only if notebook starts in cool (pre-cooled) condition

Starting right away, the boot process regularly fails, indicating the NVMe is no longer connected to the PCIe bus. To successfully boot the notebook E14412, a prior cooling to 20 °C or less is required (i.e. by storing it in cool basement for 20 to 40 minutes). As soon as booting is completed, switching to PCIe Gen2 stabilises the notebook port’s connection to the NVMe, as mentioned above.

The notebook’s BIOS as originally implemented by the OEM does not offer any option for modifying the PCIe settings (i.e. starting up with PCIe Gen2), as far as I can see. So, I have no idea how to resolve this problem.

How to go forward?

- Any known typical issues, typical checks, typical modifications of the present notebook E14412’s hardware or BIOS, I could implement to get rid of the notebook’s NVMe port issues and the NVMe disconnection occurring when running at PCIe Gen3?

- Any hidden BIOS-options for modifying PCIe settings (i.e. boot at PCI Gen2) available?

Kindly I ask for your guidance and hints. How could I get a quick help for resolving?

Many thanks in advance!

Kind regards,

dgt.dabbler

Re: E14412 PCIe Mismatch: PCIe Error 'RxErr', NVMe Link to PCIe Bridge Downgraded (LinkStatus Width

daddle — Fri, 17 Oct 2025 17:26:02 GMT

@dgtdabbler

I am sorry, but I (and Medion) can not help you any further. As I told you before already.

Medion only supports Windows issues, not Linux..

Second your Notebook came equipped with a SATA M.2 SSD. Nowhere it is said it runs a PCIe M.2 SSD.

I doubt a PCIe/NVME protocol is applied to the one and only M.2 port in your NB.

If you make use of an external USB PCIe to USB Adapter, of course a PCIe M..2 will work externally..

Third the OEM Notebook and it's Bios is produced in China or Taiwan. No one here at Medion or in the Forum will be able to get a or modify an OEM Bios. And the manufacturer in China himself will definitely not do this for a OEM product.

Except from that, Medion only supports Windows, and not Linux.

I assume, the M.2 Port in the notebook only supports SATA.

We can ask a moderator ( eg @Andi ) to check in Medions database if the PCIe protocol is linked to the only M.2 port also; or if there exists a newer Bios. But sold they all were equipped with a SATA M.2 only. This might have a reason!

But for this you have to state the MSN number of your notebook first. It's a 8 digit number, beginning with 300...... ; and printed on a sticker underneath the bottom case.

Or check in Windows with msinfo32.exe. The line System-SKU shows he MSN within it's last eight digits.

And tell us the Bios version.

Bye, daddle