My new-this-year MS-02 crashed tonight, so I’m going through journalctl -b -1 -p warning -r and I see a bunch of this repeated over and over going back for days:
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00200000/00000000 Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: AER: TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000 Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: [21] ACSViol (First) Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: [20] UnsupReq Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00300000/00000000 Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID) Oct 12 23:59:49 proxmox-06 kernel: aer_ratelimit: 119 callbacks suppressed Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: [15] HeaderOF Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: device [8086:7f44] error status/mask=00008000/00002000 Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Correctable, type=Transaction Layer, (Receiver ID) Oct 12 23:59:49 proxmox-06 kernel: aer_ratelimit: 119 callbacks suppressed
Does this mean one of the SSDs is failing already? I have 1 Crucial P310 4TB SSD for the main drive and another for backups.
=== START OF INFORMATION SECTION === Model Number: CT4000P310SSD8 Serial Number: 2545543AD7B7 Firmware Version: V8CR010 PCI Vendor/Subsystem ID: 0xc0a9 IEEE OUI Identifier: 0x00a075 Controller ID: 0 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 4,000,787,030,016 [4.00 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 00a075 01543ad7b7 Local Time is: Tue Oct 13 00:28:48 2026 EDT Firmware Updates (0x14): 2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x00d7): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Verify Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 64 Pages Warning Comp. Temp. Threshold: 86 Celsius Critical Comp. Temp. Threshold: 88 Celsius Namespace 1 Features (0x18): No_ID_Reuse NP_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 6.30W - - 0 0 0 0 0 0 1 + 2.40W - - 1 1 1 1 0 0 2 + 1.50W - - 2 2 2 2 0 0 3 - 0.0300W - - 3 3 3 3 1500 5000 4 - 0.0025W - - 4 4 4 4 5000 30000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff) Critical Warning: 0x00 Temperature: 38 Celsius Available Spare: 100% Available Spare Threshold: 5% Percentage Used: 6% Data Units Read: 2,161,355 [1.10 TB] Data Units Written: 154,163,444 [78.9 TB] Host Read Commands: 8,882,927 Host Write Commands: 610,221,348 Controller Busy Time: 2,682 Power Cycles: 24 Power On Hours: 3,278 Unsafe Shutdowns: 18 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 38 Celsius Error Information (NVMe Log 0x01, 16 of 255 entries) No Errors Logged Self-test Log (NVMe Log 0x06, NSID 0xffffffff) Self-test status: No self-test in progress No Self-tests Logged
mlfh@lm.mlfh.org 20 hours ago
Not a disk issue, but looks instead like an issue with power management on that thunderbolt root port at 0000:80:1b.4. See this thread for proxmox-specific writeup: …proxmox.com/…/kernel-7-0-x-regression-acs-violat…
And here for more: github.com/minisforum-docs/MS-02-Ultra/issues/10
Looks like you can resolve it for now by either reverting to 6.17.x kernel or creating a udev rule for the device.
TheButtonJustSpins@infosec.pub 12 hours ago
Thank you!!! I blacklisted the thunderbolt kernel module per [the linked github issue](github.com/minisforum-docs/MS-02-Ultra/issues/10#…] and I don’t see the same spam in the journal! (I should probably look into making sure there are no errors/warnings, but this is definitely a huge step forward.)
Dalraz@lemmy.ca 15 hours ago
Thanks for taking the time to answer their question. That is all