IO errors after recent update

theramatrix · 2025-11-17 01:35:59

I've got an ASUS laptop (S13 OLED, UM5302) that I've been using for ~2 years, after a recent software update I've been getting a bunch of crashes. Trying to run terminal commands result in 'input output error'.

What I've tried:
- Running fsck
- Running smartctl
- Switching to LTS kernel
- Reinstalling
- Swapping out the hard drive
- Trying a different distro
- Trying Windows (Alas didn't crash, annoyingly, ruling out simple hardware failure)

journalctl -b log: https://pastebin.com/Nxr8j0JS
dmesg log: https://pastebin.com/c3fGsxj8

Help appreciated.

Last edited by theramatrix (2025-11-17 05:58:40)

seth · 2025-11-17 15:58:30

The journal doesn't seem to include any IO errors nor other "crashes"
Generically see https://wiki.archlinux.org/title/Solid_ … leshooting

pcie_aspm=off pcie_port_pm=off nvme_core.default_ps_max_latency_us=0 iommu=soft

Trying Windows

In case you're dual booting, see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

theramatrix · Yesterday 04:16:11

So I got the feeling the IO errors meant the logs became unwritable once they started happening, but it occured to me I could try booting off the Arch install ISO with the drive mounted. Here's what I got:

dmesg:

[ 2834.887074] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
[ 2834.887089] nvme nvme0: Does your device have a faulty power saving mode enabled?
[ 2834.887094] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
[ 2834.920687] nvme 0000:02:00.0: enabling device (0000 -> 0002)
[ 2834.920883] nvme nvme0: Disabling device after reset failure: -19
[ 2834.933270] Buffer I/O error on dev nvme0n1p2, logical block 29, lost async page write
[ 2834.933342] EXT4-fs (nvme0n1p2): shut down requested (2)
[ 2834.933392] Buffer I/O error on dev nvme0n1p2, logical block 66, lost async page write
[ 2834.933479] Aborting journal on device nvme0n1p2-8.
[ 2834.933513] Buffer I/O error on dev nvme0n1p2, logical block 9567, lost async page write
[ 2834.933611] Buffer I/O error on dev nvme0n1p2, logical block 59768848, lost async page write
[ 2834.933612] Buffer I/O error on dev nvme0n1p2, logical block 121667584, lost sync page write
[ 2834.933692] Buffer I/O error on dev nvme0n1p2, logical block 59768864, lost async page write
[ 2834.933758] JBD2: I/O error when updating journal superblock for nvme0n1p2-8.
[ 2834.933848] Buffer I/O error on dev nvme0n1p2, logical block 136314883, lost async page write
[ 2834.933996] Buffer I/O error on dev nvme0n1p2, logical block 136314885, lost async page write
[ 2834.934077] Buffer I/O error on dev nvme0n1p2, logical block 243927573, lost async page write

journalctl:

Nov 18 04:09:55 archiso kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Nov 18 04:09:55 archiso kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Nov 18 04:09:55 archiso kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Nov 18 04:09:55 archiso kernel: nvme 0000:02:00.0: enabling device (0000 -> 0002)
Nov 18 04:09:55 archiso kernel: nvme nvme0: Disabling device after reset failure: -19
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 29, lost async page write
Nov 18 04:09:55 archiso kernel: EXT4-fs (nvme0n1p2): shut down requested (2)
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 66, lost async page write
Nov 18 04:09:55 archiso kernel: Aborting journal on device nvme0n1p2-8.
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 9567, lost async page write
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 59768848, lost async page write
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 121667584, lost sync page write
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 59768864, lost async page write
Nov 18 04:09:55 archiso kernel: JBD2: I/O error when updating journal superblock for nvme0n1p2-8.
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 136314883, lost async page write
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 136314885, lost async page write
Nov 18 04:09:55 archiso kernel: Buffer I/O error on dev nvme0n1p2, logical block 243927573, lost async page write

pcie_aspm=off pcie_port_pm=off nvme_core.default_ps_max_latency_us=0 iommu=soft

Thanks for the suggestion, but no dice.

In case you're dual booting

I'm not, I just figured since I was reinstalling I might as well see if Windows had the bug.

Last edited by theramatrix (Today 01:39:56)

seth · Yesterday 09:05:17

Please use [code][/code] tags. Edit your post in this regard.

Thanks for the suggestion, but no dice.

Nov 18 04:09:55 archiso kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Nov 18 04:09:55 archiso kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Nov 18 04:09:55 archiso kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug

Does

cat /proc/cmdline

show that you're indeed booting w/ those parameters?
Please post the entire system journal covering such failure:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

will upload it to 0x0.st and hand you a link to share.

theramatrix · Today 01:44:13

Does
cat /proc/cmdline
show that you're indeed booting w/ those parameters?

Yes, I can confirm that command returns the kernel parameters as expected.

Please post the entire system journal covering such failure:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
will upload it to 0x0.st and hand you a link to share.

https://0x0.st/Kf6J.txt

seth · Today 08:35:30

Nov 19 01:34:59 archiso kernel: DMI: ASUSTeK COMPUTER INC. Zenbook UM5302LA_UM5302LA/UM5302LA, BIOS UM5302LA.302 07/27/2023
Nov 19 01:34:59 archiso kernel: ACPI: AC: AC Adapter [ACAD] (on-line)

The nvme is stock? You didn't add that after market?
Do you get the same errors w/ https://grml.org/ (for a different kernel, config, userspace)?

Arch Linux

#1 2025-11-17 01:35:59

IO errors after recent update

#2 2025-11-17 15:58:30

Re: IO errors after recent update

#3 Yesterday 04:16:11

Re: IO errors after recent update

#4 Yesterday 09:05:17

Re: IO errors after recent update

#5 Today 01:44:13

Re: IO errors after recent update

#6 Today 08:35:30

Re: IO errors after recent update

Board footer