Arch Linux

shaurz

Member

Registered: 2004-02-02

Posts: 360

I/O error on eMMC drive causing root fs to remount as readonly

I have installed Arch on my Lenovo e300 laptop (Windows version, not the Chromebook) which has a 128GB SanDisk iNAND eMMC SSD.

It was originally running Windows 10 and I didn't notice any problems with it.

Unfortunately I am getting I/O errors which is causing the kernel to remount the root filesystem as read only, and also causing the filesystem to need fsck'ing to get the system to boot again.

[  765.653474] print_req_error: I/O error, dev mmcblk0, sector 118812848 flags 801
[  765.653548] Aborting journal on device mmcblk0p2-8.
[  765.653555] EXT4-fs error (device mmcblk0p2) in ext4_do_update_inode:5362: Journal has aborted
[  765.656869] EXT4-fs error (device mmcblk0p2) in ext4_orphan_del:2901: Journal has aborted
[  765.657448] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:61: Detected aborted journal
[  765.657460] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[  765.659145] EXT4-fs error (device mmcblk0p2) in ext4_do_update_inode:5362: Journal has aborted

I think the device is probably struggling to keep up with the rate of writes. The problem seems to occur with heavy I/O such as checking out a large git repo or compiling, but I've also had the problem occur while casually web browsing.

Are there any kernel options I can set so that the kernel will try a bit harder if there are any I/O errors (back off an retry)?

shaurz

Member

Registered: 2004-02-02

Posts: 360

Re: I/O error on eMMC drive causing root fs to remount as readonly

I've added errors=continue to the mount options, I'll see how that goes.

shaurz

Member

Registered: 2004-02-02

Posts: 360

Re: I/O error on eMMC drive causing root fs to remount as readonly

This sometimes works, but eventually it is failing...

[  778.062853] print_req_error: I/O error, dev mmcblk0, sector 123025640 flags 80700
[  778.065523] print_req_error: I/O error, dev mmcblk0, sector 123025641 flags 80700
[  873.063939] print_req_error: I/O error, dev mmcblk0, sector 228200728 flags 801
[  873.063961] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 3801321 (offset 0 size 65536 starting block 28525107)
[  873.063967] Buffer I/O error on device mmcblk0p2, logical block 28393763
[  873.063995] Buffer I/O error on device mmcblk0p2, logical block 28393764
[  873.064000] Buffer I/O error on device mmcblk0p2, logical block 28393765
[  873.064004] Buffer I/O error on device mmcblk0p2, logical block 28393766
[  873.064007] Buffer I/O error on device mmcblk0p2, logical block 28393767
[  873.064011] Buffer I/O error on device mmcblk0p2, logical block 28393768
[  873.064015] Buffer I/O error on device mmcblk0p2, logical block 28393769
[  873.064018] Buffer I/O error on device mmcblk0p2, logical block 28393770
[  873.064022] Buffer I/O error on device mmcblk0p2, logical block 28393771
[  873.064026] Buffer I/O error on device mmcblk0p2, logical block 28393772
[  930.174712] print_req_error: I/O error, dev mmcblk0, sector 36107960 flags 801
[  930.174732] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 3819515 (offset 0 size 16384 starting block 4513499)
[  930.174739] buffer_io_error: 6 callbacks suppressed
[  930.174742] Buffer I/O error on device mmcblk0p2, logical block 4382167
[  930.174766] Buffer I/O error on device mmcblk0p2, logical block 4382168
[  930.174770] Buffer I/O error on device mmcblk0p2, logical block 4382169
[  930.174774] Buffer I/O error on device mmcblk0p2, logical block 4382170
[  973.043618] print_req_error: I/O error, dev mmcblk0, sector 118857584 flags 801
[  973.043763] Aborting journal on device mmcblk0p2-8.
[  973.043820] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:5903: Journal has aborted
[  973.059185] EXT4-fs error (device mmcblk0p2) in ext4_dirty_inode:6087: Journal has aborted
[  973.060371] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:61: Detected aborted journal
[  973.060375] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[  973.061285] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:61: Detected aborted journal

r0b0t

Member

From: /tmp

Registered: 2009-05-24

Posts: 510

Re: I/O error on eMMC drive causing root fs to remount as readonly

I don't know if this is really happening only on Arch, but it pretty much seems the disk is done.
You could try some SMART checks on the drive , but I'd advice to back up your stuff and think about a replacement.