nvme nvme0: controller is down; will reset -> read-only filesystem

Tr1ceracop · 2023-08-06 13:54:23

Hello together,

I have been using arch now for a while on my Dell XPS Laptop and it ran fine. But about three weeks ago I had a problem with my root-filesystem the first time:
The filesystem seems to be remounted as a read-only-filesystem at some point while working.
When opening a new shell, it shows the following error:

mkdir: cannot create directory 'home/***/.cache/oh-my-zsh': Read-only file system
rm: cannot remove '/home/***/.zcompdump-dellarch-5.9':Read-only file system
locking failed for /home/***/.zsh_history: read-only file system: reading anyway

Since then, of course, the most commands and tools stop functioning normally and result in io-errors.
After a reboot (or hardreset because sudo systemctl reboot does not working either) the system continues to work normally.

The result of journalctl -k shows the following:

Aug 06 15:19:14 dellarch kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Aug 06 15:19:14 dellarch kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Aug 06 15:19:14 dellarch kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
Aug 06 15:19:14 dellarch kernel: nvme 10000:e1:00.0: enabling device (0000 -> 0002)
Aug 06 15:19:14 dellarch kernel: pcieport 10000:e0:01.2: can't derive routing for PCI INT A
Aug 06 15:19:14 dellarch kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
Aug 06 15:19:14 dellarch kernel: nvme nvme0: Disabling device after reset failure: -19
Aug 06 15:19:14 dellarch kernel: nvme0n1: detected capacity change from 2000409264 to 0
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-1, logical block 22080131, lost async page write
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-1, logical block 22053874, lost async page write
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-1, logical block 22020109, lost async page write
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-1, logical block 17826534, lost async page write
Aug 06 15:19:14 dellarch kernel: Aborting journal on device dm-2-8.
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-1, logical block 11, lost async page write
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2): ext4_journal_check_start:83: comm chrome: Detected aborted journal
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2): ext4_journal_check_start:83: comm AioMgr0-N: Detected aborted journal
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5505565 starting block 4000135)
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 4000135
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7349806)
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7349806
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350132)
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350132
Aug 06 15:19:14 dellarch kernel: Aborting journal on device dm-1-8.
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350184)
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350184
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350344)
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350344
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350345
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350346
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350348)
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350348
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350349
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on device dm-1, logical block 7350350
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-1): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journal
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350437)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350485)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350493)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-1): ext4_end_bio:343: I/O error 10 writing to inode 5507422 starting block 7350499)
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-2, logical block 0, lost async page write
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-2, logical block 4, lost async page write
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-2, logical block 6, lost async page write
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-2, logical block 6815751, lost async page write
Aug 06 15:19:14 dellarch kernel: Buffer I/O error on dev dm-2, logical block 11534342, lost async page write
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2) in ext4_reserve_inode_write:5734: Journal has aborted
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2) in ext4_do_writepages:2706: Journal has aborted
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460484)
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2) in ext4_reserve_inode_write:5734: Journal has aborted
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460505)
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2): ext4_dirty_inode:5938: inode #13560912: comm ThreadPoolForeg: mark_inode_dirty error
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): previous I/O error to superblock detected
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2) in ext4_reserve_inode_write:5734: Journal has aborted
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2) in ext4_dirty_inode:5939: Journal has aborted
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460516)
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2): ext4_dirty_inode:5938: inode #13511248: comm ThreadPoolForeg: mark_inode_dirty error
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460582)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460618)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460629)
Aug 06 15:19:14 dellarch kernel: EXT4-fs error (device dm-2): ext4_dirty_inode:5938: inode #12846406: comm Timer-0: mark_inode_dirty error
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460634)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460639)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460672)
Aug 06 15:19:14 dellarch kernel: EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 12889720 starting block 61460694)
Aug 06 15:19:14 dellarch kernel: JBD2: I/O error when updating journal superblock for dm-1-8.
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): I/O error while writing superblock
Aug 06 15:19:14 dellarch kernel: JBD2: I/O error when updating journal superblock for dm-2-8.
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): I/O error while writing superblock
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-1): I/O error while writing superblock
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-1): Remounting filesystem read-only
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): previous I/O error to superblock detected
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): I/O error while writing superblock
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): Remounting filesystem read-only
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): Remounting filesystem read-only
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): failed to convert unwritten extents to written extents -- potential data loss!  (inode 13511229, error -30)
Aug 06 15:19:14 dellarch kernel: EXT4-fs (dm-2): I/O error while wriSIGBUS handling failed: Value too large for defined data type

I would be glad for every assistance
Thank you!

Last edited by Tr1ceracop (2023-08-06 13:55:04)

seth · 2023-08-06 14:08:03

https://wiki.archlinux.org/title/Solid_ … nd_support

Arch Linux

#1 2023-08-06 13:54:23

nvme nvme0: controller is down; will reset -> read-only filesystem

#2 2023-08-06 14:08:03

Re: nvme nvme0: controller is down; will reset -> read-only filesystem

Board footer