Hi Team,
I’m using a ROCK 5T running Debian 12 , with a 36W DC adapter for power supply.
My NVMe drive is detected normally after a reboot, but after some time it automatically disconnects and the filesystem remounts read-only .
If I reboot, the NVMe is detected again and works for a while before failing.
Observed behavior:
- After some time, the NVMe controller goes down.
- Kernel logs show PCIe/NVMe reset messages followed by EXT4 I/O errors.
- Finally, the filesystem is remounted read-only.
Relevant log snippet:
Initializing XFRM netlink socket
Aug 12 08:23:48 rock-5t kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Aug 12 08:23:49 rock-5t kernel: br-39bf06d84ced: port 1(veth8c5ed68) entered blocking state
Aug 12 08:23:49 rock-5t kernel: br-39bf06d84ced: port 1(veth8c5ed68) entered disabled state
Aug 12 08:23:49 rock-5t kernel: device veth8c5ed68 entered promiscuous mode
Aug 12 08:23:49 rock-5t kernel: br-39bf06d84ced: port 1(veth8c5ed68) entered blocking state
Aug 12 08:23:49 rock-5t kernel: br-39bf06d84ced: port 1(veth8c5ed68) entered forwarding state
Aug 12 08:23:49 rock-5t kernel: br-39bf06d84ced: port 1(veth8c5ed68) entered disabled state
Aug 12 08:23:49 rock-5t kernel: eth0: renamed from veth8e5986f
Aug 12 08:23:49 rock-5t kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8c5ed68: link becomes ready
Aug 12 08:23:49 rock-5t kernel: br-39bf06d84ced: port 1(veth8c5ed68) entered blocking state
Aug 12 08:23:49 rock-5t kernel: br-39bf06d84ced: port 1(veth8c5ed68) entered forwarding state
Aug 12 08:23:49 rock-5t kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-39bf06d84ced: link becomes ready
Aug 12 08:23:51 rock-5t kernel: platform mtd_vendor_storage: deferred probe pending
Aug 12 08:24:10 rock-5t systemd-journald[401]: Time jumped backwards, rotating.
Aug 12 13:22:02 rock-5t kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Aug 12 13:22:02 rock-5t kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Aug 12 13:22:02 rock-5t kernel: nvme nvme0: Try “nvme_core.default_ps_max_latency_us=0 pcie_aspm=off” and report a bug
Aug 12 13:22:02 rock-5t kernel: nvme 0001:11:00.0: enabling device (0000 -> 0002)
Aug 12 13:22:02 rock-5t kernel: nvme nvme0: Removing after probe failure status: -19
Aug 12 13:22:02 rock-5t kernel: nvme0n1: detected capacity change from 500118192 to 0
Aug 12 13:22:02 rock-5t kernel: EXT4-fs warning (device nvme0n1p1): ext4_end_bio:343: I/O error 10 writing to inode 15204365 starting block 60859656)
Aug 12 13:22:02 rock-5t kernel: Aborting journal on device nvme0n1p1-8.
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1) in ext4_reserve_inode_write:5868: Journal has aborted
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1) in add_dirent_to_buf:2192: Journal has aborted
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on dev nvme0n1p1, logical block 30965760, lost sync page write
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1): ext4_convert_unwritten_extents:4849: inode #15204365: comm kworker/u16:1: mark_inode_dirty error
Aug 12 13:22:02 rock-5t kernel: JBD2: I/O error when updating journal superblock for nvme0n1p1-8.
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1) in ext4_convert_unwritten_io_end_vec:4888: Journal has aborted
Aug 12 13:22:02 rock-5t kernel: EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents – potential data loss! (inode 15204365, error -30)
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Aug 12 13:22:02 rock-5t kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859400
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Aug 12 13:22:02 rock-5t kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1): ext4_check_bdev_write_error:217: comm ftdc: Error while async write back metadata
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1) in ext4_reserve_inode_write:5868: Journal has aborted
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859401
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1): ext4_add_nondir:2806: inode #15204367: comm ftdc: mark_inode_dirty error
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859402
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859403
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859404
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859405
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859406
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on device nvme0n1p1, logical block 60859407
Aug 12 13:22:02 rock-5t kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1): ext4_check_bdev_write_error:217: comm ftdc: Error while async write back metadata
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1) in ext4_orphan_add:188: Journal has aborted
Aug 12 13:22:02 rock-5t kernel: EXT4-fs error (device nvme0n1p1) in ext4_create:2847: Journal has aborted
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Aug 12 13:22:02 rock-5t kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
Aug 12 13:22:02 rock-5t kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Aug 12 13:22:02 rock-5t kernel: EXT4-fs (nvme0n1p1): I/O error while writing superblock
Aug 12 13:22:02 rock-5t kernel: EXT4-fs (nvme0n1p1): Remounting filesystem read-only
Aug 12 13:22:03 rock-5t kernel: EXT4-fs (nvme0n1p1): unmounting filesystem.
At 8:24 I have rebooted the device, and then suddenly 13:22 it started failing.
Please help me with this.