cancel
Showing results for 
Search instead for 
Did you mean: 

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

7 REPLIES 7
dgtdabbler
Trainee
Message 1 of 8
362 Views
Message 1 of 8
362 Views

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

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!

7 REPLIES 7
dgtdabbler
Trainee
Message 2 of 8
313 Views
Message 2 of 8
313 Views

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

dgtdabbler
Trainee
Message 3 of 8
224 Views
Message 3 of 8
224 Views

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)

 

QDiskInfo#2.png

 
 

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.

 

WD_Dashboard-2#4Lanes_Trim#1.3.jpg

 

 

 

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!

dgtdabbler
Trainee
Message 4 of 8
214 Views
Message 4 of 8
214 Views

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?

dgtdabbler
Trainee
Message 5 of 8
163 Views
Message 5 of 8
163 Views

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?

 

D_Capabl_#01a.pngD_Capabl_#01b.png

 

 

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?

 

D_Capabl_#02a.pngD_Capabl_#02b.png

 

 

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?

D_Capabl_#03.png

 

 

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

 

D_Capabl_#04a.pngD_Capabl_#04b.pngD_Capabl_#04c.png

 

 

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.

 

D_Capabl_#05.png

 

 

 

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-..

 

D_Capabl_#06a.png

 

 

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.)

 

D_Capabl_#06b.pngD_Capabl_#06c.png

 

 

 

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.

 

D_Capabl_#08.png

 

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.

 

daddle
Superuser
Message 6 of 8
155 Views
Message 6 of 8
155 Views

@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

Fishtown
Superuser
Message 7 of 8
146 Views
Message 7 of 8
146 Views

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

--------------------------------------------------------------------------------------------------------------------------------------------------------
Alles was man lange genug, konsequent mit System durchführt, führt zwangsläufig zum Erfolg.
dgtdabbler
Trainee
Message 8 of 8
111 Views
Message 8 of 8
111 Views

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

 

 

 

7 REPLIES 7