Arch Linux

arcady

Member

Registered: 2025-07-08

Posts: 1

Secondary SSD randomly goes into read-only mode

Hi folks, I'm running into an issue where my secondary SSD randomly goes into read only mode, trying to delete or do anything there gives me a "Read-only file system" error.
I am running a dual boot installation with Windows on the side, on my primary NVME drive.

`lsblk -f` for reference, sdb3 is the partition that goes read only randomly.

NAME        FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                      
└─sda1      ntfs         HDD         167E4F197E4EF0D3                      126.4G    73% /mnt/HDD
sdb                                                                                      
├─sdb1      ntfs         SSD-Win     56657E6C7ABB576C                                    
└─sdb3      ext4   1.0   SSD-Arch    7050a79c-6304-4f78-a88b-8fb22560d652  311.7G    55% /mnt/SSD
nvme0n1                                                                                  
├─nvme0n1p1 vfat   FAT32 SYSTEM      3AD6-3E32                               1.8G     2% /boot/efi
├─nvme0n1p2                                                                              
├─nvme0n1p3 ntfs                     929A1BD09A1BB029                                    
├─nvme0n1p4 ntfs                     AC66699366695ED8                                    
└─nvme0n1p5 ext4   1.0   endeavouros 8ce3012b-d128-48b0-b148-c331fa3597fb  112.5G    56% /

running `sudo dmesg | grep -Ei 'ext4|io error|error'` gives me this output

[    2.970426] RAS: Correctable Errors collector initialized.
[    8.807971] EXT4-fs (nvme0n1p5): mounted filesystem 8ce3012b-d128-48b0-b148-c331fa3597fb r/w with ordered data mode. Quota mode: none.
[    9.306494] EXT4-fs (nvme0n1p5): re-mounted 8ce3012b-d128-48b0-b148-c331fa3597fb.
[   27.915092] EXT4-fs (sdb3): mounted filesystem 7050a79c-6304-4f78-a88b-8fb22560d652 r/w with ordered data mode. Quota mode: none.
[  287.952730] I/O error, dev sdb, sector 602192384 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0
[  287.952748] I/O error, dev sdb, sector 602193752 op 0x1:(WRITE) flags 0x0 phys_seg 3 prio class 0
[  287.952765] I/O error, dev sdb, sector 602193776 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0
[  287.952781] I/O error, dev sdb, sector 602195120 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 0
[  287.952796] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161276 starting block 75274390)
[  287.952832] I/O error, dev sdb, sector 602195824 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0
[  287.952847] I/O error, dev sdb, sector 602197728 op 0x1:(WRITE) flags 0x0 phys_seg 36 prio class 0
[  287.952849] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161276 starting block 75274716)
[  287.952864] I/O error, dev sdb, sector 602198016 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0
[  287.952867] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161276 starting block 75274920)
[  287.952884] I/O error, dev sdb, sector 602189824 op 0x1:(WRITE) flags 0x4000 phys_seg 96 prio class 0
[  287.952886] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161276 starting block 75274219)
[  287.952899] I/O error, dev sdb, sector 602106368 op 0x1:(WRITE) flags 0x0 phys_seg 135 prio class 0
[  287.952902] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33162261 starting block 75263296)
[  287.952914] I/O error, dev sdb, sector 602120192 op 0x1:(WRITE) flags 0x0 phys_seg 78 prio class 0
[  287.952916] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33162261 starting block 75265024)
[  287.952931] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161273 starting block 75275944)
[  287.952936] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161273 starting block 75276456)
[  287.952947] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161273 starting block 75276712)
[  287.952953] EXT4-fs warning (device sdb3): ext4_end_bio:368: I/O error 10 writing to inode 33161273 starting block 75276800)
[  287.953204] EXT4-fs error (device sdb3) in ext4_reserve_inode_write:5911: Journal has aborted
[  287.953224] EXT4-fs error (device sdb3): mpage_map_and_submit_extent:2342: inode #23205509: comm kworker/u49:6: mark_inode_dirty error
[  287.953233] EXT4-fs error (device sdb3): mpage_map_and_submit_extent:2344: comm kworker/u49:6: Failed to mark inode 23205509 dirty
[  287.953237] EXT4-fs error (device sdb3) in ext4_do_writepages:2757: Journal has aborted
[  287.953577] EXT4-fs error (device sdb3): ext4_journal_check_start:86: comm kworker/u50:2: Detected aborted journal
[  287.954061] EXT4-fs error (device sdb3): ext4_journal_check_start:86: comm kworker/u49:6: Detected aborted journal
[  287.963927] EXT4-fs (sdb3): Remounting filesystem read-only
[  287.964263] EXT4-fs (sdb3): ext4_do_writepages: jbd2_start: 1024 pages, ino 23205793; err -30
[  287.964857] Buffer I/O error on device sdb3, logical block 34582528
[  287.964862] Buffer I/O error on device sdb3, logical block 34582529
[  287.964865] Buffer I/O error on device sdb3, logical block 34582530
[  287.964867] Buffer I/O error on device sdb3, logical block 34582531
[  287.964870] Buffer I/O error on device sdb3, logical block 34582532
[  287.964872] Buffer I/O error on device sdb3, logical block 34582533
[  287.964875] Buffer I/O error on device sdb3, logical block 34582534
[  287.964877] Buffer I/O error on device sdb3, logical block 34582535
[  287.964879] Buffer I/O error on device sdb3, logical block 34582536
[  287.964882] Buffer I/O error on device sdb3, logical block 34582537

any ideas on how i could fix this? or what the issue is?

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,325

Re: Secondary SSD randomly goes into read-only mode

Don't grep.
There're certainly IO errors, which could be
- the disk, https://wiki.archlinux.org/title/SMART (the overall health status line is borderline meaningless, in doubt post the "smartctl -a /dev/sdb" output)
- the bus (cable…, power connector)
- some power saving going wild

Also

└─nvme0n1p5 ext4   1.0   endeavouros 8ce3012b-d128-48b0-b148-c331fa3597fb  112.5G    56% /

https://bbs.archlinux.org/misc.php?action=rules

Ie. "too late, you can post your journal since we know anyway"

Edit: also 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Last edited by seth (2025-07-12 08:25:00)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc